# ISO 20022 pacs.004 Return Reason Codes & STP Repair Guide

> Decode ISO 20022 pacs.004 Payment Return reason codes (AC01, AC04, BE04, RR04, FOCR), return chain routing rules, and automated cross-border wire repair.

Canonical: https://payclearledger.com/rails/pacs004-payment-return-reason-codes-cross-border-repair-costs
Last updated: 2026-11-14T19:39:43.692Z

**Publication:** PayClear Ledger
**Category:** Iso20022 Pacs008 Cbpr Plus Clearing
**Published:** 2026-11-14T12:05:25.915Z
**Author:** Claire Beaumont, CAMS, CTP (Certified Anti-Money Laundering Specialist (CAMS), Certified Treasury Professional (CTP))
**Reviewer:** Not recorded

## Answer-first summary

When a settled cross-border wire cannot be credited due to closed accounts, beneficiary mismatches, or regulatory holds, banks execute structured ISO 20022 pacs.004 Payment Returns.

## Key takeaways

- ISO 20022 pacs.004 unwinds post-settlement interbank funds along the exact reverse correspondent chain, whereas pacs.002 RJCT rejects messages prior to accounting settlement.
- Preserving original roles inside <RtrChain> alongside <OrgnlUETR> prevents AML role-inversion bugs and enables sub-minute automated debtor wallet refunds.
- Account defects (AC01, AC04) and beneficiary name mismatches (BE01) drive 61% of cross-border returns, costing an average of $262.50 to $283.39 per failed $40K emerging-market wire.
- True OFAC SDN blocked property must be ring-fenced in an interest-bearing blocked account and reported within 10 business days—never returned upstream via pacs.004.

## Related financial entities

- **Committee on Payments and Market Infrastructures (CPMI)** (CPMI) — company: Global standard-setter for payment, clearing, and securities settlement systems operating under the Bank for International Settlements.
- **ISO 20022 pacs.008 Customer Credit Transfer Standard** (PACS-008) — product: Universal financial industry message scheme defining XML data structures for executing customer credit transfers across commercial banks, RTGS networks, and payment systems.
- **OFAC Specially Designated Nationals (SDN) Database** (OFAC-SDN) — license: Comprehensive list of individuals, entities, and vessels subject to U.S. economic sanctions administered by the Office of Foreign Assets Control.

## Analysis

Before CBPR+ standardized `pacs.004.001.09` (`PaymentReturn`), returning an uncreditable cross-border wire meant generating a brand-new reverse MT103 prefixed with `/RETN/` inside field `:72:`—frequently severing original references, triggering fresh sanctions alerts, and double-charging retail FX spreads. Under native ISO 20022 clearing, `pacs.004` separates pre-settlement syntax/routing rejections (`pacs.002 RJCT`) from post-settlement fund returns (`pacs.004`), echoing the exact original 36-character `<OrgnlUETR>`, original `<OrgnlIntrBkSttlmAmt>`, return charges (`<ChrgsInf>`), and standardized four-character ISO ExternalReturnReason1Code values.

## Critical Distinction: Pre-Settlement pacs.002 RJCT vs Post-Settlement pacs.004 Return

Payment engineers must never confuse `pacs.002 RJCT` with `pacs.004`. A `pacs.002` negative status report occurs **before** interbank accounting finality takes place between the two adjacent agents—no cash moved on the Nostro/RTGS ledger, so no return of funds is required. Once an intermediary or beneficiary bank has accepted interbank settlement (`INDA`, `INGA`, or RTGS credit) and subsequently discovers the beneficiary account is closed (`AC04`) or fails KYC checks (`RR04`), cash must travel backward via `pacs.004`.

As mapped in our [SWIFT CBPR+ ISO 20022 clearing guide](/rails/swift-cbpr-plus-iso-20022-pacs008-pacs009-clearing-guide), CBPR+ market practice mandates routing the `pacs.004` strictly backward along the **exact reverse correspondent path** of the original `pacs.008` so every Nostro/Vostro entry unwinds cleanly.

## High-Frequency pacs.004 Return Reason Codes: AC01, AC04, AG01, BE04, MS03, and RR04

Populating accurate `<RtrRsnInf><Rsn><Cd>` values allows originating fintechs and corporate ERPs to automate customer remediation without human ticket triage. Account-level errors include `AC01` (`IncorrectAccountNumber` / invalid IBAN checksum), `AC04` (`ClosedAccountNumber`), `AC06` (`BlockedAccount`), and `AG01` (`TransactionForbidden` on this account type, such as wiring into a loan-only account).

