ISO 20022 guide
CBPR+ reject codes: how to read a pacs.002 in RJCT
A status report arrives marked RJCT. That leaves three questions open: why, who has to fix it, and whether the payment can be resent. A reject code rarely answers all three — and sometimes none of them.
Published 16 November 2026
Under MT, a rejection usually arrived as free text in an MT195 or MT199, written by a person. Under ISO 20022 it arrives as a code, produced by a system. The gain is real: the reason becomes machine-readable. So is the loss: a code tells you which family the problem belongs to, not what to correct or who should correct it.
This page covers where the code sits in the message, what the most common ones mean, and how to handle the many cases where no reason is given at all.
Where the code sits in the message
The status report is a pacs.002. The transaction status is in TxSts, and the reason, when present, in the StsRsnInf block:
<TxInfAndSts>
<OrgnlEndToEndId>INV-2026-7788</OrgnlEndToEndId>
<OrgnlTxId>TX20261116001</OrgnlTxId>
<OrgnlUETR>a3f2c1d4-5b6e-4f7a-8c9d-0e1f2a3b9c41</OrgnlUETR>
<TxSts>RJCT</TxSts>
<StsRsnInf>
<Rsn>
<Cd>AC04</Cd>
</Rsn>
<AddtlInf>Account closed on 2026-10-30</AddtlInf>
</StsRsnInf>
</TxInfAndSts>
Three elements matter for the investigation, and they should be captured together:
OrgnlUETR— the unique identifier of the original payment. This is what lets you retrieve the message you sent.OrgnlEndToEndId— the originator's own reference, often the invoice number. This is what the customer will quote when they call.AddtlInf— optional free text. When it is populated, it usually says more than the code itself.
The codes come from the ExternalStatusReason1Code list, published and maintained by ISO 20022. It is shared with other messages, notably the customer-facing pain.002 and the pacs.004 used to return funds.
The codes you will actually see
The full list runs to several hundred entries. In practice, a handful account for most of what appears on cross-border flows.
The beneficiary's account
| Code | Meaning | Where it gets fixed |
|---|---|---|
| AC01 | Incorrect account number | with the beneficiary |
| AC04 | Account closed | with the beneficiary |
| AC06 | Account blocked | with the beneficiary, sometimes with no explanation available |
| MD07 | End customer deceased | with the originator |
These are the simplest rejections to handle: the missing information sits with the beneficiary, and you only have to ask for it. They cannot be prevented by message validation, because nothing was wrong with what you sent.
Routing
| Code | Meaning | Where it gets fixed |
|---|---|---|
| RC01 | Bank identifier incorrect, invalid BIC | internal BIC reference data |
| AG01 | Transaction forbidden on this account or relationship | correspondent's terms |
| TM01 | Cut-off time missed | cut-off schedule, resubmit |
RC01 points at something structural: BIC reference data that has not kept up with mergers, branch closures and correspondent changes. It comes in waves, against the same destinations, and is better fixed upstream than case by case.
Beneficiary data
| Code | Meaning | Where it gets fixed |
|---|---|---|
| BE04 | Creditor address missing or incorrect | client reference data, upstream |
| RR03 | Beneficiary name or address insufficient for regulatory requirements | client reference data, upstream |
| RR01 to RR04 | Regulatory information missing on the account or the identity of the parties | client reference data, upstream |
| RR06 | Tax information missing or invalid | originator |
These are the codes whose volume is set to grow. They do not come from a one-off keying error but from the quality of client reference data, and they are fixed upstream of the payment — at onboarding, or when records are refreshed.
One point deserves attention: a message can be perfectly valid against the XSD schema and still come back as BE04 or RR03. The schema checks form — tags present, lengths, types. CBPR+ usage rules govern content: an address can be present and still be judged insufficient by the beneficiary bank or its screening system. See also the accepted address formats and the migration timeline.
Duplicates and amounts
| Code | Meaning | Where it gets fixed |
|---|---|---|
| AM05 | Duplication | investigate before taking any action |
| AM04 | Insufficient funds | on the sending side |
| FF01 | Invalid file format or operation code | technical chain |
AM05 is the most dangerous code on the list — not for what it costs, but for the reaction it triggers. A reported duplicate means an identical message has already been received. If the first one settled and you resend, you create a second debit and a recall far longer than the original incident. Faced with an AM05, establish the actual status of the first message, then act.
When no reason is given
| Code | Meaning | Where it gets fixed |
|---|---|---|
| MS03 | Reason not specified by the agent | call the correspondent |
| MS02 | Reason not specified by the end customer | with the originator or beneficiary |
| NARR | Reason supplied as free text in AddtlInf | human reading of the message |
MS03 and NARR are more common than people expect. They turn up in particular when the real cause is a compliance matter: a bank rejecting a payment for screening reasons will not say which one, and MS03 is then as much a deliberate answer as a lazy one. Treat these as human cases, not as candidates for automation.
The trap: a rejection may carry no reason at all
Under the CBPR+ guidelines, the StsRsnInf block of a pacs.002 is optional, including when the status is RJCT. A rejection message with no code is therefore technically compliant.
Not every infrastructure makes that choice. CPMI recommendations point the other way, and some payment systems make the reason mandatory on rejection. But on the cross-border network, a correspondent can legitimately return a silent RJCT.
The consequence is operational. A share of rejections cannot be handled by automated rule: you have to retrieve the original message from the UETR, compare it with what was sent, look for what departs from the usage rules, and often call the correspondent. This is precisely the work that shrinks when messages are checked before they are sent rather than after they come back.
Reject, return, cancellation: three different things
The confusion is common and has immediate accounting consequences. Three situations, three messages, three states of the money.
| Message | Situation | State of the funds |
|---|---|---|
| pacs.002 RJCT | The payment is refused before being executed | unsettled — nothing moved |
| pacs.004 | Return of funds already settled | settled, then returned |
| camt.056 | Cancellation request sent to the correspondent | uncertain — the answer comes back as camt.029 |
All three can carry codes from neighbouring lists, which keeps the confusion alive: an AC04 can appear in a rejection and in a return alike. But a rejection requires no reversal entry, while a return does. Reading the message type before the code avoids a processing error.
What to build internally
In most teams, knowledge of reject codes lives in the heads of two or three people. It works while they are there, and it is rebuilt from scratch every time one of them leaves.
An internal table is enough to make it durable. For each code you actually encounter, three columns:
- What it means, in one sentence, in your own vocabulary rather than the standard's.
- Who fixes it: the beneficiary, the originator, client reference data, IT, the correspondent.
- Can it be resent: yes once corrected, not without checking first, never without approval.
Do not build this table from the ISO list, which runs to hundreds of entries most of which will never occur. Build it from one month of real rejections, then extend it as new cases appear. Around fifteen codes usually cover day-to-day work.
Check before sending rather than after the rejection
MXplorer Pro analyses your CBPR+ messages on your own workstation, fully offline, and flags the anomalies that pass schema validation but break usage rules: unstructured or incomplete addresses, malformed hybrid addresses, misplaced agents. Nothing leaves the workstation, and the tool neither processes nor sends any payment. The Discovery edition is free.
Try it for freeSources
- ISO 20022 — message definitions and external code lists
- BIS Nexus — pacs.002 and differences from the CBPR+ guidelines
- Swift — CBPR+ and usage guidelines
The meanings given here are those of the ISO 20022 code list. Institutions sometimes add their own internal labels, which is why the same code can be described differently from one bank to the next.