Cut invoice processing time by 80% without replacing your accounting system

What slow invoices are actually costing you

If your team is taking around 14 days on average to process a supplier invoice, you're not unusual. The median for small businesses runs between 10 and 18 days. What most operators don't realise is how much that delay compounds once you add up all the places it shows up.

The obvious cost is late payment fees, which run between 1.5% and 2% per month on overdue balances. Across 80 or 100 invoices a month, that adds up faster than most finance teams realise. Less obvious is what happens to your supplier terms when you're consistently slow. Early-payment discounts disappear. Preferred pricing gets withdrawn. In some cases, suppliers start requiring payment upfront.

Then there's the internal cost. A typical AP coordinator at a 20-person company spends 6 to 8 hours a week chasing approvals, re-entering data, and figuring out where invoices have gone quiet. That's a full working day, every week, producing nothing new. It also tends to compress into month-end, when the scramble to close the books collides with a backlog of invoices nobody touched during the month.

The part that makes it compound: most of this cost is invisible until you actually map what's happening. And most small businesses haven't done that.

Where the time goes (it's not in the review)

Here's what a typical invoice cycle actually looks like, step by step.

A supplier sends an invoice by email. Someone forwards it to the right manager for approval. The manager doesn't see it, isn't sure if it falls within their limit, or is waiting on someone else. Three days pass. The AP coordinator sends a chase. The manager approves, but the invoice amount doesn't match the PO on file. Someone contacts the supplier. A corrected invoice arrives in a slightly different format. It gets typed into the accounting system by hand. Payment runs at the end of the week.

Total elapsed time: 11 days. Time actually spent reviewing the invoice and deciding to pay it: under four minutes.

This is where the 80/20 matters. Routing, chasing, re-keying, and waiting account for roughly 80% of elapsed time in a typical AP cycle. The human judgment call at the end, the bit that actually requires a person, takes minutes. Once you see this, the nature of the problem becomes clear. You don't need a faster accounting system. You need a better handoff between steps.

The review itself is almost never the bottleneck. The time disappears in the gaps between steps, not in the steps themselves.

Why replacing your accounting system won't fix this

This is where a lot of SMBs spend money and get disappointed.

They upgrade to a new accounting platform, add an AP module, or switch to a different invoicing tool. Six months later, invoices are still taking two weeks. The software changed; the cycle didn't.

The reason is simple: the bottleneck lives upstream of your accounting system. By the time an invoice reaches the ledger, the delay has already happened. It happened in the email thread where the approval request sat unread for four days. It happened when a scanned PDF had to be manually keyed in because the data wasn't in a usable format. It happened because nobody realised the invoice was stuck until the supplier followed up.

Your accounting system is doing exactly what it's supposed to do. It receives an approved invoice, records it, and schedules payment. The gap is in everything that happens before it gets there. Replacing the ledger to fix a routing problem is like buying a new fridge because your kitchen is too small. The investment addresses the wrong thing entirely.

The three routing failures most SMBs share

So what's actually creating these delays? Almost always, the same three patterns.

Approval paths that live in someone's head. There's no written rule about who approves what. One person just knows that routine invoices under a certain amount go straight through, anything above a threshold needs the director, and certain vendors always need a second look. When that person is on leave, approvals stall. When they leave the company, the knowledge walks out with them.

Invoice data that arrives in inconsistent formats. Some suppliers send a clean, structured PDF. Some send a photo taken on a phone. Some send a Word document with the totals in a different position every time. Every format demands a different amount of manual work to pull out the key information. None of it is standardised before it reaches anyone who needs to act on it.

No visibility into where a document is stuck. This is the most damaging of the three. When an invoice goes quiet, there's no system state you can check. It might be sitting in someone's inbox. It might have been forwarded to the wrong person. It might be waiting on a PO match that nobody started. The only way to find out is to ask someone, which takes time and creates friction, and usually results in a duplicate being sent just to be safe.

Each of these is a process failure. None of them is a software capability gap. And each one is fixable without touching your accounting system.

If your invoices are running 10 or more days from receipt to payment, which of the three routing failures is driving that delay: approval paths that live in one person's head, data arriving in formats nobody standardised, or no visibility into where a document has gone quiet? A Fastw3b automation audit is the first step that answers that question. It maps how invoices actually move through your business, finds the routing pattern eating up the most elapsed time, and hands back a ranked plan of what to automate first. The audit gives you the picture; acting on it is where the 6 to 8 hours a week of chasing comes back and a 13-day cycle becomes a 4-day one. Fix your AP routing with business automation →

How to fix the routing without touching your accounting system

The approach that works consistently follows three steps, in this order.

Intercept invoices before they reach the ledger. Instead of invoices landing in a shared inbox where a human has to decide what to do with them, route them through a single entry point that reads the key fields (vendor name, amount, PO reference) and determines what happens next. The rules don't have to be complex. A simple set that covers 90% of your invoice types is enough to start. You can handle exceptions manually while you build confidence in the process.

Standardise the data handoff. Before an invoice reaches anyone for approval, the relevant information should be in a consistent format: vendor name, invoice number, amount, due date, and the matched PO number where there is one. When an approver gets a request, they should see those fields immediately, not an attachment they have to open, scroll, and interpret themselves. This alone tends to cut approval time significantly, because the decision becomes obvious rather than investigative.

Replace the informal rules with written ones. The approval logic that currently lives in one person's memory needs to be written down and built into the routing. Invoices under a set threshold go to the line manager. Invoices above it go to the director. New vendors follow a specific path. Once the rules are explicit, they can run without anyone making a routing decision by hand each time. The accounting system stays exactly where it is, and receives a clean, approved invoice at the end of the process.

Before and after: one accounts payable routine

Here's what this looked like in practice for a professional-services business running around 80 supplier invoices a month.

Before. Invoices arrived in a shared team inbox. An AP coordinator checked it twice a day, forwarded each invoice to the relevant approver by email, and logged everything in a spreadsheet. Chasing took roughly 7 hours a week: a first reminder at day 3, a second at day 5, and a call by day 7 if nothing had moved. About 15% of invoices required manual correction because the supplier's format didn't match what the coordinator needed to enter into the accounting system. Average cycle time: 13 days.

After. Invoices route through a single entry point that reads the key fields and sends a structured approval request to the right person, based on a set of written rules. The approver sees a clean summary, not a raw attachment. If there's no response within 48 hours, a chase goes out automatically. Manual correction dropped to under 3% of invoices. Chasing time fell to under 45 minutes a week. Average cycle time: 4 days. The accounting system didn't change.

One honest caveat: the first four weeks were slower. Writing down the approval rules took time. Some edge cases surfaced that the rules hadn't accounted for, and the team had to make explicit decisions that had previously been made quietly and informally by one person. That friction is real, and worth planning for. It's a one-time cost, not an ongoing one. But if you go in expecting it, it doesn't feel like failure.

If your invoice cycle is running at 10 days or more, the bottleneck is almost certainly in the routing, not the review. The fix is a routing fix, not a software replacement.

The routing failures driving your 13-day cycle are fixable through automation, and a Fastw3b audit is where that work begins: start automating your invoice cycle →