Document reading
Read every line
and show its source
Every line of every invoice is read, from a clean PDF or a scan, and checked against the printed total.
What it reads
Header, lines, and the shape of the table
Every header field
Invoice number, dates, vendor, totals, tax, PO number and terms — plus a prepaid “do not pay” detection.
Every line, with its box
Description, quantity, price, SKU and more, each with its page position for highlighting on the PDF.
Who it is from
Vendors are fingerprinted from the first page. A vendor with a profile gets its tuned prompt and column map automatically.
Self-healing
It knows how many rows there should be
Rows are counted before extraction; missing rows, mangled PO numbers and dates are recovered.
- Verification pass with an automatic correction-and-retry loop
- Every read reconciled against the printed total
- Anything that fails is flagged for a human, with the reason recorded
- VendorAcme Utilitiesfingerprint
- Invoice #INV-1001p.1
- Line 2East site · 980.50p.1 · box
- Total2,956.25printed
Vendor profiles
The second invoice from a vendor is easier than the first
A tuned prompt, column map and examples, used automatically for that vendor’s next invoice.
- Learned by fingerprint: vendor name plus column-header signature
- Statements, credits, receipts and prepayments recognised and routed, not coded by mistake
- Scans and photographs inside a PDF are read by OCR and vision
Reading,
answered
Send it inside a PDF; scanned or photographed pages are read by OCR and vision. Email attachment types are configurable.
The composed total must equal the printed total, or the document is flagged instead of posted.
Gemini and OpenAI behind one interface. Models read; they never make the accounting decision.
See your own invoices read
Bring the ugliest scan you have. We will show you every value, where it came from, and whether it reconciles.