Supplier invoices read automatically: a plant wholesaler with 150 invoices a week
A prototype that reads Excel, PDF and photos, checks the arithmetic and asks for confirmation only on uncertain lines, before they enter the management system. It runs on the computer the office already has.
A plant wholesaler receives supplier invoices, from abroad and from Italy, by email: an Excel file, a PDF, sometimes a photo of a sheet. Every line has to be retyped into the management system, with the right item, price band, markup, customer and carrier. One person in the office did it by hand. This page tells what we measured, what I built and what is still to be verified. The status is prototype: the "after" numbers are estimates, to be confirmed on real invoices.
What was it like before?
- About 150 invoices a week: 50-70 on Wednesday and Friday mornings, about ten on the other days. About 7,200 a year.
- Timed on the office videos, a 16-line invoice took about 4 minutes; a 2-line one with a new item, 2 minutes 40.
- On Wednesdays and Fridays invoices took about 4 hours, the whole morning. Over a year, about 480 hours.
- The arithmetic (quantity times price, goods total, VAT, customs groups, plant passport) was checked by eye, when there was time.
- Only one person knew the usual choices.
What does the prototype do?
- Reads the mailbox read-only: picks supplier emails with Excel, PDF or photos, with no duplicates.
- Reads the document: Excel columns, PDF tables, and crooked or blurry scans with text recognition running on the processor, in about 5 seconds a page.
- Checks every invoice's arithmetic: packages times pieces, quantity times price, line totals, taxable amount, VAT, total, customs groups, plant passport.
- Proposes the system item, price band, markup, customer and carrier.
- Asks for confirmation only on uncertain lines, marked yellow: usually 0 to 2 per invoice.
- Prepares the file in the folder the management system imports into the delivery note.
How does it learn from corrections?
Every confirmation and correction is recorded. A rejected proposal does not come back for the same description; the supplier's description becomes a synonym of the chosen item, valid even for codes never seen; and the criteria (name, pot, height, price, supplier) are reweighted on the confirmed lines. One correction counts as three confirmations. So yellow lines drop over time, and the usual choices no longer depend on one person.
How much time does it save?
Estimates, to be verified by timing the first two weeks of real invoices:
- Today: about 480 hours a year.
- With the prototype, file in the system's folder: about 1 minute per invoice, about 120 hours a year, three quarters less.
- With the system connected directly: about 30 seconds per invoice, about 60 hours a year.
On Wednesdays and Fridays, from about 4 hours to about 1: the morning is free again, and more invoices can be handled without adding people.
Where does the data go?
The prototype runs on the office computer, processor only, with no new hardware. In the demo an online model receives only the uncertain product lines, never customer data; in production only models installed in the company are used, and nothing leaves.
What is missing to go live?
Two things, stated plainly: real invoices from all suppliers, to measure before and after, and the archive formats from the management system's vendor, to write directly into the system instead of the folder. The link is built with them, as in any business software integration.
Would it work for you?
If you receive invoices, delivery notes or orders as Excel, PDF or photos and retype them into your system, yes: the checks and fields change, the method is the same. It is described on the page about automatic reading of delivery notes and invoices. For this client I also lead the technical side as a fractional CTO. More work in the portfolio.
If you like, send me ten real documents and a few lines on how you handle them today: I will reply in writing with a proposal and a quote.