What does BE01 mean in ISO 20022?

BE01 is Inconsistent With End Customer in the ExternalReturnReason1Code code set: Identification of end customer is not consistent with associated account number, organisation ID or private ID.

What should I do when I get BE01?

Use the account holder's exact legal name as the bank holds it, and confirm the account number at the same time. Fix the data in the payment order and send a new payment with a new reference and a new UETR. A rejected or returned payment cannot be repaired and resent under its old identifiers.

Where does BE01 appear in a message?

For example in pacs.004, element TxInf/RtrRsnInf/Rsn/Cd.

ExternalReturnReason1Code

BE01 Reason Code: Inconsistent With End Customer

Written and maintained by ZagTrader. Last reviewed 21 October 2026. How this page is sourced and checked

BE01 means inconsistent with end customer in the ISO 20022 return reason code set. The name of the beneficiary or debtor does not match the account holder of the account in the payment.

Code: BE01
ISO name: InconsistentWithEndCustomer
Status: Registered
Last updated: 2021-05-01

Official definition

Identification of end customer is not consistent with associated account number, organisation ID or private ID.

Definition from the ISO 20022 External Code Sets, 2Q2026 (published 28 Aug 2026).

What it means in practice

In a pacs.004 payment return, a return reason code explains why funds that were already settled are being sent back. It sits in TxInf/RtrRsnInf/Rsn/Cd, and bank statements (camt.053, camt.054) repeat it in RtrInf/Rsn/Cd.

The name of the beneficiary or debtor does not match the account holder of the account in the payment. Name checks have become stricter with verification of payee services and sanctions screening.

What to do

Use the account holder's exact legal name as the bank holds it, and confirm the account number at the same time.
Fix the data in the payment order and send a new payment with a new reference and a new UETR. A rejected or returned payment cannot be repaired and resent under its old identifiers.

Messages and fields that use ExternalReturnReason1Code

Message	Element path
pacs.004	TxInf/RtrRsnInf/Rsn/Cd, OrgnlGrpInf/RtrRsnInf/Rsn/Cd
camt.053	Stmt/Ntry/NtryDtls/TxDtls/RtrInf/Rsn/Cd
camt.054	Ntfctn/Ntry/NtryDtls/TxDtls/RtrInf/Rsn/Cd
camt.052	Rpt/Ntry/NtryDtls/TxDtls/RtrInf/Rsn/Cd
trck.001	TrckrStsAndTx/Tx/RjctRtrRsn/Rsn/Cd, TrckrStsAndTx/TxSts/RjctRtrRsn/Rsn/Cd
trck.002	TrckrStsAndTx/Tx/RjctRtrRsn/Rsn/Cd, TrckrStsAndTx/TxSts/RjctRtrRsn/Rsn/Cd
trck.004	TrckrStsAndTx/Tx/RjctRtrRsn/Rsn/Cd, TrckrStsAndTx/TxSts/RjctRtrRsn/Rsn/Cd

BE01 in other code sets

BE01 questions

What does BE01 mean in ISO 20022?: BE01 is Inconsistent With End Customer in the ExternalReturnReason1Code code set: Identification of end customer is not consistent with associated account number, organisation ID or private ID.
What should I do when I get BE01?: Use the account holder's exact legal name as the bank holds it, and confirm the account number at the same time. Fix the data in the payment order and send a new payment with a new reference and a new UETR. A rejected or returned payment cannot be repaired and resent under its old identifiers.
Where does BE01 appear in a message?: For example in pacs.004, element TxInf/RtrRsnInf/Rsn/Cd.

All ExternalReturnReason1Code codes · ISO 20022 code sets

The ISO 20022 code names and definitions on this page are reproduced from material published at iso20022.org under the ISO 20022 Intellectual Property Rights policy. This is not the official source: the up-to-date ISO 20022 standards and repository material are published only at iso20022.org. Explanations in our own words are by ZagTrader. ZagTrader is not affiliated with or endorsed by ISO or Swift.