Geography: This article is applicable for ANZ Transactive - Global customers in Australia, China and New Zealand.
Full details are available in Features by Geography.
Full details are available in Features by Geography.
Beneficiary File Template
This functionality is currently only available for SWIFT beneficiaries.
To prepare your SWIFT beneficiary file, follow the below steps.
| STEP | ACTION |
|---|---|
| 1 |
To access the Beneficiary File template: Click Payments > File Import Summary menu, then click Upload File > Upload Beneficiaries from the Control Bar |
| 2 |
Click Download file template.
RESULT: An excel file is downloaded to your computer.
|
| 3 | Open the excel file and save it to your preferred location without changing the file name. |
| 4 | If required, click to Enable Content from the Security Warning banner in the excel |
| 5 |
Click Entry_Sheet tab to add the beneficiary details
|
| 6 |
Click Generate
RESULT: A pop-up window will appear, indicating the generated CSV file is saved to the same location as your downloaded Beneficiary File template. It will overwrite any previous file with the same name.
Your SWIFT beneficiary file is now ready to upload. |
Beneficiary Upload File Format
This functionality is currently only available for SWIFT beneficiaries.
Use this file format to prepare your SWIFT beneficiaries file.
| COLUMN NAME | SWIFT BIC | DOMESTIC ACCOUNT | FORMAT/VALIDATIONS |
| Beneficiary Account Number | Y (Mandatory) | Y (Mandatory) | Alphanumeric (34) |
| IBAN | NA | NA | N/A |
| Beneficiary Name | Y (Mandatory) | Y (Mandatory) | Alphanumeric (35) |
| Beneficiary Name (Local Language) | Y (Optional) | Y (Optional) | Alphanumeric (60) |
| Beneficiary Nick Name | Y (Mandatory) | Y (Mandatory) | Alphanumeric (35), no spaces |
| Beneficiary Address Line 1 | Y (Mandatory) | Y (Optional) | Alphanumeric (35) |
| Beneficiary Address Line 2 | Y (Optional) | Y (Optional) | Alphanumeric (35) |
| Beneficiary Country | Y (Mandatory) | Y (Optional) | Alpha (2) - ISO Country Code |
| Beneficiary City | Y (Mandatory) | Y (Optional) | Alphanumeric (35) |
| Beneficiary Email | Y (Optional) | Y (Optional) |
Email (255) One email address only |
| Account Type | Y (Optional) | N/A |
Alpha (1) Y-Individual Resident Does not apply to AU or NZ country |
| Beneficiary bank country | Y (Mandatory) | Y (Mandatory) | Alpha (2) - ISO Country Code |
| Beneficiary Bank Clearing Code Type | Y (Mandatory) | Y (Mandatory) | 01 - Bene with SWIFT BIC 02 - Bene with NCC |
| NCC type | N/A | N/A | Must be populated if Beneficiary Bank Type is NCC FW - US FEDWIRE (US) SC - UK Domestic Sort Code (UK) AU - Australian Bank Branch Code (BSB) (AU) ZA - South African National Clearing Code (ZA) CC - Canadian Payments Clearing Code (CA) NZ - New Zealand National Clearing Code (NZ) |
| Beneficiary Bank Name (SWIFT) | Y (Optional) | N/A | Alphanumeric (105) |
| Beneficiary Bank Branch Name (SWIFT) | Y (Optional) | N/A | Alphanumeric (70) |
| Beneficiary Bank Address Line1 (SWIFT) | N/A | N/A | Alphanumeric (35) |
| Beneficiary Bank Address Line2 (SWIFT) | N/A | N/A | Alphanumeric (35) |
| Beneficiary Bank Address Line3 (SWIFT) | N/A | N/A | Alphanumeric (35) |
| Beneficiary Bank City (SWIFT) | N/A | N/A | Alphanumeric (35) |
| Beneficiary Bank Code | Y (Mandatory) | N/A | SWIFT: Alphanumeric (11) |
| Beneficiary Bank Name (CNAPS) | Y (Optional) | N/A | Alphanumeric (105) - Multi-lingual (CN Only) |
| Beneficiary Bank Branch Name (CNAPS) | Y (Optional) | N/A | Alphanumeric (70) - Multi-lingual (CN Only) |
| Beneficiary Bank Address Line1 (CNAPS) | Y (Optional) | N/A | Alphanumeric (35) - Multi-lingual (CN Only) |
| Beneficiary Bank Address Line2 (CNAPS) | Y (Optional) | N/A | Alphanumeric (35) - Multi-lingual (CN Only) |
| Beneficiary Bank Address Line3 (CNAPS) | Y (Optional) | N/A | Alphanumeric (35) - Multi-lingual (CN Only) |
| Beneficiary Bank City (CNAPS) | Y (Optional) | N/A | Alphanumeric (35) - Multi-lingual (CN Only) |
| Beneficiary Bank CNAPs code |
Y (Optional) | N/A | Alphanumeric (14) - Multi-lingual (CN Only) |
Beneficiary Upload
This functionality is currently only available for SWIFT beneficiaries.
To upload SWIFT beneficiaries to your Beneficiaries screen, follow the below steps.
| STEP | ACTION |
|---|---|
| 1 |
To access the Beneficiary Upload screen: Click Payments > File Import Summary menu, then click Upload File > Upload Beneficiaries from the Control Bar |
| 2 |
If you are entitled to more than one Division, select the Division. The beneficiaries will appear in the Beneficiaries screen for the selected Division. |
| 3 |
Choose from the following File Encoding options:
|
| 4 |
Click Browse to search and select the CSV beneficiary file to upload
RESULT: The selected file is ready to upload.
|
| 5 |
Click Start Upload
RESULT: The file will be scanned and processed.
If the file does not meet the CSV Beneficiary Upload File Format, you will receive an error message. Update the file and try again.
|
| 6 |
Click Close
RESULT: The imported file will now appear in the File Import Summary screen, indicating the number of successful beneficiaries or those that are rejected or need repair.
Successful SWIFT beneficiaries will appear in the Beneficiaries screen.
|
View uploaded beneficiary file
To view the status of the uploaded SWIFT beneficiary file, follow the below steps.
| STEP | ACTION |
|---|---|
| 1 | Select Payments from the menu, then click File Import Summary |
| 2 |
Select the file from the list
RESULT: The Payment File Summary screen is displayed.
|
| 3 |
If required, review and manage the Rejected Transactions The beneficiary has not been added to your Beneficiaries screen. Please correct the beneficiary information and Create Beneficiary manually or via another Upload Beneficiaries File.
|
| 4 |
If required, click View Current Beneficiaries to review the successful beneficiaries or those that need repair.
|
Upload Beneficiaries FAQs
Can I use my own formatted CSV file to upload beneficiaries to the Beneficiaries screen?
The application only accepts a specific file format. Please use the Download file template from the Upload Beneficiaries screen. For more information, please refer to Beneficiary File Template.
Is the Upload Beneficiaries file the same as the payment file?
No. This functionality is only for SWIFT beneficiaries only and is specific to the file format requirements. For more information, please refer to Beneficiary Upload File Format.
What does the rejection reason 'Creditor Nick Name is invalid' mean?
The Beneficiary Nick Name (column E) includes a space. For more information, please refer to Beneficiary Upload File Format.
What could the rejection reason 'Unknow error' mean when uploading the file?
Check for inconsistencies between your file and the expected file format, including character length; character validation; field validation; file uploaded is CSV; there are no commas included in the excel file before generation, etc.
What does the rejection reason 'Creditor Email is invalid' mean?
The Beneficiary email address contains an invalid character. Click View Current Beneficiaries > select the beneficiary in a Needs Repair status > click Edit and manually add an email address.
What does the rejection reason 'Beneficiary nick name provided is not unique' mean?
If the Beneficiary Nick Name (column E) exists in the Beneficiaries screen or within the same file, please check the beneficiary details for duplication or spelling errors.
What does the rejection reason for 'My Beneficiary ID'?
The Beneficiary Nick Name field is invalid or incomplete.
What does the rejection reason 'Beneficiary bank country should be greater than 0 characters and less than 2 characters' mean?
Use the 2 alpha character ISO Country Code. For more information, please refer to Beneficiary Upload File Format.
What is run-time error 3004 when I click Generate?
If you receive this message when attempting to Generate the file, ensure you do not have a previous version of the CSV file open. Close the CSV and try again.
Can I remove the uploaded files from the File Import Summary screen?
Currently, there is no option to remove, archive or purge the files, as this acts as a record of events.