Reject or return in correspondent banking

L0 Explain simply

Analogy: the parcel already delivered, or not. This academy's SEPA material teaches the same underlying question for euro transfers: has the money actually moved yet? A reject means no — the payment is refused before it crosses between banks, so nothing needs undoing. A return means yes — the money already arrived, so bringing it back is a new delivery in the opposite direction, not a cancellation. Correspondent banking asks the identical question, with two extra wrinkles. First, no scheme sets a universal clock the way SEPA's rulebook fixes a beneficiary bank's return window in days — correspondent-banking timing is whatever the correspondent relationship allows. Second, a cover payment splits into two envelopes travelling separately — the announcement and the cover value — so pulling one back after both have arrived means chasing two cases, not one.

RejectReturn

L1 Core concepts

A reject travels as a negative pacs.002: a financial institution refuses the instruction before any interbank settlement happened on that leg — a format error, a compliance hold, a policy refusal — and because no money crossed, there is nothing to reverse, only an instruction to fix and resend or abandon. A return travels as a pacs.004: the interbank leg already settled, value actually moved from one correspondent's books to another's, so getting it back means a new, opposite-direction settlement, referencing the original transaction and carrying a return reason from the ISO 20022 external code set. Unlike SEPA, where the EPC rulebook fixes how many business days a beneficiary bank has to return a settled transfer, correspondent banking carries no scheme-wide return deadline: whether, and how quickly, a correspondent returns settled value is a matter of the bilateral relationship and market practice between the two banks, not a rulebook clock.

RejectReturnpacs.002pacs.004

L2 Practitioner view

Correspondent chains complicate both directions. A reject can come from any bank along the chain, not only the last one — an intermediary refuses before forwarding, and every bank upstream of it never sees a settled leg on its own books at all. A return is harder to unwind the longer the chain: the money has to retrace its way back through however many reimbursement agents carried it out, and each of those correspondents may deduct its own charge again on the way back, the same way it may have deducted one on the way out — which is why a returned amount is so often smaller than what was originally sent, and why reconciling a return means checking every hop's deduction, not only the total shortfall.

Reimbursement agent

L3 Technical details

Illustrative case: Asha Traders' cover payment to a supplier settles cleanly — Meridian carries the cover, Cassia credits the beneficiary directly — and only afterward does Asha Traders report the payment as fraudulent. By now two things have separately happened: Cassia has credited the beneficiary, the announcement's effect landing; and Meridian has completed the correspondent-account book transfer, the cover's effect landing. Getting the money back means recovering both, and neither recovery alone closes the case: a dual-leg recovery treats the instruction leg and the cover leg as two coordinated cases, tied together by the shared UETR, each needing its own request to its own bank and its own answer.

Dual-leg recovery

L4 Standards & sources

Structurally, Bank Alfa sends two separate camt.056 FI-to-FI payment cancellation requests: one to Cassia, referencing the original pacs.008's transaction identifiers, asking it to investigate and — where consent and legal constraints allow — debit the beneficiary; a second to Meridian, referencing the pacs.009 COV's identifiers, asking it to trace and coordinate reversing the correspondent-account book transfer. Each case resolves with its own camt.029, and an accepted cover-leg recovery produces a new pacs.004 returning the cover value — a fresh settlement entry that stands alongside the original pacs.008 and pacs.009 COV in the audit trail, not a deletion of either. Reconciliation only closes cleanly once both camt.029 outcomes and the reverse correspondent-account entry all tie back to the same UETR.