How to automate invoices with AI, step by step

Learning how to automate invoices with AI starts with one question: where does a supplier bill sit between arriving and being paid? In most small firms the answer is an inbox, a spreadsheet and one person who checks every bill by hand. This guide walks through the five steps, the matching logic behind them and the places where it goes wrong.

How to automate invoices with AI: what the system actually does

An invoice automation has six jobs: capture the bill, extract its fields, match it to what you ordered, flag anything odd, code it to the right accounts and post it to the ledger. AI does the reading and the suggesting. The matching and posting should run on rules you can see and change. That split matters, because when something goes wrong you need to know whether the reader misread a number or the rule did the wrong thing.

Vendors describe the goal in similar terms. Tipalti says AI agents can route invoices to the correct workflow and apply the right GL accounts, cost centres and tax codes, which cuts manual work and improves coding accuracy (Tipalti, https://tipalti.com/resources/learn/ai-invoice-processing). Domo advises starting with high-volume invoices that follow consistent logic, such as standard purchase-order invoices from recurring suppliers (Domo, https://www.domo.com/glossary/invoicing-ai-agents). That advice is the right filter. If you get thirty bills a month from twelve suppliers, start there. If every bill is a one-off with its own terms, automation will mostly generate exceptions.

Step 1: Audit your current invoice flow and find the bottlenecks

Before you buy anything, map the process as it runs today. Domo recommends mapping how invoices are received, processed, approved and posted, then looking for delays, manual touchpoints and handoffs where errors creep in (Domo, https://www.domo.com/glossary/invoicing-ai-agents). Write down each stage and who owns it.

For each stage, record four numbers: how many invoices pass through per month, how long a typical bill waits there, how often it bounces back, and how many minutes of a person's time it takes. Then check what share of your volume comes with a purchase order and how many suppliers account for most of your spend. A firm where most bills arrive without a PO is looking at a different, slower project.

The output of this step is a one-page list of bottlenecks ranked by time lost. That list tells you which step to automate first, and it gives you a baseline to measure against later. Our AI Systems & Automation service starts from $499 and typically takes 1 to 3 weeks, but the real cost of your project depends on how many suppliers, systems and approval levels you have, so scope it from this audit rather than from a price list.

Step 2: Capture and extract data from incoming invoices

Capture means getting every bill into one place. The common routes are a dedicated AP mailbox, a supplier portal, and scanned paper. Set up email rules so anything with an invoice attachment lands in the same folder, and forward supplier emails there rather than to individual staff. If bills arrive by post, scan them the same day.

Extraction is where the AI reads the file. Microsoft's prebuilt invoice model is trained to recognise common fields such as invoice ID, invoice date, amount due and PurchaseOrder reference (Microsoft Learn, https://learn.microsoft.com/en-us/ai-builder/prebuilt-invoice-processing). Its guidance is to provide one clear scan or photo per invoice, in JPEG, PNG or PDF, under 20 MB (Microsoft Learn, https://learn.microsoft.com/en-us/ai-builder/prebuilt-invoice-processing). Multi-invoice PDFs, faint photos and handwritten notes in the margin are the usual reasons extraction fails, so tell your suppliers what you need.

You don't need an enterprise platform to start. A VectorShift tutorial shows a Gmail-to-Google Sheets workflow that detects invoice PDFs, extracts structured data, stores it in a sheet and emails an AI summary, with no coding (YouTube, VectorShift tutorial, https://www.youtube.com/watch?v=HV__T4zGNwg&vl=en). One practitioner on Reddit reported saving 5 to 6 hours a week by doing this for invoice entry (Reddit, r/smallbusinessowner, https://www.reddit.com/r/smallbusinessowner/comments/1qvs56r/how_i_automated_invoice_entry_from_gmail_to/). That is one person's account, not a benchmark, but it shows the scale of time a basic setup can recover.

Step 3: Match invoices to purchase orders and receipts

Matching is the core of invoice control. It answers one question: did we order this, did we receive it, and does the bill agree with both?

Two-way matching compares the invoice with the purchase order. The system finds the PO number on the invoice, then checks supplier, line items, quantities, unit prices and totals against the PO. Three-way matching adds the goods receipt, the record that someone confirmed delivery, and checks the invoice against both the PO and the receipt. Three-way is the safer default for physical goods. Two-way is often enough for services or subscriptions where there is no delivery to log.

The logic runs in order. If the PO number is missing or not found, the invoice is an exception. If the supplier does not match the PO, it is an exception. Then each line is compared. Quantities should not exceed what was ordered or received. Unit prices should match the PO. Totals should sit within a tolerance you set with your finance lead. Tolerances are a policy choice. Many firms start tight, for example a small fixed amount or a low percentage, and widen it only after they have seen the exceptions it produces.

Two-way matching

Documents

Purchase orderGoods receiptSupplier invoice

Checks

Supplier and PO numberQuantities and line itemsUnit prices and totals

Result

Pass to codingRoute to exception

Worked example: matching one invoice

The figures below are made up to show the method. They are not from a real supplier.

Inputs:

• Purchase order: 40 units at £12.50 each, net £500.00
• Goods receipt: 40 units received in full
• Supplier invoice: 40 units at £13.00 each, net £520.00
• VAT at the UK standard rate of 20%
• Tolerance set by policy: 1% of the PO value, or £5, whichever is lower

Steps:

1. PO number found and supplier matches. Pass.
2. Quantity: invoice 40, received 40. Pass.
3. Unit price: invoice £13.00, PO £12.50. Difference £0.50 per unit, £20.00 in total, which is 4% of the PO value. Fail, because it is outside the tolerance.
4. Route to the budget holder as a price variance exception.

If the budget holder approves the higher price, the invoice goes through with the variance recorded. If not, the supplier is asked for a credit note or a corrected invoice.

VAT check on the invoice as billed:

• Net: 40 × £13.00 = £520.00
• VAT at 20%: £520.00 × 0.20 = £104.00
• Gross: £520.00 + £104.00 = £624.00

The point of the example is that the system does not decide to pay or reject. It finds the £20 difference, applies the tolerance and sends the decision to a person who can act on it.

Step 4: Flag exceptions and route them for approval

An exception is any invoice the rules cannot pass cleanly. Common types are: no PO, price variance, quantity above what was received, possible duplicate, new supplier, bank details changed, missing VAT number, and amounts above an approval threshold.

Routing should follow the type of problem. A missing PO usually goes to the AP clerk, who either finds the order or asks the requester to raise one. A price or quantity variance goes to the budget holder who placed the order. Anything above a set amount goes to a director. Write these rules down before you switch anything on.

The correction path is where most small firms get vague, so be specific. The person who resolves an exception should correct the source of the error, not overwrite the extracted number silently. Re-run the match after the correction. Log the reason in the record, for example 'supplier re-issued invoice at agreed price', and keep the original PDF attached. If the same exception keeps recurring for one supplier, fix the supplier or the PO process rather than clearing it by hand every time.

Confidence tiers help here too. Yooz describes an approach where high-confidence coding is populated automatically, medium-confidence coding is recommended for review, and low-confidence coding is left to the user (FinTech Magazine, Yooz press release, https://fintechmagazine.com/globenewswire/3385517). That is a sensible model to copy even if you use a simpler tool: the system should be most confident where it has the most evidence, and least confident where a human should decide.

Step 5: Code to the GL, cost centres and tax codes, then post to accounts

Coding is the step that turns a matched invoice into a ledger entry. Each invoice needs a general ledger account, a cost centre or department, and a tax code. Most of this can come from the supplier record and the PO. A stationery supplier defaults to the office supplies account. The PO carries the cost centre of the person who raised it. The tax code follows the supplier's VAT treatment.

In the first few months, review coding before anything posts. Check a sample every day, then every week once the error rate is low. Posting can be a direct integration with your accounting software or a scheduled import file. Either way, keep a record of what was posted, when and under which rule, because your accountant will ask.

Don't automate posting for a supplier until its coding has been right for a stretch of invoices you have checked. Coding errors are quiet. They don't show up as failures, they show up months later in management accounts.

Failure points to watch and how to control them

Most invoice automation failures are not dramatic. They are small errors that repeat because nobody is checking. The table below lists the ones that matter most for a 5 to 100 person firm.

Failure point	What it looks like	Control
Misread numbers	Wrong total or invoice number after extraction	Sample check against the original PDF; track error rate by field
Wrong coding	Costs in the wrong account or cost centre	Supplier default codes; review before posting; monthly reconciliation
Duplicate invoices	Same bill entered twice, or re-sent and paid again	Duplicate check on supplier, invoice number, date and amount
Tolerance drift	Small variances accepted again and again	Log every variance; review the top suppliers quarterly
Bank detail change fraud	A 'new bank account' email from a supplier	Changes need a call-back to a number already on file, plus a second approver
Approval bypass	Invoices posted without the right sign-off	Thresholds enforced by the system, not by habit
No audit trail	Nobody can say who changed what	Keep the original file, the extracted data, the rule applied and the approver

Measure accuracy before you trust the system. Take 50 invoices, key them by hand, then compare the extracted output field by field: supplier name, invoice number, date, total, PO number and GL code. Work out the error rate for each field. Run the system in shadow mode, where it suggests but doesn't post, for a month, and set a threshold you agree in advance. Fifty is a practical sample size for a first check, not a statistical rule, so repeat the test as your supplier mix changes.

If your invoices contain personal data, such as named contacts or individual sole traders, factor that into your set-up. The ICO's position on AI agents is worth reading before you give any system access to a ledger (see our summary at /blog/what-ico-says-about-ai-agents).

Choosing a tool for a 5 to 100 person firm, with a rough starting path

There are three rough tiers, and the right one depends on your volume and how much control you need.

• DIY setup (Gmail, Google Sheets and a workflow tool): cheapest to start, fine for low volume and light matching. Weak on approvals and audit trail, so you will need to build those carefully yourself.
• OCR-based builder (for example Microsoft's prebuilt invoice model inside a low-code platform): better extraction, useful if someone in the team is comfortable building flows. It still needs your own matching and approval logic.
• Enterprise AP platforms (for example Tipalti): built for approvals, payments and multi-entity ledgers, with more set-up effort and a higher cost. Get written quotes, because pricing depends on vendor, volume and modules.

A roadmap that works for most small firms looks like this:

1. Run the audit and rank your bottlenecks.
2. Pick one group of recurring suppliers with consistent POs.
3. Set up capture and extraction into a single sheet or AP system.
4. Add two-way or three-way matching for that group, in shadow mode.
5. Add approval routing and the duplicate and bank-change controls.
6. Turn on posting for the group once coding has been accurate for several weeks.
7. Extend to the next supplier group.

We cover tool choices in more detail in our roundup of the best AI automation tools for small business (/blog/best-ai-automation-tools-for-small-business), and our AI Systems & Automation service (/services/ai-automation) covers builds of this kind.

Where to start

• Map your invoice flow and count monthly volume and PO coverage.
• Pick the one supplier group with the most predictable invoices.
• Write down your tolerances, approval thresholds and bank-change rule before you build anything.
• Test extraction on 50 real invoices and measure the error rate by field.
• Run in shadow mode for a month before letting the system post.

For a fixed view of what automation could save you, read whether it is worth it for your size of business (/blog/is-ai-automation-worth-it), then how to measure the return (/blog/how-to-measure-ai-automation-roi). If you want a second pair of eyes on your invoice flow, the Free AI Audit is a free, no-obligation 30-minute call with a strategist who will list the top tasks AI could take over and leave you with a plan you can keep. You can get a free AI plan at /go/free-ai-plan or book a call at /book.

Sources

• Tipalti
• Domo
• Microsoft Learn
• FinTech Magazine (Yooz press release)
• YouTube (VectorShift tutorial)
• Reddit r/smallbusinessowner