NetSuite Bank Integration in Australia: A Worked Example

For Australian finance managers who want supplier payments out and bank data back in NetSuite without retyping.

Last reviewed: 13 November 2026. Product details reflect this review date. Availability and behavior can vary by account, role and release.

A NetSuite bank integration in Australia runs in two directions. Supplier payments leave as ABA files built by the Electronic Bank Payments SuiteApp, and bank transactions come back through the Australia Bank Feeds SuiteApp for matching. Set up bank records and the feed link, then review exceptions before reconciling each week.

What does a NetSuite bank integration in Australia cover?

A bank integration is the set of connections that send payment instructions from NetSuite to your bank and bring bank transactions from your bank back into NetSuite. In Australia it has two halves.

Money out. The Electronic Bank Payments SuiteApp builds payment files in ABA format, the file layout Australian banks use for bulk electronic funds transfers. It covers vendor bills and employee expenses. Direct debits from customers use the ABA DD format.

Money in. The Australia Bank Feeds SuiteApp is a free, managed SuiteApp from Oracle. It imports daily transactions from banks domiciled in Australia through SISS Data Services, its data provider.

Matching joins the two halves. NetSuite pairs each imported bank line with a payment or deposit on the Match Bank Data page, and you close the month on Reconcile Account Statement. Our explainer on NetSuite Intelligent Transaction Matching shows how the matching rules work.

A hypothetical Brisbane wholesaler's week

A hypothetical Brisbane wholesaler runs one AUD operating account. It pays suppliers every Thursday, and most customers pay by EFT. It starts the week with A$250,000 in the bank.

The A$66,000 run includes A$6,000 of GST on A$60,000 of purchases. Assume all purchases qualify for credits and valid tax invoices are held. On the accruals basis, this company already claimed the GST from those bills on its business activity statement (BAS). This payment creates no second credit.

On a cash basis, claim to the extent paid, subject to invoice requirements. Confirm timing with your BAS agent.

The rest of this post follows that week through NetSuite, setup first.

How do you set up the company bank record for ABA files?

Install the Electronic Bank Payments SuiteApp, then create a File Cabinet folder for payment files and note its internal ID. Then:

1. Go to Payments > Setup > Bank Details > New. Create company bank records on this page only, not by CSV import or script, because NetSuite validates and sources the fields here.
2. Select the GL Bank Account. NetSuite fills Currency and, in OneWorld, Subsidiary.
3. Enter the Legal Name exactly as your bank holds it.
4. Select ABA as the EFT Template, and ABA DD as the DD Template if you collect direct debits.
5. Enter the folder's internal ID in File Cabinet Location ID and click Save.
6. On the EFT Template Details subtab, enter the Bank Code, the six digit Bank Company ID your bank assigned, both parts of the BSB and the account number.
7. Ask your bank whether it needs a balancing line. Check Insert Balancing Line? only if it does, then save.

For scheduled batches, confirm an active Electronic Bank Payments license, enable Process Bills Automatically and use the Batch Details subtab. Set Batch Details Name, Saved Search and Payment Schedule, then click Add and Save. Schedules can create and submit batches for processing, so configure approval routing before using them.

The wholesaler's bank wants a balancing line. So each Thursday file holds 12 credit lines to suppliers and one debit line of A$66,000 against the operating account.

How do supplier bank details get into NetSuite safely?

Each supplier needs its own bank record before NetSuite can pay it by file. On the vendor record, open the Bank Payment Details subtab, check EFT Bill Payment and save. Then click New Bank Details and enter:

• Payment File Format: ABA.
• Type: primary or secondary account.
• BSB Number (Bank) and BSB Number (Branch).
• Bank Account Number and Bank Account Name.
• Bank Account Payment Description, the text the supplier sees on its statement. Your customer number with that supplier works well.

For the first load, the Import Assistant can bring in bank details for many suppliers by CSV. Our wholesaler loaded 120 active suppliers that way. A second person then compared every BSB and account number with the old system before the first run.

