Payments Academy
Repair: correcting payment PAYMENT OPERATIONS STARTED LIVE 01 Repair - means correcting a payment that has been ACTIVE 02 Return - happens after a payment has been executed QUEUED 03 Recall - have already been credited to the beneficiary QUEUED 04 Cancellation - executed, and it is the remedy QUEUED 05 Analyst's job across all four remedies - record the full audit trail QUEUED Repair means correcting a payment that has been stopped before settlement, so that it can proceed without the customer having to start again. Step 1 of 5 Repair: correcting payment STARTED Repair means correcting a payment that has been ACTIVE Return happens after a payment has been executed QUEUED Recall have already been credited to the beneficiary QUEUED Cancellation executed, and it is the remedy QUEUED Analyst's job across all four remedies record the full audit trail QUEUED Repair means correcting a payment that has been stopped before settlement, so that it can proceed without the customer having to start again.
Return: payment has been executed PAYMENT OPERATIONS IN PROGRESS LIVE 01 Repair - means correcting a payment that has been DONE 02 Return - happens after a payment has been executed ACTIVE 03 Recall - have already been credited to the beneficiary QUEUED 04 Cancellation - executed, and it is the remedy QUEUED 05 Analyst's job across all four remedies - record the full audit trail QUEUED A return happens after a payment has been executed but the beneficiary bank cannot credit it, so the money is sent back to the sender. Step 2 of 5 Return: payment has been executed IN PROGRESS Repair means correcting a payment that has been DONE Return happens after a payment has been executed ACTIVE Recall have already been credited to the beneficiary QUEUED Cancellation executed, and it is the remedy QUEUED Analyst's job across all four remedies record the full audit trail QUEUED A return happens after a payment has been executed but the beneficiary bank cannot credit it, so the money is sent back to the sender.
Recall: request to return funds PAYMENT OPERATIONS IN PROGRESS LIVE 01 Repair - means correcting a payment that has been DONE 02 Return - happens after a payment has been executed DONE 03 Recall - have already been credited to the beneficiary ACTIVE 04 Cancellation - executed, and it is the remedy QUEUED 05 Analyst's job across all four remedies - record the full audit trail QUEUED A recall is a request to return funds that have already been credited to the beneficiary, and it is the hardest remedy to obtain because the money is no longer in the banking system. Step 3 of 5 Recall: request to return funds IN PROGRESS Repair means correcting a payment that has been DONE Return happens after a payment has been executed DONE Recall have already been credited to the beneficiary ACTIVE Cancellation executed, and it is the remedy QUEUED Analyst's job across all four remedies record the full audit trail QUEUED A recall is a request to return funds that have already been credited to the beneficiary, and it is the hardest remedy to obtain because the money is no longer in the banking system.
Cancellation stops payment before execution PAYMENT OPERATIONS IN PROGRESS LIVE 01 Repair - means correcting a payment that has been DONE 02 Return - happens after a payment has been executed DONE 03 Recall - have already been credited to the beneficiary DONE 04 Cancellation - executed, and it is the remedy ACTIVE 05 Analyst's job across all four remedies - record the full audit trail QUEUED Cancellation stops a payment before it is executed, and it is the remedy that customers most often ask for when they realise they have made a mistake. Step 4 of 5 Cancellation stops payment before execution IN PROGRESS Repair means correcting a payment that has been DONE Return happens after a payment has been executed DONE Recall have already been credited to the beneficiary DONE Cancellation executed, and it is the remedy ACTIVE Analyst's job across all four remedies record the full audit trail QUEUED Cancellation stops a payment before it is executed, and it is the remedy that customers most often ask for when they realise they have made a mistake.
Analyst's job across all four remedies PAYMENT OPERATIONS COMPLETE LIVE 01 Repair - means correcting a payment that has been DONE 02 Return - happens after a payment has been executed DONE 03 Recall - have already been credited to the beneficiary DONE 04 Cancellation - executed, and it is the remedy DONE 05 Analyst's job across all four remedies - record the full audit trail ACTIVE The analyst's job across all four remedies is to record the full audit trail Step 5 of 5 Analyst's job across all four remedies COMPLETE Repair means correcting a payment that has been DONE Return happens after a payment has been executed DONE Recall have already been credited to the beneficiary DONE Cancellation executed, and it is the remedy DONE Analyst's job across all four remedies record the full audit trail ACTIVE The analyst's job across all four remedies is to record the full audit trail

