Your invoices, read and filed. Without anyone typing.
An invoice lands in your inbox. The system reads it, checks it, and files or posts it where it belongs. Anything unusual waits for a person. Live in 2 days to 2 weeks.
- Built to SOC 2 controls
- GDPR aligned · DPA on request
- Private AI on your own servers: yourtrained.ai
- fromNorthwind Ltd
- date02 Sep 2026
- net4,000.00
- VAT960.00
- total4,960.00
One example. The invoice arrives by email, gets read into clean fields, checked, and filed where it belongs. A person approves anything unusual.
- From €2,500
- One-off, or €2,000 setup + €200/mo run
- 5 steps
- Arrives, read, checked, filed, matched
- 2 days to 2 wks
- First call to live
One invoice, inbox to ledger, every step drawn.
This is the pipeline we run on our own books, drawn as it runs: the mail lands, the page is read into ten fields, four checks run, a person is asked only when something does not add up, and the invoice is filed, matched and posted. The values are examples. The month’s count is real.
- 09:14
Contabo billing
Invoice CN-2026-08-4471
- Mon
Bank
Your statement for July is ready
- Mon
Calendar
Weekly planning moved to 10:00
- SupplierContabo
- Invoice numberCN-2026-08-4471
- Date03 Aug 2026
- Due date17 Aug 2026
- CurrencyEUR
- Net148.00
- VAT rate19%
- VAT28.12
- Total176.12
- PO referencePO-2026-0412
- Net + VAT148.00 + 28.12 = 176.12
- VAT rate19% · as on the supplier file
- Due date17 Aug · net 14 from 03 Aug
- PO referencePO-2026-0412 · on the PO list
Every check passed. Nothing for a person to look at.
charges · matched · open
statement line 14 of 26 · matched
Sheet 01/03run time s · example
Illustration of the run on our own books, August 2026. The values are examples; the month's count of 26 charges, 24 matched and 2 open is real.
How it works
One invoice, start to finish. Every step is grounded in the document itself, and anything unusual waits for a person.
- 01
Arrives
An invoice lands by email or in a shared folder. The pipeline picks it up automatically, no upload step for your team.
- 02
Read
Every field is extracted, vendor, dates, line items, tax, totals, with a confidence score per field, tied to where it appears on the page.
- 03
Checked
Duplicates, VAT math, and supplier match are checked against your statement lines. A person sees anything the system flags.
- 04
Filed
Clean invoices are filed into a folder structure, named and dated, so anyone can find one without asking.
- 05
Matched
Each charge on the bank statement is tied to its invoice. The open ones are listed with a reason, never guessed.
What it plugs into
Folders and document stores today. Posting into an accounting system is scoped per build.
Proof: our own books, and the strongest document-automation proof on file
We run this pipeline on Code2b’s own invoices every month, and the same reading and confirmation approach is behind the deepest document build we have shipped for a client.
26 outgoing charges in one month. 24 documented and matched to the statement, 2 left open with a reason, €18.10 between them. It caught a full refund that needed a credit note before it could be expensed, one invoice that covered three separate card charges, and a subscription billed in arrears that would have landed in the wrong month.
On a client build, via a partner: Five document types including tenders, extracted from Greek PDFs at roughly 90%+ field accuracy, with a mandatory human confirmation step before anything is saved, and counterparties deduplicated on tax number.
Our own books, August 2026. No hours-saved claim on this page: only what was measured.
Questions, answered straight.
It is read the same way. The system extracts the same fields from a photo as it does from a PDF, with a confidence score per field, and anything it cannot read cleanly is flagged for a person instead of guessed.
It is read in that language, and the fields come out the same: vendor, dates, line items, tax, and totals, tied to where they appear on the page.
The field is flagged and a person corrects it. The correction is logged, so the same case is handled better next time.
Posting to an accounting system is scoped per build. Today it files into folders and document stores; wiring it into your ledger is a build we scope with you.
See it read one of your invoices
Book a 15-minute call. We look at the documents you process today and scope a fixed price and a go-live date, in writing.
- Built to SOC 2 controls
- GDPR aligned · DPA on request
- Private AI on your own servers: yourtrained.ai
Every invoice automation engagement is led personally by Code2b's founders, Alex and Dusan. Fixed scope and go-live date agreed up front. No surprise costs.