Accounts payable is the most automatable process in finance, and usually the last one anybody gets to. It is not glamorous, it does not affect revenue, and it works well enough that nobody escalates it.
It is also where a surprising amount of controllable time and control risk sits.
Invoice capture. Extracting supplier, date, amount, GST and line detail from a PDF or email. Modern capture handles the majority of standard invoices without templates.
Coding. Suggesting the account, cost centre and tax code based on supplier history. The system proposes; a person confirms until confidence is established.
Matching. Comparing invoice to purchase order and to goods receipt. Two-way and three-way matching flags discrepancies rather than requiring a person to compare documents line by line.
Approval routing. Sending the invoice to the right approver based on value, cost centre and delegation of authority, with escalation when it sits too long.
Payment scheduling. Grouping approved invoices into payment runs by due date, with the file prepared for banking.
Two things international AP tools frequently miss.
ABN validation. If a supplier does not quote an ABN on an invoice for a taxable supply, you are generally required to withhold at the top marginal rate. Validating ABNs at supplier onboarding — and re-validating periodically — avoids discovering this later. It also catches suppliers whose ABN has been cancelled, which happens more often than most teams expect.
Tax invoice compliance. To claim an input tax credit above the low-value threshold, you need a valid tax invoice with the required elements. An automated capture process should flag invoices missing an ABN, missing the words "tax invoice", or with GST that does not compute against the stated amounts.
Both are cheap to check automatically and expensive to remediate at audit.
Automating approval without tightening authority. If your delegation of authority is vague, routing it faster just distributes ambiguity more efficiently. Fix the policy first.
Trusting extraction without a confidence threshold. Capture accuracy is high, not perfect. Coding errors that flow straight to payment are worse than manual entry, because nobody is looking. Set a threshold below which a human reviews.
Removing the second pair of eyes entirely. Payment fraud in Australian businesses is overwhelmingly invoice redirection — a genuine supplier, a changed bank account. A control that requires independent verification of bank detail changes, out of band, is worth keeping manual.
Automating a bad supplier master. Duplicate suppliers, stale bank details and inconsistent names produce automated chaos rather than manual chaos. Clean the master data first.
Invoices arrive, are captured and coded automatically, route to the right approver, and appear in a payment run without anyone retyping anything. Exceptions — unmatched, missing ABN, over threshold, new bank details — surface in a queue that a person genuinely reviews.
The measure is not invoices processed per hour. It is whether your AP function scales without headcount and whether your AP ageing is accurate on any given day rather than only after month-end tidying.
AP configuration is usually one of the faster wins in an implementation, because the process is well understood and the rules are stable. We set up the Australian-specific validations that generic configurations skip.
Get in touch, or see our month-end close checklist for where AP sits in the wider process.