Party Identification in ISO 20022

A payment message is fundamentally a statement about people and institutions: someone pays someone else, routed through banks. Getting those identities right — unambiguously and in machine-readable form — is essential for routing, sanctions screening, and fraud prevention. ISO 20022 replaces the cramped free-text party fields of older formats with a structured party model. This post explains how party identification works and why it matters.

The cast of parties

ISO 20022 distinguishes the economic parties to a payment from the institutions that move it:

• Debtor and Creditor — the parties whose accounts are ultimately debited and credited; the payer and payee in plain terms.
• DebtorAgent and CreditorAgent — the banks (agents) holding those accounts.
• UltimateDebtor and UltimateCreditor — the parties on whose behalf the payment is really made, when they differ from the account holders. This matters when a payment is initiated by an intermediary or on behalf of a group entity.
• InitiatingParty, InstructingAgent and InstructedAgent — who kicked off the instruction and the banks passing it along the chain.

Separating the economic party from its agent is a deliberate improvement: it makes clear whether "who" refers to the customer or the bank, something legacy formats routinely muddled.

How a party is described

Each party carries a structured set of attributes rather than a blob of text. A typical party can include a Name, a structured PostalAddress (with discrete elements for street, building number, town, post code, and country), and an identification block. The push toward fully structured addresses — replacing free-text address lines — is a significant part of the ISO 20022 migration, because structured fields are far easier to screen and validate.

Identifying agents: the BIC

Financial institutions are identified by the BIC (Business Identifier Code), the 8- or 11-character ISO 9362 code long familiar from SWIFT. In ISO 20022 the agent's identification uses the FinancialInstitutionIdentification structure, where the BIC (as BICFI) sits alongside optional clearing-system member identifiers such as a national sort code or routing number. This lets a message carry both the international identifier and the domestic scheme member ID.

Identifying organisations and people

Non-financial parties use two distinct identification structures:

• OrganisationIdentification for legal entities. The standout element is the LEI (Legal Entity Identifier), a globally unique 20-character ISO 17442 code that pins down exactly which legal entity a party is — no small feat when many companies share similar names. Other coded and proprietary organisation identifiers can also appear.
• PrivateIdentification for individuals, supporting elements such as date and place of birth or other national identifiers, again in a structured, coded form.

The LEI is increasingly emphasised in market-infrastructure ISO 20022 rollouts, because a verifiable entity identifier dramatically reduces the ambiguity that plagues name-only matching.

Why structured identity matters

The payoff of all this structure is concentrated in compliance and operations. Sanctions screening works far better when a name, structured address, country, and LEI arrive in dedicated fields rather than mashed into one line — fewer false positives from misaligned text, and fewer false negatives from hidden data. Fraud and AML monitoring can reason about ultimate parties and originator/beneficiary details, supporting requirements such as the travel rule that both ends of a transfer be identified. And routing benefits from unambiguous agent identification. When party data is truncated or dumped into free text — a real risk during migration — those benefits evaporate, which is why schemes are progressively mandating structured, complete party information rather than treating it as optional.

Common pitfalls in practice

Several mistakes recur when firms first work with the party model. One is mapping everything to Name and leaving the identification and structured-address elements empty, which reproduces the old free-text problem inside a modern message. Another is confusing the agent with the party — populating a bank's details where the customer belongs, or vice versa — which breaks both routing and screening. A third is dropping the ultimate party when a payment is made on behalf of someone else, hiding the party regulators most want to see. Getting the model right means treating each element as meaningful: put the legal entity's LEI in OrganisationIdentification, the customer in Debtor or Creditor, and the bank in the agent fields, every time.

Key takeaways

• ISO 20022 separates economic parties (Debtor/Creditor) from their banks (DebtorAgent/CreditorAgent) and supports ultimate and initiating parties.
• Parties carry structured names and addresses plus an identification block.
• Financial institutions are identified by BIC (BICFI) alongside optional clearing-system member IDs.
• Organisations use the LEI; individuals use PrivateIdentification elements like date and place of birth.
• Structured identity data sharply improves sanctions screening, AML monitoring and routing — provided it is not truncated or free-texted.