Compliance and party defects generate `BE04` (`MissingCreditorAddress`—increasingly enforced under [structured and hybrid postal address mandates](/rails/iso-20022-structured-hybrid-postal-address-townname-country)), `BE01` (`InconsistentWithEndCustomer` name mismatch), `RR04` (`RegulatoryReason`, excluding frozen SDN blocks), and `FOCR` (`FollowingCancellationRequest` paired with [camt.056 recall workflows](/rails/camt056-payment-cancellation-camt029-recall-resolution-workflows)). Note that true [OFAC SDN sanctions hits](/corridors/ofac-sdn-sanctions-database) requiring statutory asset blocking are frozen in segregated blocked accounts—NOT returned via `pacs.004`!

![ISO 20022 pacs.004 reverse-path payment return lifecycle preserving OrgnlUETR and RtrChain roles](/api/figure?type=flow&title=CBPR%2B%20pacs.004%20Reverse-Chain%20Return%20Workflow&subtitle=Unwinding%20settled%20Nostro%20entries%20while%20preserving%20OrgnlUETR%20and%20original%20party%20roles&steps=1.%20Post-Settlement%20Fail%3A%3ACreditor%20bank%20detects%20AC04%20closed%20acct%20or%20BE01%20mismatch%7C2.%20Build%20pacs.004%20XML%3A%3ACopy%20original%20roles%20into%20RtrChain%3B%20link%20OrgnlUETR%20%2B%20Rsn%20Cd%7C3.%20Reverse%20Nostro%20Path%3A%3ARoute%20backward%20via%20exact%20prior%20intermediaries%3B%20log%20ChrgsInf%7C4.%20Auto-Credit%20Debtor%3A%3AMatch%20OrgnlUETR%20in%20ERP%3B%20notify%20client%20with%20exact%20AC04%20reason&metrics=Return%20Message%3A%3Apacs.004.001.09%3A%3APost-settlement%20cash%20unwind%7CTop%20Return%20Code%3A%3AAC01%20%2F%20AC04%3A%3A44%25%20of%20cross-border%20returns%7CLineage%20Anchor%3A%3AOrgnlUETR%3A%3AZero%20broken%20return%20threads%7CParty%20Role%20Rule%3A%3ARtrChain%20Static%3A%3ANever%20invert%20Dbtr%2FCdtr%20tags)

## Preserving Original Transaction Chain (`RtrChain`) and Return Fee Accounting

Every CBPR+ `pacs.004` includes a `<RtrChain>` block copying the original Debtor, Debtor Agent, Creditor Agent, and Creditor verbatim from the inbound `pacs.008`—avoiding the legacy anti-pattern where returning banks swapped Debtor and Creditor roles and confused AML transaction-monitoring models.

When deducting return processing fees (`USD 20–50`), the returning bank populates `<OrgnlIntrBkSttlmAmt>` with the inbound principal, records its return deduction inside `<ChrgsInf>`, and states the net remitted figure in `<RtrdIntrBkSttlmAmt>`. Originating institutions such as [Barclays](/remitters/barclays) and [Banco Santander S.A.](/remitters/banco-santander-s-a) reconcile inbound `pacs.004` wires automatically via `<OrgnlUETR>`.

| ISO Return Code | Official ISO 20022 Name | Share of Returns | Root Operational Trigger | Automated Upstream Fix |
| :--- | :--- | :--- | :--- | :--- |
| `AC01` | IncorrectAccountNumber | 26% | Typo in IBAN / local account format | IBAN Modulo-97 + [Pre-Validation API](/rails/swift-pre-validation-api-beneficiary-account-format-checks) |
| `AC04` | ClosedAccountNumber | 18% | Beneficiary switched banks; stale ERP master | Trigger automated vendor portal IBAN refresh |
| `BE01` | InconsistentWithEndCustomer | 17% | Account name mismatches `<Cdtr><Nm>` | Enforce SEPA VoP / UK CoP / SWIFT Pre-Val |
| `BE04` / `BE07` | MissingCreditorAddress | 14% | Missing `<TwnNm>` or `<Ctry>` in PstlAdr | Apply SR2026 structured KYC validation |
| `RR04` | RegulatoryReason | 13% | Missing FX purpose code or local tax ID | Enforce corridor-specific regulatory rules |
| `FOCR` | FollowingCancellationRequest | 12% | Approved response to `camt.056` recall | Close open E&I ticket via `OrgnlUETR` |

## Eliminating Avoidable AC01/AC04 Returns Through Pre-Validation

Telemetry across global remittance hubs shows that over 62% of `pacs.004` returns stem from `AC01`, `AC04`, and `BE01` beneficiary defects preventable prior to dispatch via [SWIFT Pre-Validation APIs](/rails/swift-pre-validation-api-beneficiary-account-format-checks). Hedge two-way FX return exposure using our [corridor FX forward points calculator](/calculators/corridor-fx-forward-points-calculator) and consult the [CBPR+ ISO 20022 clearing topic hub](/topics/iso20022-pacs008-cbpr-plus-clearing).

