Reduce Manual Invoice Processing
A supplier emails you a PDF with new bank details and a polite note that the old account has been closed. The amount is ordinary, the logo looks right, and the person who handles payables is on leave, so a colleague covering for her pays it. Three weeks later the real supplier asks why they have not been paid. This is one of the most common frauds against small businesses, and it works because manual invoice handling depends on people noticing things at speed.
If you are the controller of a 30-person firm, you probably carry two worries at once. Invoices take too long, and you suspect the process is not as safe as it looks. Fortunately, the same changes that save time tend to improve control. This article walks the accounts payable flow from the first email to the bank payment, shows where the manual effort hides, and explains which controls to automate and which to keep human.
Follow one invoice end to end
Take a single invoice and trace it. Most firms follow something like this sequence, whether or not anyone wrote it down.
- Receipt. The invoice arrives by email, post, a supplier portal, or a text message to someone's phone.
- Capture. Someone reads the vendor, number, date, amounts, and tax, and enters them in the accounting system.
- Validation. Someone checks that it is real, that it is not a duplicate, and that the supplier is known.
- Matching. Someone compares it to what was ordered and what was received.
- Coding. Someone decides which accounts and projects the cost belongs to.
- Approval. Someone with authority says it is fine to pay.
- Payment. Money moves, by check, bank transfer, or card.
- Reconciliation and filing. The payment is matched to the bank statement and the paperwork is stored.
Time your next ten invoices through this path and note where each one waited. Most of the elapsed time is waiting, in an inbox, on a desk, or for a manager who is traveling. Hands-on work is often a small fraction. That tells you where to aim. Automating the typing helps, but shortening the waits often saves more.
Three-way match, explained plainly
A three-way match compares three documents before anything is paid. The purchase order says what you agreed to buy and at what price. The receiving record, sometimes called a goods receipt, says what actually arrived. The invoice says what the supplier is charging. If all three agree on quantity and price, within a small tolerance, the invoice is cleared. If they disagree, it goes to a person.
This control catches overbilling, billing for items never delivered, and price changes nobody approved. It does require that purchase orders and receiving records exist, which not every service business has. So here is a decision rule.
- Goods you order and receive, such as supplies, equipment, and inventory, deserve a three-way match.
- Services and recurring bills, such as rent, software, and utilities, usually get a two-way match against a contract or a purchase order, or a simple check against the prior month.
- One-off professional fees get approval by the person who requested the work, who confirms the work was done.
Set a tolerance so people do not chase pennies. For example, you might accept a price difference of 2 percent or $25, whichever is smaller. Choose numbers that fit your volumes. The point is that the tolerance is written down and applied by the system rather than by mood.
Where the manual hours really go
Controllers often assume data entry is the main cost. It is a big one, but exceptions and chasing are frequently larger. A rough breakdown of where effort tends to hide follows.
| Step | Typical manual cost | What automation can do |
|---|---|---|
| Capture | Retyping header and line data | Read the document and propose values for review |
| Duplicate check | Memory and luck | Compare vendor, number, date, and amount automatically |
| Matching | Pulling up purchase orders by hand | Match automatically and show only differences |
| Coding | Guessing the account | Suggest codes from past invoices from the same vendor |
| Approval | Chasing people by email | Route to the right approver and send reminders |
| Exceptions | Phone calls and email threads | Queue with a reason and an owner |
Notice that automation here does not remove people. It reduces the number of items people must touch and gives them better information when they do.
Coding and approvals that people will actually follow
Coding means assigning each invoice to accounts, departments, or projects. Poor coding quietly damages your reports, so it is worth designing well.
- Keep the chart of accounts short enough that people can choose correctly. If there are 14 different kinds of office expense, people will pick at random.
- Store a default coding on each vendor record. A recurring cleaning service, for instance, can be coded automatically every month, with a person only reviewing exceptions.
- For project work, require a project on every invoice that relates to one. Retrofitting it at month end is painful.
Approvals work best as simple rules rather than a maze. A common structure uses amount thresholds and roles.
- Under a low amount, the budget owner approves.
- Between the low amount and a higher one, the budget owner and the controller approve.
- Above the higher amount, an owner or partner also approves.
Add two protections. First, the person who approves an invoice should not be the person who can change vendor bank details or release the payment. This is called segregation of duties, and with 30 people it may mean dividing tasks between just two or three individuals. Second, build in delegation. When an approver is away, the system should route to a named backup rather than sit idle or encourage someone to share a password.
A worked example, with illustrative numbers
The following figures are hypothetical, built only to show the arithmetic.
Imagine a 30-person firm that processes 220 supplier invoices a month. Suppose each invoice takes 12 minutes of hands-on time through entry, matching, coding, and routing, and about 15 percent need an extra 20 minutes because of a mismatch or missing information.
- Base handling is 220 times 12 minutes, which is 2,640 minutes, or 44 hours.
- Exception handling is 33 invoices times 20 minutes, which is 660 minutes, or 11 hours.
- Total is about 55 hours a month.
Now assume the firm moves to extraction with human review, default coding by vendor, and automatic routing, so that hands-on time falls to about 5 minutes per invoice and exceptions fall to 8 percent because of better vendor records. The new total is 220 times 5, or 1,100 minutes, plus 18 invoices times 20, or 360 minutes. That is about 24 hours. The saving of about 31 hours a month is real but secondary. The larger benefit in this example is that every invoice now has a duplicate check and an approval record, which the old process did not guarantee.
Replace these numbers with your own measured ones before drawing any conclusions.
Fraud controls that deserve your attention first
Invoice fraud is rarely sophisticated. It succeeds on urgency and trust. Several controls give the most protection for the least effort.
Vendor bank-change verification
Treat any request to change payment details as high risk, no matter how it arrives. A safe procedure looks like this.
- Never act on an emailed instruction alone. Email accounts get compromised, and a message from a real supplier's address may not come from the supplier.
- Call the supplier on a phone number you already had on file, not a number in the message. Confirm the change with a known contact.
- Record who verified it, when, and how.
- Require a second person to approve the change before it takes effect.
- Pause payments to that vendor for a short period after the change, or require extra review of the first payment.
Duplicate invoice detection
Duplicates arrive when a supplier resends an invoice, when it comes in both by email and by post, or when it is lightly altered. Match on vendor, invoice number, amount, and date, and also flag near matches, such as the same vendor and amount within a few days.
Vendor master hygiene
Your vendor list is a control surface. Remove inactive vendors, restrict who may add new ones, and compare new vendors' tax information and bank details against existing records. A new vendor whose bank account matches an employee's is worth a second look.
Payment release controls
Where your bank allows it, use dual approval for transfers above a threshold, and set daily limits. A payment file should be reviewed against the approved list before it is sent.
Review of changes
Produce a monthly report of vendor changes, manual overrides, and invoices approved just under a threshold. Splitting an invoice to stay below an approval limit is a classic pattern.
What to automate and what to keep human
Keep a person in the loop for new vendors, bank-detail changes, unusual amounts, and any invoice the system cannot match. Automate the repetitive, rule-based parts, such as reading standard invoices, looking for duplicates, applying vendor defaults, routing for approval, and sending reminders.
Be cautious with extraction that reads invoices from images or PDFs. Even good tools make mistakes with unusual layouts, handwritten notes, or poor scans. Use confidence scores to send low-confidence fields to review, and compare totals, since the line items must add up to the invoice total, and the tax must be plausible. A simple arithmetic check catches many errors.
Failure modes and tradeoffs
- Automation with bad data. If your vendor list has duplicates and your purchase orders are informal, matching will produce noise. Clean the vendor master first.
- Approvers who rubber-stamp. If every invoice is routed to the same busy person, approvals become reflex. Route by budget owner and keep thresholds meaningful.
- Shadow channels. Invoices sent to personal email addresses or messaging apps bypass your controls. Publish one address for invoices, such as a shared inbox, and ask suppliers to use it.
- Connectivity and power. Storm season in Puerto Rico can interrupt your office for days. Prefer a cloud accounting system and a shared inbox that more than one person can reach from anywhere, plus an approval path that works from a phone.
- Tax and compliance rules. Requirements for sales and use tax, withholding, and record retention vary by jurisdiction and by transaction. Confirm them with your accountant or counsel, since this article is not legal or tax advice.
What to ask a vendor
- How does the tool detect duplicates, and what fields does it compare?
- Can it show a confidence score for each extracted field, and route low scores to review?
- How does it support three-way and two-way matching, and with what tolerances?
- What audit trail is kept for approvals, edits, and vendor changes?
- How are bank-detail changes controlled and who must approve them?
- Can I export all invoices, images, and history if I leave?
What to do Monday morning
- Send ten recent invoices through the eight steps and record where each waited.
- Write the bank-change verification procedure on one page and share it with everyone who touches payables.
- Check whether the same person can both add a vendor and release a payment, and split those duties.
- Publish a single invoice inbox and ask suppliers to use it.
- Run a duplicate check on the last quarter's payments using vendor, number, and amount.
- Pick tolerance numbers for matching and write them down.
None of this needs new software. All of it makes the later automation more effective.
If you would like help designing the flow or choosing tools that fit a firm your size, Ozcorp InfraOps works with small teams on exactly this. InfraOps Base starts at $500 per month, with vendor and license charges billed separately. Whatever route you take, start with the bank-change procedure. It costs nothing, and it addresses the failure that hurts most.
Discuss your infrastructure requirements
Review the current service offer or schedule a conversation about the scope you need.
Stay in touch
Follow Ozcorp
Leave your details for occasional notes about new articles and Ozcorp updates.