Video by Infi Studio
Swift's ISO 20022 coexistence period ended on 22 November 2025, marking the mandatory switch to MX messaging for cross-border payments. For Australian remittance operators, this isn't just a technical upgrade — it fundamentally changes how you capture, transmit, and report customer data for compliance purposes.
The old MT format that many operators built their systems around is now obsolete for Swift payments. While larger banks and payment providers prepared for this transition years ago, smaller remittance businesses relying on legacy integrations face immediate challenges in adapting to the new data-rich format.
Key Takeaways
- Coexistence ended 22 November 2025 — ISO 20022 is now mandatory for all Swift cross-border payments
- Richer data requirements include structured payer/payee information, purpose codes, and enhanced address fields
- AUSTRAC systems updated to accept ISO 20022 data through the REST Program, improving IFTI reporting quality
- Sanctions screening improves with standardised fields reducing false positives by up to 30%
- Small operators using MT-based integrations must upgrade systems or risk transaction failures
What Changed When Coexistence Ended
For three years, Swift allowed both old MT messages and new ISO 20022 MX messages to coexist on its network. This gave financial institutions time to upgrade their systems while maintaining compatibility. That grace period is now over.
Since 22 November 2025, all Swift cross-border payment messages must use ISO 20022 format. Banks can no longer send or receive MT103 messages for customer payments. Any system still trying to send MT format messages will see transactions rejected at the network level.
The change affects several message types critical to remittance:
| Old MT Format | New MX Format | Purpose |
|---|---|---|
| MT103 | pacs.008 | Customer credit transfers |
| MT202 | pacs.009 | Financial institution transfers |
| MT199 | camt.026 | Unable to apply |
| MT195 | camt.027 | Claim non-receipt |
| MT196 | camt.029 | Resolution of investigation |
Why ISO 20022 Matters for Remittance Compliance
The new format isn't just about technical standards — it dramatically improves the quality and structure of payment data. For remittance operators, this translates into better compliance outcomes and reduced operational friction.
Enhanced Customer Information
MT messages allowed only 35 characters per line for names and addresses, often resulting in truncated or abbreviated information. ISO 20022 expands these fields significantly:
- Name fields: Up to 140 characters (vs 35 in MT)
- Address lines: Structured components for street, city, postcode, country
- Identification: Dedicated fields for passport numbers, tax IDs, dates of birth
- Purpose codes: Standardised codes for payment purpose (family support, education, medical)
This structured data makes it easier to meet AUSTRAC's customer due diligence requirements under the reformed AML/CTF Act.
Improved Sanctions Screening
With properly structured data, sanctions screening systems can match against watchlists more accurately. According to Swift's analysis, financial institutions using ISO 20022 see:
- 30% reduction in false positive alerts
- Faster straight-through processing for legitimate transactions
- Better audit trails with complete customer information preserved
For remittance operators dealing with high volumes of small-value transfers, reducing false positives means less manual review work and faster customer service.
Travel Rule Compliance Built-In
The Travel Rule requirements that took effect in March 2026 align perfectly with ISO 20022's data structure. The format includes dedicated fields for:
- Ordering customer (sender) full details
- Beneficiary customer (receiver) full details
- Intermediary institution information
- Purpose of payment codes
This means your Swift payment messages automatically capture the data needed for Travel Rule compliance, reducing the need for separate information exchanges.
Impact on AUSTRAC Reporting
AUSTRAC updated its systems to accept ISO 20022 data through the REST Program upgrade. For remittance operators, this brings several improvements to IFTI reporting:
Better Data Mapping
The old process of extracting data from MT messages and reformatting it for AUSTRAC reports often led to data quality issues. ISO 20022's structured format maps directly to AUSTRAC's reporting fields:
- Customer names appear in full without truncation
- Addresses include proper postcode and country codes
- Transaction purpose codes align with AUSTRAC's categories
- Reference numbers maintain consistency across systems
Reduced Reporting Errors
With cleaner source data, remittance operators should see fewer AUSTRAC data quality warnings and rejection notices. The structured format eliminates common issues like:
- Mixed-up sender and receiver information
- Incomplete addresses causing validation failures
- Missing or incorrect country codes
- Truncated names triggering manual reviews
Future-Proof Reporting
AUSTRAC has indicated that future reporting enhancements will leverage ISO 20022's capabilities. This includes potential real-time reporting obligations and enhanced data analytics to detect suspicious patterns.
Challenges for Small Remittance Operators
While large banks invested millions in ISO 20022 readiness, smaller remittance businesses face unique challenges:
Legacy System Dependencies
Many remittance operators built their businesses on software that only understands MT format messages. These systems cannot process the new XML-based MX messages without significant upgrades. Common integration points affected include:
- Core banking connections: Systems that receive MT103 confirmations
- Reconciliation tools: Software matching incoming payments to customer orders
- Compliance platforms: Sanctions screening and transaction monitoring systems
- Accounting integrations: Tools that parse payment messages for bookkeeping
Cost of Upgrades
For a small remittance business, the cost of upgrading to ISO 20022 compatibility can be substantial:
| Upgrade Component | Typical Cost Range |
|---|---|
| Software licensing updates | $5,000 - $25,000 |
| System integration work | $10,000 - $50,000 |
| Staff training | $2,000 - $5,000 |
| Compliance system updates | $3,000 - $15,000 |
| Testing and validation | $5,000 - $10,000 |
Partner Bank Requirements
Your correspondent banking partners may impose additional requirements related to ISO 20022 compliance:
- Data quality standards: Banks may reject transactions with incomplete structured data
- Testing requirements: Mandatory testing periods before going live
- Documentation updates: New technical specifications and integration guides
- Cut-off time changes: Different processing windows for MX messages
What Small Operators Should Do Now
If your remittance business hasn't fully transitioned to ISO 20022, immediate action is needed:
1. Audit Your Current Systems
Identify every system that touches Swift payment data:
- Payment initiation platforms
- Compliance and screening tools
- Reconciliation systems
- Reporting interfaces
- Archive and retrieval systems
Determine which systems need upgrades or replacement to handle ISO 20022 messages.
2. Contact Your Software Vendors
Reach out to all technology providers immediately:
- Confirm ISO 20022 compatibility status
- Get upgrade timelines and costs
- Understand data migration requirements
- Request training materials and documentation
If vendors cannot provide ISO 20022 support, start evaluating alternative solutions.
3. Review Banking Partner Communications
Your correspondent banks should have sent multiple notices about ISO 20022 requirements:
- Check for specific data field requirements
- Note any testing deadlines or windows
- Understand contingency procedures for failed messages
- Confirm new cut-off times and processing schedules
4. Update Compliance Procedures
The richer data in ISO 20022 messages requires updates to compliance workflows:
- Revise customer data collection forms to capture all required fields
- Update staff procedures for handling enhanced payment information
- Adjust transaction monitoring rules for new data elements
- Document how ISO 20022 data maps to AUSTRAC reporting fields
5. Test Thoroughly
Before processing live customer transactions:
- Send test messages through all payment corridors
- Verify data appears correctly in all systems
- Confirm sanctions screening works with new format
- Validate AUSTRAC report generation with ISO 20022 data
Connection to Broader Compliance Changes
The ISO 20022 transition doesn't happen in isolation. It connects to several major compliance initiatives affecting Australian remittance:
AUSTRAC's REST Program
AUSTRAC's system modernisation explicitly supports ISO 20022 data formats. The REST API endpoints can accept the richer structured data, improving report quality and reducing manual intervention.
AML/CTF Act Reforms
The comprehensive AML/CTF reforms that took effect in March 2026 emphasise data quality and record-keeping. ISO 20022's structured format helps meet these enhanced obligations by preserving complete customer information throughout the payment chain.
De-Banking Pressures
Banks reviewing remittance relationships often cite poor data quality as a risk factor. Operators fully compliant with ISO 20022 demonstrate sophisticated systems and strong compliance controls, potentially reducing de-banking risk.
Looking Ahead: Beyond Compliance
While the immediate focus is on maintaining Swift connectivity, ISO 20022 adoption brings longer-term benefits:
Operational Efficiency
- Straight-through processing rates increase with clean, structured data
- Customer service improves with complete transaction information readily available
- Reconciliation becomes easier with standardised reference fields
New Service Opportunities
- Purpose codes enable targeted marketing for education or medical remittances
- Enhanced data supports value-added services like payment tracking
- Structured addresses facilitate last-mile delivery partnerships
Competitive Positioning
Operators who master ISO 20022 can differentiate themselves:
- Faster processing times attract time-sensitive customers
- Better data quality reduces payment investigations
- Compliance strength helps secure and maintain banking relationships
Key Dates and Deadlines
| Date | Milestone |
|---|---|
| 22 Nov 2025 | ISO 20022 coexistence period ended — MX format mandatory |
| 31 Mar 2026 | Full AML/CTF Act reforms effective |
| 30 May 2026 | Compliance officer notification deadline |
| Ongoing | AUSTRAC REST Program enhancements |
Frequently Asked Questions
What happens if my system still sends MT format messages?
Swift will reject MT format messages at the network level. Your transactions will fail to process, and customers won't receive their funds. You must upgrade to ISO 20022 compatible systems immediately.
Do all remittance payments need ISO 20022 format?
Only Swift payments require ISO 20022 format. Other payment networks and corridors may use different standards. However, many are also transitioning to ISO 20022 for consistency.
Can I manually convert MT to MX format?
While technically possible for low volumes, manual conversion is error-prone and unsustainable. The complex XML structure of MX messages requires automated systems for reliable processing.
Will ISO 20022 make compliance more expensive?
Initial upgrade costs are significant, but ongoing compliance should become more efficient. Better data quality reduces manual reviews, false positives, and AUSTRAC queries about incomplete reports.
Take Action on ISO 20022 Compliance
The end of Swift's coexistence period marks a critical moment for Australian remittance. Operators who embrace ISO 20022's capabilities position themselves for growth, while those clinging to legacy systems risk losing Swift connectivity entirely.
For guidance on upgrading your remittance systems and maintaining compliance through this transition, explore our comprehensive guide to starting and operating a remittance business in Australia.