How do I stop manually entering invoices?

Accounts payable teams rarely fail at automation because the software cannot read a PDF. They fail because the work is four jobs stapled together: getting invoices into one place, reading them, matching them against a purchase order or contract, and deciding what to do when something does not match. Buying a reader solves exactly one of those.

The second reason is shape. Generic OCR hands back a page of text or a loose bag of key-value pairs, so somebody still writes the code that turns "TOTAL DUE ......... 4,125.60" into a number your ledger will accept. That code is where projects die: it works for the twelve vendors you tested and breaks on the thirteenth.

• Intake: email attachments, a shared mailbox, supplier portals, paper that gets scanned.
• Reading: turning the file into named fields with types you can post.
• Matching: purchase order, receipt, contract rate, or none of the above.
• Exceptions: who fixes a mismatch, and what happens to the invoice while they do.

Before evaluating any tool, write these four answers down. They determine whether automation sticks far more than the tool choice does.

• Field list: the smallest set your ledger needs. Most teams need vendor, invoice number, invoice date, due date, PO number, currency, subtotal, tax, total, and line items. Anything else is a nice-to-have that adds review work.
• Acceptance rule: what has to be true for an invoice to post without a human. Start with "line items sum to subtotal, subtotal plus tax equals total, invoice number is not already in the ledger".
• Exception owner: one named person or queue. An exception with no owner becomes a spreadsheet.
• Matching policy: which invoices need a PO match at all. Many teams discover that only a minority do.

Full automation of payment approval is not the goal — a wrong payment is expensive and slow to unwind. Keep a person in the loop wherever the failure is money leaving the company rather than a typo in a description field.

A practical split: auto-post invoices that pass every arithmetic check, come from a vendor you have paid before, and fall inside the range you normally pay that vendor. Route everything else — new vendors, changed bank details, unusual amounts, missing purchase orders — to review. Changed bank details deserve a manual callback to a known phone number regardless of how confident any software is.

You do not need an industry statistic to justify this; you need your own numbers. Time one person entering ten real invoices end to end, including the interruptions. Multiply the median by your monthly volume. That is the hours side. Then estimate the review rate you are willing to accept — if 20% of invoices go to a human, you are still removing four in five keystroke sessions.

The number that surprises most teams is not the entry time; it is the correction time. A single mis-keyed total that reaches the ledger costs a reversal, a re-post, and an awkward vendor email. Counting those makes the arithmetic checks below the highest-return part of the whole project.