Full details are available in Features by Geography.
If the menu is not visible, this will be for one of two reasons:
- Your user profile has not been provisioned with access; or
- Your organisation has not been provisioned with access.
Your Administrator can confirm if your organisation has been provisioned by viewing the list of available roles in the Role Management screen.
- If the All Entitlements Role is shown, then your Administrator can assign it to you.
- If the All Entitlements Role is not shown, please contact your ANZ Representative for further assistance.
For more information, please also refer to New User FAQs.
- The Payments menu is used to create and manage payments in Australia, China, Hong Kong, India, New Zealand, the Philippines, Singapore, and Vietnam.
- The Asia & Pacific Payments menu is used to create and manage:
- Cash Management payments in Indonesia, Laos, the Pacific Islands, and Taiwan.
- Cross Border Fund Transfer (Import Payments) in India for Trade Finance.
Only users with the Payroll entitlement enabled in their Payments User Permissions can view and process Salary Payments.
- Select the payment in the Current Payments or Past Payments screen, scroll down to the Beneficiary Details section and double click on the beneficiary in the list.
- Users with Payment Reports menu (Hong Kong, India, the Philippines, Singapore, Vietnam): Create and schedule a Payment Detail Report
- Users with Report Centre menu (Australia, China, New Zealand): Create and schedule a Payment Detail Report
The user's daily discretion is determined by the payment's Value Date, not the date the payment was approved.
If multiple roles assign conflicting approval discretion values for a payment type, the lowest value will apply.
Batch and Transaction discretion limits work separately.
This means that even if a user’s batch approval limit is high, they must also stay within their transaction limit for each individual payment.
Example:
- Batch limit: $3 million
- Transaction limit: $1 million
If the user tries to approve a batch containing one transaction of $2 million, the approval will fail because the transaction limit of $1 million is exceeded, even though the batch limit allows $3 million.
If multiple roles assign conflicting approval discretion values for a payment type, the lowest value will apply.
See Processing & cut-off times for more information.
| Payment Type | Payment Purpose | When will the beneficiary receive funds?* |
| Domestic | Everyday regular payments. |
ANZ beneficiaries will receive funds on the same day. Beneficiaries with other major banks will receive funds on the next business day. Beneficiaries with other financial institutions including credit unions may take up to 3 days to receive funds. |
| RTGS/SCP | Urgent or high-value payments. | Same day, generally within 4 hours. |
| Osko | Urgent payments or payments addressed to a Pay ID. | Almost immediately if the beneficiary’s account has Osko by BPAY®. |
- Domestic return of funds: Up to 5 business days.
- International return of funds: Up to 10 business days.
- Recall of funds: Up to 30 business days.
- Web application is displayed in the Time Zone set up in User Settings > Settings & Preferences.
- Mobile application is displayed in the payment time zone. The system determines the cut-off time based on the following attributes: Country payment originated, Payment Type and Payment Currency.
Batch conditions:
- Has a Batch Status other than Draft, Deleted, Approver Rejected, Bank Rejected or Needs Repair
- Requested Value Date is either in the past 6 business days, current date or next 6 business days
- Part of the same customer Division
Has the same batch level details:
- Batch Debtor Account Number
- Batch Name
- Number of Items
- Batch Total Instructed Amount
- Batch Instructed Currency
Payment level details (first item in the batch):
- Creditor Account Number
- Instructed Amount
- Instructed Currency
- Customer Reference
Accounts must be registered and assigned to your user entitlements. To add or remove accounts, please refer to your company Administrator to Update Accounts/Account Groups to your user entitlements.
If you are selecting an account domiciled in Hong Kong, India, the Philippines, Singapore, or Vietnam, you must be logged in with two-factor authentication (2FA) for the accounts to be visible. For more information, please also refer ANZ Managed vs Company Managed Users or New User FAQs.
To ensure a payment is processed successfully, there are several criteria that needs to be met:
- Your debit account is sufficiently funded
- The payment must include all mandatory fields for the payment type
- The payment instructions must be correctly formatted
- If required, the SWIFT instructions are correctly advised and/or formatted
- The payment instructions do not contain any Anti-Money Laundering (AML), Counter Terrorism Financing (CTF) or Sanctions issues
To minimise payment processing delays, payment instructions can be checked against the File Format Guides or use the File Checker (for AU domestic ABA payment files only) to validate your instruction before uploading.
Error message will display as 'Payment rejected due to registration changes’.
The following fields are marked CONFIDENTIAL for all users with access to Singapore payments.
- Beneficiary Bank,
- Beneficiary Details (name),
- Payment Details and,
- Invoice Details
Customers in Hong Kong, India, the Philippines, and Singapore can either perform the Resubmit action manually for payments that fail due to Insufficient Funds or wait for ANZ to process the payment for you. The Insufficient Funds Retry feature applies to all payment types, however please note:
- Payments involving Foreign Exchange (FX) and/or itemised debits will be rejected at the end of the day.
- All other payments will stay in Insufficient Funds status until you Resubmit or ANZ retries them. In this event, the value date updates to the current date, and the transaction is released for further processing.
Different payment types in Australia rely on data from different payment networks:
- Direct Entry (DE) and RTGS payments use BSB information provided by the Australian Payments Network [https://bsb.auspaynet.com.au]
- Osko payments use BSB data from Australian Payments Plus.
It Is important to note that a BSB may be enabled for some payment types but not others. For example, a BSB might be valid for Direct Entry and Osko payments, but not valid for RTGS, or vice versa.
If you receive this error, check whether the BSB supports the payment method you are attempting to use.
You can import SWIFT beneficiaries using Upload Beneficiaries (SWIFT) article.
This instruction is applicable to customers banking Australia, India, Hong Kong, New Zealand, the Philippines, Singapore or Vietnam.
As a standard process and based on your user entitlements, new beneficiaries within a template will automatically be saved to your Beneficiaries screen. Depending on your organisation's set-up, the beneficiaries may need to be approved before using the template to create a payment.
To add a large number of beneficiaries to your Beneficiaries screen, follow the steps below:
| STEPS | DESCRIPTION |
| 1 |
Upload a domestic payment file containing the beneficiaries. Choose one of the following methods:
|
| 2 |
Create a template from the payment. Choose one of the following methods:
|
| 3 | Enter a Template Name and Template Description, then click OK. |
| 4 | Click View this Template. |
| 5 |
Click Submit on the Control Bar to save the beneficiaries to your Beneficiaries screen. RESULT:
|
| 6 | If required, delete the payment created from the upload option, and the template created from the payment. |
ERROR MESSAGE:
"The following beneficiaries could not be automatically added to your Beneficiaries screen as they may already exist. Try adding the beneficiary into your Beneficiaries screen manually via the Beneficiaries menu feature."
REASONS:
- Beneficiary name in the file will automatically be populated in the My Beneficiary ID field. If there are multiple beneficiary line items with the same name (different account, address, etc.), this can cause an apparent duplication of the My Beneficiary ID. My Beneficiary ID must be unique.
- Beneficiary name and ID might already exist in your Beneficiaries screen.
ACTIONS:
- Remove the duplicated names from the template and create beneficiary manually to your Beneficiaries screen, using a unique Beneficiary ID or
- Edit the existing My Beneficiary ID of the duplicated Beneficiary Name from the Beneficiaries screen and resubmit the template.
When attempting to validate a large payment file, the process can time you out if there are multiple errors identified.
REASONS:
- The application is performing multiple validations when attempting to submit the template and save all the beneficiaries to the Beneficiaries screen
- The application cannot list all errors in the message, therefore timing out the validation process.
ACTIONS:
- Remove all identical beneficiaries from the import file, and load manually into the Beneficiaries screen, using a unique Beneficiary ID
- Validate if any beneficiaries in the file are already existing in the Beneficiaries screen
- Ensure the file is correctly formatted against the File Format Guides
- Reduce the size of the file
To view a sample report and the fields available, please refer to Payment Report Types.
- A Beneficiary Advice is received as a PDF attachment
- If you have downloaded a Beneficiary Advice within ANZ Transactive - Global, the account number will not be masked
For more information, please refer to User Permissions > Cash Management Roles & Permission Settings.
Confirmation of Payee is available for Osko and Direct Entry payments in Australia. It checks the account name, BSB and account number you have entered against the details held by the beneficiary's bank and lets you know whether it is a match.
This can help you make a decision about what to do next, e.g. continue with the payment, check the details again or choose not to proceed with the payment altogether.
- When you make an Osko or Direct Entry payment to a BSB and account number for the first time; or
- Create a new Beneficiary; or
- Amend an existing Beneficiary account details saved in your Beneficiary list.
ANZ Transactive - Global will automatically initiate a Confirmation
of Payee lookup.
Confirmation of Payee will check the account details you
entered
against the details held by the beneficiary's bank and let
you
know whether it’s a ‘match’, ‘close match’ or if the details
do not match at all. This information can help to inform
you
what to do next and gives you more confidence that your payment
is going to the correct account.
We encourage you to be scam aware and always take steps to make sure you know who you are paying, as scams or mistaken payments may not be recoverable.
A No Match result means the account name
entered
does not match the account. No match can also be returned
where the
character limit is exceeded, or middle name/s are not included.
If you have a no match outcome, check the account name, BSB
and account
number with the beneficiary to ensure that the details you
have entered
are correct.
It is recommended you continue to confirm directly with the beneficiary the new or changed bank account details.
The invalid characters can include: ["$%*;<>\^{}=@`] </> Only characters specified in Payment Parameters are allowed.
Pasting content from other sources may cause formatting issues that trigger the error. We recommend free typing to ensure smooth processing.
It is recommended you continue to confirm directly with the beneficiary the new or changed bank account details.
Confirmation of Payee can be completed via the Create and Manage Beneficiaries screens in ANZ Transactive - Global before updating your accounting system.
Dynamic Rate
Available to customers banking in Australia, New Zealand, Singapore and Hong Kong.
A Dynamic rate allows you to obtain real-time foreign
exchange
rates for cross-currency payments. Once the payment has
been
approved by all required approvers, the user can use
the
Get Rate
feature to obtain the dynamic rate.
In Singapore and Hong Kong, you can obtain a dynamic
rate for
less than or equal to USD$500,000. Values above USD$500,000
will
require a Contract rate to be booked.
Dynamic - Auto Trade
Available to customers banking in Singapore and Hong Kong.
A Dynamic - Auto Trade rate allows you to obtain a foreign exchange rate for cross-currency payments. Once the payment has been approved by all required approvers, the Foreign Exchange (FX) rate will be applied to the payment without users needing to perform the Get Rate action.
Transactions above 500k USD (using indicative rate) cannot use Dynamic - Auto Trade.
To apply Dynamic - Auto Trade to a file upload payment, please specify AUTOTRADE as the FX Deal ID in the Contract Reference field.
- If FX Deal ID is blank, the Rate Type will default to Dynamic, and a user will need to perform the Get Rate action.
- If a payment batch includes both transactions with and without a FX Deal ID, the entire batch will be rejected. The exception to this is when itemised debit is used, as a separate batch is created.
Future Dated payments are auto released on the value date with an auto applied FX rate.
Contract Rate
A Contract rate is organised and arranged with your in-country markets dealer. You will be assigned a Contract ID for the booked exchange rate. Upon creating a payment in ANZ Transactive – Global, you can then choose the FX contract to apply to your payment, for the same value date.
Payments to IDR (Indonesian Rupiah) need to use an FX contract to fund the payment.
Bank Book
Available to customers banking in India, the Philippines, and Vietnam.
A Bank Book rate is booked by ANZ on your behalf once validation of the payment and if any supporting documentation provided is successful. Bank Book can be used when:
- you do not have an existing FX contract to readily use or,
- the value of the payment is less than or equal to the equivalent of USD$500,000.
For current day payments, once the payment is approved
and sent
to the bank, the payment will appear in your Current
Payments
grid in a Processing status. After the bank has booked
the contract
rate and all other validations are finalised, the payment
will
move to the Past Payments screen in a Completed status.
For future dated payments, the payment will appear in
your Current
Payments grid until the value of the payment. The status
will
update to Processing, pending the bank to book a contract
rate.
After the bank has booked the contract rate and all other
validations
are finalised, the payment will move to the Past Payments
screen
in a Completed status.
The contract rate details will appear on the debit and credit advices.
Some payments require a contract to be used when paying from or to a particular currency. If the currency requires a contract, the dynamic rate option will not be available to select. In these instances, please contact your local ANZ Markets dealer to book a rate.
Currencies requiring a foreign exchange (FX) contract are listed in the Cross-Currency Payments section of the Processing & cut-off times article.
| GEOGRAPHY | SWIFT CODE |
| Australia | ANZBAU3MXXX |
| China | ANZBCNSH – multiple cities |
| Hong Kong | ANZBHKHXXXX |
| India | ANZBINBXXXX |
| New Zealand | ANZBNZ22XXX |
| Philippines | ANZBPHMXXXX |
| Singapore | ANZBSGSXXXX |
| Vietnam | ANZBVNVXXXX |
For an international payment, the following Beneficiary and Beneficiary Bank details may be required and are subject to the currency(ies) and geographies used in the payment instruction.
-
Beneficiary:
- Full Beneficiary name
- Full address including city/state/country or region (do not use PO Box addresses)
-
Account Number e.g.:
- BSB (Bank, State, Branch) for payments to Australia. Format: six-digit BSB, then account number
- IBAN (International Bank Account Number) for payments to Europe and selected other countries and regions. Format: two-character country code, two check digits, and up to thirty-five alphanumeric characters (no spaces or hyphens).
- RTN (Routing Transfer Number) or ABA routing number for payments to United States of America. Format: nine-digits
-
Beneficiary Bank:
- Full bank name and address
-
Clearing Code, e.g:
- SWIFT/BIC (Bank Identifier Code). Format: 8-11 characters
Amendments to existing payment templates should take no longer than 10 minutes depending on the information to be amended. To amend a payment template, follow the steps below:
- Select Payments from the Menu
- Select Templates from the sub-menu
- Select the required template from template list
- Click Edit on the Control Bar
- Amend required details
- Click Review and Submit
- Review changes and click Submit
For more information, please refer to Manage Payment Templates.
Payments available for full tracking must satisfy all the criteria below:
- Payment initiated and successfully processed by ANZ within the last 30 days.
- Payment must be cross-banks (i.e. not ANZ to ANZ).
- All banks within the payment route must be a SWIFT GPI member bank.
- Payment must be cross-border, Real Time Gross Settlement (AU RTGS) or Same-Day Cleared Payment (NZ SCP).
Note that Multibank payments are excluded.
Payment Tracking is only available after a payment has been processed by ANZ, and in a completed status. If you have recently submitted a payment to ANZ for processing, it might still be waiting for ANZ to process. To check if this is the case:
- Click Payments > Current Payments menu.
- Search or select the international payment you would like to check for payment tracking.
- If the payment is in an "In Progress" status, then it is still pending payment processing within ANZ.
- If the payment is in a "Completed" status, it will be displayed in the Payment Tracking screen.
'In Progress' payments in the Payment Tracking screen can be due to two different reasons:
- The payment is still processing by the intermediary or beneficiary bank, or
- The payment was sent to a non-GPI compliant bank, and ANZ will not receive any further updates from the intermediary or beneficiary banks.
If there is no change to payment tracking status after 3 working days, please contact your relevant ANZ Customer Service Centre for a trace or investigations request.
To use Dynamic-Auto Trade in a file upload, specify AUTOTRADE as the FX Deal ID in the Contract Reference field. Please note:
- If FX Deal ID is blank, the Rate Type will default to Dynamic and a user will need to perform the Get Rate action.
- If a payment batch includes both transactions with and without a FX Deal ID, the entire batch will be rejected. The exception to this is when itemised debit is used, as a separate batch is created.