ISO 20022 — Financial Messaging Standard
|
|
| Regulator |
N/A |
| Jurisdiction |
Global |
| Status |
live |
| Applicability |
Platform |
ISO 20022 is the international standard for financial messaging, replacing legacy SWIFT MT formats
and older domestic payment standards. It uses XML-based message structures with structured,
semantically rich fields including structured remittance information, Legal Entity Identifiers (LEI),
and purpose codes. Compliance with ISO 20022 is mandatory for participation in schemes where it
is the designated format — it is not voluntary.
Three scheme mandates directly affect the bank:
- NPP (Australia) — the New Payments Platform is natively ISO 20022 from inception; all
NPP/Osko messages use the ISO 20022 message families (pacs.008, pacs.002, camt.054).
Participation requires ISO 20022 message support.
- SWIFT cross-border payments — SWIFT mandated ISO 20022 (pacs.008 / pacs.009) for all
cross-border payments from November 2025. MT103 and MT202 are being withdrawn. Banks that
cannot originate or process ISO 20022 SWIFT messages cannot participate in cross-border
correspondent banking.
- ESAS (New Zealand) — RBNZ is migrating the Exchange Settlement Account System to ISO 20022.
Banks transacting through ESAS must support the new message formats.
ISO 20022 structured data improves AML/CFT screening quality: richer originator and beneficiary
fields reduce false positives in sanctions screening and improve IFTI/CMIR reporting.
Compliance register
This register maps every material obligation arising from ISO 20022 scheme mandates to the platform
control or institutional process that satisfies it. It is the static traceability layer for the
Totara compliance report — dynamic data (module build status, test evidence, control test dates)
is overlaid at runtime.
Scope legend
| Symbol |
Meaning |
| 🤖 Automated |
Platform enforces or performs the obligation. Primary control mode is GATE, AUTO, CALC, or ALERT. Human action is not required in the normal case. |
| 📊 Evidenced |
Platform captures the evidence trail automatically. Human compliance decision sits on top. Primary control mode is LOG. |
| 🏛 Institutional |
Obligation is met by a process entirely outside the platform — scheme certification, regulatory notification, testing. Platform may generate evidence inputs but does not own the process. |
| N/A |
Obligation does not apply to this deployment configuration. |
Build legend
| Symbol |
Meaning |
| ✅ |
Module built and deployed |
| 🔨 |
Module planned — not yet built (build_status: Not started) |
| ❌ |
Uncontrolled gap — no module attributed |
SWIFT cross-border (mandatory from November 2025)
| Ref |
Obligation |
Scope |
Policy |
Platform controls |
Build |
| SWIFT — pacs.008 |
Originate cross-border customer credit transfers in ISO 20022 pacs.008 format; structured originator and beneficiary data fields populated |
🤖 Automated |
PAY-002, AML-008 |
MOD-026 (AUTO) — originator and beneficiary data populated on every outbound wire; SWIFT/ISO 20022 message enrichment automated |
🔨 |
| SWIFT — pacs.009 |
Originate financial institution credit transfers in ISO 20022 pacs.009 format |
🤖 Automated |
PAY-002 |
MOD-026 (AUTO) — SWIFT message formatting automated; message family selection (pacs.008 / pacs.009) applied from payment type |
🔨 |
| SWIFT — LEI |
Include Legal Entity Identifier (LEI) in cross-border corporate payment messages where required |
🤖 Automated |
PAY-002 |
MOD-026 (AUTO) — LEI population in message header applied from entity profile; missing LEI for required messages is a validation gate failure |
🔨 |
| SWIFT — Message validation |
Validate inbound and outbound ISO 20022 messages against scheme schema before processing or submission |
🤖 Automated |
PAY-002 |
MOD-026 (AUTO) — schema validation applied to every message; malformed messages rejected before entering the payment flow |
🔨 |
| SWIFT — AML enrichment |
Structured ISO 20022 originator/beneficiary data used to improve sanctions screening and IFTI/CMIR reporting |
🤖 Automated |
AML-008 |
MOD-026 (AUTO) — enriched message data feeds IFTI/CMIR pipeline; MOD-013 uses structured beneficiary data for sanctions screening |
🔨 |
| Ref |
Obligation |
Scope |
Policy |
Platform controls |
Build |
| NPP — ISO 20022 messages |
All NPP/Osko payment messages comply with ISO 20022 message specifications required by NPPA; pacs, camt, and pain message families |
🤖 Automated |
PAY-002 |
MOD-120 (where implemented) — NPP/Osko participation requires ISO 20022 message compliance from inception; message formatting and validation integrated into the NPP gateway |
🔨 |
| NPP — PayID resolution |
PayID resolution uses the NPP address look-up service; CoP integration for Osko payments |
🤖 Automated |
PAY-002 |
MOD-120 — PayID resolution integrated in NPP payment initiation; MOD-144 uses PayID for CoP on NPP payments |
🔨 |
ESAS (New Zealand)
| Ref |
Obligation |
Scope |
Policy |
Platform controls |
Build |
| ESAS — ISO 20022 migration |
Support RBNZ ESAS ISO 20022 message format for RTGS settlement; migrate from legacy format on RBNZ's mandated timeline |
🤖 Automated |
PAY-002 |
MOD-026 (AUTO) — SWIFT and ESAS message formatting automated; ESAS ISO 20022 migration implemented as a configuration update to the payment clearing module |
🔨 |
Structured remittance data
| Ref |
Obligation |
Scope |
Policy |
Platform controls |
Build |
| Remittance — Structured fields |
Populate structured remittance information (purpose code, creditor reference) in outbound payments where the scheme requires it |
🤖 Automated |
PAY-002 |
MOD-026 (AUTO) — message enrichment includes structured remittance fields; purpose codes applied from payment instruction type |
🔨 |
Certification and testing
| Ref |
Obligation |
Scope |
Policy |
Platform controls |
Build |
| Scheme certification |
Pass scheme connectivity and message certification tests before going live on each ISO 20022 network (SWIFT, NPP, ESAS) |
🏛 Institutional |
PAY-002 |
Platform provides technically compliant messages; SWIFT and NPPA certification is an institutional testing and approval process |
— |
| Obligation |
Owner |
Platform evidence input |
| SWIFT connectivity and BIC registration |
Head of Payments |
Institutional scheme membership process |
| NPP indirect participation agreement (via sponsor bank if applicable) |
Head of Payments |
Platform provides NPP-compliant messages |
| RBNZ ESAS settlement account and participation agreement |
CFO |
MOD-026 provides the compliant ESAS messages |
| Scheme certification testing with SWIFT / NPPA |
Head of Payments / Technology |
Platform module is the subject of testing; testing programme is institutional |
Coverage summary
| Area |
Total obligations |
Platform automated 🤖 |
Platform evidenced 📊 |
Institutional 🏛 |
N/A |
| SWIFT cross-border |
5 |
5 |
0 |
0 |
0 |
| NPP (Australia) |
2 |
2 |
0 |
0 |
0 |
| ESAS (New Zealand) |
1 |
1 |
0 |
0 |
0 |
| Structured remittance |
1 |
1 |
0 |
0 |
0 |
| Certification and testing |
1 |
0 |
0 |
1 |
0 |
| Total |
10 |
9 (90%) |
0 |
1 (10%) |
0 |
All attributed modules are currently build_status: Not started — the compliance position will
update as modules are built and deployed.
Related pages
Official documentation
Policies referencing this standard
(None yet)
Compiled 2026-05-22 from source/entities/regulations/industry-iso20022.yaml