Invoices that read themselves — inbox to structured books
Jessy Mariau
The most boring job in any business: supplier invoices arrive as email attachments, and someone retypes them into the books. It's slow, it's error-prone, and it's exactly the work nobody should still be doing by hand.
Inbox → AI → structured books
How it reads them
An inbox pipeline watches for invoices over IMAP, hands each one to Gemini to classify and extract — supplier, line items, totals, dates — and applies the structured result straight into a Postgres/Supabase ledger. It was hardened against a reliability corpus of real invoices, so it holds up on the messy documents suppliers actually send, not just clean samples.
Where it runs
Inside BakeryOS, a production operations platform. (The visual above is synthetic — real supplier identities never leave the system.)
The same inbox→extract→apply shape lifts onto any document-heavy back office — invoices today, contracts or receipts tomorrow.
Like this project
Posted Jul 12, 2026
Supplier invoices arrive as PDFs in a mailbox and leave as structured rows in the books. IMAP watches, AI reads the document, the numbers land in Postgres — and anything it isn't confident about gets flagged for a human rather than quietly guessed.
