pacs.004 FOCR: Check Both Cover Legs Before a Refund
Lumina Academy
A pacs.004 with FOCR does not settle every refund question; check the beneficiary outcome, cover funds and reconciliation before refunding.
Payment Series — Episode 18
One camt.055 leads to two camt.056 messages, and then a pacs.004 arrives with return reason FOCR. The money is back, so can we refund the customer straightaway? I would pause here, because a cover payment has two linked legs, and the returned funds do not automatically explain the outcome of both.
One customer payment, two linked legs
Take a USD10,000 cross-border payment sent using the Cover Method. The pacs.008 carries the direct instruction to the beneficiary bank. The pacs.009 COV carries the cover funds through the correspondent chain. I see one customer payment, but I need to understand two linked positions before making a refund decision.
The customer then requests cancellation through camt.055. Depending on the situation, the bank may need one camt.056 for each leg. That distinction matters: a cancellation request relating to one leg is not evidence that the other leg has also been resolved.
The sequence in this example is:
1. pacs.008: direct instruction to the beneficiary bank.
2. pacs.009 COV: cover funds through the correspondent chain.
3. camt.055: customer cancellation request.
4. camt.056: cancellation requests may be needed for the respective legs.
5. pacs.004: returned funds arrive with FOCR.
At the last step, I still need to ask which original message the return relates to. Without that question, the sequence can look complete when the underlying payment position is not.
FOCR explains why; OrgnlMsgNmId helps identify what
FOCR means Following Cancellation Request. It explains why the funds were returned. OrgnlMsgNmId identifies the original message type associated with the return. I would read these together, rather than make the return reason do more work than it can.
For example, “following cancellation” does not tell me that both legs have been resolved. Equally, knowing the original message type does not, by itself, establish the beneficiary account outcome. The fields answer different questions, and neither replaces the reconciliation needed before refunding.
I would first check:
• What reason is given for the return?
• Which original message type does OrgnlMsgNmId identify?
• Which part of the customer payment does this return relate to?
• What remains unknown about the other leg?
There is also a naming point worth keeping precise: COV is a usage of pacs.009, not a separate ISO message type. I would not assume that the original message name alone supplies all the context needed to identify the cover leg.
The refund decision depends on the linked outcome
If the return relates to pacs.008, I would confirm the beneficiary outcome, verify the cover-funds position and reconcile before refunding. I would not skip the cover check just because the return concerns the direct instruction.
If OrgnlMsgNmId identifies pacs.009, I would first confirm that it relates to the cover leg. An intermediary may have returned the cover funds even though the beneficiary bank has already credited the beneficiary. In that situation, “funds returned” and “beneficiary not paid” are not equivalent statements.
The pacs.008 status therefore needs verification using camt.029, the gpi Tracker or MT199, where applicable. These are not interchangeable tools to use without context; the applicable route for establishing the outcome still matters.
Now imagine refunding the debtor while the beneficiary keeps USD10,000. The customer refund would have been made without resolving the linked positions. Who bears that loss? That question is why I insist on three checks before the refund decision: beneficiary outcome, cover-funds position and accounting reconciliation.
So, What Makes the Difference?
A good BA does not stop at identifying the return message. I would expect the requirement discussion to:
• Distinguish the customer payment from its two linked legs.
• Separate the return reason from the identity of the original message.
• Confirm whether a pacs.009 return actually relates to the cover leg.
• Establish the beneficiary’s outcome instead of inferring it from returned cover funds.
• Connect the refund decision to both funds positions and accounting reconciliation.
The practical skill is asking what is still unresolved. A familiar reason code can make a case feel straightforward, but the next financial action needs evidence, not just a recognisable label.
Key Takeaways
• FOCR EXPLAINS WHY: It does not prove that both payment legs are resolved.
• CHECK THE ORIGINAL MESSAGE: OrgnlMsgNmId helps identify what the return relates to.
• COVER RETURN IS NOT BENEFICIARY OUTCOME: The beneficiary may already have been credited.
• RECONCILE BEFORE REFUNDING: Establish the beneficiary outcome and cover-funds position together.
At Lumina Academy, I use linked-payment scenarios to practise this kind of BA decision-making. For individual guidance, you can book a conversation at https://topmate.io/jebaraj_d.
Changed: Converted the latest Episode 18 revision into a blog, preserving the USD10,000 example and the applicable camt.029, gpi Tracker or MT199 status checks.
More stories
- Late consent after a payment recall
- Why payments need multiple statuses
- When the expected Nostro debit is missing
- Which STP failures belong in repair?
- Preferred versus mandatory intermediaries
- Should a failed cover payment be recredited?
- How banks set a payment cut-off
- When does camt.055 trigger camt.056?
- INDA vs INGA — One Code, Two Accounting Outcomes 🤔
- pacs.028: A Missing pacs.002 Does Not Mean Payment Failure
- Payment Routing: Preferred Does Not Mean Mandatory
- pacs.009 COV Rejected with FF01: Do Not Rush the Refund
- Payment Cut-Off Times: Work Backwards from the Deadline
- camt.055 to camt.056: Check the Payment Lifecycle First
