Invoice Reading and Pre-Accounting

An invoice photographed on site, the night before closing

A subcontractor’s invoice sometimes arrives as a phone photo, taken on the bonnet of a van next to a hand-annotated delivery note. The accountant still has to match it against the purchase order, check the VAT, and assign it to the right cost centre before the month closes.

What breaks once you leave the demo

A reading engine trained on clean PDFs extracts totals from a standard invoice well enough. Faced with a blurred scan, a handwritten invoice, or a document with crossings-out, it produces wrong values with the same confidence as an easy case. The promised time saving disappears if every proposal has to be checked line by line regardless, and a pilot built only on the tidiest invoices will look better than the process it is meant to replace.

Channels that are already settled

This works only if invoices arrive through a limited, identified set of channels, a dedicated inbox or a supplier portal, rather than scattered across site managers’ personal mailboxes. It also assumes a chart of accounts and coding rules already exist, even informally, and that finance has agreed an acceptable confidence threshold. Where supplier names shift month to month or cost centres get redefined mid-year, maintaining the system eats into the time it was meant to save.

A proposed entry, never posted on its own

We extract supplier, amounts, VAT and billing lines, then match the invoice against its purchase order where one exists. Every proposed entry carries a visible confidence score. Below the agreed threshold, it goes straight to an accountant for manual review; above it, it still waits for validation before anything is posted.