ISO 20022 Consultant and Migration Help
Practitioner-led ISO 20022 consulting for banks and fintechs. I help teams move from MT to MX, map and validate the new messages, and protect the rich data that makes ISO 20022 worth the effort, without breaking the flows that already work.
What is ISO 20022?
ISO 20022 is the global standard for financial messaging. It replaces terse, fixed-format messages with structured, richly described data, so a payment carries far more context: clean party identification, structured addresses, remittance information, and purpose codes.
For cross-border payments it is the foundation of the SWIFT migration from the legacy MT messages to the MX (pacs, pain, camt) message set. The standard is well defined; the hard part is moving real systems onto it without losing data or stalling flows.
Where ISO 20022 migrations actually get hard
The standard is sound. The friction is in your estate: legacy systems that were built around 35-character fields, party data that was never structured, and downstream processes that quietly depend on the old format.
- Truncation and data loss: rich MX data has nowhere to go when an internal system still assumes MT-era field lengths.
- Coexistence: during the migration window you must handle MT and MX in parallel and translate between them without dropping information.
- Structured party data: names and addresses that were free text for years have to be parsed into structured components.
- Validation: message and network rules are stricter, so weak data that used to pass now fails at the gateway.
How I approach an ISO 20022 engagement
I work end to end: scoping which message types and flows are in play, mapping MT to MX (and back, for coexistence), fixing the data quality problems that surface during mapping, and putting validation in place so messages are clean before they leave your bank.
ISO 20022 sits on top of reference data. Clean BIC, IBAN, and LEI data is what lets you populate structured party fields correctly, so the messaging work and the reference-data work are done together, not in isolation.
Why the rich data is the point
It is tempting to treat ISO 20022 as a format change to survive. The value is the structured data: better sanctions screening with fewer false positives, straight-through reconciliation from structured remittance information, and cleaner Verification of Payee and fraud controls.
A migration that just maps fields and truncates the rest passes the deadline but leaves the upside on the table. The goal is to carry the rich data through your estate, not strip it at the first hop.
November 2026: the structured-address change
From November 2026, the relevant CBPR+ address change removes fully unstructured postal addresses, leaving structured and hybrid models for flows in scope. Customer, beneficiary, and counterparty address data has to be assessed for structured or hybrid PstlAdr use, with validation, exception, and remediation rules defined without forcing uncertain text into precise fields.
The ISO 20022 Address Parser reference build is a public technical preview of a reviewable workflow with field-level confidence bands, reason codes, and strict output validation. Its published evaluation uses held-out data and is not a promise of performance on a client's data.
What an engagement can cover
Consulting work is scoped to a bounded deliverable rather than a generic transformation program. Depending on the flows in scope, an engagement may cover:
- Migration scope and message inventory: payment flows, message types, interfaces, market practices, data owners, operational queues, and cutover dependencies.
- Message and data mapping: source fields mapped to target elements with explicit transformation rules, data-loss warnings, and review points, preserving source values so a reviewer can explain each output.
- Structured address readiness: assessment of address data for structured or hybrid use, plus validation, exception, and remediation rules.
- Reference-data controls: BIC, IBAN, LEI, and related party data validated against the appropriate current sources.
- Testing and readiness evidence: test cases for valid flows, missing data, truncation, duplicates, repairs, rejects, translation boundaries, late changes, cutover, and rollback.
- Operational workflow review: how investigations, repairs, approvals, sanctions review, and reconciliation change when richer messages reach existing operations.
Typical deliverables
A scoped engagement may produce a current-state flow and dependency map, an MT and MX mapping review, an address-readiness assessment, a field and rule catalogue, validation and exception design, a test pack and evidence matrix, a data-loss and truncation analysis, a cutover and rollback checklist, an implementation or vendor review, and owner-ready findings and priorities.
The deliverables depend on the agreed scope. No certification, legal advice, network approval, or production readiness is claimed without the relevant evidence and testing.
Scope boundaries
I can support analysis, design, mapping, data quality, testing, tooling, and implementation review. The regulated institution retains policy, legal interpretation, production approval, release authority, and operational accountability.
No client names, results, or certifications are implied by this page. Public projects are reference implementations unless explicitly stated otherwise.
Frequently Asked Questions
- What is the difference between MT and MX messages?
- MT is the legacy SWIFT message format with terse, fixed-length fields. MX is the XML-based ISO 20022 message set (such as pacs, pain, and camt) that carries structured, far richer data. The migration moves cross-border payments from MT to MX.
- What is coexistence in ISO 20022?
- Coexistence is the migration window during which both MT and MX are in use. Systems must process both formats and translate between them without losing the rich data that only MX can carry.
- Why do ISO 20022 migrations cause data loss?
- Legacy systems were built around short, fixed-length fields. When richer MX data is mapped into them it gets truncated or dropped. Avoiding that means fixing internal data models and party data, not just translating messages.
- How does reference data relate to ISO 20022?
- ISO 20022 needs clean, structured party data to populate its fields correctly. Accurate BIC, IBAN, and LEI data is what lets you fill structured identification and address components, so reference-data quality and the messaging migration are done together.
- What do ISO 20022 migration consulting services cover?
- They can cover scope, message and data mapping, structured address readiness, reference-data quality, validation, testing, operational workflow, cutover, and implementation review.
- Can you help with the November 2026 structured-address change?
- Yes. The work can assess source data, structured and hybrid mapping, validation, exceptions, testing, and remediation priorities for flows in scope.
- Do you provide legal or regulatory certification?
- No. The service provides technical and operational analysis. The institution and its advisers retain legal interpretation, regulatory accountability, and production approval.
- Can you guarantee parser or migration results?
- No. Results depend on source data, systems, scope, and testing. Public project evaluations are evidence about those defined test conditions, not guarantees for another dataset.
- Can the engagement be limited to one deliverable?
- Yes. A scoped mapping review, readiness assessment, test pack, or control design can be delivered without creating an open-ended transformation program.