Photo by val-suprunovich
AUSTRAC is upgrading its reporting systems to handle ISO 20022 data standards — the same format that SWIFT and major banks are adopting worldwide. For remittance operators submitting International Funds Transfer Instructions (IFTIs), this means new data fields, higher processing capacity, and potentially easier integration with your banking partners. The changes are optional for now, but understanding them today positions you for tomorrow's compliance landscape.
Key Takeaways
- AUSTRAC's REST Program introduces ISO 20022-compatible IFTI-E reporting schemas
- The upgraded system handles larger volumes of reports — critical for growing remittance businesses
- ISO 20022 alignment means your AUSTRAC reports can match your bank's data formats
- Small operators can continue using current reporting methods, but automation opportunities await
- The upgrade connects to the global SWIFT ISO 20022 migration happening through 2025
What Is the REST Program?
The Reporting Entity System Transformation (REST) Program is AUSTRAC's multi-year initiative to modernise how Australian businesses submit regulatory reports. Think of it as AUSTRAC building a new highway alongside the existing road — you can keep using the old route, but the new one offers more lanes and smoother connections.
For remittance operators, the most relevant upgrade is to IFTI-E reporting — the electronic submission of international fund transfer instructions. Every time you send money overseas for a customer, you submit an IFTI report to AUSTRAC within 10 business days. The REST Program doesn't change this obligation, but it changes how you can fulfil it.
The program addresses a growing problem: as Australia's remittance sector expands, some operators are hitting capacity limits in AUSTRAC's legacy systems. If you're processing hundreds or thousands of transactions daily, you've likely experienced slow upload times or system timeouts. The REST upgrade promises to eliminate these bottlenecks.
ISO 20022: The New Language of Global Payments
ISO 20022 isn't just another technical standard — it's becoming the universal language for financial messaging worldwide. By November 2025, SWIFT will complete its migration to ISO 20022 for cross-border payments. Major Australian banks are already using it for their New Payments Platform (NPP) domestic transfers.
For remittance operators, ISO 20022 brings structure to chaos. Instead of free-text fields where "John Smith" might be entered as "J Smith" or "Smith, John", the standard defines specific data elements:
- Structured name fields (given name, family name, middle names)
- Standardised address formats (street, city, state, postal code)
- Purpose of payment codes (salary, family support, property purchase)
- Enhanced remittance information (invoice numbers, reference codes)
This structure matters because it reduces false positives in sanctions screening. When your screening software knows exactly which field contains the beneficiary's surname, it can match more accurately against sanctions lists.
What's Actually Changing in IFTI-E Reporting
The new IFTI-E schema under REST introduces several practical improvements:
Enhanced Data Fields: The schema now accommodates longer and more detailed information. Where the old system might truncate a beneficiary address at 35 characters, the new format handles complete addresses. This reduces the risk of compliance failures due to incomplete data.
Structured Party Information: Instead of cramming customer details into limited fields, you can now properly separate:
- Ordering customer (sender) details
- Beneficiary (receiver) details
- Intermediary financial institution information
- Ultimate creditor/debtor relationships
Purpose Codes: The new schema includes standardised purpose-of-payment codes aligned with international standards. Instead of typing "family support" differently each time, you select code "FAMILY" from a defined list.
Higher Volume Capacity: AUSTRAC hasn't published specific numbers, but the REST infrastructure is designed to handle the growing transaction volumes that were straining the legacy system. For high-volume remitters processing thousands of daily transactions, this means fewer technical failures and faster report acknowledgements.
Practical Implications for Your Remittance Business
For Small Operators (Under 100 Transactions Daily)
If you're manually entering IFTI reports through AUSTRAC Online or using basic remittance software, the REST upgrade won't immediately change your workflow. You can continue using existing reporting methods. However, consider these opportunities:
Improved Data Quality: Even if you stick with manual entry, the new structured fields help ensure you're collecting complete information. When AUSTRAC Online eventually migrates to the new schema, you'll see clearer field labels and validation rules.
Future Software Selection: When evaluating remittance software, ask vendors about ISO 20022 support. [INTERNAL LINK: /guides/choosing-remittance-software] Software that speaks ISO 20022 will integrate more smoothly with banks and AUSTRAC.
For Medium to Large Operators (100+ Transactions Daily)
The REST upgrade offers immediate benefits if you're using automated reporting:
Streamlined Bank Reconciliation: If your correspondent banks provide MT103 or ISO 20022 payment confirmations, you can map these directly to your IFTI reports. The matching data structures eliminate manual reconciliation work.
Enhanced Automation: ISO 20022's structured format makes it easier to automate report generation from your transaction systems. Instead of complex string manipulation to format free-text fields, you populate defined data elements.
Reduced Compliance Risk: Structured data reduces the chance of reporting errors. When purpose codes come from a defined list rather than free text, you eliminate spelling variations that might trigger unnecessary reviews.
Connection to Banking Relationships
The REST Program's ISO 20022 alignment matters for your banking relationships. As Australian banks complete their own ISO 20022 migrations, they'll expect partners to handle structured payment data. Remittance operators who can send and receive ISO 20022 messages will find:
- Faster payment processing
- Fewer queries about payment details
- Better straight-through processing rates
- Potentially lower transaction fees (as banks spend less on manual interventions)
Technical Considerations for Implementation
If you're using remittance software or building custom integrations, here's what to discuss with your technology providers:
API Compatibility: AUSTRAC's REST Program uses modern RESTful APIs (hence the name) rather than legacy file uploads. These APIs support real-time validation and immediate error feedback.
Data Mapping: Your existing customer and transaction data needs mapping to ISO 20022 elements. Start by reviewing:
- How you currently store customer names (single field vs structured)
- Address formats in your database
- Purpose of payment capture methods
Testing Environment: AUSTRAC provides a test environment for the new REST APIs. Your software vendor should use this to validate their integration before you go live.
Backwards Compatibility: The good news — AUSTRAC will maintain legacy reporting channels during the transition. You won't wake up one day to find your current reporting method has stopped working.
What About Sanctions Screening?
ISO 20022's structured data significantly improves sanctions screening accuracy. [INTERNAL LINK: /guides/sanctions-screening-for-remittance] Here's why:
Name Matching: With separate fields for given names, family names, and middle names, screening algorithms can apply appropriate fuzzy matching logic to each component. This reduces both false positives (innocent customers flagged) and false negatives (actual matches missed).
Address Precision: Complete, structured addresses help identify customers more accurately. When screening systems have full address data, they can differentiate between customers with similar names.
Transaction Purpose: Standardised purpose codes help risk-assessment systems. A payment coded as "SALARY" carries different risk than one coded as "CHARITY" or "INVESTMENT".
For operators using third-party screening services, check whether your provider can ingest ISO 20022 formatted data. Most major providers already support it, given the global SWIFT migration.
The Global Context: Why This Matters Now
AUSTRAC's REST Program doesn't exist in isolation. It's part of a global shift in payment standards:
SWIFT Migration: By November 2025, all SWIFT cross-border payment messages must use ISO 20022. Your correspondent banks are already preparing for this change.
Central Bank Initiatives: The Reserve Bank of Australia endorses ISO 20022 for payment system modernisation. Other central banks worldwide are mandating its use.
Regulatory Alignment: Financial intelligence units globally are adopting ISO 20022 for regulatory reporting. This standardisation helps combat money laundering and terrorism financing by improving data sharing between countries.
For Australian remittance operators, especially those with international expansion plans, ISO 20022 capability becomes a competitive advantage. [INTERNAL LINK: /guides/expanding-your-remittance-business-internationally]
What To Do Now
-
Audit Your Current Reporting Process: Document how you currently prepare and submit IFTI reports. Identify manual steps that could benefit from automation.
-
Check Your Software Roadmap: If using remittance software, ask your vendor about their ISO 20022 and REST API timeline. Get this commitment in writing.
-
Review Data Collection: Ensure you're collecting complete customer information that maps to ISO 20022 fields. Update your customer onboarding forms if needed.
-
Plan for Testing: Once AUSTRAC announces REST Program timelines for remittance operators, allocate time for testing new reporting methods before mandatory adoption.
-
Consider Integration Opportunities: If you're planning system upgrades, prioritise solutions that support ISO 20022 throughout the payment chain — from customer onboarding through payment execution and regulatory reporting.
Looking Ahead
The REST Program represents AUSTRAC adapting to modern payment realities. As remittance volumes grow and payment methods diversify, regulatory systems must keep pace. For operators, this modernisation brings both challenges and opportunities.
The challenge lies in adaptation — updating systems, training staff, and managing transition periods. But the opportunities are significant: better automation, improved accuracy, easier banking relationships, and positioning for future growth.
Small operators shouldn't feel pressured to immediately adopt new reporting methods. AUSTRAC understands the sector's diversity and maintains multiple reporting channels. However, understanding these changes helps you make informed decisions about technology investments and business growth.
For established operators processing significant volumes, the REST Program offers a path to operational efficiency. When your regulatory reporting aligns with your payment processing, compliance becomes less of a burden and more of a business enabler.
Stay Informed About Regulatory Changes
Regulatory landscapes shift quickly in the remittance sector. Australia Remittance provides regular updates on AUSTRAC requirements, reporting obligations, and technology developments affecting money transfer operators.
Visit the compliance section for guides on meeting your AML/CTF obligations while growing your remittance business.
Frequently Asked Questions
When must I switch to the new REST reporting system?
AUSTRAC hasn't announced mandatory adoption dates for the REST Program's IFTI-E reporting. Current reporting methods remain valid. Monitor AUSTRAC communications for transition timelines, likely providing 12-18 months notice before mandatory adoption.
Will the REST Program change my IFTI reporting deadlines?
No. You must still submit IFTI reports within 10 business days of the transfer instruction. The REST Program changes how you submit reports, not when you submit them.
Do I need new software to use ISO 20022 reporting?
Not necessarily. If you manually enter reports through AUSTRAC Online, you can continue doing so. For automated reporting, check with your current software vendor about ISO 20022 support. Many vendors are adding this capability as a free upgrade.
How does ISO 20022 affect my correspondent banking relationships?
Positively. Banks increasingly expect partners to handle ISO 20022 payment data. Remittance operators supporting this standard often experience faster payment processing and fewer manual queries from banking partners.