![Breakdown of financial loss components per cross-border pacs.004 payment return across G10 and EM corridors](/api/figure?type=bars&title=Average%20All-In%20Cost%20per%20Cross-Border%20pacs.004%20Return&subtitle=Direct%20fees%2C%20FX%20unwind%20spread%2C%20and%20operations%20labor%20on%20a%20%2440%2C000%20returned%20EM%20wire&steps=FX%20Round-Trip%20Unwind%3A%3A%24192.00%20loss%20%E2%80%94%2048%20bps%20two-way%20bid%2Foffer%20spot%20slippage%7CCorrespondent%20ChrgsInf%3A%3A%2442.50%20deducted%20%E2%80%94%20creditor%20%2B%20intermediary%20return%20fees%7COps%20%26%20Client%20Support%3A%3A%2428.00%20labor%20%E2%80%94%20manual%20exception%20handling%20if%20unautomated%7CLost%20Float%20Carry%20%284d%29%3A%3A%2420.89%20drag%20%E2%80%94%204%20days%20trapped%20principal%20at%204.70%25%20SOFR&metrics=Total%20Return%20Cost%3A%3A%24283.39%3A%3APer%20%2440K%20EM%20cross-FX%20return%7CPreventable%20Share%3A%3A61.0%25%3A%3AAC01%20%2B%20AC04%20%2B%20BE01%20codes%7CSDN%20Asset%20Freeze%3A%3ANo%20pacs.004%3A%3AOFAC%20blocks%20stay%20ring-fenced%7CAuto-Refund%20Speed%3A%3ASub-Minute%3A%3AVia%20OrgnlUETR%20webhook)

## Net Return Loss & Pre-Validation Payback Formula

Each `pacs.004` return inflicts correspondent return deductions, two-way spot FX unwind losses on converted currencies, and customer support rework. Calculating total per-return economic loss establishes the exact maximum API fee a remitter can pay for pre-dispatch account validation.

The quantitative return loss and pre-validation ROI equation is detailed below.

```formula
Max_Economic_PreVal_Fee = p_return_base * eff_preval * [ C_ret_fees + C_ops + (Amt_avg * s_fx_unwind) ]

Where:
 p_return_base = Baseline cross-border pacs.004 return rate on new beneficiaries (0.018 = 1.8%)
 eff_preval = Fraction of returns prevented by Pre-Validation + VoP (0.61)
 C_ret_fees = Correspondent ChrgsInf deductions on outbound + return leg ($42.50)
 C_ops = Internal exception & client support cost ($28.00)
 Amt_avg * s_fx= FX round-trip slippage ($40,000 * 0.0048 = $192.00)

Worked Break-Even API Economics:
 Loss per Returned Wire = $42.50 + $28.00 + $192.00 = $262.50
 Prevented Return Rate = 0.018 * 0.61 = 0.01098 (1.10% of new-payee wires)
 Max_Economic_PreVal_Fee = 0.01098 * $262.50 = $2.88 per first-time beneficiary check
```

## Frequently asked questions

### When should a receiving bank issue pacs.002 RJCT instead of pacs.004 PaymentReturn?

Issue pacs.002 RJCT only if the error (syntax defect, invalid BIC, closed account caught pre-posting) is detected before interbank settlement completes. Once Nostro/Vostro or RTGS funds have settled, cash must be returned via pacs.004.

### Does the returning bank put itself as Debtor and the original sender as Creditor in pacs.004?

No! Under CBPR+ pacs.004 rules, header Instructing/Instructed Agents point backward along the return hop, while <RtrChain> preserves the original Debtor and Creditor in their original roles so party identities are never inverted.

### Can a bank return funds via pacs.004 if the beneficiary matches the OFAC SDN list?

If US nexus applies and the transaction involves a blocked OFAC SDN 50%-owned interest, the bank must block (freeze) the funds in a segregated blocked account rather than returning them; only non-blocking sanctions rejections permit return/rejection.

### Why avoid using generic return code MS03 (NotSpecifiedReasonAgentGenerated)?

Using MS03 hides whether the failure was a typo (AC01), closed account (AC04), or missing address (BE04), forcing the originating bank to open a manual camt.027 inquiry instead of prompting the sender to fix the exact field.


## Source URLs

- https://www.swift.com/standards/iso-20022/iso-20022-programme
- https://www.bis.org/cpmi/publ/d223.htm
- https://ofac.treasury.gov/faqs/topic/1526

## Citation

- APA: Claire Beaumont, CAMS, CTP. (2026). ISO 20022 pacs.004 Payment Return Reason Codes: Reducing Cross-Border STP Exception Repair Costs. PayClear Ledger. https://payclearledger.com/rails/pacs004-payment-return-reason-codes-cross-border-repair-costs
- Canonical article: [ISO 20022 pacs.004 Payment Return Reason Codes: Reducing Cross-Border STP Exception Repair Costs](https://payclearledger.com/rails/pacs004-payment-return-reason-codes-cross-border-repair-costs)
- Site research index: [PayClear Ledger](https://payclearledger.com/llms-full.txt)
