From Treasury Masterminds
ISO 20022 is one of those initiatives that sounds like a banking problem… right up until it quietly lands on the corporate desk. Treasury, finance operations, IT, ERP teams, payments, compliance. Congratulations, you’re all invited.
SWIFT’s ISO 20022 migration replaces legacy MT messages with MX (XML-based) messages. Banks are doing most of the heavy lifting, but corporates still need to pay attention. This change affects payment data quality, reconciliation, investigations, compliance, and yes, costs.
This is a corporate-focused, neutral view. No hype. No fear-mongering. Just what matters.
So what is actually changing?
In very practical terms:
- MT messages
- Legacy format
- Limited structured data
- Heavy use of free text fields
- MX messages (ISO 20022)
- XML-based
- Highly structured
- Much richer data model
MX messages can carry more detail: structured addresses, party roles, identifiers, remittance data. That’s a good thing. Until that rich data gets squeezed back into MT during translation and information gets truncated or lost.
So no, this is not “just a formatting upgrade”. It changes how reliably information travels through the payment chain.
“But we’re a corporate, not a bank”. Why should we care?
Because this affects daily treasury reality more than most people expect.
Payments and rejections
ISO 20022 introduces stricter structure and validation.
- Better data quality
- Less tolerance for sloppy formatting
- Potentially different rejection reasons
If your ERP, TMS, or payment factory relies on creative free text, expect more noise.
Reconciliation and reporting
In theory, ISO 20022 improves reconciliation.
- More structured remittance data
- Better matching possibilities
In practice, many corporates still flatten everything into legacy fields internally. If your systems don’t store the richer data, the benefit disappears before it reaches accounting.
Compliance and investigations
Structured party data supports:
- Better sanction screening
- Clearer investigations
- Faster root-cause analysis
But if messages are translated back to MT somewhere in the chain, key details can still vanish.
The uncomfortable reality: coexistence and translation
We are in the “messy middle” for a while.
During the transition you’ll see combinations like:
- MT sent → converted to MX
- MX received → translated back to MT
- Mixed environments across banks and regions
SWIFT offers translation services to bridge the gap. Helpful, yes. Perfect, no.
Important to understand:
- MT simply cannot carry all MX data
- Translation can cause truncation
- What the bank sees is not always what you store
This matters for investigations, audit trails, and operational confidence.
What this means in daily corporate life
ERP and TMS readiness
Even if you don’t connect directly to SWIFT:
- Can your ERP generate proper pain.001 files?
- Can your TMS ingest ISO 20022 reporting formats like camt.053?
- Are references and remittance data mapped correctly?
“Let the bank handle it” only works up to a point.
Vendor and customer payments
High-volume payment runs amplify small issues.
- Payroll
- Supplier payments
- Intercompany flows
ISO 20022 increases consistency, but reduces flexibility. That’s a trade-off corporates need to manage.
Investigations and exceptions
Expect:
- More structured error messages
- Different investigation paths
- Potential mismatch between MX reality and MT-based internal logs
Runbooks may need updating.
Very important: check your pricing
This deserves its own section because it’s easy to miss.
During the transition, SWIFT applies additional charges for MT to MX conversion and translation services.
Key points corporates should be aware of:
- MT messages converted to ISO 20022 can incur additional costs
- Translation services for payment instructions become chargeable from 1 January 2026
- Charges may apply automatically unless explicitly opted out
- These costs are not always included in fixed or bundled SWIFT pricing
Now the corporate twist:
Most corporates don’t pay SWIFT directly.
Instead, these costs can surface as:
- Higher bank transaction fees
- “Message handling” charges
- Connectivity or service fees
- Project or implementation add-ons
What to do now
Ask your banks and connectivity providers one clear question:
“Are there additional costs during the MT to MX coexistence period, and where do they appear in our pricing?”
If the answer is vague, dig deeper. Silence is not the same as “no cost”.
A simple corporate ISO 20022 checklist
Use this as a sanity check, not a project plan.
Data
- Which flows depend on MT-style free text?
- Where could truncation cause issues?
Systems
- ERP payment format readiness
- TMS reporting ingestion
- Mapping consistency
Banks
- Native ISO 20022 vs translation
- Roadmap and timelines
- What data they actually process end-to-end
Operations
- Validation and rejection handling
- Investigation procedures
- Training for treasury ops teams
Costs
- Conversion and translation charges
- Potential fee increases from 2026
- Where costs show up commercially
Final thought
ISO 20022 is inevitable. For corporates, the real risk is not the standard itself, but drifting through the transition without visibility.
The danger zone looks like this:
- data loss due to translation
- noisier operations
- rising costs that nobody explicitly approved
The smart corporate response is calm and practical:
understand your data flows, align systems, challenge your banks, and keep control over the pricing story.
That’s not transformation theatre. That’s just good treasury.
Also Read
- What does commodity volatility mean for treasurers?
- Treasury Trends for 2026: Building Smarter, Faster and More Resilient Treasury Functions
- Treasury Trends for 2026: Building Smarter, Faster and More Resilient Treasury Functions
- Webinar Recap: De-Dollarisation & How Treasurers Can Build the Right Hedging Strategy
- Climate Risk: The Next Frontier in Treasury Strategy
- Webinar Recap: De-Dollarisation & How Treasurers Can Build the Right Hedging Strategy
- De-Dollarisation: Why Treasurers Can’t Ignore the Shift (And How to Build a Hedging Strategy That Survives It)
- The Rise of Alternative Payment Rails: What Treasurers Should Know About Thunes–MoMo and TerraPay Xend
- In-House Banks and Cash Pooling: Why They’re the Hot Treasury Topic of 2025
Join our Treasury Community
Treasury Mastermind is a community of professionals working in treasury management or those interested in learning more about various topics related to treasury management, including cash management, foreign exchange management, and payments. To register and connect with Treasury professionals, click [HERE] or fill out the form below to get more information.