Link a bank line to the transfer journal entry that already booked it

Required API key scope: accounting:write

Links an unreconciled bank feed line to an EXISTING bank-transfer journal entry and posts nothing.

The problem it solves. Banks post the two legs of one internal transfer on different days. When the first leg is recorded as a transfer and the second arrives afterwards, the second leg has no twin to be matched against (the first is already matched), so the only other verb available records a SECOND transfer entry for the same money — one bank GL permanently overstated, the other understated. This endpoint is the alternative: the movement is already on the books, so the line is attached to the entry that booked it.

The server re-validates, and the caller cannot steer it. The journal_entry_id must still satisfy the same predicate the review queue proposed from, re-checked under a row lock: a posted, unreversed, unvoided CASH_MOVEMENT entry whose single attached bank line sits on ANOTHER of this entity’s bank accounts, carries the same amount in the opposite direction within 2 days, is not pending, and whose own memo reads as a transfer between the operator’s accounts. Anything else is 422 transfer_link_invalid.

Bounded and idempotent by construction. A candidate entry must have exactly ONE bank line attached today, so once this call succeeds the same line cannot be linked twice and no third line can be attached to a transfer that already has both halves.

No GL postings occur. One audit row (bank_transaction.linked_to_transfer) and one bank_transaction.matched event. Undo is the normal unmatch: the line is restored to unreconciled and the journal entry is left alone.

POST /accounting/bank-transactions/{id}/link-transfer

Link a bank line to the transfer journal entry that already booked it

cURL

curl --request POST \
  --url https://api.arcuserp.com/v1/accounting/bank-transactions/{id}/link-transfer \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "journal_entry_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a"
}
'

200

{
  "data": {
    "bank_transaction_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
    "journal_entry": {
      "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
      "entry_number": "<string>"
    },
    "counterparty_bank_transaction_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
    "posted_on": "2023-12-25",
    "reconciliation_status": "matched",
    "journal_entry_posted": false
  }
}

Authorizations

Authorization · string · header · required

API key issued per entity via Settings > Developers > API Keys. Each key carries scopes (e.g. orders:read, products:write). Bearer token format: Authorization: Bearer ark_live_ent_Test keys use ark_test_ent_. Both are issued per entity
via Settings > Developers > API Keys.

Path Parameters

id · string<uuid> · required

The bank transaction to link.

Body

application/json

journal_entry_id · string<uuid> · required

The already-posted transfer journal entry that booked this movement.

Response

200

application/json

Linked

data · object

Show child attributes