Where does the time go in accounts payable today?
Most of it goes on reading and chasing rather than deciding. Invoices arrive by email, by upload to a supplier portal and on paper that someone scans. Each one is opened, keyed into the finance system, compared with a purchase order that may or may not exist, and then sent round by email for someone to approve. When the price does not match or the goods have not been booked in, the invoice sits in an inbox until somebody remembers it.
Month end makes it worse. Supplier statements arrive listing invoices nobody has seen, approvers are chased for items that have been waiting weeks, and the finance team spends its days on lookups instead of on the numbers. The capacity calculator shows what that time is worth once it is freed, and the audit helps you check whether payables is the right place to start.
What makes invoice processing slow and risky?
Three things, usually together. Capture is manual, so every invoice is typed by a person. Matching is done by eye, so a price above the PO or a short delivery is easy to miss on a busy day. And approval travels by email, so nobody can see where an invoice is or why it is stuck.
The same gaps create the fraud exposure. A duplicate invoice with a new reference, an amount far outside a supplier's normal pattern, or an email asking you to update bank details all rely on a tired person not noticing. A process that checks every invoice the same way, every time, closes those gaps without adding work.
What does a rebuilt accounts payable process do?
It is configured to your own approval rules, tolerances and finance system, and it runs every invoice through the same steps.
| Step | What happens |
|---|---|
| Capture | Invoices are collected from the accounts inbox, uploads and scans into one queue |
| Read | AI reads the supplier, PO number, lines and totals; anything uncertain is held for a person, never guessed |
| Fraud checks | Duplicates, unusual amounts and changed bank details are flagged before anything else happens |
| Match | Each line is matched 2-way to the PO, or 3-way to the PO and the goods receipt in your finance system |
| Post | Matches within your agreed tolerance post automatically with the invoice image attached |
| Exceptions | Everything else is held by reason, such as PO not approved, price above PO or not goods receipted, and sent to the right person in one daily list |
Approvals are routed by department, value and entity, so a group with several companies sends each invoice to the right budget holder. Supplier statements are reconciled against what has been received, and missing invoices are requested from the supplier. Invoices that arrive without a PO, where your policy requires one, are returned to the supplier with the reason.
A changed bank detail always stops the invoice for a phone check by your team. The system never makes payments and never changes bank details. Every action, from capture to posting, is recorded in a tamper-evident audit trail.
What changes for the finance team and approvers?
The finance team stops keying invoices and starts working a single list of exceptions, each with the reason it was held and the evidence beside it. Approvers get one daily list instead of a stream of forwarded emails, and they see the purchase order, the receipt and the variance before they decide. Controllers can see at any point what has posted, what is waiting and why, which makes month end a review rather than a hunt. When the auditors ask how an invoice was approved, the answer is already recorded.
Which businesses should start with payables?
Any business where invoices arrive in volume against purchase orders, and where the finance team is small for the work it carries. Facilities management providers buying parts and subcontracted services across many sites, property and asset managers processing supplier invoices for several owners or entities, and engineering and environmental consultancies buying specialist services all fit. Where purchasing itself is the problem, pair it with purchasing so the POs that invoices match against are right from the start.
How is accounts payable rebuilt?
We begin by mapping how invoices reach you today, the approval limits, the tolerances you will accept and the exceptions that cause the most chasing, using a sample of recent invoices and statements. The build connects to your finance system and is tested on your own documents. It then runs in parallel with the current process on live invoices, so your team can compare every outcome with what they would have done. Nothing posts on its own until your finance lead signs it off, and support continues under the subscription. The timing for each stage is agreed at scoping.