Reading the invoice is the easy part.
Most tools can read an invoice now. The value is in what it is checked against, and that work starts with the order.
Reading invoices used to be the hard part. A supplier sends a PDF, a scan, a photo of a folded sheet or a structured e-invoice, in whatever language it trades in, and somebody types it into the accounting system. Software that did the typing was the whole promise.
That part is largely solved. A model can now read a crooked scan in Spanish and a clean PDF in English, and most finance teams can buy that capability off the shelf. If reading is all a system does, it is a commodity, and it is priced like one.
An invoice is only right against something
A correctly read invoice can still be wrong. The price may not be the one that was agreed. The line may be for something nobody ordered. Reading tells you what the supplier says. It cannot tell you whether the supplier is right.
To know that, the invoice has to be checked against two things: the order it answers and the price the business agreed. Both have to exist before the invoice does, in a form a machine can use. In many businesses they do not. Orders live in a message to a supplier or a notebook by the stove. Agreed prices live in an email from last spring, or in the memory of one buyer.
So the work starts earlier than the invoice. It starts with the order.
Four steps, one flow
The way we build it, purchasing and finance run as one flow.
Orders follow the forecast. Each site’s order is drafted from what it expects to use and what it already has in stock. The person who runs the site confirms it, and from then on the order is a record, not a recollection.
One best price, every site. When the group agrees a price with a supplier, every site orders at that price. A site that pays more is no longer a surprise found months later. It is a line flagged on the next invoice.
The invoice, checked against both. In any language and any format, each line is read and compared with the order and the agreed price. A difference is flagged with its reason, and a person decides what happens to it.
The close as a by-product. Orders, deliveries and invoices are matched as they arrive. When the month ends, the close starts from lines that already agree, instead of from a pile of documents nobody has looked at together.
Only the third step is about reading. It is the visible one, and the easiest to copy.
Rules we build to
A price typed by a person stays. When a buyer corrects a price by hand, no automatic update overwrites it. The system can show the price it would have used next to it, and flag the gap. It does not undo a human decision.
Every list of suggestions ends with “none of these”. When the system proposes the catalogue item an invoice line refers to, the person reviewing it can always say that no suggestion is right. A list without that option teaches people to pick the least wrong answer, and the error goes into the books looking validated.
Numbers are read with their conventions. On a Portuguese invoice, 1.250 is twelve hundred and fifty. On an English one, it is one and a quarter. A system that reads the digits without the convention is wrong by a factor of a thousand, with complete confidence.
Nothing uncertain reaches the accounts. Syntexia prepares the entry, and anything it is unsure of waits for someone with the authority to post it.
Where to start
If you want to know whether this would work for your business, the first question is not about invoices. It is where your orders and your agreed prices live today. Tell us, and we will show you what the first step looks like.