ABA Files Made Simple: How to Pay Australian Suppliers in Bulk Without Touching Your Bank

If you run a business in Australia, you have probably had this Friday afternoon: thirty supplier invoices are sitting in your accounting software, all approved, all due next week. Now you have to pay them. The fast way is to generate a batch payment file (an ABA file) and upload it to your business banking portal in one click. The slow way is to type in BSB and account numbers one by one into your bank's online interface, hoping nobody made a typo when they sent you their details.

ABA files exist precisely because the slow way does not scale. The Australian Bankers' Association format, also referred to as CEMTEX in some banking portals, lets you bundle dozens or hundreds of payments into a single text file, upload it once, and pay every supplier at the same time. Every major Australian bank (NAB, ANZ, CBA, Westpac, Bendigo, Bank Australia, BCU, Macquarie, and the rest) accepts ABA files, and most business accounts have batch payment functionality built in.

The catch is that getting from "my invoices are captured" to "my ABA file is ready" usually involves two or three pieces of software talking to each other. Today we are making that part disappear. ABA file generation is now live in Gennai for Australian users. If your invoices are flowing through Gennai (from Gmail, Outlook, WhatsApp, or upload), you can now select which ones you want to pay and generate a compliant ABA file directly. No exporting to Xero first, no third-party intermediary, no spreadsheet.

This post explains what ABA files are, why Australian businesses use them, and how the new functionality in Gennai fits into the typical AP workflow.

What is an ABA file (and why does Australia use one when most countries do not)

An ABA file is a plain text file with a very specific structure that Australian banks understand. It contains three sections: a header record (who is making the payments and from which account), a series of detail records (one line per payment, with BSB, account number, name, amount, and reference), and a trailer record with totals and a checksum.

The format is governed by the APCA Direct Entry standard (Australian Payments Clearing Association), which is the same standard that underpins direct debits and direct credits across the Australian banking system. Every business bank account that supports batch payments accepts ABA files, and most banks offer a built-in validator so you can check the file before processing.

Why does Australia have its own format when many other countries use SEPA or ACH? The short version is historical: ABA was standardised long before international interbank standards converged, and once a format becomes the default for thousands of banks and accounting tools, switching costs are enormous. The result is that Australian SMEs have an unusually clean batch payment infrastructure compared to many other markets, but it lives behind a file format that nobody outside Australia uses.

For a business owner, the practical effect is simple: if you want to pay 30 suppliers at once on a Friday, you need an ABA file. There is no real alternative. Some banks let you enter payments one by one through their online interface, but that is the slow path. Some accounting platforms also support PayTo or NPP integrations for faster payments, but ABA remains the standard for routine batch processing across the SME segment.

The typical Australian AP workflow (and where it gets stuck)

Most Australian small businesses follow a similar routine. It looks something like this:

Step 1: Invoices arrive throughout the month, mostly by email, sometimes as paper, sometimes through supplier portals.

Step 2: Someone (you, your bookkeeper, your AP clerk) captures them into your accounting platform. Xero, MYOB, QuickBooks. The invoices get OCR-scanned, coded to the correct account, and approved.

Step 3: At some point in the cycle (weekly, fortnightly, monthly), you decide which bills are ready to be paid. You select them in the accounting platform.

Step 4: You generate an ABA file from the accounting platform. Xero calls this "create a batch payment". MYOB calls it "prepare electronic payments". The file ends up in your downloads folder.

Step 5: You log into your business banking portal, find the batch payments section, upload the ABA file, validate it, approve it, and submit.

Step 6: Money goes out, suppliers get paid, you reconcile the transactions when they appear on your bank statement.

On paper this looks fine. In practice, the friction sits in Steps 2 and 4. Step 2 takes time because invoices have to be physically captured into the accounting platform before they can be paid, even if you already know the supplier and the amount. Step 4 only works smoothly when the invoices in the accounting platform have correct supplier banking details (BSB, account number, account name). If a new supplier's banking details have not been entered yet, the ABA generation fails or excludes that line.

