ANZ Fileactive FAQs – ANZ Digital Services Help

Geography: This article is applicable for ANZ Transactive - Global customers banking in all ANZ geographies.
Full details are available in Features by Geography.

ANZ Fileactive - General FAQs

Learn more about Fileactive, onboarding steps, timelines and pricing basics.

What is ANZ Fileactive?

ANZ Fileactive is ANZ’s integration service for automated file and API message exchange between your systems and ANZ for payments, reporting and workflow management. It supports straight‑through processing (STP), optional hybrid approval workflow via ANZ Transactive – Global, and near real‑time APIs.

Is onboarding different for host-to-host and API

No. The onboarding process is similar for both. ANZ will guide you through the steps based on your chosen connectivity option.

How long does set up take?

Implementation time depends on connectivity, file formats and services in scope. ANZ will provide a detailed project plan outlining timeframes specific to your organisation at the start of any ANZ Fileactive implementation.

How much does ANZ Fileactive cost?

Pricing is tailored to your organisation’s requirements. Contact your ANZ representative for details.

Glossary of Abbreviations

Common abbreviations frequently used when referring to ANZ Fileactive.

ABBREVIATION	DEFINITION
AES	Advanced Encryption Standard is a method of encryption to protect sensitive data.
API	Application Programming Interface is a software intermediary that allows two applications to communicate with each other.
AS2	Applicability Statement 2 is a file transfer protocol that allows businesses to exchange data with their trading partners.
BCP	Business Continuity Planning is a process outlining how a business will continue operating during an unplanned disruption to its service.
CURL	Client Uniform Resource Locator is a command-line tool used to transfer data to and from a server.
ERP	Enterprise Resource Planning is a management software that integrates a business' essential departments.
FTP	File Transfer Protocol is a method of transferring files between computers.
GET	The HTTP method for a customer system to retrieve data in an API message sent back from ANZ Fileactive API.
H2H	Host-to-Host is an automated solution for secure electronic data transfer between banks and their corporate clients.
HTTP	Hypertext Transfer Protocol is an application protocol that allows users to communicate data on the World Wide Web.
HTTPS	Hypertext Transfer Protocol Secured is an extension to HTTP allowing for secure encrypted communications over a computer network.
JSON	Javascript Object Notation is a lightweight format that is used for data interchanging.
MDN	Message Disposition Notification is a receipt document that contains the message ID and status information of the original message.
OAuth	OAuth is an open standard for delegating customer system access to ANZ Fileactive API’s.
PGP	Pretty Good Privacy is a high-security RSA public key encryption application.
POST	The HTTP method for a customer system to send an API message to ANZ Fileactive API.
REST/RESTful	Representational state transfer is a software architectural style created to guide the design and development of the World Wide Web.
SFTP	Secure File Transfer Protocol is a network protocol that provides secure encrypted file access, transfer and management over any reliable data stream.
SMIME	Secure Multipurpose Internet Mail Extensions enable encryption of emails to allow for secure exchange of e-mail and attached documents.
SOAP	Simple Object Access Protocol is a messaging protocol for exchanging structured information in the implementation of web services in computer networks.
SSH	Secure Shell is a network protocol for secure data communication.
SSL	Secure Sockets Layer is a security protocol that provides privacy, authentication, and integrity to Internet communications.
STATUS CODE	HTTP status codes are what the ANZ Fileactive API server sends in the response back to the customer system with regards to the status of the request.
STP	Straight Through Processing is an automated process completed through electronic transfers with no manual intervention involved.
VPN	Virtual Private Network enables online privacy and anonymity by creating a private network from a public internet connection.

ANZ Fileactive - Connectivity FAQs

Learn more about connectivity options and how Fileactive integrates with your systems.

What connectivity options are available?

ANZ Fileactive supports:

Straight Through Processing (STP) for secure file-based host-to-host data exchange
Application Programming Interface (API) messages for near real‑time processing
Hybrid integration with ANZ Transactive – Global

What is Host-to-Host?

