top of page

How to Validate Payee Information in a Payment

Why It Matters

Verifying complete and accurate payee (recipient) information is essential to ensuring payment traceability, as required under FATF Recommendation 16 and Regulation (EU) 2015/847. Payments missing key payee details can violate legal obligations, obstruct sanctions screening, or result in payment rejection by downstream institutions.


What You Need to Validate

Before executing a payment, the following payee information must be included:


  1. Full Name of the payee

  2. Account Number (or a unique transaction identifier if no account exists)


These two elements are required regardless of the payment value or risk level. Unlike payer data, no additional identifiers (e.g. address or document number) are required under standard EU rules—but consistency and accuracy remain critical.


Note: If a simplified regime applies under local legislation, ensure you follow jurisdiction-specific guidance on what data may be omitted.


What if Additional Payee Information Is Provided?

If the payment message includes extra details beyond the required name and account number (such as a payee address or identification number), these must still comply with the requirements of Regulation (EU) 2015/847 and FATF R.16. Even though this information is not mandatory, if it is included, it must be accurate, complete, and capable of supporting sanctions screening and payment traceability. Incorrect or inconsistent additional data can lead to downstream issues, including screening errors or rejection by receiving institutions.

Step-by-Step Validation Process


  1. Check for Required Payee Data Elements

    Verify that the payment message includes the payee’s full legal name and either an account number or another unique identifier. These are mandatory under EU Regulation 2015/847 and FATF Recommendation 16 to ensure traceability of funds. The absence of either field renders the payment non-compliant.

  2. Validate Payee Name & Identifier Quality

    Review the payee’s name to ensure it is complete and not abbreviated. Incomplete names, such as first names only or use of initials, do not satisfy compliance requirements. Confirm that the account number or alternative identifier is structurally correct and specific enough to identify the payee uniquely.

  3. Verify Structural Accuracy & Field Placement

    Ensure that payee information is accurately mapped to the correct fields in the message format being used, such as ISO 20022 or SWIFT MT103. Confirm that the name is placed in the name field, the account number is located in the account field, and that no data has been misrouted into address, notes, or free-text fields.

  4. Detect Placeholder, Inconsistent or Manipulated Data

    Scan for entries that suggest the use of dummy or evasive data. Common indicators include non-specific inputs such as TEST, 12345, or XXX. Also flag truncated names, invalid account structures, or implausible identifiers that may reflect data manipulation or an attempt to bypass controls.

  5. Reconcile Payee Information with Internal Records Where Applicable

    If the payee is a known party (e.g. a customer, part of a recurring payment relationship or internal account transfer), compare the payee information in the payment instruction with existing records. Mismatches in name, account number, or identifiers should be reviewed for potential errors or fraud.

  6. Categorise & Document Validation Issues

    Record any anomalies or deficiencies in payee data. Use clear categories such as Missing Account Number, Invalid Name, Incorrect Field Mapping, or Suspicious Placeholder Entry. Maintaining an accurate log supports monitoring, reporting, and ongoing compliance improvement.

  7. Escalate & Remediate as Required

    Refer any issues involving missing, incomplete, or suspicious payee information to the FCC team or MLRO. Payments with invalid payee data should not be processed until corrected. Recurrent data quality issues may indicate systemic gaps and should trigger review of upstream controls or third-party interfaces.

Red Flags to Watch For

  • Incomplete or abbreviated payee names

  • Incorrect, missing, or generic account numbers

  • Transactions routed through outdated systems that don’t support structured fields

  • Repeated exceptions involving the same beneficiary


When to Escalate

If payee data is missing or appears unreliable:


  • Suspend or reject the payment depending on your institution’s risk policy

  • Query the sending institution or internal team for correction

  • Notify compliance if repeated or high-risk issues arise


Summary

Validating payee information is a simple but non-negotiable requirement under wire transfer regulations. Ensuring that names and account numbers are complete and accurate not only fulfils your legal duty; it ensures payments flow efficiently and reduces reputational and operational risk.

bottom of page