Key points of this lesson, in order.

0:00 / 3:21 Step 1 of 5

Payment Repair, Return, Recall and Cancellation

Payment Exceptions and Investigations, Lesson 3 of 7, Narration 3:21, D11 Operations, exceptions and reconciliation

SettlementExceptionpacs.004

What you will learn

Your objective. By the end of this lesson, you will be able to explain payment repair, return, recall and cancellation. Repair means correcting a payment that has been stopped before settlement, so that it can proceed without the customer having to start again.

Why it matters. A payment of USD 60,000 may be held because the beneficiary address is incomplete, or because the intermediary bank details are missing, and the operations team can repair it by adding the missing information from the customer instruction or from a standing arrangement.

Chapter objective: Learner investigates payment exceptions, including non-receipt, wrong amount, duplicate, and delayed payments, and runs a structured investigation from first report to resolution. Learner demonstrates this skill using realistic banking examples, explaining each step clearly and using correct terminology throughout.

Key learning points

  • Repair: correcting payment
  • Return: payment has been executed
  • Recall: request to return funds
  • Cancellation stops payment before execution
  • Analyst's job across all four remedies

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.

Exception: A payment that cannot be processed normally and needs manual handling, investigation or repair. Exceptions arise from missing data, failed screening, account errors or system faults.

pacs.004: An ISO 20022 message used to return a payment that was already settled but cannot be credited to the beneficiary.

Exception investigation workflow showing Payment Repair, Return, Recall and Cancellation.

Insights and practice scenarios

Worked insights and practice scenarios for this lesson. Each one is a reusable PaymentForge case, so the same case may appear in more than one lesson.

Practise this lesson

Exercise

Handle the exception described in this lesson the way the lesson prescribes.

Use the exception type, the reason code and the recovery path in this lesson.

  1. What to do. State what happened, what the correct action is, what must not be done, and what the post-incident review should capture.

Correct result. The correct action is the one the lesson prescribes for this exception type, with the right reason code and the right message. The payment must not be resent without checking whether it already settled, because that creates a duplicate.

Why. An exception handled wrongly is worse than the exception itself. A duplicate payment is a loss, and an unlearned exception will happen again.

Check your understanding

Practice question

A customer reports a payment that arrived short: they expected 10,000 and received 9,950. The investigation finds an intermediary deducted a charge. What should the operations team tell the customer, and what should they check?

Takeaway and next step

What to remember

Good exception handling is therefore as much about documentation as it is about moving money.

Reconcile the payment in this lesson against its statement and find the break.

Open the Accounting and Reconciliation Lab →

The general return, recall and cancellation explanation. The CBPR+ technical deep dive is ch58, which covers pacs.002 and pacs.004, INDA and INGA, and the reject versus return rule in detail.

Transcript and full text

Show transcript

