Bill to Sample Foods NV
| Description | Qty | Unit | Amount |
|---|---|---|---|
| Pallet transport, Rotterdam to Utrecht | 4 | EUR 85.00 | EUR 340.00 |
| Waiting time (hours) | 1 | EUR 60.00 | EUR 60.00 |
- Subtotal
- EUR 400.00
- VAT 21%
- EUR 84.00
- Total
- EUR 484.00
Pay to IBAN NL91 ABNA 0417 1643 00
Live demos
See it work before you talk to us.
Three short demos: a voice agent, a chat on an open-weight model that we host and document AI. Nothing here is a client system.
01 / Voice agent
Talk to a voice agent
A hosted voice agent that handles a simple intake call. It answers in English or Dutch, asks a few questions and offers to book a call with us.
Checking whether this demo is switched on
02 / Sovereign AI chat
Chat with an open-weight model we host
A short chat on an open-weight model served through an OpenAI-compatible endpoint. It shows what a self-hosted set-up feels like. Answers are short on purpose.
Checking whether this demo is switched on
03 / Document AI
Three documents, read into structured data
Pick a sample. On the left is the document as it arrives. On the right are the fields we extract as JSON and as a table, each with the check that decides whether a person must look at it.
Fictional sample
1 to review. Fields that fail a check go to a person, with the reason attached.
Fields and checks
| Field | Value | Check |
|---|---|---|
| Supplier | Example Freight BV | Checked Found on the document |
| Customer | Sample Foods NV | Checked Found on the document |
| Invoice number | INV-2026-0147 | Checked Found on the document |
| Invoice date | 2026-11-09 | Checked A valid date |
| Due date | 2026-12-09 | Checked A valid date, after the invoice date |
| Purchase order reference | null | Needs a person Not found on the document. A person adds it or confirms it is empty |
| Bank account (IBAN) | NL91ABNA0417164300 | Checked The bank account number passes its checksum |
| Subtotal | 400 | Checked Equals the sum of the line items |
| VAT amount | 84 | Checked Equals 21% of the subtotal |
| Total | 484 | Checked Equals subtotal plus VAT |
Extracted as JSON
{
"document_type": "invoice",
"fields": {
"supplier": "Example Freight BV",
"customer": "Sample Foods NV",
"invoice_number": "INV-2026-0147",
"invoice_date": "2026-11-09",
"due_date": "2026-12-09",
"po_reference": null,
"iban": "NL91ABNA0417164300",
"subtotal": 400,
"vat_amount": 84,
"total": 484
},
"line_items": [
{
"description": "Pallet transport, Rotterdam to Utrecht",
"quantity": 4,
"unit_price": 85,
"amount": 340
},
{
"description": "Waiting time (hours)",
"quantity": 1,
"unit_price": 60,
"amount": 60
}
],
"needs_review": [
"po_reference"
]
}What happens with exceptions
A person checks the doubtful ones
No document reader is right every time, so the design assumes it is not.
Every field gets a check
Failures go to a queue
A person decides
Corrections are kept
How each step works
- Every field gets a check. Totals must add up, dates must parse, a bank account number must pass its checksum and required fields must be present. The rules are plain code you can read.
- Failures go to a queue. A field that fails is not guessed. The document goes to a review queue with the field, the reason and the original page side by side.
- A person decides. The reviewer corrects or confirms the field in one place. Only then does the document continue to your ERP or TMS.
- Corrections are kept. Each correction is stored with the document, so you can see where the reader needs work and measure it on your own paperwork.
Want to see this on your own paperwork? Send us three sample documents and we run the test.
Next step
Tell us what you want to build
Bring one process, one platform or one idea. We reply within two working days and say plainly whether we are the right team for it.
Currently accepting projects for Q4 2026