Reading the invoice is the easy half.
Anything can pull a total off a page. The expensive mistakes are not on the page at all: the invoice that arrived twice, the supplier whose bank account quietly changed, the beef that costs a quarter more than it did in March. None of those is visible in the document you are holding. All of them are obvious across the pile.
Two live demos. Pick one.
Step 1 of 3
September's paperwork, nobody has opened it
30 documents: supplier invoices from the kitchens, and two invoices going out for function bookings. Nothing has been read, so nothing yet knows which are money in and which are money out. Fifteen more from March onwards are already on the books, which is what makes the next step possible.
30 scans, nothing opened
Click any one to see the page. Supplier, amount and direction stay unknown until they are read.
Every company, person, price and account number here is invented for the demo, and the IBANs are not valid. What is real is the checking: anything found here is produced by running the same functions the test suite runs, over these documents. Nothing on this page is a sentence somebody typed in advance — change a number in the data and the finding moves or disappears with it.
Everything above runs on invented documents, which is exactly as convincing as any other demo. So drop a real one. It is read in your browser, sent once, and never stored, and the same checks run on it.
Drop a folder of invoices here.
Photos, scans or PDFs. They are read in your browser, sent once, and never stored. Up to 20 at a time on this demo.
None of these need a person. All of them need more than one piece of paper, which is exactly why a person doing it by hand misses them — the evidence is spread across documents read weeks apart.
Is this the same invoice twice?
Matched on the supplier's own reference, which is the only thing that actually proves it. Buying the same case of chicken twice in a week is not a duplicate, and a check that says it is gets switched off by Friday.
Has this supplier changed their bank account?
The commonest large fraud in business: a real looking invoice with somebody else's account on it. Nobody remembers the IBAN from March, so nobody catches it. Comparing against every previous invoice does.
Does the invoice agree with itself?
Line items, VAT, total. A printed total is what gets paid and the line items are what got agreed, and when they differ it is money moving for a reason nobody can point at.
Did what was billed actually arrive?
The invoice against the signed delivery note, matched on the item rather than the row order. Somebody signed for it at six in the morning without knowing what any of it cost.
Has the price moved?
The same line across months. No single invoice is wrong: beef at 22.60 in September is a perfectly correct invoice. It is only wrong next to the same line at 18.40 in March, and nobody has both pages open.
Is this money in or money out?
Decided from who the document is addressed to, not from what it looks like. When neither party is you, it says so rather than guessing — revenue filed as a cost is a wrong set of books, not a typo.
What changes: the checking stops depending on somebody remembering.
Every one of these is a control your accountant already knows about and already means to do. They are skipped for the same reason every time: doing them properly means finding a document from three months ago, and there is a payment run this afternoon. A supplier invoice that agrees with itself, arrives once, matches the delivery note and asks for the account it always asks for is the normal case. Catching the one in forty that does not is worth more than the typing, and it is the part nobody has time for.
Nothing above replaces your accounting system. It sits in front of it and decides what should be allowed to reach it.
Tell us how many supplier invoices you get in a month, what has to be checked before one is paid, and what your accounting sits in. That is enough for us to tell you whether this fits.
Or email hello@ahlelak.com