# ISO 20022 is a data project, not an IT project.

A payment operations manager sent me a six-week plan: map MT103 to pacs.008, switch the channel, declare cross-border done. I asked for it to be rewritten as a data plan, with the software line at the end. The decision is not whether to adopt ISO 20022 — CBPR+ coexistence ended in November 2025 — but how much work to finish before a deadline that, since 27 August 2026, has no date. Which fields can you populate, and who owns them?

## What changed

**27 August 2026 — the release moved, the data did not.** Swift postponed the entire November 2026 Standards Release after accepting a deferral of the structured address deadline; no new date was published. The Bank of England postponed its RTGS release to match.

**November 2025 — coexistence ended, for payments.** CBPR+ cross-border payments moved fully to MX, and the deferral does not reopen MT. Trade finance did not move: MT700, MT707, MT734, MT754, MT756 and the MT760 family remain the working messages with no mandatory replacement.

**15 April 2026 — document rules are stable.** The ICC Banking Commission's 2026–2027 action plan does not revise UCP 600 or ISBP 821: five business days to examine (article 14), one refusal notice (article 16).

**18 October 2026 — the map is eight rows.** MT103 to pacs.008, MT202 to pacs.009, MT202 COV to pacs.009 plus underlying data, MT900 and MT910 to camt.054, MT940 and MT950 to camt.053, MT942 to camt.052 or camt.054, MT300 and MT320 to fxtr, and MT700 and MT760 with no mandatory equivalent.

### The field-level gap

- **Address.** `50K` free-format becomes structured `TwnNm`, `CtrySubDvsn` and `Ctry`. A record holding only `AdrLine` must be decomposed — a data-quality judgement, not a mapping rule.
- **Charges.** `71A` OUR, SHA and BEN map to `ChrgBr` DEBT, CRED and SHAR, with SLEV as the service variant. The mapping is trivial; agreeing which applies is not.
- **References.** `:20:` and `:21:` become `EndToEndId` and `InstrId`, and the trace rests on the 36-character `UETR` in block 3 field 121. Regenerate it mid-route and the chain breaks silently.
- **Free text.** `:72:` and `:79:` become `Purp` and `RmtInf`. What was stuffed into `:72:` is now a code from a maintained list, or a string that breaks reconciliation.
- **Structure.** A `pacs.008` is a GroupHeader plus transaction blocks. ISO 20022 itself mandates very few fields; the usage guideline mandates them, so two banks on different guidelines can both claim compliance and still fail each other.

Five failures recur: address piled into `AdrLine`, a duplicated UETR, a charge bearer against the agreement, a purpose code outside the list, and a one-to-one mapping that runs but is not clean.

## The decision framework

Score six criteria before the vendor conversation. The weights reflect a bank already running a payment hub; write yours down and hold them.

| # | Criterion | Weight | What "high" looks like |
|---|---|---|---|
| 1 | Field completeness at source | 20% | Town, subdivision and country captured at origination, not parsed at send |
| 2 | Reference integrity | 15% | One UETR per transaction from initiation, never regenerated, traceable on every hop |
| 3 | Reconciliation ownership | 20% | camt.053 matches the ledger by reference and UETR same day, with a named owner |
| 4 | Code list discipline | 15% | Purpose, charge bearer and reason codes validated at capture |
| 5 | Counterparty readiness | 15% | Tested with real correspondents on real messages, not mock-ups |
| 6 | Change discipline | 15% | A field change is a versioned mapping with tests, not a channel edit |

Criterion 3 carries most weight because nobody assigns it: the hub produces camt.053, the ledger the booking, and the gap is where a programme quietly fails.

## Options and trade-offs

