IFTI Reporting Requirements for Remittance Operators

International funds transfer instructions (IFTIs) are the backbone of AUSTRAC's transaction monitoring system. As a remittance operator, you must report every international transfer — whether incoming or outgoing — within 10 business days of the transaction date.

Missing IFTI deadlines or submitting incomplete reports can trigger enforcement action from AUSTRAC, with civil penalties reaching AUD 23.1 million per breach. Yet many operators struggle with the technical requirements, particularly around data formatting and the new ISO 20022 standards that became mandatory in March 2025.

Key Takeaways

Report all international transfers (inbound and outbound) within 10 business days
Each unreported IFTI can attract penalties up to AUD 23.1 million
ISO 20022 format is now mandatory for all IFTI submissions since March 2025
Batch reporting via AUSTRAC Online is most efficient for high-volume operators
The Travel Rule requires additional originator data for transfers over AUD 1,000

What Counts as an IFTI for Remittance Operators?

Under the AML/CTF Act 2006, an IFTI is any instruction to transfer money or property between Australia and a foreign country. For remittance operators, this captures virtually every transaction you process.

You must report IFTIs when:

A customer sends money from Australia to any foreign country
You receive an instruction to pay money to someone in Australia from overseas
You transfer funds between your Australian and overseas accounts
You settle with overseas agents or correspondents

Common IFTI scenarios for MTOs:

Customer sends AUD 500 from Sydney to family in Manila
Business pays AUD 25,000 to a supplier in Shanghai
You transfer AUD 100,000 to your nostro account in Mumbai for settlement
Agent in London instructs you to pay AUD 2,000 to a beneficiary in Melbourne

The reporting obligation applies regardless of the transfer amount — there's no minimum threshold. A AUD 50 transfer to Fiji requires the same IFTI report as a AUD 500,000 business payment to the United States.

IFTI Reporting Deadlines and Penalties

AUSTRAC gives you 10 business days from the date of the transaction to submit your IFTI report. This deadline is non-negotiable, and AUSTRAC's systems automatically flag late submissions.

Key deadlines:

Transaction occurs: Day 0
IFTI report due: Day 10 (business days only)
Late submission: Triggers compliance assessment

Penalty framework under section 53 of the AML/CTF Act:

Civil penalty: Up to 5,500 penalty units (currently AUD 23.1 million) per unreported transaction
Criminal penalty: Up to 2 years imprisonment for deliberate non-compliance
Infringement notices: 60 penalty units (currently AUD 252,000) for less serious breaches

AUSTRAC's enforcement approach typically follows an escalation model. First-time breaches might receive a warning letter or remedial direction. Repeated failures or high-volume non-compliance trigger formal enforcement action.

Required Data Fields for IFTI Reports

The mandatory data fields for IFTI reports expanded significantly with the ISO 20022 migration in March 2025. You must now capture and report more detailed information about transaction parties and payment purposes.

Sender Information (Originator)

Full legal name (as shown on ID)
Date of birth
Full residential address (not PO Box)
Occupation or business
Customer identification number
Account or reference number (if applicable)

Beneficiary Information

Full name
Account number or unique reference
Address (if available)
Financial institution details

Transaction Details

Transaction reference number (unique)
Date and time of instruction
Amount in original currency
Amount in AUD (converted)
Exchange rate applied
Fees charged
Purpose of transfer
Payment method (cash, bank transfer, card)

Institution Information

Your AUSTRAC reference number
Branch or agent location
Correspondent bank details (if used)
SWIFT/BIC codes for all institutions in the payment chain

How to Submit IFTI Reports Through AUSTRAC Online

AUSTRAC Online remains the primary channel for IFTI submissions, though the interface now supports the new ISO 20022 format requirements.

Manual Entry (Low Volume)

For operators processing fewer than 50 IFTIs per day, manual entry through the web portal works adequately:

Log into AUSTRAC Online with your reporting entity credentials
Navigate to "Submit Report" > "IFTI"
Select transaction type (E1 for outgoing, E2 for incoming)
Complete all mandatory fields
Review for accuracy
Submit and save the confirmation number

Batch Upload (High Volume)

Operators processing hundreds of daily transactions should use batch reporting:

Export transaction data from your system in ISO 20022 XML format
Validate the file using AUSTRAC's schema validator
Log into AUSTRAC Online
Navigate to "Batch Reporting" > "Upload IFTI File"
Select your validated XML file
Monitor processing status
Download acknowledgment receipts

API Integration (Automated)

Large operators can integrate directly with AUSTRAC's REST API:

Real-time submission as transactions occur
Automatic acknowledgment receipts
Built-in validation before submission
Reduced manual effort and error rates

Common IFTI Reporting Mistakes to Avoid

Based on AUSTRAC's enforcement actions and guidance notes, these errors frequently trigger compliance issues:

Incomplete Sender Verification

Problem: Accepting abbreviations or nicknames instead of full legal names Solution: Match names exactly to government-issued ID Example: Report "Mohammad Abdul Rahman" not "M. Rahman" or "Mo Rahman"

Generic Purpose Codes

Problem: Using "personal transfer" for every transaction Solution: Capture specific purpose: "university tuition fees", "medical expenses for mother", "purchase of electronics inventory"

Missing Correspondent Details

Problem: Only reporting your direct counterparty, not the full payment chain Solution: Include all financial institutions involved, especially intermediary banks

Currency Conversion Errors

Problem: Using outdated exchange rates or calculating AUD amounts incorrectly Solution: Apply the actual rate used for the customer transaction, including your margin