Host‑to‑Host enables a direct, secure, automated exchange of files between your ERP or treasury systems and ANZ. It supports large‑volume payments, reporting and reconciliation.

Can one Host-to-Host connection cover multiple accounts or regions?

Yes. You can integrate multiple accounts and entities under one connection, subject to setup requirements.

What is the difference between STP and Hybrid?

STP is fully automated data exchange and processing with no manual intervention required
Hybrid automatically imports payment files from your system into ANZ Transactive – Global where they require approval by an authorised user before processing

What is an API?

Fileactive APIs allow your systems to connect directly with ANZ for near real-time integration. They support:

Payments: Initiate and manage payments including domestic, international, PayTo, and FX transactions. APIs also enable dynamic FX rate retrieval and Confirmation of Payee checks.
Reporting: Access account statements, transaction status updates, and real-time notifications for payment events
Automation: Embed banking functions into ERP or treasury workflows, including automated PayID checks and account management operations.

APIs use secure authentication (OAuth/JWT), comply with ANZ security standards, and are available 24×7 for high-frequency, low-latency messaging.

ANZ Fileactive - Security FAQs

Learn more about encryption, PGP key management and API authentication.

How does ANZ Fileactive keep data secure?

Fileactive uses PGP encryption for file transfers and secure protocols for connectivity. APIs use OAuth and JWT for authentication.

What is a PGP key?

PGP (Pretty Good Privacy) is a public/private key encryption method used to secure data during transfer, generating a keypair and providing a unique signature.

How do I download the current PGP key?

You can download the current public PGP key below. Contact your organisation’s technical support or ERP administrator to update your system with the new key.

ANZ Fileactive PGP Key
The current PGP key is valid until 17 November 2027
Version: SecureBlackbox 20
File Type: .pub
File Size: 2KB

How often are PGP keys updated?

ANZ updates PGP keys periodically. The current key is valid until 17/11/2027. Customers should monitor expiry dates and update keys before they expire.

Can I renew the PGP Key before expiry?

Yes. You can renew and start using the new key before expiry.

For file signing customers, coordinate updates with ANZ to ensure Fileactive is updated at the same time.

What happens if I do not update the PGP Key by the expiry date?

Your files fail decryption and won’t be processed. You also won’t receive any acknowledgement files from ANZ.

What encryption standards does Fileactive use?

Fileactive uses industry-standard encryption such as AES-256 for data at rest and TLS 1.2 or higher for data in transit.

What happens if authentication fails for APIs?

If OAuth or JWT authentication fails, API requests will be rejected. Check token validity and refresh tokens as required.

Is Fileactive compliant with security standards?

Yes. Fileactive aligns with ANZ’s enterprise security policies and industry standards for encryption, authentication, and secure file transfer.

ANZ Fileactive - Implementation & Support FAQs

What is a typical implementation timeline?

Host-to-Host implementation generally takes 4-8 weeks, depending on:

Complexity of integration (number of file types, currencies, and clearing systems)
Security approvals and internal governance processes
Testing scope (positive flows, error handling, reconciliation)
Resource availability on both sides

Early engagement and readiness (e.g., providing IPs, keys, and test files promptly) can significantly shorten timelines.

Is a testing environment available?

Yes. ANZ provides non-production environments for connectivity and functional testing. Availability depends on your integration approach:

SFTP: Dedicated non-prod folders and endpoints
API: Sandbox or test gateway with mTLS setup
SWIFT FileAct: SWIFT test network where applicable

Testing includes:

Connectivity and authentication
File schema validation
End-to-end processing and reconciliation
Error/reject scenarios

What is ANZ Fileactive’s typical service availability?

ANZ Fileactive is generally available 24/7 x 365 with planned maintenance scheduled outside of business hours to minimise disruption. Processing may still be restricted by payment type or currency cut-off times.

Access is on an ‘as is, as available’ basis and may be interrupted for various reasons, including some outside ANZ’s control (such as network outages or third-party issues).

ANZ Fileactive - Payments & Reporting FAQs

How do I determine in ANZ Transactive – Global if a payment was processed through Fileactive (Hybrid)?

