The hidden costs sitting in your AP workflow
A CFO described his AP function as fine. AP cost was four percent of revenue. He had not measured it. The number was high for four reasons, all invisible from the org chart. A note on the costs that hide inside healthy-looking AP.
The CFO of a fifty person engineering services firm told me last summer that his AP team was running at "fine." He had two people, both competent, payments went out on time, suppliers were not complaining. He did not see why he should be looking at the function at all.
I asked him what his AP cost was. He had to look it up. About four percent of revenue. That is much higher than it should be for a business of his size, and he had no idea because no one had ever asked him.
The number was high for four reasons, all of them invisible from the org chart. None of them showed up as a problem on anyone's dashboard. All of them quietly cost him more every quarter than the salaries of the people running the function.
One. Duplicate POs
Two buyers in two departments order the same product from the same supplier in the same week because the requisition system does not show them each other's orders until the PO is approved. The supplier ships both. Both get paid. The first time the operations head finds out is when the warehouse runs out of room and someone goes looking for the second order.
Mid-market firms hit this often enough that most AP teams have an unwritten "duplicate hunt" they do once a month. The hunt is the cost. The duplicates are the symptom.
Two. Last-minute supplier substitution
Your preferred supplier slips delivery. The buyer needs the material this week. They call a substitute, accept a worse price, run the PO through an emergency approval. The emergency price is twelve to twenty percent higher than the rate card. The buyer marks the substitution as a one-off. It happens about twice a quarter across the buying team. None of those one-offs roll up into a number anyone reports.
The cost is real. The cost lives in the spread between the rate card price and the actual paid price across the year. On a thirty million annual spend, a one and a half percent spread is half a million dollars walking out the door without an invoice line item that calls itself "expensive substitution".
Three. Payment timing slop
The AP team runs a Friday payment batch because that is when the bank window suits them. Suppliers expect payment on the date the contract says. Half are paid early, eating working capital. Half are paid late, eating goodwill. The treasurer cannot manage cash position because she does not know which invoices are inside her control window and which are at risk.
Better timing alone is worth between fifty and a hundred and fifty basis points on the working capital line of a typical mid-market business. That is a number you can prove. Most CFOs have never measured it.
Four. Reconciliation tax
Month end takes a week because the supplier statements do not match the AP ledger. They do not match because of duplicates, because of substitutions, because of timing slop, and because the supplier master data is half wrong. Reconciliation is the visible cost. The invisible cost is the senior person spending five business days on reconciliation who would otherwise be doing the work that actually moves the business.
What we do about it
None of these costs are exotic. None of them require AI to see. What they require is data that is structured around the business partner, not around the document. Invoices belong to a supplier BP. POs belong to the same BP. Bank accounts belong to the same BP and are verified separately. When the data shares an identity, duplicates fall out, substitutions are visible at the moment they happen, timing becomes a treasury decision rather than an operations habit, and reconciliation gets simple because the matching is already done.
That is what buyer-side Calabash is. A way of holding the data so the costs above stop being invisible. We are not promising to make the costs go away. We are promising to make them visible enough that you can decide what to do about them.
If you have an AP function you describe as "fine" and you have not actually measured the four costs above, that post-it on your monitor is now my fault. The Calabash SME edition is at calabash.app. Sign up if you want to compare notes.
