Recovering both legs: a cover payment reversed after settlement
Trigger: The debtor reports the payment as fraudulent after the cover payment fully settled — Cassia has already credited the beneficiary, and Meridian has already completed the correspondent-account book transfer.
What operations sees first: Reversing the payment means addressing two independent legs, not one: the beneficiary credit at the creditor agent, and the cover value sitting at the correspondent.
WHERE IS THE MONEY?
Recovered from the beneficiary at Cassia, returned across the correspondent path, and re-credited to the debtor at Bank Alfa.
DID SETTLEMENT HAPPEN?
Both original settlements stand in the audit trail; the recovery creates new, separate reversing entries rather than erasing them.
WHO ACTS NEXT?
Bank Alfa (debtor agent) Bank Alfa closes both leg-specific cases only after the camt.029 outcome and the reverse correspondent entry both reconcile to the same UETR.
PLAY THE EXCEPTION
Trigger: The debtor reports fraud after Cassia credited the beneficiary. Bank Alfa must coordinate the pacs.008 instruction leg and the pacs.009 COV value leg; stopping only one leaves an unmatched payment.
The debtor initiates the cross-border payment
Debtor (payer) → Bank Alfa (debtor agent) · pain.001
A corporate treasury sends a pain.001 with structured party and remittance data. The same starting point as a serial payment — what differs is how Bank Alfa routes the instruction and the money.
Step 1 of 16: The debtor initiates the cross-border payment
- 02ProcessingBank Alfa validates, screens, and debitsBank Alfa (debtor agent)
- 05SettlementMeridian settles the cover across its booksMeridian Bank (correspondent)
- 06ProcessingCassia sees the cover arrive on its nostroCassia Bank (creditor agent)
- 07ProcessingCassia matches the instruction against the coverCassia Bank (creditor agent)
- 08PostingThe creditor is creditedCassia Bank (creditor agent)
- 12 · EXCEPTION PATHPostingCassia secures the recoverable fundsCassia Bank (creditor agent)
- 15 · EXCEPTION PATHSettlementThe cover value settles back to Bank AlfaMeridian Bank (correspondent)
- 16 · EXCEPTION PATHPostingBank Alfa credits the recovered amountBank Alfa (debtor agent)
- OUTCOME
- Funds
- Recovered from the beneficiary, returned across the cover path, and re-credited to the debtor.
- Settlement
- The original cover settlement remains recorded; pacs.004 caused a separate reverse settlement.
- Who acts next
- Bank Alfa (debtor agent) — Close both leg-specific cases only after the camt.029 outcome and reverse correspondent entry reconcile to the same UETR.
Full step-by-step text (works without JavaScript)
- 02ProcessingBank Alfa validates, screens, and debitsBank Alfa (debtor agent)
After checks and screening on the structured fields, the customer account is debited and the bank chooses the cover method: announce directly to the creditor agent, and fund through correspondents.
- DR Debtor's account at Bank Alfa — USD 1,250,000.00
Screening checkpoint: Outbound cross-border screening — Both the direct instruction and the cover leg are screened by every bank that touches them.
- 05SettlementMeridian settles the cover across its booksMeridian Bank (correspondent)
As in the serial flow, settlement is a book transfer between the two banks' USD accounts held at Meridian, the shared correspondent.
- DR Bank Alfa's USD account at Meridian (vostro) — USD 1,250,000.00
- CR Cassia's USD account at Meridian (vostro) — USD 1,250,000.00
- 06ProcessingCassia sees the cover arrive on its nostroCassia Bank (creditor agent)
A credit notification tells Cassia the money side is complete on its account at Meridian. Now it has both halves of the payment: the instruction and the funds.
- 07ProcessingCassia matches the instruction against the coverCassia Bank (creditor agent)
The creditor agent pairs the pacs.008 with the incoming cover by UETR, references, and amount. Crediting on the pacs.008 alone would be paying before being paid.
- 08PostingThe creditor is creditedCassia Bank (creditor agent)
With instruction and funds matched, Cassia credits its customer. The cover method gives the creditor agent the details sooner, but the credit still waits for the money to actually arrive.
- CR Creditor's account at Cassia — USD 1,250,000.00
- 12 · EXCEPTION PATHPostingCassia secures the recoverable fundsCassia Bank (creditor agent)
In this accepted branch Cassia obtains the required authority and debits the beneficiary. A refused or unavailable recovery would end with a negative camt.029 and no reverse value movement.
- DR Creditor's account at Cassia — USD 1,250,000.00
- 15 · EXCEPTION PATHSettlementThe cover value settles back to Bank AlfaMeridian Bank (correspondent)
Meridian debits Cassia's USD account and credits Bank Alfa's account. Operations matches this reverse entry to both cancellation cases before closing them.
- DR Cassia's USD account at Meridian (vostro) — USD 1,250,000.00
- CR Bank Alfa's USD account at Meridian (vostro) — USD 1,250,000.00
- 16 · EXCEPTION PATHPostingBank Alfa credits the recovered amountBank Alfa (debtor agent)
The debtor is re-credited only after the returned cover value is received. Case status and account evidence remain separate controls.
- CR Debtor's account at Bank Alfa — USD 1,250,000.00
- OUTCOME
- Funds
- Recovered from the beneficiary, returned across the cover path, and re-credited to the debtor.
- Settlement
- The original cover settlement remains recorded; pacs.004 caused a separate reverse settlement.
- Who acts next
- Bank Alfa (debtor agent) — Close both leg-specific cases only after the camt.029 outcome and reverse correspondent entry reconcile to the same UETR.
THE TIMELINE
- 01Bank Alfa's customer (debtor)Reports the payment as fraudulent after both interbank legs have already settled.camt.055
- 02Bank Alfa (debtor agent)Opens two separate cancellation cases, since no single message reaches both legs: one to Cassia about the beneficiary credit, one to Meridian about the cover value.camt.056
- 03Cassia Bank (creditor agent)Investigates, obtains the required authority, and debits the beneficiary to secure the recoverable funds.
- 04Cassia BankReports the accepted recovery on the instruction leg, then returns the recovered cover value to Meridian as a new movement.pacs.004
- 05Meridian Bank (correspondent)Credits the reversed cover value back to Bank Alfa; the cover-leg case closes only once this entry reconciles to the shared UETR.
Resolution: A cover payment settles in two places — the beneficiary credit at the creditor agent, and the cover value at the correspondent. Recovering it after settlement means opening and resolving both cases; closing only one leaves the other side of the payment unaccounted for.
Sources for this scenario3
- Official requirement
ISO 20022 Catalogue of messages ↗ — ISO 20022 Registration Authority · camt.056 FIToFIPaymentCancellationRequest and camt.029 ResolutionOfInvestigation message definitions
Each message set is described by a Message Definition Report; earlier versions remain available in the ISO 20022 messages archive.
- Market practice
Cross-Border Payments and Reporting Plus (CBPR+) usage guidelines ↗ — Swift (CBPR+ working group) · cancellation and investigation usage for cover payments
Full guidelines require MyStandards access. Public guidance states that after 14 November 2026 fully unstructured addresses are removed for in-scope CBPR+ traffic, with explicit message exceptions including admi.024, camt.025, camt.052, camt.053, camt.054 and camt.060.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
What this simplifies: Single correspondent on the cover leg and a single accepted-recovery path shown; real cases may span more correspondents, take longer, or be refused at any hop.
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.