Automate Invoice Processing: an End-to-End Demo
Incoming invoices from inbox to GoBD archive: four entry channels, one data model, posting to DATEV/SAP/Odoo. Demo reference architecture.
- Industry
- Bookkeeping · 100–500 invoices a month
- Build, estimated
- 6 weeks
At a glance
- It starts with
- Four inbound channels
- The machine handles
- 9 of 11 steps
- A person keeps
- Check uncertain fields · Approval
- Bottom line
- ~440 %Year-1 ROI (example)
The problem
Real talk: nobody enjoys processing invoices. It's one of those jobs that exists because invoices keep coming — not because anyone signed up for it.
In a thirty-person company with three hundred invoices a month, it's one person's job. They open every PDF, type vendor names and amounts, hunt down purchase orders, chase managers for approval, post, file. Twelve minutes per invoice, sixty hours a month — time that produces nothing.
Then comes the day this exact person gets sick, quits, or goes on vacation for two weeks. Intake stalls. Cash discounts gone. Suppliers calling.
That's what we solve here — not in twelve months of consulting, but in six weeks of pipeline.
Example scenario: a business with about 30 employees, 35 €/h personnel cost, ~600,000 €/month purchase volume. A single person handles invoice intake — 300 invoices a month, 12 to 15 minutes manual work each.
Open PDF, type vendor, number, date, net, VAT, find purchase order, route for approval, wait, post, file. That's 60 to 75 hours a month producing nothing. Plus 5 to 8 % typing errors, occasional duplicate payments (avg. 1,500 € each), regularly missed cash discount deadlines.
The unaddressed question: what happens when this one person gets sick, quits, or takes two weeks off? Intake stalls, suppliers wait, cash discounts are gone. Bus factor of 1 — that's the real risk, not just the hours.

