AI agent · Retail & e-commerce · Match & reconcile
Supplier invoice matching
The agent reads each supplier invoice, finds the purchase order and the goods receipt, and matches them line by line. Invoices that agree within tolerance are posted; exceptions arrive with the reason they failed and the person who can fix them.
Typical volumes for this process, not a client figure.
Invoice, order, receipt — three documents, one person.
Matched three ways; exceptions with the reason they failed.
Where the time goes today
A retailer buys from hundreds of suppliers, and each invoices in its own layout: PDFs by email, portal downloads, structured files from the larger ones, the odd paper invoice. An accounts payable clerk checks the header, then compares each line with the purchase order for price and with the warehouse receipt for quantity. Retail adds its own complications. One order for forty lines arrives in three deliveries and is invoiced twice; invoices carry promotional allowances, deposits on returnable crates and freight that appear nowhere on the order.
Time goes on lookups: finding the order number the supplier did not quote, translating the supplier's item codes into yours, deciding which receipt belongs to which partial invoice. Errors run the other way: a price increase paid without anyone agreeing to it, a short delivery paid in full, a credit note never applied, the same invoice paid twice under a reformatted number. Exceptions sit in an inbox with no reason attached, so the buyer asked to resolve one has to redo the clerk's work first.
How the agent works
- Read the invoiceThe agent reads the header (supplier, invoice number, dates, currency, tax) and every line (item, quantity, unit price, allowances, charges), whatever the layout.
- Find order and receiptsIt locates the purchase order from the quoted number or, when there is none, from supplier, items, dates and amounts. Supplier item codes are mapped through your cross-reference; a new mapping is used only after a person confirms it.
- Match line by linePrice is compared with the order, quantity with what was received and not yet invoiced, and charges with the agreed terms, using the tolerances finance has set.
- Check for duplicatesIt compares the invoice with those already posted: same supplier, similar amount and date, a number that differs only in formatting.
- Post or explainInvoices within tolerance are posted for the normal payment run. The rest go to an exception queue with the reason in words, such as unit price above the order on three lines, and are routed to the buyer or the receiving team.
What stays with a person
People decide what an exception means: whether a price difference was agreed by phone, whether a short delivery will be completed or credited, whether to pay the undisputed part now. Buyers and receiving staff own those answers. The agent brings them the three documents side by side and records what they decide.
People also own the tolerances and the supplier master data. The agent never adds a supplier, changes bank details or accepts a new item mapping on its own, because those are the points where payment fraud gets in.
What it reads, what it produces
| It reads | It produces |
|---|---|
| Supplier invoices and credit notes: PDF, structured e-invoice, EDI, scans | Posted invoices, each linked to its order and receipt lines |
| Purchase orders and their amendments | An exception queue with the reason and a suggested owner |
| Goods receipts and warehouse receiving records | Duplicate alerts, held before posting |
| Supplier master data and the item cross-reference | Lists of receipts not yet invoiced and invoices waiting for a receipt |
| Agreed price lists and promotional or allowance agreements | |
| The payables ledger: posted invoices and payments |
Controls that come with it
- Price and quantity tolerances are set per supplier or category by finance; the agent never widens them.
- Invoices above an amount threshold go to a person even when they match.
- A weekly sample of auto-posted invoices is re-checked, sized from what an escaped overpayment costs against the time the review takes.
- No changes to supplier records or bank details by the agent, under any circumstances.
- Each line records the invoice line, order line, receipt, tolerance applied and outcome. A posting can be reversed before the payment run, which keeps its existing approval.
How you know it works
- Share of invoices posted without a person, and how many of those the weekly sample finds wrong
- Days from invoice receipt to posting, and early-payment discounts missed
- Age of open exceptions, and exceptions reopened after resolution
- Overpayments and duplicate payments recovered after the event
Is your process ready?
- The matching rules are written: tolerances, and how to treat freight, deposits, allowances and partial deliveries.
- The ERP exposes orders, receipts and posting through an interface or export, and its licence permits a software user to post.
- A match can be checked in seconds with the three documents side by side.
- Invoice volume and supplier count make matching a daily workload, not an occasional one.
- Payables, buying and the warehouse describe the exception flow the same way. If each team believes another owns price differences, settle that first.
The five candidacy checks are explained, with an exam, in the free Module 01.
What goes wrong
- Receipts are entered late or in bulk at the warehouse, and the agent raises exceptions against an incomplete receipt. Set a waiting window before a missing receipt counts as an exception.
- Supplier item codes were never mapped to your catalogue, and the first months go on building the cross-reference.
- Promotional allowances and retrospective rebates are agreed outside the order system. Unless those agreements are readable, every promotional invoice becomes an exception.
- Tolerances are widened to raise the auto-post figure, which lets small overcharges through at volume.
- Credit notes are matched to the wrong invoice when a supplier nets several invoices together.
Questions we get
Does it replace the matching function in our ERP?
Usually not. ERP matching works when the data arrives clean and structured, as it often does from large suppliers sending EDI. The agent handles what comes before and around it: reading invoices in any layout, finding the order when none is quoted, mapping item codes and explaining exceptions. Where your ERP already matches a supplier well, keep it.
How does it handle partial deliveries and split invoices?
It tracks, per order line, what has been received and what has already been invoiced. An invoice can consume part of a receipt, and the remainder stays open for the next one. If an invoice arrives before its goods, the agent waits for a set period before raising an exception, so the receiving team is not flooded with timing differences.
What stops it posting a fraudulent invoice?
It does not pay anything; it posts for your existing payment run and its approvals. It never changes supplier bank details, flags invoices from new suppliers or with changed payment details, checks for duplicates, and sends large amounts to a person. These controls reduce the risk. They do not replace your payment approval or your supplier verification procedure.
How should we set the tolerances?
Start from your current policy and run the agent on past invoices whose outcome you know. You see how many would have been posted automatically and how many of those were later disputed. The rest is arithmetic: the cost of a small overpayment slipping through against the cost of a person reviewing it. Finance owns the numbers and signs them off.
Want this agent on your process?
Tell us about your version of this process — volumes, systems, what goes wrong. A person answers with an approach and a price, usually within two working days, or tells you it is the wrong project.