| Field | Meaning | Required |
|---|---|---|
Assgnmt | The assignment block holding the identification of the cancellation request, the assigner and the assignee. It identifies the request for tracking and audit. Th | M |
Undrlyg | The underlying transaction block holding the original payment reference and details. It tells the receiving bank exactly which payment the cancellation refers t | M |
OrgnlGrpInf | Information about the original message group, including its message identification and creation date. It helps the receiving bank find the original message in i | O |
OrgnlInstrId | The instruction identification of the original payment, copied into the cancellation request. It is the primary key the receiving bank uses to find the payment. | M |
OrgnlEndToEndId | The end to end identification of the original payment, copied into the cancellation request. It stays unchanged through the chain and lets all parties refer to | O |
OrgnlTxId | The transaction identification of the original payment, assigned by the instructing agent. It gives the receiving bank a further matching key. Banks use it to c | O |
OrgnlIntrBkSttlmAmt | The interbank settlement amount of the original payment, copied into the request. It confirms which payment is being cancelled when several payments share simil | O |
OrgnlIntrBkSttlmDt | The interbank settlement date of the original payment, copied into the request. It confirms the value date of the payment to be cancelled. The receiving bank us | O |
CxlRsnInf | The reason for the cancellation, with a coded reason and additional text. Codes include DUPL for duplicate payment, FRAD for fraud, CUST for customer request an | M |
OrgnlTxRef | Reference data from the original payment, such as amount, currency, debtor and creditor, copied into the request. It helps the receiving bank match the cancella | O |
Case | Case information for the cancellation, including the case identification and the creator of the case. It links the cancellation request to an investigation or c | O |
CtrlData | Control data for the cancellation request, such as the number of transactions covered. It is used when one request covers several payments. The receiving bank c | O |
Meridian Bank London sends a camt.056.001.08 to Harbour Bank Singapore to cancel the pacs.008 with end to end identification MER-20261105-1187, reason DUPL, duplicate payment sent twice by the customer. Harbour Bank confirms the payment has not yet been credited and stops it.
Valid example from the message catalogue. Scheme rules: camt.056 is a base ISO 20022 message: the structure and fields below are the base definition, and each scheme adds its own rules for its rail. Under SEPA a recall may only use the reasons DUPL, TECH o
Exceptions and Investigations: camt.056, camt.029 and pacs.004 Returns
What you will learn
Your objective. By the end of this lesson, you will be able to explain exceptions and investigations: camt.056, camt.029 and pacs.004 returns. A camt.056 is the FI to FI Payment Cancellation Request, and it is the message Meridian Bank Paris sends when Loire Components asks it to stop a payment that has already left the bank.
Why it matters. Timing decides whether a camt.056 can succeed, and a business analyst must design the process around that fact.
Chapter objective: Message flows, exchange periods and the 2024 transition
Key learning points
- Camt.056: FI to FI Payment
- Camt.056 asks for action
- Camt.029 carries a status
- Clearing system settles
- Cancellation request sent within minutes
- SCT scheme rules set time limits
Key terms
Settlement: The final movement of funds between banks to discharge obligations created by cleared payments. Settlement is usually made in central bank money or through correspondent accounts.
camt.056: An ISO 20022 message used to request cancellation of a payment instruction that was already sent. It is used for recalls, where the sender asks the receiving bank to return the funds.
camt.029: An ISO 20022 message that reports the resolution of an investigation, such as a cancellation request or a claim of non receipt.
ISO 20022 XML explorer showing Exceptions and Investigations: camt.056, camt.029 and pacs.004 Returns.
Practise this lesson
Exercise
Read the camt.056 message described in this lesson and identify its key parts.
Use the message structure, fields and example in this lesson.
- What to do. List the main blocks of the message, name the field that carries the amount, and name the field that identifies the payment.
Correct result. The message is made of blocks, each carrying a part of the payment instruction. The amount field and the identification field are the two a receiving bank checks first, because without them it cannot process or reconcile the payment.
Why. A message is only useful if you can read it. The blocks tell the receiving bank what to do, and the amount and identification fields are what it checks first.
Check your understanding
Practice question
Which of the following best describes exceptions and investigations: camt.056, camt.029 and pacs.004 returns?
Takeaway and next step
What to remember
The SCT scheme rules set time limits for these steps, and the banks must follow them.
Run the exception from this lesson and follow the investigation to its resolution.
Open the Exception Investigation Simulator →
Builds on "Interbank Space: pacs.008, pacs.002 and pacs.004 Step by Step".
Transcript and full text
Show transcript
A camt.056 is the FI to FI Payment Cancellation Request, and it is the message Meridian Bank Paris sends when Loire Components asks it to stop a payment that has already left the bank. Suppose the treasury team at Loire Components discovers on Tuesday morning that it sent the EUR 48,250 payment twice, once by file and once by online banking, and it asks Meridian Bank Paris to cancel the duplicate. Meridian Bank Paris sends a camt.056.001.08 to Harbour Bank Frankfurt, naming the original pacs.008, the end to end identification LOIRE-RHINE-2026-1148, and the reason for the cancellation request. The camt.056 asks for action, but it does not move money by itself. Harbour Bank Frankfurt answers the cancellation request with a camt.029.001.09 Resolution of Investigation message, and that answer decides what happens next. If the duplicate payment has not yet been credited to Rhine Metals, Harbour Bank Frankfurt can stop it and reply with a positive camt.029, confirming the cancellation. If the funds have already been credited, the bank cannot simply take them back, and it replies with a negative camt.029, explaining that the payment has already been settled to the beneficiary. The camt.029 carries a status and a reason code, so Meridian Bank Paris knows whether to expect a return or to start a different recovery process. When a cancellation succeeds, the funds come back through a pacs.004 Payment Return, and the return is a new settlement instruction in its own right. Harbour Bank Frankfurt sends a pacs.004.001.09 for EUR 48,250, carrying the original end to end identification, the return reason code, and the reference to the original pacs.008. The clearing system settles the return in the next exchange period, Meridian Bank Paris receives the funds, and it credits EUR 48,250 back to the Loire Components account. Meridian Bank Paris then sends a pain.002 report to Loire Components confirming the return, so the treasury team can reconcile the duplicate and close the investigation. Timing decides whether a camt.056 can succeed, and a business analyst must design the process around that fact. A cancellation request sent within minutes of the original payment has a good chance of catching the payment before the beneficiary bank credits it. A request sent a day later, after Rhine Metals has already used the funds to pay its own suppliers, will almost certainly receive a negative camt.029. In that case, the recovery depends on Rhine Metals agreeing to return the money voluntarily, and Meridian Bank Paris may need to send a new instruction or a request for a refund. The SCT scheme rules set time limits for these steps, and the banks must follow them. Worked example with numbers: on Tuesday morning Loire Components discovers it sent the EUR 48,250 payment twice, once on Monday and once on Tuesday, and asks Meridian Bank to stop the second payment. Meridian Bank sends a camt.056.001.08 cancellation request to Harbour Bank Frankfurt, and Harbour Bank checks whether the duplicate has been credited to Rhine Metals. If it has not, Harbour Bank stops it and replies with a camt.029.001.09 confirming the cancellation, and the funds come back through a pacs.004.001.09 for EUR 48,250 carrying the original end to end identification and the return reason code AM05, duplicate payment. If the duplicate has already been credited, Harbour Bank cannot stop it, and Meridian Bank must ask Rhine Metals to return the funds voluntarily. Failure and recovery: a cancellation fails when it arrives too late, and the timing is the whole story. A camt.056 sent within minutes of the original payment has a good chance of catching it before the beneficiary bank credits it, but a request sent a day later will almost always fail, because the funds have already been credited and the beneficiary bank cannot take them back without the beneficiary consent. The recovery for a late cancellation is a request to the beneficiary to return the funds, and if the beneficiary refuses, the originator must take legal action. A business analyst must therefore design the cancellation process around speed, with a clear route from the customer request to the camt.056, and a clock that shows how long the payment has been in flight For a business analyst, product owner or subject matter expert, the cancellation requirement must state the messages, camt.056 out, camt.029 back, and pacs.004 for the return, and must state the timing rule, a cancellation is likely to succeed only if it arrives before the beneficiary bank credits the account. The requirement must also state the recall deadlines, 10 banking business days for a duplicate or technical reason and 13 months for fraud, and that the beneficiary bank must respond within 15 banking business days. The test pack must include a cancellation that succeeds, one that arrives too late, and one for fraud. Source: EPC SCT Rulebook 2025 version 1.1, sections 4.3.2.3 and 4.3.2.4 last reviewed 7 November 2026.
A camt.056 is the FI to FI Payment Cancellation Request, and it is the message Meridian Bank Paris sends when Loire Components asks it to stop a payment that has already left the bank. Suppose the treasury team at Loire Components discovers on Tuesday morning that it sent the EUR 48,250 payment twice, once by file and once by online banking, and it asks Meridian Bank Paris to cancel the duplicate. Meridian Bank Paris sends a camt.056.001.08 to Harbour Bank Frankfurt, naming the original pacs.008, the end to end identification LOIRE-RHINE-2026-1148, and the reason for the cancellation request. The camt.056 asks for action, but it does not move money by itself.
Harbour Bank Frankfurt answers the cancellation request with a camt.029.001.09 Resolution of Investigation message, and that answer decides what happens next. If the duplicate payment has not yet been credited to Rhine Metals, Harbour Bank Frankfurt can stop it and reply with a positive camt.029, confirming the cancellation. If the funds have already been credited, the bank cannot simply take them back, and it replies with a negative camt.029, explaining that the payment has already been settled to the beneficiary. The camt.029 carries a status and a reason code, so Meridian Bank Paris knows whether to expect a return or to start a different recovery process.
When a cancellation succeeds, the funds come back through a pacs.004 Payment Return, and the return is a new settlement instruction in its own right. Harbour Bank Frankfurt sends a pacs.004.001.09 for EUR 48,250, carrying the original end to end identification, the return reason code, and the reference to the original pacs.008. The clearing system settles the return in the next exchange period, Meridian Bank Paris receives the funds, and it credits EUR 48,250 back to the Loire Components account. Meridian Bank Paris then sends a pain.002 report to Loire Components confirming the return, so the treasury team can reconcile the duplicate and close the investigation.
Timing decides whether a camt.056 can succeed, and a business analyst must design the process around that fact. A cancellation request sent within minutes of the original payment has a good chance of catching the payment before the beneficiary bank credits it. A request sent a day later, after Rhine Metals has already used the funds to pay its own suppliers, will almost certainly receive a negative camt.029. In that case, the recovery depends on Rhine Metals agreeing to return the money voluntarily, and Meridian Bank Paris may need to send a new instruction or a request for a refund. The SCT scheme rules set time limits for these steps, and the banks must follow them.
Worked example with numbers: on Tuesday morning Loire Components discovers it sent the EUR 48,250 payment twice, once on Monday and once on Tuesday, and asks Meridian Bank to stop the second payment. Meridian Bank sends a camt.056.001.08 cancellation request to Harbour Bank Frankfurt, and Harbour Bank checks whether the duplicate has been credited to Rhine Metals. If it has not, Harbour Bank stops it and replies with a camt.029.001.09 confirming the cancellation, and the funds come back through a pacs.004.001.09 for EUR 48,250 carrying the original end to end identification and the return reason code AM05, duplicate payment. If the duplicate has already been credited, Harbour Bank cannot stop it, and Meridian Bank must ask Rhine Metals to return the funds voluntarily.
Failure and recovery: a cancellation fails when it arrives too late, and the timing is the whole story. A camt.056 sent within minutes of the original payment has a good chance of catching it before the beneficiary bank credits it, but a request sent a day later will almost always fail, because the funds have already been credited and the beneficiary bank cannot take them back without the beneficiary consent. The recovery for a late cancellation is a request to the beneficiary to return the funds, and if the beneficiary refuses, the originator must take legal action. A business analyst must therefore design the cancellation process around speed, with a clear route from the customer request to the camt.056, and a clock that shows how long the payment has been in flight
For a business analyst, product owner or subject matter expert, the cancellation requirement must state the messages, camt.056 out, camt.029 back, and pacs.004 for the return, and must state the timing rule, a cancellation is likely to succeed only if it arrives before the beneficiary bank credits the account. The requirement must also state the recall deadlines, 10 banking business days for a duplicate or technical reason and 13 months for fraud, and that the beneficiary bank must respond within 15 banking business days. The test pack must include a cancellation that succeeds, one that arrives too late, and one for fraud. Source: EPC SCT Rulebook 2025 version 1.1, sections 4.3.2.3 and 4.3.2.4 last reviewed 7 November 2026.
Full lesson text (all scenes)
Completing a lesson updates your progress dashboard on the homepage.
Scene timestamps are estimated by allocating the narration text proportionally across the real audio length. The audio playback position is the source of truth: pause freezes the visual, seeking restores the correct scene, replay restarts the scene animation.