After go live, treat every bank detail change as a control. Confirm the change by phone on a number you already hold, and have someone other than the requester approve it. Our guide to NetSuite vendor bank change approval sets out the approval steps.

What happens in a payment run from bill to bank?

For this example, use manual processing with Process Bills Automatically clear. Check approval preferences with your administrator first. The accounts payable officer then runs Thursday’s payments:

1. Go to Payments > Payment Processing > Bill Payment Processing and select the operating account and A/P Account.
2. Select the 12 bills due this week, A$66,000 in total, and submit.
3. NetSuite creates the bill payments and builds the ABA file. The record opens on the Payment File Administration page, where you can follow its status.
4. The finance manager checks the file total against the approved payment list.
5. The officer uploads the file to the bank's business portal, where a second person authorizes it.

What if the bank rejects a line?

If the bank rejects a line, for example for a closed account, confirm the bank’s final settlement status first. Reverse or roll back only the failed NetSuite payment as appropriate, fix the supplier record and reprocess that bill. Never resend the whole file, because the other 11 suppliers have already been paid. Our post on NetSuite rejected payment files explains a safe resubmission.

Test this run before go live. Treat the first ABA file as a test scenario with a trial upload to your bank, the same way our NetSuite UAT guide for Singapore treats GIRO and FAST files.

How do bank transactions come back into NetSuite?

The Australia Bank Feeds SuiteApp needs the Custom Records, Client SuiteScript and Server SuiteScript features. Enable them at Setup > Company > Setup Tasks > Enable Features on the SuiteCloud subtab. Then:

1. Install Australia Bank Feeds from SuiteApps.
2. Go to Transactions > Bank > Australia Bank Feeds and click Activate next to SISS Data Services.
3. Accept the terms of service and grant consent in the SISS window.
4. Click Connect, name the connection and click Login.
5. On the Bank Accounts subtab, click Update Account Profile and link each bank account to its GL account. Saving the profile starts the import.
6. Check the Bank Import History subtab. A green check mark means the import finished.

Imports run every two hours during a daily import window. Confirm the current window for your account in Oracle help. In a sandbox, the SuiteApp connects only to the SISS sandbox, which holds made up bank data, so prove the setup there and prove real matching in production. If your bank is not on the SISS list, the Auto Bank Statement Import SuiteApp is the fallback.

How does the wholesaler's week match?

After the bank releases Friday’s transactions, the wholesaler imports 40 receipt lines, one debit of A$66,000 and one fee of A$45. Its bank shows the whole ABA run as one line, so the team matches that line to all 12 bill payments at once. Some banks list each payment separately instead. Ask yours, because it changes how you set the matching rules.

If your bank uses its own transaction codes, map them on the Bank Transaction Codes subtab, so each line imports as the right type of credit or debit.

First record and apply customer payments to the invoices. Match the imported receipts to those payment or deposit records using references and amounts. The fee becomes a rule that creates the expense entry each month. Reconcile Account Statement then shows A$302,355 in NetSuite and at the bank.

Choose the setup that fits your business

Plan the first live run as an event. Put the first ABA payment run on your hypercare calendar, with a named owner and your bank's support line ready.

At CuriousRubik, we set up the bank records, supplier details and feeds with your finance team and test the first file with your bank. Our NetSuite finance and payments integration team can take you from setup to a reconciled first month. We work with businesses across Australia, from single entity wholesalers to groups with several subsidiaries.

Related reading

NetSuite Intelligent Transaction Matching for US Teams

How NetSuite matches imported bank lines to transactions, from system rules to your own rules.

NetSuite Vendor Bank Change Approval Controls

How to approve supplier bank detail changes in NetSuite before money moves.

NetSuite Rejected Payment Files and Safe Resubmission

What to do when a bank rejects a payment file, without paying anyone twice.