Skip to content
ISO 20022 Navigator
Donate

ISO 20022 reason code

AM05: Duplication

The payment is a duplicate of one already received. AM05 is an ISO 20022 reason code used as a status reason and a return reason: you will see it in pain.002, pacs.004 and camt.053.

AM05 at a glance
CodeAM05
NameDuplication
ISO code listsExternalStatusReason1Code (status reason); ExternalReturnReason1Code (return reason)
WhereStsRsnInf/Rsn/Cd; RtrRsnInf/Rsn/Cd (pacs.004), TxDtls/RtrInf/Rsn/Cd (camt)

What AM05 means

The receiving bank or the clearing system believes the payment duplicates one it already received: same amount, references and parties.

Not to be confused with: AM05 is a repeat found by its content (amount, parties, references); DU01 to DU05 are repeats of one identifier, and DUPL is the reason a payer gives to recall a payment it sent twice.

A reason code always comes with a status or an action: on its own it says why, not what happened. In a status report look at the status next to it (RJCT means the payment will not be executed); on a statement the returned entry tells you the money has come back.

Where AM05 appears

AM05 belongs to two of the ISO 20022 reason code lists, so it can arrive in these places:

  • Status reason (ExternalStatusReason1Code): in a payment status report (pain.002 from a bank to its customer, pacs.002 between banks) that rejects or holds a payment.
  • Return reason (ExternalReturnReason1Code): in a payment return (pacs.004) after the money has moved, and the returned entry on the account statement (camt.053) or notification (camt.054).

In a status report, AM05 explains a status such as RJCT, at transaction level here (the same StsRsnInf block can sit under the group or a payment block):

pain.002.001.10 · a rejected transaction
<OrgnlPmtInfAndSts>
  <OrgnlPmtInfId>PMT-20261028-03</OrgnlPmtInfId>
  <TxInfAndSts>
    <OrgnlEndToEndId>INV-2026-0042</OrgnlEndToEndId>
    <TxSts>RJCT</TxSts>
    <StsRsnInf>
      <Rsn>
        <Cd>AM05</Cd>
      </Rsn>
      <AddtlInf>Free text from the bank, if any</AddtlInf>
    </StsRsnInf>
  </TxInfAndSts>
</OrgnlPmtInfAndSts>

What to do about AM05

  • If you sent the payment or the collection: Check whether the first payment went through (on the pain.002 or the statement). If it did, there is nothing to do. If the second payment was intended, send it with new references so it is not taken for a copy.

Your bank’s implementation guide and the scheme’s rulebook (for SEPA, the EPC rulebooks) say exactly when it may use AM05; banks do not all apply a code the same way.

Look up AM05 from a script or an AI agent

Scripts and AI agents get this code’s name, definition, where it sits and the address of this page from GET /api/v1/explain, keyless, or from the explain_code tool of the MCP server (API and MCP docs; add it to Claude, Cursor or VS Code).

REST · curl
curl -s 'https://iso20022-navigator.com/api/v1/explain?code=AM05&kind=status_reason'