Nobody Was Hired to Type Invoices
An accounts payable seat spends most of its week moving numbers from a document somebody else already typed into a system that could have read it. The judgement in the role is real. The typing around it is not.
Does the work of
- Accounts Payable Officer
- Accounts Payable Clerk
- Purchase Ledger Officer
- Accounts Assistant
A supplier types an invoice. It arrives as a PDF. Somebody reads the PDF and types the same numbers into your ledger, then walks the result around the office looking for whoever is allowed to say yes. Nothing in that sequence produced a single piece of information that did not already exist.
In short
- The problem
- An accounts payable seat spends most of the week moving numbers from a document somebody else already typed into a system that could have read it.
- Why it persists
- The judgement in the role is real, so the typing around it never gets separated out. Invoices stall in five identifiable places and most of them are a person not being at a desk.
- What we would automate
- Capture, the three-way match your paperwork actually supports, and the approval workflow up to the point of release.
- What stays with a person
- Releasing the payment run, any change to a supplier's bank details, genuine disputes, deciding what to hold, and a new supplier's first invoice.
Want the whole thing by email?
This paper, plus the rest of the library. One click to stop them.
1. What the Week Actually Contains
Read an accounts payable job ad closely and it describes three different jobs wearing one title. There is data entry: invoices arrive and their contents are typed into a ledger. There is comparison: the invoice is checked against what was ordered and what turned up. And there is chasing: an approval that has not come back, a supplier wanting to know where their money is, a statement that will not reconcile.
Only the middle one is really a decision, and even then only when the numbers disagree. The rest is transport and follow-up. That matters because it tells you what automation is worth here: not replacing the person, but deleting the transport so the person spends their week on the disagreements.
The volume is the part that surprises people. A business with a hundred suppliers and a few hundred invoices a month is not doing anything complicated, but it is doing the same eleven keystrokes several thousand times a year, and every one of them is an opportunity to fat-finger a bank detail or a due date.
The bottom line
A supplier invoice is a structured document that arrives as an unstructured one. Almost the entire cost of accounts payable comes from that single fact, and it is the part a machine handles best.
2. The Five Places an Invoice Stalls
Late supplier payments are almost never a decision to pay late. They are an invoice sitting in one of five places, and each one has a different fix. Knowing which is which is most of the work.
Worth noting: only the last of these is a cash-flow choice. The other four are process, and process is automatable.
It arrived somewhere nobody watches
Sent to a personal inbox, or to the person who left. It is not late yet because nobody knows it exists.
It cannot be coded
No purchase order, an unfamiliar description, a job number that means nothing to the ledger. It waits for somebody to ask around.
It does not match
The price, the quantity or the freight differs from what was ordered. This one deserves a person, and usually gets them weeks later than it should.
It is waiting on an approval
Sitting with a manager who is on site, in an email thread with no reminder attached to it. The most common cause of an aged creditor by a wide margin.
It is being held deliberately
A genuine cash decision. Fine, but it should be a decision somebody made on purpose, not the default outcome of the four above.
3. The Three Automations
Payables breaks into three pieces that are built separately, bought separately, and worth having separately. In order, because each one depends on the one before it.
3.1 Invoice capture
Invoices land in one monitored address instead of several inboxes, and arrival is logged before anything else happens. Each one is read (a PDF, a scan, a photograph of a docket, or the body of an email), and the fields that matter are extracted: supplier, ABN, invoice number, date, line items, GST, total, bank details, and any reference to a purchase order or job.
Extraction returns a confidence score per field, which is the part that makes the rest safe. A total read at high confidence can flow on untouched; a smudged handwritten docket goes to a person with the image beside the fields. Without that score you are choosing between trusting everything and checking everything.
3.2 Matching, and the blocker underneath it
The extracted invoice is checked against what was agreed. Where a purchase order exists, that means the order and, if receipt is recorded, the delivery: three documents, one question, were we billed for what we ordered at the price we agreed for goods that arrived.
Most businesses this size do not raise purchase orders consistently, so the honest default is two-way: this invoice against the authority to spend, and against what this supplier has billed before. Section four sets out all three depths and which one your paperwork actually supports. Buying the deepest version when the documents for it do not exist is the most common way an accounts payable project fails.
Agreement on supplier, price, quantity and total is the ordinary case and needs no human at all: it is coded and queued. Disagreement is the interesting case, and it is routed to a person with the specific difference already stated (“invoiced 24 units at $31.50, ordered 24 at $28.00”) rather than as an attachment to work out from scratch.
The more valuable half is often not the mismatch but the blocker: naming what a bill is actually waiting on, and for how long. An invoice stuck at sixty days for want of a purchase order number is not a payment problem, it is an admin problem wearing a payment problem’s clothes, and nobody finds it because nothing is watching for it. The same check pointed at your own creditors tells you which supplier relationships are about to get difficult.
3.3 Approval workflows
Approvals stop being email threads. An invoice over a threshold, or outside a matching tolerance, goes to whoever owns that spend with the supporting documents attached. The reminder is attached to the invoice rather than to somebody’s memory, escalates on a schedule you set, and every approval is recorded against the invoice with who and when. Nothing sits waiting silently, which is the single most common cause of an aged creditor.
The payment run then assembles itself: everything approved, coded and due, with duplicate detection and a bank-detail change check run before a person releases it. A person still releases it. That is deliberate, and section seven explains why.
4. Which Match Your Paperwork Supports
Everything upstream of the match is transport, and everything downstream is consequence. The match is where the money is, in both directions: it is the check that catches an overcharge, and it is also the step whose absence explains most of the invoices nobody can code.
What follows is the useful distinction between the three matching depths, because businesses often buy the third when the first would have solved their problem.
| Depth | What it compares | What it catches |
|---|---|---|
| Two-way | Invoice against purchase order | Price and quantity that differ from what was agreed. Cheap, and it finds most of it |
| Three-way | Invoice, purchase order and delivery record | Being billed for what never turned up. Needs someone to actually record receipt |
| No order to match | Invoice against history and a coding rule | The realistic case for most small businesses: no PO exists, so the check is against what this supplier normally bills and what it is normally coded to |
The honest version
Most small businesses do not raise purchase orders consistently, so a three-way match has nothing to match against. Pretending otherwise is how automation projects here fail. The third row is the one that usually pays, and it is also the one you can start on this month.
5. Key Benefits
One Way In
Every invoice arrives at one monitored address and is logged on arrival. Nothing is late because nobody knew about it.
Read, Not Re-Typed
Supplier, ABN, dates, line items, GST and totals extracted from the document itself, whatever format it turned up in.
Exceptions, Not Everything
Invoices that agree with the order are coded and queued. A person sees the ones that disagree, with the difference already stated.
Approvals That Chase Themselves
The reminder is attached to the invoice rather than to somebody's memory, so an approval cannot go quiet.
Duplicate Detection
The same invoice arriving twice, once by email and once with a statement, is caught before it is paid twice.
Bank Detail Change Alerts
A supplier's account number changing is the single most expensive event in accounts payable. It should never pass silently.
Statements That Reconcile
Supplier statements matched against the ledger automatically, so the monthly hunt for the missing two invoices stops being a task.
Supplier Queries Answered
"Where is our payment" is answerable from the ledger without interrupting anyone, and most of those emails never need a person.
6. End-to-End Workflow
- 1Invoice arrives at one monitored address and is logged on arrival
- 2Document read and fields extracted, whatever the format
- 3Supplier identified and matched to the ledger, or flagged as new
- 4Invoice compared against the purchase order, delivery record, or supplier history
- 5Agreement coded and queued automatically against the right account and job
- 6Disagreement routed to a person with the specific difference stated
- 7Approval requested from the owner of that spend, with reminders attached to the invoice
- 8Duplicates and changed bank details checked before anything reaches a payment run
- 9Payment run assembled from what is approved, coded and due, for a person to release
- 10Supplier statements reconciled and remittances sent, with exceptions listed
7. What Stays With a Person
Automating accounts payable badly is expensive in a way that automating most things is not, because the output is money leaving the business. So it is worth being specific about what should not move.
Releasing the payment run
A machine can assemble it perfectly and still be wrong about something nobody encoded. The release is cheap to keep human and expensive to hand over.
Any change to a supplier's bank details
This is the fraud vector in accounts payable. It should require a person, a call to a known number, and no exceptions.
Genuine disputes with a supplier
A contested amount is a relationship conversation. The machine's job is to surface it early and with the numbers already lined up.
Deciding what to hold
Paying late on purpose is a cash-flow decision belonging to whoever owns the cash position, not to a rule in a workflow.
A new supplier's first invoice
Onboarding is where the checks belong: ABN, GST registration, bank details, insurance if the work needs it.
8. Potential Tech Stack
One workable shape. The layers matter more than the specific products, and most businesses already own two or three of them.
| Layer | Options | Role |
|---|---|---|
| Accounting Ledger | Xero, MYOB, QuickBooks | Source of truth for suppliers, coding, purchase orders and what is owed |
| Intake | A monitored mailbox, supplier portal, Hubdoc | One way in, with arrival logged before anything else happens |
| Document Extraction | Claude, GPT-4o, Azure Document Intelligence | Reads PDFs, scans and photographs into structured fields with a confidence score |
| Matching Rules | Serverless functions, n8n, Make.com | Tolerances, coding rules, thresholds, duplicate and bank-change detection |
| Approvals | Teams, Slack, email with tracked state | Requests routed to the owner of that spend, with reminders on the invoice |
| Exception Queue | A simple internal dashboard | The list a person actually works, showing the difference rather than the document |
| Reporting | Looker Studio, custom dashboard | Touchless rate, exception reasons, days to approve, aged creditors over time |
A note on scope
This is a build rather than something you switch on. Our own product Office Voice works the other ledger (getting money in rather than out) so if the pressing problem is your debtors rather than your creditors, start with the receivables paper instead. For payables, the honest answer is a scoped project, and the first step is working out which of the five stalls in section two is actually costing you.
9. ROI Snapshot
Illustrative figures for a business processing about 400 supplier invoices a month with one person on accounts payable. Your numbers will differ: the point is which levers move.
60-80%
Touchless
Invoices that agree with the order or the supplier's history and need no human at all
Days
Off approval time
Driven almost entirely by reminders being attached to the invoice rather than to a person
Zero
Duplicate payments
The same invoice arriving by email and again on a statement is the classic double payment
The gain that shows up in the accounts is rarely the labour. It is the early payment discounts you stop missing, the duplicate you stop paying, and the overcharge that gets questioned in week one instead of at the end of the quarter.
10. Getting Started
- 1
Count the invoices and the formats
How many a month, and how many arrive as email bodies, PDFs, scans, or photographs of dockets. The format spread decides how hard the extraction is.
- 2
Find out how many have an order to match against
If the answer is 'not many', you are building the third row of section four, not a three-way match. Knowing that up front saves the project.
- 3
Time the approval step
Pull the gap between invoice received and invoice approved for last month. This is usually the largest single number and the cheapest one to fix.
- 4
Write the tolerances down
What price variance passes without a human, what dollar value needs approval and from whom. This is the actual product decision, and it is yours.
- 5
Start with one supplier group
Pick your twenty highest-volume suppliers with consistent invoice formats. They are most of the volume and least of the difficulty.
Not ready to talk yet?
Leave your email and we’ll send this paper to your inbox, with a link to the rest of the library. We publish a new one every few weeks and you’ll get those too, one click to stop them.
Your email is used to send you the papers and nothing else. We don’t share it.
Hiring for the typing, or for the judgement?
Get in touch with AI Pathway. We will look at how your invoices arrive and tell you which part of the pipeline is worth automating first, or whether a change to how suppliers send them gets you most of the way there for nothing.