Staged scene
Friday, 6:50 pm
One person knows how incoming invoices work. From Monday she is on leave for two weeks.
Everything has to be posted before then, or it waits. The workflow below no longer depends on one person.
How the automated invoice intake works
About 10 minutes from incoming email to finished posting. Including the question rarely asked: what happens when your bookkeeper is sick, on vacation, or quits?
Read the full guideThe process, step by step
Scroll through. The diagram stays put and highlights the step you are on.
- 01
Four inbound channels
Email / SFTP / Peppol / Portal
Invoices arrive four ways: a dedicated mailbox (invoices@company.com), scans via SFTP, Peppol/AS4 for XRechnung and regular fetching from supplier portals. Everything runs into the same pipeline; there is no second path on the side.
- 02
Detect format
PDF / ZUGFeRD / XRechnung
Format detection separates classic PDFs, ZUGFeRD PDFs with embedded XML and pure XRechnung files. That decides whether the invoice is read or recognised.
- 03
Extraction
OCR + LLM / XML parse
For classic PDFs, OCR reads the text and a language model maps the fields, even when every supplier writes "invoice number" differently. ZUGFeRD and XRechnung are read directly as XML to EN 16931.
- 04
One data model
invoice.json with confidence
All three paths end in the same data model. Every field carries a confidence score: how sure is the machine about the amount, the date, the IBAN?
- 05Branch
All fields certain?
- 06Human decides
Check uncertain fields
only these, not the whole invoice
Only the fields the machine is unsure about go to a person. They correct those instead of typing the whole invoice.
- 07
Five checks
Schema / VAT / Duplicate / Master data / Sanctions
Five checks run in parallel: EN 16931 schema, VAT plausibility, duplicate hash, a match against ERP master data and the EU sanctions list. Duplicate invoices stop here.
- 08Branch
Over €500?
- 09Human decides
Approval
1 click in Slack/Teams, four eyes from €5,000
Up to €5,000 the department approves with one click in Slack or Teams; above that, four eyes with management. If someone is away, the approval goes to their deputy; after 24 hours it escalates.
- 10
Posting
DATEV / Lexware / SAP / Odoo
Once approved, the invoice is posted: DATEV, Lexware Office, sevDesk, SAP FI or Odoo. The AI suggests the cost centre from earlier postings.
- 11
GoBD archive
Hash chain, 10 years
The original is archived unchangeably, with a hash chain and ten years of retention under GoBD. The export for an audit is one click.
What changes
Possible setup, not a packaged product
The figures are modelled target values for a possible setup, derived from industry benchmarks and our own tests. They do not come from a customer project; real values depend on your business. We do not sell this setup as a finished product: we measure where your bottleneck is, then build with your team. For systems that require certification (e.g. HIS, gematik, DATEV-certified) we work with specialised partners.
Before vs. After
| Aspect | Before | After |
|---|---|---|
| Time per invoice | Before: 12–15 min manual | After: 1–2 min spot check |
| Hours / mo (300 invoices) | Before: 60–75 h | After: 8–10 h exceptions + sampling |
| Total cost / mo | Before: ~2,350 € | After: ~665 € (incl. software & maintenance) |
| Cash discount usage | Before: 30–50 % | After: > 90 % |
| Error rate | Before: 5–8 % | After: < 0.5 % |
| Throughput intake → booking | Before: 8–12 days | After: < 2 days (median ~4 h) |
| Duplicate payments / yr | Before: 2–5 cases @ ~1,500 € | After: 0 (hash duplicate lock) |
| Audit readiness (GoBD) | Before: ad-hoc, 3–5 days prep | After: permanent, one-click export |
| Bus factor | Before: 1 person holds the knowledge | After: Pipeline + caretaker (replaceable) |
Technology
Technology Stack
Integrations
Systems this setup can connect to
- DATEV Rechnungswesen / Unternehmen OnlineBookkeeping
- DATEVconnect online for direct receipt upload, EXTF-CSV as fallback for tax advisor handover.
- Lexware Office / sevDeskBookkeeping (REST API)
- Native integration via Lexware Office and sevDesk APIs. Voucher with original PDF, cost center and tax code in one step.
- SAP S/4HANA / Business OneERP
- OData and BAPI interfaces for PO matching (three-way-match) and posting to SAP FI.
- Odoo / Microsoft Business CentralERP
- REST/XML-RPC for Odoo, Microsoft Graph for Business Central. Full receipt flow, no manual re-entry.
- Peppol Access PointE-invoicing
- AS4 receipt for XRechnung — relevant for public sector and the German B2B mandate from 2027. Implemented via Phase4 or providers like ecosio.
- Slack / Microsoft TeamsApproval
- Block Kit (Slack) or Adaptive Cards (Teams) for approval buttons. Delegate routing and escalation built in.
- Azure Document Intelligence / Google Cloud VisionOCR
- Text recognition for classic PDF and scanned invoices.
- OpenAI GPT-4 Vision / Anthropic ClaudeAI structuring
- Function calling / tool use for field-level extraction with confidence scores. EU endpoints, zero data retention.
Security & Compliance
What the setup takes care of
- GoBD-compliant archive
- Original PDF hashed at intake (SHA-256) and archived tamper-evident for 10 years. Compliant with the German Ministry of Finance directive of 28.11.2019.
- GDPR & EU hosting
- Processing in EU data centers, DPA per GDPR Art. 28. LLM API calls (OpenAI/Anthropic) via EU endpoints with zero data retention.
- Append-only audit log
- Every step — intake, extraction, correction, approval, booking — logged in an immutable hash chain. One-click export for audits.
- IBAN and sanctions check
- Before each booking IBAN is validated against schema and check digit, vendor checked against the EU consolidated sanctions list.
Frequently Asked Questions
What would this look like at your company?
This workflow is a demo. Whether it pays off for you depends on where things get stuck at your company. The method page shows how to find out. To place a workflow of your own, use the free assessment. No call needed.