What we have heard repeatedly from Gennai users in Australia is the same pattern: capture the invoice in Gennai, then re-enter or manually export to Xero or MYOB just to generate the ABA file, then upload to the bank. The capture-to-payment journey crosses three tools when it really only needs one.

What we just shipped: ABA file generation inside Gennai

The new functionality is straightforward. If you are an Australian Gennai user, you can now generate ABA files directly from your captured invoices without going through your accounting platform first. Here is how it works in practice.

Configure your business bank details once. In Gennai's settings, you enter your APCA User ID (your DE User ID, assigned by your bank), your bank account BSB and account number, and your registered business name. This is the data that appears in the ABA file header and tells the bank where the payments are coming from. You set this up once and it applies to all future ABA files.

Add supplier banking details as they come in. When an invoice arrives from a supplier you have not paid before, Gennai flags it for banking detail entry. You add their BSB, account number, and account name once. From that point on, every future invoice from the same supplier is automatically eligible for batch payment. If a supplier sends their banking details in the body of the invoice (which is increasingly common in Australia), Gennai's extraction picks them up automatically.

Select which invoices to pay. When it is time to run a payment batch, open the dashboard, filter by status "approved and unpaid", and select the invoices you want to include. You can group by due date, by supplier, by amount, or by Xero account if you have that integration active. The selection respects whatever criteria your finance process uses.

Generate the ABA file. One click. Gennai builds the file according to the APCA Direct Entry specification: correct header structure, properly formatted detail records, valid trailer with checksum. The file is downloaded with the standard .aba extension, ready to upload to any Australian bank's batch payment portal.

Upload to your bank and pay. This part is unchanged. You log into NAB Connect, ANZ Internet Banking for Business, CommBiz, Westpac Corporate Online, or whichever portal your bank provides, navigate to batch payments, upload the ABA file, validate, and approve. The same flow you use today.

Once the payments process, Gennai marks the corresponding invoices as paid and (if you have Xero, MYOB, or QuickBooks connected) syncs the payment status back to your accounting platform. The reconciliation that follows is the standard one for batch payments: when the consolidated debit appears on your bank statement, you match it against the batch in your books.

Why doing this in Gennai changes the math

There are already excellent ABA generation features in Xero, MYOB, and QuickBooks. We are not claiming to replace them. What is different about generating ABA files in Gennai is where the data starts.

If your invoices are arriving through email, WhatsApp, Telegram, manual uploads, or supplier portals, they are already in Gennai before they are anywhere else. The capture, the OCR, the categorization, the supplier matching, all of it happens in one place. By the time you are ready to pay a batch of bills, you do not need to push anything anywhere first. The data is already structured, the suppliers are already identified, and the banking details are already attached.

This matters in three specific situations:

For businesses with a high mix of one-off and small suppliers. The longest part of any AP cycle in Australia is dealing with new suppliers (entering their details, verifying their banking info, coding them properly). When capture and payment happen in the same workspace, you do that once and you never re-enter it.

For accountants and bookkeepers managing multiple clients. Switching between Xero or MYOB sessions for ten different clients to generate ten different ABA files is a workday. Generating them all from a single Gennai dashboard, with each client as a separate workspace, is materially faster.

For founders and operators who do not want to live inside an ERP. The accounts payable function does not need to be deep in Xero. It needs to be done. If you can capture invoices, approve them, and pay them all from the same place, you spend less time inside accounting tools and more time on the actual business.

The supporting data on automation impact is consistent across the industry. Xero's own research shows that automation cuts invoice processing time from over 10 days with manual methods to around 3 days with automated systems, a roughly 70% reduction. The pattern in Australia specifically is that ABA generation is one of the steps where time disappears most quickly when invoice capture and payment are unified.

If you are already using Xero alongside Gennai, the auto-categorization functionality we shipped recently for Xero invoices works hand in hand with ABA generation: the post on auto-categorizing Xero invoices covers how supplier coding learns from your history. Combined with ABA file generation, the end-to-end path from invoice arrival to supplier payment becomes almost entirely automatic.

