Integration Consultant, Australia

ABA files, BPAY and bank feeds

Payment integrations deserve the most care, because mistakes leave the business immediately. In Australia they usually involve three separate mechanisms:

• ABA batch files. Supplier payment runs are commonly exported from the ERP as an ABA file and uploaded to the bank's business platform. I specify how the batch is built, who approves it, how the bank's response is recorded and how a rejected line returns to the payables ledger without being paid twice.
• BPAY. On the paying side, bills with biller codes and reference numbers need those details held on the supplier record. On the receiving side, a business that issues BPAY references needs incoming payments matched to invoices from the reference rather than from the payer's name.
• Bank feeds and merchant settlements. Feeds bring transactions in for reconciliation, while card terminals and online gateways settle in batches net of fees. I design the split of each settlement into sales, fees and refunds before matching.

Changes to supplier bank account details are one of the most exploited weak points in payables, so the design limits who can make them, requires confirmation through a known contact and records each change for review. Your bank confirms file requirements, and the first live payment run is checked line by line against a parallel run before anyone relies on it. The finance automation page covers the wider process changes that usually accompany this work.

Single Touch Payroll, super and the payroll journal

Payroll in most Australian businesses runs in a dedicated product that handles Single Touch Payroll reporting, and super is usually paid from it or via a clearing service. The ERP does not need to replace any of that. It needs an accurate, timely journal so labor costs, liabilities and accruals appear in the right places. Your payroll provider and accountant own the payroll obligations themselves.

The journal design covers:

• Where costs land. Wages, overtime, allowances and on-costs mapped by entity, department, job or project, so job margins include real labor cost.
• Liabilities. PAYG withholding, super payable and other deductions posted to clearing accounts that reconcile to the payments made.
• Leave. Whether leave accruals come across with each pay run or as a periodic adjustment.
• New pay items. A check that blocks or flags any earnings or deduction code with no mapping, instead of posting it to a suspense account nobody reviews.
• Timesheets. Where hours come from a job app or rostering tool, how they reach payroll and the ERP without being keyed twice.

For businesses with several entities, such as an operating company and a labor hire entity, I specify how intercompany charges follow the payroll journal. The result is tested against a real pay run before go-live, with finance reconciling the totals.

Peppol e-invoicing and the data behind the BAS

Australia has adopted the Peppol framework for e-invoicing, and government agencies and some large buyers encourage or expect suppliers to use it. Its relevance to your business turns on your customer and supplier base, and your advisor can confirm the current position. If it does, Peppol becomes another integration to design rather than a tick box.

The design covers sending, receiving and the exceptions:

• Which access point provider connects the ERP to the network, either built in or as a separate service.
• How customers are addressed, usually by ABN, and how that identifier is kept accurate on customer records.
• The rules for pairing each received e-invoice with its purchase order and goods receipt, and the exception route when they disagree.
• How rejected, duplicate or credit invoices are handled on both sides.

The same exercise is a good moment to trace how GST data reaches the BAS. Online stores, POS systems, job apps and expense tools all create transactions with GST, and each one must carry the right tax code into the ledger. I list every source, check that its codes map consistently and flag any figure that is adjusted by hand before lodgement. Your accountant or BAS agent reviews the findings and decides the treatment. Detailed GST setup in specific products is covered on pages such as Odoo Accounting Australia and Zoho Books Australia.

Online stores, job apps, freight and warehouses

Operational apps generate most of the transaction volume, and they are where integrations most often drift out of step:

• Online stores and marketplaces. Orders, refunds and payouts arrive from Shopify, WooCommerce or Amazon. I decide with you whether orders post individually or as daily summaries, how product codes and bundles map, and how GST-inclusive prices are carried into the ledger correctly.
• Field service and job management. Jobs, labor, materials used on site and completion photos often live in a separate app. The design states which system creates the job, which one holds stock, and how completed work becomes an invoice against the right customer and job.
• Freight. Carrier booking tools need addresses, weights and service choices, and return consignment numbers, tracking and freight costs. Over long distances, freight cost per order matters to margin, so it must land against the sale.
• Third-party warehouses. Released orders and item data go out; dispatch confirmations and stock snapshots come back. A daily stock comparison catches differences before customers do.

For each flow I record the trigger, direction, frequency, mapping, error handling and business owner. That document is what the developer builds from and what the tester tests against, and it is also what a future developer reads before changing anything. Businesses with significant field work may find the ERP for field service page useful context.

Method, responsibilities and life after go-live

Each flow gets its own method decision. A native app connection is often right for a standard pairing, but I test it on your awkward cases, such as a partial refund, a split shipment or a job with variations, before relying on it. Middleware such as Zoho Flow, Make, Zapier or n8n helps when several apps share data and you want one place to watch it. Custom API work suits high volumes or rules no connector handles, at the cost of ongoing maintenance. Scheduled file exchange remains sensible for ABA files and payroll journals. The broader comparison is on my ERP integration page.

Every flow, however built, must validate records before writing them, retry within limits, refuse duplicates and send failures to a named person. Cutover avoids pay days and BAS preparation, with closer monitoring through the first month-end.

Delivery is remote, with working sessions inside Australian business hours and site visits by arrangement only. For the sales side, see my CRM consultant Australia page; for broader advice, the ERP consultant Australia page and the Australia hub. My overall integration method is explained under system integration.