Translation is not modernization.
A four-week diagnostic that turns structured addresses, MT101 exit, exceptions and investigations, and statement retirement into one remediation register through 2028.
4 weeks · Fixed fee quoted after a short scoping call
Who this is for
- Banks, switches and correspondent teams that survived MX cutover with translators
- CIOs and heads of payments who need a fundable phase-two register, not three sponsor decks
- Teams facing 2026–2028 dates on addresses, MT101, exceptions and statements
Treat phase two as one data programme. I produce the register.
Cutover survival deferred the data problem
Many institutions met Swift ISO 20022 cutover by translating. That bought time and deferred whether customer, remittance and reconciliation data can support ISO 20022 without a crutch. Structured-only addresses, MT101 discontinuation, exceptions and investigations messaging, and MT9xx retirement each expose that debt. This diagnostic lists translation debt honestly and attaches a 2026–2028 roadmap a CIO and CFO can fund together.
How phase two becomes one programme
- Data remediationStructured-address and remittance quality treated as owned work, not a Swift side project.
- Operating readinessMT101 exit and exceptions/investigations on ISO 20022 messages — processes, not only formats.
- Remediation registerOne list of translation debt with owners and dates through 2028.
What you leave with
- Structured-address data remediation planOwners and sequencing for records that still fail structured rules
- MT101 exitPath off MT101-shaped behaviour before the date bites
- Exceptions and investigations readinessView against the ISO 20022 message set, not PDF-and-phone habits
- Register of translation debtHonest inventory of hubs and cores still on crutches
- 2026–2028 roadmapSingle funded path a board can recognise
How the four weeks run
- Week 1Lock scope across addresses, MT101, exceptions and statements. Leave with a shared inventory of known translation crutches.
- Weeks 2–3Deepen remediation plans and readiness views. Leave with owners attached to each major debt item.
- Week 4Package the register and 2026–2028 roadmap. Leave with a decision-ready path into a remediation programme with design authority.
Scope fence
This is payments data and operating-model advisory. I am not Swift, your core vendor, or your counsel.
In scope
- Diagnostic and remediation register design
- Structured-address, MT101, exceptions and statement readiness framing
- Translation-debt inventory
- 2026–2028 roadmap for funding
Out of scope
- Writing or filing regulatory submissions
- Core replacement or large-scale build delivery in this engagement
- Vendor sales for translators as a target state
- Open-ended T&M without a named register
If you only staffed the cutover, restaff for phase two. This diagnostic is how that conversation starts.
What I need from you
- A named owner across payments, data, ops and correspondent banking
- Current MX / translator architecture and programme packs — under NDA
- A decision-maker present for the week-4 readout
4 weeks · Fixed fee quoted after a short scoping call