You can extract reports from Past Payments in ANZ Transactive - Global for all payment types (excluding Account Transfers). Transaction reports look similar for payments created in ANZ Transactive - Global to those created via Fileactive, but these key differences identify Fileactive payments:

Payment ID prefix will commence with 3, 4 or 5
Input Method shows Host-to-Host
Created by displays SYSTEM

In addition, Fileactive will send status reports back to your ERP system reflecting payment statuses for individual files and transactions.

How do I check if a transaction in a payment batch file has been rejected?

Review the return status file for Host-to-Host payments. It shows the status of each payment in the batch, including any that were rejected along with the rejection reason.

How do I check if a transaction in a payment batch file needs repair?

For Host-to-Host non-Straight Through Processing (NSTP) payments, the return status file indicates the status of each payment, including those that require repair.

How do I check if a transaction in a Direct Debit batch file has been rejected?

For Host-to-Host non-Straight Through Processing (NSTP) Direct Debits, the return status file lists the status of each Direct Debit, including any rejected items and the rejection reason.

How do I check if a transaction in a Direct Debit batch file needs repair?

For Host-to-Host non-Straight Through Processing (NSTP) Direct Debits, the return status file shows the status of each Direct Debit, including those that need repair.

What Host-to-Host reporting is available?

Reporting varies by customer setup, but commonly includes:

Acknowledgements confirming file receipt
Payment status files for individual transactions
End-of-day or intraday account statements in any format, including ISO 20022
Exception and reject reports for failed or repaired transactions
Return and recall reports

ANZ Fileactive - File Formats & Limits FAQs

Which File Formats does ANZ Fileactive support?

ANZ recommends ISO 20022 XML (pain.00x, camt.052,camt.053), as the global standard for data-rich financial messaging.

Alternatively, ANZ Fileactive supports all industry-standard or bespoke file types, including ABA, BAI2, CSV and SAP Multicash.

Excel spreadsheets are not recommended due to formatting variability. ANZ Fileactive supports and recommends text--based formats (e.g. CSV, XML) as a suitable alternative.

What are the file format specifications?

Please refer to the below PDF guides:

What is the maximum batch size that ANZ Fileactive can process?

ANZ Fileactive can process up to 80,000 items per batch, with a file size of 4mb or less. Each physical file or message can contain a maximum of 500 batches.

For detailed specifications, see File Formats - Host-to-Host

Can I upload a payment file containing multiple currencies or payment types?

Yes. Fileactive automatically splits the file into single-currency or single-payment method –batches when processing.

Do NSTP payments support NCC types in ISO format?

Yes. NSTP payments support National Clearing Code (NCC) types in ISO format (5 characters).

Debit Account Country	Payment Method Given Under Local Instrument	Beneficiary NCC Type	Derived NCC Type
AU	Y	CACPA	CC
AU	N	USABA	FW
NZ	Y	INFSC	IN
NZ	N	ZANCC	ZA
CN	Y	GBDSC	SC
CN	N	NZNCC	NZ

How long can payment files be backdated in Fileactive?

Payment files can be backdated based on the payment type:

Direct Entry, Direct Debit: 7 days
International Payments, BPAY, RTGS/SCP, Multibank: 14 days
OSKO: 14 days

What is ISO 20022 and what does it mean for me?

ISO 20022 is a global standard for data-rich XML file format (PAIN.00x, CAMT.052 and CAMT 053) that will become the industry standard for financial messaging.

For more information about the migration to ISO20022, visit ISO20022 - The new global language of payments or contact your ANZ Representative.

Can Confidential Data Group’s (CDG) be applied to payment files processed via Fileactive STP (straight-though processing)?

Currently, this option is not available. However, you can apply CDG to Fileactive NSTP (non-straight through processing) payment files processed via Fileactive or ANZ Transactive - Global's manual and hybrid models.

Can Confidential Data Group’s (CDG) be applied to payment files after processing?

Yes. Please contact the ANZ Customer Service Centre to request this.

We recommend ensuring that your Fileactive NSTP payment files include the CDG status (where applicable) before being sent for processing.