| Option | Strength | Risk | Three-year cost shape |
|---|---|---|---|
| **Translate at the edge** — map in the hub, leave sources alone | Fastest to demonstrate, no core release, contains blast radius | Every new field is another mapping in the same place; weak data returns | Front-loaded integration, then mapping maintenance; small licence change |
| **Fix at source** — structured capture in channel, ERP and core | Removes the cause; one standard serves every message | Multi-team, no visible milestone for months, competes with revenue work | High people cost year one, falling repair cost after |
| **Rebuild the data spine** — canonical party, account and instruction model | Best for reconciliation; makes the next standard cheaper | Longest path, hardest governance, easy to over-scope into a core replacement | Largest year one, lowest marginal cost per change |

Most banks do all three, in the wrong order: fix the fields reconciliation depends on, translate the rest, then argue about the canonical model.

## The numbers

The sources carry no cost figure; I will not invent one. What they quantify is the shape of the work.

- **Five business days** to examine under UCP 600 article 14; **one notice** to raise discrepancies under article 16. Timers that short are set by clean data, not harder work.
- **Eight MT-to-MX rows** make up the conversion map; **ten trade message types** stay on MT. That asymmetry is the biggest planning fact in the programme.
- **Five recurring errors** and **six exception reason codes** — invalid account, closed account, name mismatch, wrong BIC, insufficient funds, plus a sanctions hold — show where operating cost lands after go-live.

My estimate: in a mid-size bank effort concentrates in address and name data, counterparty testing, and repair volume in the first two quarters. Licence is the smallest line. A business case built on licence delta will understate the programme.

## What I would do in 30 / 60 / 90 days

Twelve weeks, independent of the new date.

**Weeks 1–4 — count, do not design.** Run an address census: how many party records can produce town, subdivision and country today. Name one owner per field; two owners means none. Rank last quarter's repair reasons; that is the backlog. List the counterparties that must test with you.

**Weeks 5–8 — fix at source, one field at a time.** Start with account identification, name and end-to-end reference. Put validation in front of the send, not behind the rejection. Write the exception playbook against the reason codes. Run one full round trip with a correspondent on real messages.

**Weeks 9–12 — prove it, then freeze it.** Measure repair and straight-through rates before and after on the same volume. Freeze the mapping under version control with tests. Record the trade finance decision separately. Tell the sponsor what moved, what did not, and what the next Swift announcement triggers.

## What I would not do

- **I would not read the deferral as extra time.** It removed a date, not a work item; address data was already the long pole.
- **I would not buy a new channel to fix a data problem.** A cleaner front end on an unclean core produces the same exceptions faster.
- **I would not run a one-to-one field mapping.** That is how a programme ships a system that passes validation and still cannot reconcile.
- **I would not let the UETR be generated anywhere except at initiation.** Every downstream regeneration is a broken trace found later by operations, not tests.

## For the non-technical sponsor

ISO 20022 is not a software upgrade; it is a change in the quality of the data the bank captures. The deadline moved in August 2026, but addresses, names, references and reconciliation cannot be compressed later. Twelve weeks now is cheaper than a rescue programme after a cutover nobody can date. Approve the data work before the software.

## Sources

- [Swift — ISO 20022 and CBPR+](https://swift.com/standards/iso-20022)
- [Swift — standards and MyStandards](https://swift.com/standards)
- [Bank of England — delay to the November 2026 RTGS standards release (27 August 2026)](https://bankofengland.co.uk)
- [ICC — UCP 600, ISBP 821, URDG 758, URC 522, URR 725](https://library.iccwbo.org)
- [Documentary Credit World — ICC Banking Commission 2026–2027 action plan: no UCP revision (15 April 2026)](https://doccredit.world)
- [TradeFinance.training — ICC releases updated versions of eUCP and eURC (3 July 2023)](https://tradefinance.training)
- [ISO 20022 — message repository and code lists](https://iso20022.org)
- [Swift — gpi and UETR](https://swift.com/our-solutions/swift-gpi)

*Personal views. Client and employer details are anonymised. Figures are third-party estimates, not vendor quotes, and are dated November 2026.*
