The cost gap between manual and automated invoice processing is wider than most finance teams realise. The ATO and Deloitte Access Economics put manual paper invoice processing at around $30.87 per invoice. Manual PDF processing comes in at $27.67. Automated e-invoicing sits at roughly $9.18.
That is a gap of more than $20 per invoice for every invoice, every month, every year. For a business processing circa 1,000 invoices a month manually, it is around a quarter of a million dollars left on the table annually.
With FY27 starting, this AP line item is either being addressed in the opening quarter of the new FY or carried forward at full cost into another 12 months. The case for treating July as the deadline, rather than the start, comes down to that.
The real cost of "same as last year"
The quarter-million figure is the line that gets most attention but it sits alongside a set of operational costs that don't always make it into the business case for change. For example:
- Invoice processing cycles stretching to 90 or 120 days, well past the point where suppliers start asking questions or pulling credit terms.
- Reconciliation errors that surface as supplier disputes, credit-note loops and month-end delays.
- Audit findings citing manual invoice controls as a material weakness.
- Single-person dependencies that become visible and expensive the moment a key AP staff member resigns.
Viewed through these lenses, “same as last year” isn't really a decision to hold steady. It is a decision to absorb the same costs again and to keep absorbing them while they quietly grow.
Why now, specifically?
The timing argument works at three levels.
For the CFO, an AP project that starts in Q1 and goes live by Q2 still has two full quarters to deliver against this year's cost-reduction targets.
A project that starts in Q3 doesn't have that runway and the savings accrued will be pushed into the next reporting period, which from a board's perspective is roughly the same as not doing the project at all.
Capex and operating expenditure decisions made now, against a freshly approved budget, are also materially easier to defend than mid-year re-forecasts.
For the COO, starting implementation in July means the team is trained and adopted before Q3 trading volume returns.
Miss this window and the next realistic slot is February, by which point another half-year of manual cost has been absorbed and the EOFY clock is ticking again.
For the AP manager, July is the only point in the FY where the team genuinely has bandwidth for change management. From Q2 onwards, the operational load makes implementation projects significantly harder to land well.
The window where "yes" is the easy answer is open right now and it is narrower than it looks.
The compliance ground is shifting
If you trade with the federal government, the compliance ground has already shifted under you. All Commonwealth agencies have been able to receive PEPPOL e-invoices since 1 July 2022 and the direction of travel since then has only accelerated.
NSW Health has publicly committed to PEPPOL for its suppliers. Other state governments and major private-sector buyers are moving in the same direction. The ATO continues to actively encourage adoption across the economy.
None of this means manual invoicing stops working tomorrow. The point is any AP solution chosen in 2026 should be PEPPOL-ready out of the box, not retrofitted later when a major customer or government counterparty makes it a condition of trade.
For finance and operations leaders, this is straightforward risk management and the cost of choosing a compliant path now is lower than the cost of retrofitting one later.
The decision isn't really whether to move to e-invoicing. It is which path to take and when.
The upside the cost case usually misses
The cost-per-invoice line is where most AP business cases stop. The full picture is broader and it is where the strategic value usually sits:
- Cash flow visibility. Real-time view of what is owed, to whom and when without running a query. Critical for any business managing working capital tightly.
- Supplier negotiation leverage. Predictable, on-time payment behaviour is a card a finance team can play in renegotiating terms, prices or both.
- Scalability without proportional headcount. Invoice volume can grow without the AP team growing alongside it. This is particularly relevant for any business in growth or M&A mode.
- Audit and controls posture. Automated AP creates an auditable trail by default, reducing the manual control burden that increasingly draws audit committee scrutiny
These are the compound-interest benefits. Harder to quantify upfront, which is why they often don't make the initial business case but usually where the long-term value sits.
HOW: Building an AP automation business case
A business case for an AP project typically needs to do four things to get over the line.
1. Lead with a number the CFO can defend in
the board pack.
The strongest opening figure is the
annualised cost saving calculated from current invoice volume against the gap
between current cost-per-invoice and the automated benchmark. If current
cost-per-invoice isn't measured internally, the ATO/Deloitte figures ($27.67
PDF, $30.87 paper) are defensible substitutes.
For example, a business processing 1,000 invoices a month, mostly via PDF, is looking at roughly $220,000 a year in saving, a number that survives scrutiny because it is anchored to public data, not vendor claims.
2. Quantify the second-order costs.
The cost-per-invoice line is
rarely the strongest argument on its own but the case gets meaningfully
stronger when it includes things like:
- The financial impact of late payments (lost early-payment discounts, supplier credit term tightening).
- Reconciliation errors (rework hours, supplier disputes and AP staff turnover (recruitment, training, productivity gap during backfills).
Put dollar figures next to each one. Even rough estimates change the shape of the case.
3. Frame the risk of inaction, not just the
benefit of action.
Boards approve projects faster
when the alternative carries visible risk. The risks worth naming explicitly:
- Audit findings on manual invoice controls
- PEPPOL compliance exposure with government and large-buyer counterparties
- Key-person dependency in the AP function
- The cumulative cost of another 12 months of manual processing.
Inaction is a decision with a price tag and the business case should show it.
4. Set a realistic timeline and tie it to
the FY.
A business case dated July with a
Q2 go-live and benefits realised in Q2–Q4 of FY27 is materially easier to
approve than an open-ended "we should automate AP".
Show the timeline:
- Contract signature in July.
- Implementation across August and September, supplier onboarding running in parallel.
- Go-live by October, full benefit realisation through Q3 and Q4.
The board approves projects with end dates, not aspirations.
The case for fixing AP in July isn't really about AP. It is about which version of FY27 you want to be running. One version looks a lot like FY26, i.e. same cost gap, same 90-day cycles, same key-person risk, same compliance question hanging over the team. The other version starts with a business case put together this month, signed off against a fresh budget and benefits showing up by Q3-4.
Both are choices. One of them just costs a quarter of a million dollars more. If you have any questions, feel free reach out to our friendly team for a chat.