BE01 Reason Code: Inconsistent With End Customer

Official definition

What it means in practice

In a pacs.002 or pain.002 status report, a status reason code explains why a payment instruction was rejected (RJCT) or why it has another status. It sits in TxInfAndSts/StsRsnInf/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 ExternalStatusReason1Code

And 8 more messages: see the ExternalStatusReason1Code page.

Related reason codes

• BE04Missing Creditor Address
• BE05Unrecognised Initiating Party
• BE06Unknown End Customer
• BE07Missing Debtor Address
• BE08Missing Debtor Name
• BE09Invalid Country
• BE10Invalid Debtor Country
• BE11Invalid Creditor Country

BE01 in other code sets

• BE01 in ExternalReturnReason1Code
• BE01 in ExternalMandateReason1Code

BE01 questions

What does BE01 mean in ISO 20022?

BE01 is Inconsistent With End Customer in the ExternalStatusReason1Code code set: Identification of end customer is not consistent with associated account number. (formerly CreditorConsistency).

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.002, element TxInfAndSts/StsRsnInf/Rsn/Cd.