Photo by Frolopiaton Palm
Effective 31 March 2026, every business in Australia that transfers money or property must collect, verify, and pass on specific information about the sender and recipient through the entire transfer chain. For remittance operators, this is arguably the most operationally disruptive element of the AML/CTF reforms — and it's live now.
The travel rule isn't a new reporting obligation to AUSTRAC. It's a transparency requirement that mandates information to travel alongside the transaction itself, from the ordering institution through any intermediaries to the beneficiary institution. If you're a remittance operator, this changes how you handle every single transfer.
Here's what the travel rule requires, how it affects your operations, and what you need to do to comply.
Background: From IFTI Reporting to Transaction-Level Transparency
Australian remittance operators are already familiar with International Funds Transfer Instruction (IFTI) reporting — the requirement to report details of international money transfers to AUSTRAC. IFTI reporting has been a cornerstone of Australia's AML/CTF regime since 2008.
The travel rule is fundamentally different. While IFTI reporting is a government reporting obligation (you send data to the regulator), the travel rule is a transparency obligation between institutions. You must share specific originator and beneficiary data with the other institutions in the value transfer chain — your counterparties, correspondents, and intermediary banks or payment providers.
This distinction matters because it introduces new bilateral data-sharing obligations that require operational changes, technology updates, and potentially renegotiated agreements with counterparty institutions.
The travel rule concept isn't new globally — it originates from FATF Recommendation 16 and has been implemented in various forms across major financial centres. But for Australian remittance operators, its introduction through the AML/CTF Amendment Act 2024 and AML/CTF Rules 2025 represents a significant operational shift.
Who Is Affected
The travel rule applies to all businesses that provide value transfer designated services. In the remittance context, this includes:
- Remittance service providers (both independent dealers and affiliates of registered network providers)
- Banks and authorised deposit-taking institutions involved in money transfers
- Payment service providers facilitating transfers of money or property
- Virtual asset service providers (from 1 July 2026 — deferred from the initial 31 March 2026 date)
The rule applies regardless of the amount being transferred. There is no minimum threshold — every value transfer triggers the obligation.
What Information Must Travel With the Transaction
The travel rule specifies different data requirements depending on your role in the transfer chain. The Act creates three distinct institutional roles:
Ordering Institution (the entity accepting the transfer instruction from the payer)
As the ordering institution, you must collect and include the following payer information with the transfer message:
Payer (originator) information:
- Full name
- Account number or unique transaction reference
- One of the following: physical address, date of birth, or national identity number
Payee (beneficiary) information:
- Full name
- Account number or unique transaction reference
This information must be verified — either through your initial customer due diligence (CDD) when onboarding the payer, or specifically for the purposes of the travel rule before passing on the transfer message.
Intermediary Institution (any entity that receives and passes on the transfer between ordering and beneficiary institutions)
Intermediary institutions must:
- Monitor whether the required payer and payee information has been received with the transfer
- Pass on all received information to the next institution in the chain
- Take action if required information is missing — this may include refusing the transaction, requesting the missing information from the previous institution, or filing a suspicious matter report
Beneficiary Institution (the entity making the transferred value available to the payee)
Beneficiary institutions must:
- Monitor whether the required payer and payee information has arrived with the transfer
- Take action if required information is missing — including refusing the transaction or requesting the missing data
- Retain all received information for record-keeping purposes
How This Differs From IFTI Reporting
To understand the operational impact, it helps to compare the travel rule with the existing IFTI reporting regime:
| Aspect | IFTI Reporting | Travel Rule |
|---|---|---|
| Who receives the data | AUSTRAC (the regulator) | Counterparty institutions in the transfer chain |
| Direction of data flow | Vertical (business → regulator) | Horizontal (business → business) |
| When data is shared | After the transfer (reporting) | With the transfer (transparency) |
| Applies to | International transfers only | All value transfers — domestic and international |
| Minimum threshold | Applies to all international transfers | No minimum threshold — all amounts |
The key takeaway: IFTI reporting continues alongside the travel rule. You now have both obligations — report to AUSTRAC and share data with counterparties. The reformed Act also introduces updated International Value Transfer Service (IVTS) reporting requirements to replace IFTI reporting, though transitional rules defer full implementation of the new IVTS format until 2029.
The Operational Impact on Remittance Operators
For many remittance operators, the travel rule will require changes across several operational areas:
Data Collection at Point of Sale
Your customer-facing processes — whether in-branch, online, or via mobile app — must now collect all travel rule data elements before the transfer can proceed. For existing customers already onboarded with full CDD, much of this data should already be on file. For walk-in customers or occasional users, this may require additional identity documentation at the point of transaction.
Transfer Messaging Systems
Your payment messaging infrastructure must be capable of including and transmitting the required originator and beneficiary data fields. If you rely on SWIFT messaging, the relevant MT or MX message formats already accommodate travel rule data. If you use proprietary systems or APIs with correspondent partners, you may need to update message schemas and data field mappings.
Counterparty Agreements
The travel rule creates bilateral obligations. Your correspondent institutions, agent networks, and payment partners must be able to receive, process, and pass on the required data. This may require updating existing service agreements to include travel rule data-sharing provisions and establishing protocols for handling incomplete or missing data.
Screening and Monitoring
The travel rule data — particularly originator and beneficiary names and identification details — must be screened against sanctions lists and other watchlists. If you're not already screening beneficiary details at the point of transaction (many operators only screen the originator), your screening processes will need to expand.
Record Keeping
All travel rule data received and transmitted must be retained as part of your record-keeping obligations. Ensure your systems can store and retrieve this data for compliance reviews, regulatory inspections, and audit purposes.
What Happens When Data Is Missing
The travel rule includes specific provisions for handling incomplete information:
For intermediary institutions: if the required payer or payee information hasn't been received, you must not simply process the transfer and hope for the best. The rules require you to either refuse the transaction, request the missing information from the previous institution in the chain, or take other appropriate action including filing a suspicious matter report.
For beneficiary institutions: similarly, if required information hasn't arrived with the transfer, you must take action. Processing a transfer without the required travel rule data is a compliance breach.
This means remittance operators who are sloppy about data collection will find their transfers rejected or delayed by downstream institutions — creating customer service problems on top of regulatory exposure.
Virtual Asset Transfers: Deferred to 1 July 2026
The travel rule for transfers involving virtual assets — including cryptocurrency — has been deferred to 1 July 2026. This affects virtual asset service providers (VASPs) that are newly regulated under the Tranche 2 reforms.
For remittance operators that don't deal in virtual assets, this deferral is not directly relevant. However, if your business handles any virtual asset transfers or operates across both fiat and crypto corridors, note the separate commencement date and plan accordingly.
What To Do Now: Your Action Plan
Step 1: Map Your Value Transfer Chains
Identify every product and corridor you operate. For each, chart the complete transfer chain: who is the ordering institution, who are the intermediaries, and who is the beneficiary institution? Understanding your role in each chain determines your specific travel rule obligations.
Step 2: Conduct a Data Gap Analysis
Compare the information you currently collect from payers and payees against the travel rule requirements (full name, account number/reference, address or date of birth or national ID). Identify where gaps exist — particularly for beneficiary data, which many operators historically collected in less detail than originator data.
Step 3: Update Your Systems and Processes
Modify your customer-facing forms, digital interfaces, and internal processing systems to capture and transmit all required data fields. Test that your transfer messaging systems can include the required information in the correct format for each counterparty and corridor.
Step 4: Engage Your Counterparties
Contact your correspondent institutions, agent networks, and payment partners to confirm they are ready to receive and pass on travel rule data. Update service agreements where necessary. Establish escalation protocols for handling transfers with missing information.
Step 5: Train Your Team
Front-line staff, compliance officers, and operations teams all need to understand the travel rule — what data must be collected, when it must be passed on, and what to do when information is missing. Run tabletop exercises to test your processes before issues arise in live transactions.
Key Dates
| Date | What Happens |
|---|---|
| 31 March 2026 | Travel rule commences for all fiat value transfers (money and property). |
| 1 July 2026 | Travel rule commences for virtual asset transfers. |
| 2029 | Transitional period ends for new IVTS reporting format (replacing IFTI). |
The Bottom Line
The travel rule fundamentally changes the data obligations for Australian remittance operators. It's no longer sufficient to collect customer data for your own records and report to AUSTRAC — you must now ensure that specific originator and beneficiary information travels with every transfer, visible to every institution in the chain.
For operators with strong existing CDD processes and modern payment infrastructure, the transition should be manageable. For those relying on manual processes, minimal data collection, or legacy systems, this is a significant compliance and operational lift.
The rule is live. Transfers processed without the required information risk rejection by downstream institutions, regulatory scrutiny from AUSTRAC, and ultimately enforcement action. The time to implement is now — not next quarter.
Is your AML/CTF program updated for the travel rule? Build your AML/CTF program free → — includes data collection requirements and transfer chain obligations.