Address Format Issues

Problem: Accepting PO boxes or incomplete addresses Solution: Require full street address with postcode/ZIP code

The Travel Rule and Enhanced IFTI Requirements

Since the Travel Rule came into effect, transfers of AUD 1,000 or more require enhanced originator and beneficiary information that must "travel" with the payment through the entire chain.

Additional Travel Rule requirements:

Originator's account number or unique transaction reference
Originator's address must be verified (not self-declared)
Beneficiary name must be included in the payment message
All data must be passed to the next institution in the chain

Practical impact for MTOs: You can't simply collect this information for AUSTRAC reporting — you must actively transmit it to your correspondent banks and receiving agents. Many legacy systems struggle with these requirements, forcing manual interventions.

ISO 20022 Migration: What Changed for IFTI Reporting

The mandatory switch to ISO 20022 format in March 2025 introduced structured data requirements that affect every IFTI submission.

Key changes:

Purpose of payment now requires specific codes from AUSTRAC's approved list
Address fields are broken into structured components (street, city, state, country, postcode)
Enhanced party identification with Legal Entity Identifiers (LEI) where applicable
Structured remittance information fields for invoice matching

Migration challenges: Many remittance systems still generate MT103 messages internally. You'll need translation middleware to convert these to ISO 20022 format before AUSTRAC submission. Budget AUD 25,000-50,000 for system upgrades if you haven't already migrated.

IFTI Reporting for Different Transaction Types

Cash-Funded Transfers

When customers pay cash for international transfers, you must:

Report the cash receipt as a Significant Cash Transaction (if AUD 10,000 or more)
Submit the IFTI for the international transfer
Link both reports using consistent reference numbers

Bank-Funded Transfers

For transactions funded via bank transfer:

The IFTI clock starts when you receive confirmation of funds
Include the funding bank account details in your IFTI
Report the actual sender, not your bank account

Card-Funded Transfers

Credit and debit card funding adds complexity:

Capture cardholder name (must match sender identity)
Include card BIN (first 6 digits) in payment method field
Be aware that chargebacks don't eliminate IFTI obligations

Building an IFTI Compliance Framework

Successful IFTI compliance requires more than just submitting reports on time. You need systems and processes that ensure accuracy and completeness.

Daily Reconciliation Process

Export all international transactions from your core system
Match against IFTI submission logs
Identify any missing or rejected reports
Resubmit corrections within the 10-day window
Document reasons for any delays

Quality Assurance Checks

Automated validation of mandatory fields before submission
Daily sampling of 5-10% of IFTIs for manual review
Monthly analysis of AUSTRAC rejection reasons
Quarterly testing of disaster recovery procedures

Staff Training Requirements

All customer-facing staff must understand IFTI data requirements
Compliance team needs deep knowledge of reporting obligations
IT staff should monitor API performance and error rates
Regular refreshers when AUSTRAC updates requirements

Managing High-Volume IFTI Reporting

Operators processing thousands of daily transactions face unique challenges in maintaining IFTI compliance.

Volume management strategies:

Automated Data Capture

Integrate identity verification systems directly with your transaction platform:

OCR scanning of identity documents populates IFTI fields
Address verification APIs ensure complete location data
Real-time sanctions screening provides clean data for reporting

Batch Processing Optimisation

Submit IFTIs every 2-3 business days to balance timeliness and efficiency
Use AUSTRAC's off-peak hours (10 PM - 6 AM AEST) for large batches
Implement automatic retry logic for failed submissions
Monitor AUSTRAC's system status page for planned maintenance

Exception Management

Create separate queues for problematic transactions
Assign specialist staff to resolve data quality issues
Maintain a decision log for unusual scenarios
Escalate systematic issues to AUSTRAC liaison team

Record Keeping Requirements for IFTIs

AUSTRAC requires you to maintain comprehensive records of all IFTI reports and supporting documentation for seven years from the transaction date.

Required records include:

Copy of submitted IFTI report
AUSTRAC acknowledgment receipt
Source documents (ID copies, transaction receipts)
System logs showing submission timestamp
Any correspondence with AUSTRAC about the transaction

Storage considerations:

Electronic storage is acceptable if records remain accessible
Implement backup procedures for business continuity
Ensure records are searchable by transaction reference
Protect customer privacy while maintaining accessibility

Frequently Asked Questions

Do I need to report transfers between my own accounts internationally?

Yes, you must report all international funds transfers, including those between accounts you control. These "book transfers" for liquidity management or settlement purposes are still IFTIs under the AML/CTF Act.

What happens if I discover unreported IFTIs from previous months?

Submit the late IFTIs immediately and consider making a voluntary disclosure to AUSTRAC. Proactive disclosure often results in reduced penalties compared to AUSTRAC discovering the breach independently.

Can I correct an IFTI after submission?

You cannot edit submitted IFTIs, but you can submit a corrected report with a reference to the original. Include clear notes explaining the correction reason and maintain documentation of both reports.

How do I handle IFTIs for transactions that ultimately fail or reverse?

Report the initial instruction as an IFTI regardless of ultimate success. If the transaction fails after reporting, maintain records of the reversal but don't submit a "negative" IFTI.

Next Steps for IFTI Compliance

Strong IFTI reporting is just one component of your broader AML/CTF obligations. Consider reviewing these related requirements:

Enhance your AML/CTF program with automated transaction monitoring
Understand the new 2026 AML/CTF reforms affecting IFTI requirements
Review your suspicious matter reporting processes for transactions flagged during IFTI preparation