Supplier invoices arrive by email, in different layouts, and each one has to be checked against what was ordered and what actually turned up. The improved process collects them in one place, reads the key details, matches each invoice to its order and delivery note, and puts the ones that don't agree in front of a person with the difference spelt out.
The system prepares the match. It never approves an invoice, never pays one and never changes anything in the accounts until a named person has said yes.
The job today
Invoices land in a shared mailbox or someone's personal inbox. The bookkeeper opens each one, finds the matching purchase order in one system and the delivery note in another, checks quantities and prices by eye, then keys the invoice into the accounts. Queries go back to the supplier by email, and the thread is easy to lose. At month end there is a scramble to work out what has been received but not yet invoiced.
Where it breaks
- Invoices sit unopened in personal inboxes, so due dates are missed or early-payment terms are lost.
- Price and quantity differences are only spotted if someone happens to look closely.
- The same invoice can be entered twice when a supplier sends a reminder copy.
- Nobody has a clear picture of what has been spent against each order until the month is closed.
The improved process, step by step
- Collect invoices in one placeInvoices are forwarded to, or sent directly to, one address. Each one is saved with the email it came from, so nothing lives only in a personal inbox.
- Read the key details AI preparesThe system reads supplier, invoice number, date, lines, totals and VAT from each document, and flags any it cannot read clearly.
- Match to order and deliveryEach invoice is checked against the purchase order and delivery record using rules you agree: right supplier, right items, quantities and prices within your tolerance.
- Flag duplicates and differencesPossible duplicates and any line that doesn't agree are listed with the difference shown side by side, ready for a decision.
- A person approves for payment A person approvesThe bookkeeper or budget holder reviews matched invoices and the exceptions, and approves which go into the accounts and the payment run. Nothing is posted without that approval.
- Track spend against each orderApproved invoices are recorded against their order, so actual spend is visible as it happens rather than at month end.
Where a person must approve
A named person approves every invoice before it is posted to the accounts or added to a payment run. Anything that sends, changes or cannot be undone waits for that approval.
Queries to suppliers can be drafted for you, but they are only sent when a person has read and approved them.
The data boundary
- The system can read invoices, purchase orders and delivery records. It cannot make payments, change supplier bank details or post to the ledger on its own.
- Supplier bank detail changes are never taken from an invoice or email. They are always checked by a person through a known contact.
- Documents stay in your own systems and mailbox.
- Every reading, match, flag and approval is logged with who did what and when.
Checklist before you start
- We know where supplier invoices arrive today, including personal inboxes.
- Purchase orders and delivery records exist somewhere we can read them.
- We have agreed tolerances for price and quantity differences.
- We know who approves invoices, and the limit for each person.
- We have a rule that bank detail changes are always confirmed by phone.
- We know how our accounts software accepts approved invoices.
This is an illustrative walkthrough of a common pattern. It is not a client case study, and the details will differ in your organisation.