ISO 20022 Messages and Reason Codes for Exceptions (pacs.002, pacs.004, camt.056, camt.029, pain.002 with real reason codes)

The pacs.002 message, known as the payment status report, is the standard way for a bank to tell the sender whether a payment was accepted, rejected, or is still pending. It carries the original payment reference, the status, and, when the payment was rejected, a reason code that explains why. Common codes include AC01 for an incorrect account number, AC04 for a closed account, AM04 for insufficient funds, AM05 for a duplicate payment, and MD07 for an end customer who is deceased. An analyst who receives a pacs.002 with code AC01 knows immediately that the account number must be corrected by the customer, while a pacs.002 with code AM04 knows that the payment can be retried once funds are available. The pacs.004 message, known as the payment return, is sent when a payment that was already executed must be sent back to the sender. It carries the original payment reference, the returned amount, and a reason code, and it is the formal record that the money is on its way back. Typical return codes include AC04 for a closed account, AC06 for a blocked account, BE04 for a missing creditor address, and MD07 for an end customer who is deceased. The returned amount may be less than the original amount if fees were deducted in transit, for example a USD 10,000 payment returned as USD 9,975 after a USD 25 intermediary fee, and the reconciliation team must account for that difference explicitly. The pain.002 message, known as the customer payment status report, is the message a bank sends to its corporate customer to report the status of a payment the customer instructed. It is the customer-facing equivalent of the pacs.002, and it uses the same reason codes, so a corporate treasury system can process it automatically. For example, a company that submits a file of five hundred payments through a host-to-host connection will receive a pain.002 for each payment that fails, with codes such as AC01, AM05, or RR04 for a regulatory reason. The treasury team can then correct the failed payments and resubmit them without manual intervention, which is why large corporates insist on receiving pain.002 reports. The camt.056 message, known as the payment cancellation request, is used when the sending bank asks for a payment to be returned after it has already been executed, and it is the formal start of a recall. It carries the original payment reference, the reason for the recall, and the amount to be returned. The receiving bank replies with a camt.029 message, known as the resolution of investigation, which states whether the recall was accepted or rejected, and gives a reason code for the decision. Common camt.029 outcomes include a successful return, a rejection because the beneficiary does not agree, and a rejection because the funds are no longer available. The pair of messages creates a complete audit trail for the recall attempt. Analysts should treat reason codes as a language to learn, not as random letters to look up each time, because the same codes appear across messages and across banks. AC codes relate to account problems, AM codes relate to amount and duplicate problems, MD codes relate to the end customer, and RR codes relate to regulatory reasons. A payment rejected with code AC06, meaning a blocked account, needs a different conversation with the customer than a payment rejected with code AM04, meaning insufficient funds. Learning the twenty most common codes, and knowing which message carries each one, will make exception investigations faster, more accurate, and far less stressful for everyone involved.