Repair means correcting a payment that has been stopped before settlement, so that it can proceed without the customer having to start again. A payment of USD 60,000 may be held because the beneficiary address is incomplete, or because the intermediary bank details are missing, and the operations team can repair it by adding the missing information from the customer instruction or from a standing arrangement. Repair is the cheapest and fastest remedy, because the money has not yet moved and no second payment is needed. The repaired payment keeps its original reference, but the repair itself must be logged, including who made the change and what was changed, so that auditors can trace it. A return happens after a payment has been executed but the beneficiary bank cannot credit it, so the money is sent back to the sender. The beneficiary bank initiates the return by sending a pacs.004 message, which carries the original reference, the returned amount, and a reason code such as AC04 for a closed account or BE04 for a missing creditor address. The sending bank matches the pacs.004 to the original pacs.008, credits the customer account with the returned funds, and notifies the customer. A return is not a failure of the sending bank, but the customer still needs to know why the payment came back and what they should do differently next time. A recall is a request to return funds that have already been credited to the beneficiary, and it is the hardest remedy to obtain because the money is no longer in the banking system. The sending bank sends a camt.056 message, known as a payment cancellation request, asking the beneficiary bank to return the funds, and the beneficiary bank replies with a camt.029 message stating whether the recall was accepted or rejected. A recall may succeed if the beneficiary agrees, or if the credit was made in error and the beneficiary bank can reverse it, but it may fail if the beneficiary has already spent the money. A recall is therefore a request, not a guarantee, and the customer must understand that distinction. Cancellation stops a payment before it is executed, and it is the remedy that customers most often ask for when they realise they have made a mistake. A customer who instructed a payment of GBP 15,000 to the wrong supplier may call the bank within minutes and ask for it to be cancelled. If the payment is still held in the payment engine and has not yet been sent to the clearing system, the bank can cancel it immediately and restore the funds. If the payment has already been sent, cancellation is no longer possible, and the bank must use a recall instead. The cut-off between those two states is measured in minutes, which is why cancellation requests are treated as urgent. The analyst's job across all four remedies is to record the full audit trail, from the original instruction to the final outcome, so that the customer, the auditor, and the regulator can all see what happened. That trail includes the original pacs.008, the pacs.002 or pacs.004 that reported the problem, the camt.056 and camt.029 if a recall was attempted, and the ledger entries that moved the money back to the customer. A remedy without an audit trail is a risk, because the bank cannot prove that it acted correctly or that the customer received their money back. Good exception handling is therefore as much about documentation as it is about moving money.

Repair means correcting a payment that has been stopped before settlement, so that it can proceed without the customer having to start again. A payment of USD 60,000 may be held because the beneficiary address is incomplete, or because the intermediary bank details are missing, and the operations team can repair it by adding the missing information from the customer instruction or from a standing arrangement. Repair is the cheapest and fastest remedy, because the money has not yet moved and no second payment is needed. The repaired payment keeps its original reference, but the repair itself must be logged, including who made the change and what was changed, so that auditors can trace it.

A return happens after a payment has been executed but the beneficiary bank cannot credit it, so the money is sent back to the sender. The beneficiary bank initiates the return by sending a pacs.004 message, which carries the original reference, the returned amount, and a reason code such as AC04 for a closed account or BE04 for a missing creditor address. The sending bank matches the pacs.004 to the original pacs.008, credits the customer account with the returned funds, and notifies the customer. A return is not a failure of the sending bank, but the customer still needs to know why the payment came back and what they should do differently next time.

A recall is a request to return funds that have already been credited to the beneficiary, and it is the hardest remedy to obtain because the money is no longer in the banking system. The sending bank sends a camt.056 message, known as a payment cancellation request, asking the beneficiary bank to return the funds, and the beneficiary bank replies with a camt.029 message stating whether the recall was accepted or rejected. A recall may succeed if the beneficiary agrees, or if the credit was made in error and the beneficiary bank can reverse it, but it may fail if the beneficiary has already spent the money. A recall is therefore a request, not a guarantee, and the customer must understand that distinction.

Cancellation stops a payment before it is executed, and it is the remedy that customers most often ask for when they realise they have made a mistake. A customer who instructed a payment of GBP 15,000 to the wrong supplier may call the bank within minutes and ask for it to be cancelled. If the payment is still held in the payment engine and has not yet been sent to the clearing system, the bank can cancel it immediately and restore the funds. If the payment has already been sent, cancellation is no longer possible, and the bank must use a recall instead. The cut-off between those two states is measured in minutes, which is why cancellation requests are treated as urgent.

The analyst's job across all four remedies is to record the full audit trail, from the original instruction to the final outcome, so that the customer, the auditor, and the regulator can all see what happened. That trail includes the original pacs.008, the pacs.002 or pacs.004 that reported the problem, the camt.056 and camt.029 if a recall was attempted, and the ledger entries that moved the money back to the customer. A remedy without an audit trail is a risk, because the bank cannot prove that it acted correctly or that the customer received their money back. Good exception handling is therefore as much about documentation as it is about moving money.

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.