Most finance teams do not have an invoice problem. They have a data-entry problem wearing an invoice costume. A supplier sends a PDF, someone opens it, retypes the totals into an ERP, then chases a manager for approval. Multiply that by a few hundred documents a month and the month-end close becomes a scramble.

Automating the flow does not mean removing people from accounts payable. It means giving them better work: reviewing exceptions, negotiating terms, watching cash. The order below — capture, extract, validate, route — is the one that tends to hold up, because each stage depends on the one before it.

Map one invoice from inbox to payment

Before evaluating any software, follow a single invoice. Write down every hand it passes through, every system it lands in, every field somebody types. Do this for five invoices from five different suppliers and a pattern appears quickly.

You will usually find that keying is not the largest cost. The real time sink is chasing: a missing purchase order, a price that does not match the contract, an approval sitting in an inbox while the approver is on leave. Note those delays specifically, because they shape your exception rules later.

Capture: funnel every channel into one queue

Invoices arrive as email attachments, portal downloads, paper mail, and structured feeds such as EDI or XML. Each channel needs its own entry point, but they should all land in the same queue carrying the same metadata.

• Use a dedicated AP mailbox rather than a shared personal inbox, and forward portal downloads into it automatically.
• Keep the original file untouched. Downstream steps should read from it, never overwrite it.
• Stamp each document on arrival with a timestamp and source, so disputes can be traced.
• Run a first-pass duplicate check on supplier name, invoice number, and total before anything else happens.

Digital PDFs and scanned images behave differently. A PDF with embedded text extracts cleanly; a phone photo of a crumpled invoice needs image cleanup first. Tag documents by type so the extraction step can choose the right path.

Extraction: header fields first, line items second

Optical character recognition turns pixels into text. Layout models then work out which string is a supplier name and which is a total. Together they read the fields your ERP needs.

Start with the header: supplier name and tax identifier, invoice number, invoice date, purchase order number, currency, subtotal, tax, total, payment terms, and remittance bank details. Add line items only if you need them for general ledger coding or three-way matching. They multiply both the work and the error surface.

What to keep from every extraction

Store the confidence score for each field alongside the value. Store the raw text too. When a supplier disputes an amount three months later, you want to see exactly what the document said and what was read from it.

Vendor matching matters more than perfect reading. If the name reads as "Acme Ind. Ltd" but your master file says "Acme Industries Limited", match on tax identifier and bank account before matching on the string. Template the twenty suppliers who send you the most invoices; volume concentrates, and templates cut errors sharply.

Expect trouble with multi-page documents, rotated scans, faintly stamped PO numbers, and any invoice that quietly changes bank details. That last one deserves a hard rule: treat a change of payment account as an exception, always, and verify it through a contact you already know.

Validate with rules, not with eyeballs

Validation is where automation earns its keep, because rules are cheap and consistent. Run them in order and stop at the first failure, so the reason recorded on the exception stays clear.

1. Arithmetic: line items sum to the subtotal; subtotal plus tax equals the total.
2. Duplicates: same supplier, same invoice number, same amount, within a rolling window.
3. Purchase order match: the invoice references a PO that exists and is still open.
4. Price and quantity tolerance: the billed amount sits within an agreed percentage of the PO or contract.
5. Vendor master: the supplier is active, not blocked, and the tax identifier is present.
6. Sanity checks: dates are plausible, currency is expected, totals are positive.

Keep tolerances configurable and visible. A two percent price variance might be fine for freight and unacceptable for machined parts. Whoever owns the process should be able to change a threshold without filing a support ticket.

Route by exception, not by default

Invoices that clear every check should post, or queue for payment, without human touch. Everything else goes to a named owner with the reason attached.

Route approvals to a role, never to a person's inbox. Set a service target — one business day is a common starting point — and escalate automatically when it lapses. Approvals should be one click on a phone, with the invoice image and the matched PO side by side. If an approver has to log into a desktop system to see the document, the queue will grow.

Handling the exceptions properly

A good exception queue is a worklist, not a graveyard. Every item needs a category, an owner, and a clock.

• Low-confidence extraction: send to a reviewer who corrects the field and confirms it. Save the correction so the same supplier reads better next time.
• Missing PO: query the supplier from a template email, and notify the buyer who should have raised the order.
• Price mismatch: route to procurement with both figures shown side by side.
• Suspected duplicate: hold payment and check against the current payment run before releasing.

Review the categories weekly. If one keeps growing, the fix is usually upstream — a supplier quoting the wrong PO reference, or a tolerance set too tightly. Track how long exceptions take to clear, not just how many arrive.

Pilot, measure, then widen the pipe

Run the pipeline in shadow mode for a couple of weeks: it reads invoices while your team keeps processing them the usual way. Compare field accuracy and study where the two disagree. Go live first with suppliers who send clean digital PDFs, then add scanned documents, then the awkward ones.

Keep a manual path available, and train people on exceptions and rules rather than on typing speed. Before you retire paper handling entirely, check your retention and e-invoicing obligations with your accountant or tax adviser — the requirements differ by country and change from time to time.

Get the first four stages right and the fifth one shrinks on its own.

Photo: stevepb / Pixabay