Case
Supplier email → document in the accounting system
An invoice from a PDF becomes a draft receipt without typing.
≈ the owner's estimate from his own experience
Before
Supplier invoices and goods receipts arrived by email as PDF or Excel files. Someone opened them, created a document in the accounting system and typed the items by hand. An hour or two a day, and errors in the numbers that surfaced during reconciliation.
What I built
- The mailbox reads itself: every email is classified — invoice, goods receipt, payment, not a document.
- The attachment is parsed: PDF and Excel, with its own parser for each regular supplier.
- A draft goods receipt, invoice or payment appears in the accounting system, with the counterparty, the items and the totals.
- The operator checks it and posts it. Anything unrecognised is parked for review.
After
A draft a minute after the email. Checking instead of typing.
What it gave
Documents are in the books on the day they arrive, not when someone got round to them. Balances with suppliers are accurate, and reconciliation stopped being an event.
For your company
The parsing is set up around your suppliers and your documents: for some companies that is invoices and goods receipts, for others price lists, acts and customs papers. What the system posts by itself and what it leaves for a person to check is your rule: you can start with an operator looking at every draft, and relax it later.
Stack: Python, IMAP, PDF and XLSX parsing, email classification
Related service: Documents from email into the accounting system