pacs.004.001.11 — Payment Return

Field	Value
ISO name	PaymentReturnV11
Registration status	Registered
Year	2019
Version	11

Overview

The pacs.004 message returns a payment that has already settled. It sends funds back when a payment cannot be applied.

Reviewed 23 March 2026. ISO catalogue date: 2025-02-27.

Key data elements

GrpHdr — Group Header with message identification and creation timestamp.
TxInf — Transaction Information with return amount and parties.
OrgnlGrpInf — Original Group Information linking to the source message.
RtrRsnInf — Return Reason Information with structured reason codes.
OrgnlTxRef — Original Transaction Reference for matching and reconciliation.

Business context

Handles post-settlement returns when the beneficiary's account cannot be credited.
Supports recall scenarios where the originator requests funds back.
Carries structured return reason codes.
Applies to both credit transfer returns (pacs.008) and direct debit returns (pacs.003).

Key data elements and business context
Key data elements	Business context
GrpHdr — Group Header with message identification and creation timestamp	Handles post-settlement returns when the beneficiary's account cannot be credited
TxInf — Transaction Information with return amount and parties	Supports recall scenarios where the originator requests funds back
OrgnlGrpInf — Original Group Information linking to the source message	Carries structured return reason codes
RtrRsnInf — Return Reason Information with structured reason codes	Applies to both credit transfer returns (pacs.008) and direct debit returns (pacs.003)
OrgnlTxRef — Original Transaction Reference for matching and reconciliation	The instructed agent sends pacs.004 back through the payment chain to return settled funds. Each agent in the chain processes the return and credits back the relevant accounts.

CBPR+ and scheme context

Replaces MT103 RETURN and cover-method return messaging.
Return reason codes are standardised and machine-readable under ISO 20022.
CBPR+ requires the full original transaction reference for matching.
SWIFT gpi tracking also covers returns.

Message flow

The instructed agent sends pacs.004 back through the payment chain to return settled funds. Each agent in the chain processes the return and credits back the relevant accounts.

Version commentary

ISO 20022 last updated this business area on 2025-02-27. This site documents pacs.004.001.11. The latest catalogue version is pacs.004.001.14.

Use this page for the version that pacs008 implements today, and review the newer catalogue version for roadmap planning.

Version-diff table

Version history and implementation guidance
Version range	Why it matters	Implementation takeaway
pacs.004.001.11	Current implementation in pacs008	Aligns with current templates for payment returns.
pacs.004.001.12-14	Later catalogue revisions	Review later return-message revisions when scheme upgrades or new counterparties are in scope.

Scheme-specific notes

For SEPA credit-transfer flows, pacs.004 sits in the wider return and exception path defined by the EPC SCT rulebook and EPC SCT Inst rulebook.
In CBPR+, Swift maps pacs.004 alongside pacs.008, pacs.009, and pacs.002. See the CBPR+ roadmap.

When to use this message

Use pacs.004 when settled funds need to move back to the original sender because the payment cannot be applied or must be returned after settlement.

When not to use this message

Do not use pacs.004 when the original instructing agent is requesting an upstream reversal before or around settlement; that is pacs.007 territory.

Implementation notes

Map return reason codes into internal exception categories early.
Keep the original transaction reference easy to find.
Expect scheme and correspondent-bank rules to limit which return reasons are acceptable after specific processing stages.

Common failure modes

Mixing up return and reversal processes.
Losing the link to the original transaction and value date.
Assuming every rejected beneficiary credit should become a pacs.004 automatically.

Worked XML fragment

<PmtRtr>
  <GrpHdr>
    <MsgId>RTRN-2026-0003MsgId>
  GrpHdr>
  <TxInf>
    <OrgnlInstrId>PAY-2026-8841OrgnlInstrId>
    <RtrdIntrBkSttlmAmt Ccy="EUR">25000.00RtrdIntrBkSttlmAmt>
    <RtrRsnInf>
      <Rsn><Cd>AC04Cd>Rsn>
    RtrRsnInf>
  TxInf>
PmtRtr>

Field commentary

OrgnlInstrId: This must point back to the settled transaction being returned.
RtrdIntrBkSttlmAmt: Return amount should reflect the actual returned value, not a reconstructed business amount.
RtrRsnInf: Reason-code quality is critical for downstream customer communication and operational routing.

Decision flow

Has value already settled and now needs to move back?
Yes -> Use pacs.004.
No -> Is the instructing side trying to stop or reverse the payment?
Yes -> Consider pacs.007 instead.
No -> Review scheme exception handling before you choose a message.

Compare pacs.004 vs pacs.007

Comparison of pacs.004.001.11 and pacs.007
Dimension	pacs.004.001.11	Comparison message
Primary purpose	Return settled funds	Reverse a previously instructed payment
Initiated by	Receiving / beneficiary side	Original instructing side
Direction of flow	Back through the chain	Forward through the chain
Best fit	Post-settlement return handling	Recall, error, or fraud-driven reversal handling

Implementation FAQ

What is the difference between pacs.004 and pacs.007?

pacs.004 returns settled funds from the receiving side, while pacs.007 requests reversal from the original instructing side.

Should every failed beneficiary credit become pacs.004?

Not automatically. The right path depends on scheme rules, settlement stage, and counterparty handling.

Primary references

Related messages

Message type	Description	Overview
`pacs.008.001.13`	FI to FI Customer Credit Transfer	The pacs.008 message is the main customer credit-transfer instruction between banks. It carries party, amount, and remittance data.
`pacs.003.001.09`	FI to FI Customer Direct Debit	The pacs.003 message carries a customer direct debit between banks. It lets the creditor bank collect funds from the debtor bank.
`pacs.002.001.12`	FI to FI Payment Status Report	The pacs.002 message reports the status of an earlier payment instruction. It tells another institution whether the payment was accepted, rejected, pending, or settled.