What about NPP, PayTo, and the future of Australian payments

Australia has been gradually rolling out faster payment infrastructure for several years. The New Payments Platform (NPP) supports near-real-time payments, and PayTo allows businesses to authorise direct debits with more flexibility than the old DDR system. Some banks now offer NPP-based batch payments alongside ABA.

ABA is not going anywhere in the short term. The format is too entrenched in business banking and accounting software to be displaced quickly. Most Australian SMEs we talk to use ABA for routine batch payments and use NPP transfers only for individual urgent payments. The two coexist.

Where Gennai sits today is on the ABA side, where the volume is. As Australian banks expand their NPP and PayTo support, we will follow that infrastructure. The architecture of the system is the same regardless of file format: capture upstream, structure the data correctly, hand it off in the format the bank expects. ABA today, NPP-batched payments tomorrow, both running through the same payment selection workflow.

If you are evaluating where this fits in the broader move toward automated AP in Australia, our post on agentic AI in accounts payable covers how capture, coding, and payment are converging into a single workflow rather than three separate ones.

Practical setup checklist for Australian users

If you want to enable ABA generation in your Gennai account today, here are the things to have ready:

Your APCA User ID (also known as the DE User ID). This is a six-digit number assigned by your bank when you registered to make direct credits. If you do not have one, contact your bank's business banking team and ask for direct entry capability on the account. This is a one-time setup with the bank and is generally free for business accounts.

Your business bank account details. BSB, account number, and the account name as registered with the bank. The account name in the ABA file must match what the bank has on record, otherwise the file will be rejected at upload.

Your suppliers' banking details. For each supplier you intend to pay via batch, you need their BSB, account number, and account name. Most Australian invoices include this in the footer. If a supplier has only sent international banking details (SWIFT, IBAN), they cannot be paid via ABA and need to be handled separately.

A clear approval process for which invoices go into a batch. Gennai supports approval workflows so the person generating the ABA file is paying only invoices that have been signed off. For sole operators this is automatic. For teams with finance approvers, set up the approval rules before running your first batch.

Your bank's batch payment portal credentials. The actual upload still happens on your bank's side. NAB Connect, ANZ Transactive, CommBiz, Westpac Corporate Online, or whichever portal you use needs to have batch payment functionality enabled. Ask your bank if you are not sure.

Once these are in place, generating your first ABA file in Gennai takes about as long as selecting the invoices to include. The setup itself is closer to 10 minutes than to a project plan.

A note on security and validation

Anything that touches supplier banking details and payment files deserves a clear answer on security. The relevant points for Gennai users in Australia:

Supplier banking details and your APCA User ID are stored encrypted at rest with AES-256-GCM, the same standard used in Australian online banking. Only authenticated users with the right workspace permissions can view or modify them.

ABA file generation happens server-side in our European infrastructure, which is GDPR-compliant. The generated file is downloaded to your device for upload to your bank. Gennai does not transmit ABA files to any third party.

The actual payment authorisation happens entirely inside your bank's portal, with whatever multi-factor authentication and approval rules your bank applies. Gennai never has access to your business banking login or the ability to authorise payments. The ABA file is data; the payment authorisation is yours.

Files are validated against the APCA Direct Entry specification before download. If something is malformed (a missing BSB digit, an account name that exceeds the character limit, a checksum that does not balance), Gennai surfaces the issue before generation rather than letting the bank reject the file at upload.

Ready when you are

ABA file generation is now available to all Australian Gennai workspaces. If your account is set to AU and you have invoices flowing through, the option will appear in your dashboard the next time you select bills for payment.

For users on Xero, MYOB, or QuickBooks: nothing changes about your current setup. You can continue generating ABA files in your accounting platform if that is what fits your workflow. The new Gennai feature is there for the cases where doing it directly from the captured invoices saves time, particularly for businesses with high invoice volume, multiple entities, or accountants managing several clients.

If you are not yet using Gennai and want to see how this works end to end, you can start a free trial and connect your inbox in a few minutes. The Australian setup includes ABA generation from day one.