Most procurement automation projects fail for the same reason: someone tries to automate the whole process before fixing the parts that are actually broken. The real leverage is narrower than it looks — routing approvals by amount, keeping people inside the vendor catalog, and matching what was ordered against what arrived and what was billed. Everything else is process theatre layered on top of those three things.
Requisitions and approval routing
A purchase requisition is just a request: someone wants to buy something and needs sign-off before a PO gets cut. The automation here is approval routing based on amount thresholds — a $200 office-supplies request auto-approves or goes to one manager, a $20,000 equipment purchase routes through department head and finance, and anything over a set ceiling hits the CFO regardless of category. The rule set is simple in principle: threshold, category, and cost-center ownership decide the approval chain, and the system enforces it instead of relying on someone remembering the spending policy.
A common bug in home-grown approval rules: they check each line against the threshold instead of the requisition total. Five $150 line items on one requisition add up to $750 — if the rule only inspects individual lines, it never triggers the review that a $750 purchase should get.
Catalogs and maverick spend
Maverick spend is purchasing that happens outside the negotiated vendor list — someone buys from whoever shows up first in a search instead of the supplier procurement already has pricing and payment terms with. It's the single biggest source of avoidable cost in most mid-size companies, and it's rarely explicit sabotage; it's mostly people avoiding a purchasing process for something that's inconvenient. A punch-out catalog or preferred-vendor list built into the requisition screen fixes most of it by construction: if the only items a requester can pick from are pre-negotiated ones, there's no "off-catalog" purchase to make in the first place. The cases that fall outside the catalog need an explicit, slightly harder path — not a blocked one — or people route around the system entirely and you're back to expense reports and unauthorized invoices.
Three-way matching is the real control
Three-way matching compares the purchase order, the goods receipt, and the vendor invoice before anything gets paid — quantities and prices have to agree across all three documents, within a defined tolerance. This is the automation that actually removes manual work, because without it, accounts payable is manually cross-checking paper or PDFs for every invoice that comes in. Automate the match and AP only touches the invoices that don't line up: wrong quantity received, a price that doesn't match the PO, or an invoice with no matching receipt at all. Those exceptions are supposed to be rare; if most invoices are landing in the exception queue, the PO data or the receiving process is the actual problem, not the matching logic.
A common shortcut is a blanket tolerance — "auto-approve if within 5% of the PO amount" — to cut down exception volume. That's fine for shipping cost variance; it's how a vendor's repeated small overcharges go unnoticed for a year, because each one individually clears the tolerance check.
The tension between control and speed
Every additional approval step is sold as risk reduction, and every additional approval step is also a delay that someone eventually works around. The failure mode isn't usually "not enough controls" — it's a purchasing process with so many sign-offs that people start splitting orders to stay under approval thresholds, using personal cards and expensing it later, or going straight to a vendor relationship they already have instead of requisitioning through the system. A procurement process that's too slow doesn't get followed less carefully; it gets abandoned quietly, and you lose the visibility you added the controls to get in the first place. The right amount of approval friction is the amount people will actually tolerate before they start finding the side door.
Wrapping up
Procurement automation earns its keep in three places: approval routing that scales sign-off to the size and category of the spend, a catalog that makes the compliant path the easy path, and three-way matching that turns invoice reconciliation from a manual audit into an exception queue. Adding process for its own sake — more approvers, more required fields, more manual review — doesn't add control; past a certain point it just teaches people to route around the system, which is worse than no process at all.
Independent software engineer in Nairobi specialising in Acumatica customisations, Laravel backends, and tax fiscalisation integrations across East and Southern Africa.