Voids a fund transfer.

POST /banking/fund-transfers/{id}/void

Group: Banking › Fund Transfers · Operation ID: voidFundTransfer

Voiding is not deleting. The transfer, its number and its audit trail all stay, and the ledger effect is withdrawn. There is no endpoint to delete a fund transfer.

Voiding is terminal. Nothing un-voids a transfer, and a second void fails with FUND_TRANSFER_ALREADY_VOIDED.

The journal entry behind the transfer is stamped voided rather than reversed, so no reversing entry is posted. Amortization-schedule journal entries derived from it are voided too, any pending approval becomes rejected, and bank transactions matched to the transfer are unmatched. Attachments and lines are left unchanged.

The posting period must be open for every entity the transfer touches. An intercompany transfer touches two, and either one being closed refuses the void.

The response is empty. Read the transfer back with GET banking/fund-transfers/:id to see its voided state. voidReason is stored on the transfer but no read endpoint returns it.

Open in the interactive reference

Parameters

Name	In	Type	Required	Description
`Api-Version`	header	`"v1"`	yes	The API version this request targets, named by its public identifier. Required on every request; omitting it, or naming a version this company does not have, is answered with 400. This document describes version `v1`.
`Idempotency-Key`	header	string	no	An opaque caller-chosen string (1-255 characters) that makes this request safe to retry. Repeating the same key with an identical request body replays the original response instead of re-executing - but only once that original request succeeded; a failed attempt re-executes on retry. Repeating the key with a different body is answered with 422. A key still in flight is answered with 409 - as is a key whose original request was interrupted before it finished, for a few minutes afterwards, until that attempt is presumed dead. A completed response stays replayable for 24 hours. The key is scoped to the caller, not to the action: reusing it for a different action is answered with 409 or 422 rather than treated independently. On read actions this header is ignored. On write actions that cannot offer the guarantee it is answered with `400 IDEMPOTENCY_NOT_SUPPORTED` rather than silently ignored.
`id`	path	string	yes	The unique identifier for the fund transfer to void.

Request body

Required, application/json: voidFundTransferInput.

Field	Type	Required	Description
`voidReason`	string	yes	The reason the transfer is being voided. It is stored on the transfer and shown in the audit trail. An empty or whitespace-only value is refused.

Example:

{
  "voidReason": "Duplicate of FT-881"
}

Response

200 Success

Response headers

Idempotency-Replayed — Present and true only when this response replays a previously stored one for the same Idempotency-Key, rather than reflecting a live execution. Absent on a live response - never sent as false.

Errors

Code	Status
`NOT_FOUND`	400
`VOID_REASON_REQUIRED`	400
`FUND_TRANSFER_ALREADY_VOIDED`	400
`POSTING_PERIOD_NOT_OPEN`	400
`VOID_FAILED`	400
`IDEMPOTENCY_KEY_CONFLICT`	409
`IDEMPOTENCY_PAYLOAD_MISMATCH`	422

Statuses

400 — Invalid request or business failure. Codes: NOT_FOUND, VOID_REASON_REQUIRED, FUND_TRANSFER_ALREADY_VOIDED, POSTING_PERIOD_NOT_OPEN, VOID_FAILED
401 — Missing or invalid access token
403 — Not authorized
404 — Not found
409 — The Idempotency-Key is still being processed by another request.
422 — The Idempotency-Key was already used with a different request payload.
429 — Too many requests
500 — Internal server error