AP Is Not a Finance Problem — Until It Is: How Broken Payables Processes Cost More Than You Think
Accounts payable doesn't get much attention until something goes wrong. A supplier puts the organisation on stop credit. An invoice gets paid twice. A manager complains that their purchase order has been sitting unapproved for three weeks. At that point, AP becomes very much finance's problem — even if the root cause has nothing to do with the finance team specifically.
That's the structural issue with payables in most organisations: the process spans multiple functions, but when it breaks, the failure lands on finance. Procurement raises the order. Operations receives the goods. The approving manager sits somewhere in between. Finance processes the payment. When any link in that chain doesn't perform, the invoice either stalls, gets paid incorrectly, or creates a relationship problem with a supplier that finance then has to manage.
Most AP problems aren't payment problems. They're process design problems — and they're costing organisations more than finance teams typically track.
The Real Cost of a Broken AP Process
The visible cost of poor AP is easy to identify: duplicate payments, missed early payment discounts, late fees on overdue accounts. These are real and they show up in the ledger. But the less visible costs are often larger.
Supplier relationship deterioration. Suppliers talk to each other. An organisation known in its supply chain for slow or unreliable payment becomes a lower-priority customer — which means less flexibility on terms, less goodwill in a supply crunch, and reduced willingness to negotiate on pricing. For organisations that depend on a small number of key suppliers, this is a material commercial risk, not just an administrative inconvenience.
Staff time absorption. When the AP process relies on manual chasing — finance following up approvers, re-sending invoices, reconciling supplier statements because the ledger doesn't match what the supplier says is outstanding — the cost in staff hours accumulates quickly and invisibly. It rarely appears as a line item anywhere. It appears as a finance team that's perpetually behind and can't explain why, because the time is being absorbed by low-value process management rather than high-value financial work.
Audit and compliance exposure. A disorganised AP process is a control risk. Invoices approved without a purchase order. Payments made to vendors not on the approved supplier list. Duplicate invoice numbers processed by different team members. None of these are necessarily fraudulent — but all of them are the kind of thing an auditor will flag, and the remediation work is time-consuming and embarrassing.
|
2–5%
Estimated rate of duplicate or erroneous payments in organisations without automated AP controls — a figure that compounds quickly at volume and is rarely tracked until an audit or supplier dispute surfaces it.
|
30–45 days
Typical invoice approval cycle in organisations running AP through email — a timeline that regularly breaches standard trading terms and quietly damages supplier relationships over time.
|
Where AP Processes Actually Break Down
The approval bottleneck. In most organisations, invoice approval sits with a manager who has seventeen other things on their plate. Finance sends the invoice. The manager means to approve it. Three weeks later, finance follows up. The manager approves it the same day. This cycle repeats across dozens of invoices every month, and the cumulative effect is an average payment cycle that bears no relationship to the trading terms on the invoice.
The deeper problem is that the approval step often doesn't add the value it's supposed to. If a manager is approving invoices in batches at the end of the month without reviewing them in detail — which is what happens when approval requests accumulate — the control purpose of the step isn't being achieved anyway. Finance is waiting three weeks for a rubber stamp that isn't actually functioning as a control.
The purchase order gap. A significant proportion of AP problems trace back to invoices arriving without a corresponding purchase order. The supplier delivered something. Operations accepted it. But no PO was raised, so finance has no basis to verify what was ordered, at what price, and whether the invoice matches the agreement. The reconciliation work this creates — going back to the operational team to reconstruct what was actually agreed — is time-consuming and often contentious.
The PO discipline problem is rarely a finance problem. It's an operational discipline problem. But finance carries the reconciliation burden when it breaks down. The sustainable fix involves a conversation that goes beyond the finance team's immediate control — which is why AP process improvement is rarely just a finance project.
The supplier statement reconciliation cycle. When the AP ledger is consistently out of sync with what suppliers are reporting as outstanding, reconciling supplier statements becomes a monthly exercise that absorbs hours of finance staff time. The root cause is usually a combination of timing differences, unapplied credits, and disputed invoices sitting in limbo. A well-functioning AP process resolves these in real time. A poorly functioning one accumulates them and reconciles them retrospectively — which is slower, more error-prone, and more damaging to supplier relationships.
What Good AP Actually Looks Like
A well-designed AP process isn't complicated. The core requirements are straightforward: invoices are matched to purchase orders before they enter the approval workflow. Approval is delegated to the appropriate level with a clear timeline expectation. Finance processes payment within terms once approval is received. The ledger is reconciled to supplier statements monthly with minimal exceptions.
What separates organisations that achieve this from those that don't isn't usually technology — although the right tools help. It's the clarity of the process design and the organisational agreement about who owns what. Finance can't approve invoices on behalf of the business. Finance can't enforce PO discipline in operational teams. But finance can design a process that makes both of those things easier to do correctly, and harder to bypass.
The organisations that get AP right have typically had a frank conversation about what the process is supposed to achieve — not just "pay the invoices" but maintain supplier relationships, preserve cash flow predictability, satisfy audit requirements, and give the finance team accurate forward visibility on the creditors ledger. When AP is framed that way, it becomes a business process that the whole organisation has a stake in, rather than a finance administrative task that other teams occasionally interact with.
The Supply Chain Cost Nobody Models
There's a version of the AP problem that sits entirely inside one organisation — slow approvals, reconciliation backlogs, the occasional duplicate payment. Frustrating, but largely self-contained. Then there's a version that quietly destroys relationships and supply chains over time, and the organisation causing the damage is often the last to understand what it's done.
The pattern is consistent enough to be recognisable. A large organisation has an internal AP process that relies on managers approving invoices before payment is released. Those managers are busy. Approvals get batched and submitted at the last possible moment — the day before the payment run, or the day after it's already been missed. The invoice goes into the next cycle. The supplier, who submitted that invoice on 30-day terms three weeks ago, is now sitting at 50 days outstanding. Finance is aware the payment is overdue. Nobody is doing anything wrong exactly — the process is just slow, and the bottleneck is internal.
For a large supplier, this is an inconvenience. For a small or mid-size subcontractor operating on thin margins, 50-day payment cycles on what were agreed as 30-day terms is a cash flow problem. If it happens consistently — and with large enterprise clients, it often does — that subcontractor starts making decisions: drawing down on credit facilities to cover wages, deferring their own supplier payments, cutting costs where they can. Eventually, some of them don't survive it.
Australia's Payment Times Reporting Scheme exists partly because this pattern is so widespread. Large businesses — those with annual turnover above $100 million — are required to publicly report their payment times to small suppliers every six months. The data regularly shows a gap between agreed terms and actual payment behaviour across some of the country's largest organisations. The public disclosure is intended to create accountability. It works imperfectly.
The commercial irony is that when a subcontractor collapses due to cash flow pressure created in part by a large client's slow payment, the problem doesn't stay with the subcontractor. The large organisation loses a supplier it depended on — often a specialised one that isn't easily replaced. It inherits the disruption, the rework, the retendering cost, and in some cases the project delays that flow from a gap in its supply chain. The AP process failure that looked like an internal administrative issue turns out to have external consequences that are materially more expensive than whatever the approval bottleneck was saving in manager time.
This isn't an argument that large organisations are acting in bad faith. Most aren't. It's an argument that AP process design in large organisations has consequences that extend beyond the ledger — and that the real cost of a slow, approval-dependent payment cycle rarely gets modelled against the cost of fixing it.
The AP Conversation Finance Teams Should Be Having Right Now
With FY2027 seven weeks away, now is a reasonable time to ask whether the AP process is in the shape it needs to be for the year ahead. Not because July 1 creates a hard deadline for process change — it doesn't — but because budget season is a natural point at which finance teams assess operating costs, and the cost of a poor AP process is one that rarely gets formally measured.
If the creditors ledger at month-end regularly contains invoices more than 60 days old that aren't disputed, that's a process signal. If the finance team is spending more than a few hours a month chasing approvals, that's a process signal. If supplier statements consistently don't reconcile cleanly, that's a process signal.
None of these problems fix themselves. But all of them are fixable — with process redesign, clearer ownership, and in some cases better tooling. The starting point is being honest about where the current process is actually failing, rather than accepting it as the cost of doing business.
Is Your AP Process Costing More Than You Think?
PFL works with Australian NFP, NDIS, and SME organisations on finance process improvement — including AP design, approval workflow structure, and the operational conversations that make process change stick. If the creditors function is absorbing more time and creating more friction than it should, let's talk about what a better-designed process looks like.
Get in Touch with PFL →
Comments
Post a Comment