Your AP Inbox Is Not an Approval Workflow
An accounts payable inbox is not a workflow. It is a waiting room with attachments.
Invoices arrive. Then someone forwards them. A manager replies with “approved”. Meanwhile, finance copies numbers into a spreadsheet, checks supplier details, asks one more question, and hopes the same invoice does not appear again next week. Somehow this passes for process design, because business software has not yet cured human optimism.
In small and mid-sized Australian businesses, AP often becomes painful before anyone notices. The business grows, supplier volume increases, approval rules get more complex, and month-end starts depending on whoever remembers which email thread matters.
The CFO issue in one sentence
If invoice approvals live in email, finance cannot reliably see what has arrived, what has been approved, what has changed, what has been paid, or what still creates risk.
That does not mean the business needs a full ERP replacement tomorrow. However, it does mean the AP process needs proper structure.
What usually goes wrong
- Approvals hide in email threads. As a result, finance can spend more time searching than processing.
- Supplier details change without enough control. Consequently, payment and fraud risk increases.
- Coding becomes inconsistent. As a result, reporting quality drops.
- Managers approve without enough context. For example, they may not see budget, purchase order, contract or prior invoice history.
- Month-end accruals become guesswork. Meanwhile, unprocessed invoices sit outside the reporting view.
- Duplicate handling creeps in. Eventually, one invoice can travel through multiple inboxes before anyone knows the status.
None of these problems look dramatic in isolation. Together, however, they make finance slower, controls weaker and reporting less reliable.
Where eInvoicing fits
eInvoicing helps because it allows businesses to exchange invoice data through software rather than relying on PDFs, paper or email attachments. business.gov.au explains that eInvoices are not PDF invoices that need to be printed, posted or emailed. The ATO also provides guidance for businesses getting started with eInvoicing.
That matters because structured invoice data is easier to validate, route and reconcile. However, eInvoicing does not remove the need for approval rules. It improves the front door. Finance still needs the house behind it to make sense.
A better AP workflow
A practical AP workflow does not need to be over-engineered. In many growing businesses, the first version can be simple: capture the invoice, validate the supplier, check for duplicates, code the expense, route approval, log exceptions, then release payment only after the right controls pass.
Microsoft Power Automate, for example, supports approval workflows across services such as SharePoint, Dynamics 365, Salesforce, OneDrive, Zendesk and WordPress. That does not mean Power Automate is always the answer. Instead, it shows the pattern CFOs should look for: structured requests, human decisions, status tracking and audit history.
The approval rules that matter
In practice, the workflow should reflect commercial risk, not just organisational chart theatre.
- Low-value recurring invoices: automate more, then review by exception.
- For new suppliers: require supplier validation and bank detail checks.
- For high-value invoices: require senior approval and budget context.
- Project or capex invoices: route them to project owners and finance.
- For unmatched invoices: stop payment until the exception is resolved.
- Supplier bank changes: treat them as a control event, not admin trivia.
In practice, CFOs should not design one approval path for every invoice. That is how workflows become either too loose or too painful.
Where AI can help, carefully
AI can help with invoice classification, anomaly detection, document extraction and exception summaries. Also, Australian Government guidance on moving AI from proof of concept to scale highlights the need for clear problem statements, success criteria, data management and testing.
For AP, that means AI should support review rather than approve payments on its own. Use it to highlight odd invoices, suggest coding, summarise supplier history or draft exception notes. However, keep humans in the loop for supplier changes, payment approval and material judgement calls.
A quick AP workflow scorecard
Use this scorecard in a finance meeting. However, if most answers are “no”, the inbox has become the system. Terrifying, but at least diagnosable.
- Can finance see every invoice received this month?
- Do managers see what they are approving and why?
- Can the CFO see approval bottlenecks before payment runs?
- Are supplier bank changes tracked and approved?
- Do duplicate invoices get detected before payment?
- Can finance accrue unapproved invoices at month-end?
- Can AP coding rules support reporting and forecasting?
- Finally, can auditors follow the approval trail without opening someone’s mailbox?
Commercial impact
Better AP workflow design creates value in boring but important ways. However, boring is often where the money hides. Payments become easier to control. Month-end accruals improve. Supplier queries reduce. Managers spend less time hunting invoices. Finance gains cleaner spend data.
More importantly, CFOs get visibility before problems become expensive. That is the real point of automation: not replacing people, but stopping skilled people from babysitting bad process.
When to get help
External help makes sense when AP issues sit across finance, systems and operations. For example, the business may need to connect invoice capture, eInvoicing, supplier master data, approval routing, payment controls and reporting.
Think Numbers can help design and build practical finance workflows that improve control, reduce manual handling and give leaders better visibility. The goal is not to build a monster system. The goal is to stop pretending an inbox is a finance process.
FAQs
Why is email a poor AP approval workflow?
Email is difficult to control, audit and monitor. It can hide bottlenecks, duplicate invoice handling, unclear approval status and weak evidence of review.
Does eInvoicing replace AP approvals?
No. eInvoicing can improve invoice exchange and reduce manual handling, but finance still needs approval rules, exception checks, payment controls and reporting.
What should an AP approval workflow include?
A strong AP workflow should include invoice capture, supplier validation, coding, approval routing, exception handling, audit trail, segregation of duties and payment sign-off.
Can small and mid-sized businesses automate AP without replacing their ERP?
Yes. Many businesses can improve AP using workflow tools, invoice capture, eInvoicing, controlled data tables and integration into the existing accounting or ERP system.
Where can AI help in AP automation?
AI can assist with invoice classification, anomaly detection and first-pass exception review. However, finance should keep human review and clear controls around payment decisions.