Automate Invoice Verification – 12→2 Day Throughput
Automate incoming invoices: three-way match, ZUGFeRD & XRechnung, role-based approval. Throughput 12→2 days, discount capture >90%, GoBD-compliant.
- Throughput
- 12→2 days
- Industry
- Finance / Procurement / Accounting
- Implementation
- 6–10 weeks
At a glance
- It starts with
- Intake Channel
- The machine handles
- 12 of 13 steps
- A person keeps
- Approval Cascade
- Bottom line
- 12→2 daysThroughput
The problem
You know the drill: 200 to 300 incoming invoices a month. Two-eyes principle, PO match, goods-receipt match, cost center assignment, approval, posting, archiving.
Every step a person, every person a bottleneck. When an invoice from vendor XY disappears between receiving and accounting — which happens more often than you think — it eventually gets paid twice. Or too late, no early-payment discount.
At €600,000 monthly purchase volume, that's four-figure amounts simply vanishing.
Here's how it runs in a pipeline that handles the three-way match without anyone watching.
Above roughly 150 incoming invoices per month, manual verification becomes a structural bottleneck. Standard flow: invoice arrives by email, PDF, post, or since 2025 mandatorily as XRechnung/ZUGFeRD for public-sector suppliers.
Accountant opens each one, matches against the purchase order in SAP or Odoo, matches the goods receipt (three-way match), checks prices, quantities, discounts, VAT, picks the right cost center, forwards via email or ticket to the functional approver, chases after 5 and 10 days, posts in DATEV or SAP FI after approval, archives GoBD-compliant.
12–18 minutes per invoice, 5–8 % error rate with manual entry. At 300 invoices/month = 80–90 hours of pure review time.
Hidden costs are larger: missed early-payment discounts (typically 2 % for 10-day payment vs. 30 = 0.7 % of purchasing volume), duplicate payments on missed duplicates, supplier escalations, audit findings on patchy three-way-match.
E-invoice migration (XRechnung/ZUGFeRD mandatory from 2025 for public sector, 2027 B2B-wide in Germany) makes the manual process not just expensive but soon regulatory-insufficient.
Three-way match in a pipeline – with nobody watching
About 10 minutes: from invoice intake through PO and goods-receipt match all the way to GoBD-compliant archiving. With honest numbers.
Read the full guideYou know the drill: 200 to 300 incoming invoices a month. Two-eyes principle, PO match, goods-receipt match, cost center assignment, approval, posting, archiving. Every step a person, every person a bottleneck.
In the video we show how this runs as a pipeline: four entry channels (email, scan, Peppol/XRechnung, supplier portals), format detection for PDF, ZUGFeRD and XRechnung, OCR plus GPT-4 Vision for extraction, five validation checks, automated three-way match against SAP, Odoo or Business Central, role-based approval in Slack or Teams, posting to DATEV, SAP FI or Odoo, GoBD-compliant archive with signature trail.
And: what that means in numbers. In the example scenario about eight thousand euros net effect per month, payback in under three months – even with conservative assumptions removing the cash-discount effect.
This is the kickoff. On the channel we cover automation from different angles — finance, sales, HR, operations. One task per video, no slides.
How the process runs — step by step
Scroll through. The diagram stays put and highlights the step you are on.
- 01
Intake Channel
Email / Peppol / Portal
Invoices arrive via three channels: dedicated email (PDF attachment), Peppol network (XRechnung for public sector), or supplier upload portal. All feed the same pipeline.
- 02
Detect Format
PDF / ZUGFeRD / XRechnung
Format detection: pure PDF (needs OCR), PDF with embedded ZUGFeRD XML (read XML directly), pure XRechnung XML (parse UBL/CII). Format switch decides the extraction path.
- 03
Data Extraction
OCR / XML parse
For PDF: Google Cloud Vision or Azure Document Intelligence extracts text and structure. For ZUGFeRD/XRechnung: direct XML parse per EN 16931. Both land in the unified data model.
- 04
Duplicate Check
Hash + semantic
Duplicate check on two levels: exact hash (seen this file before?) and semantic (same invoice number from same supplier?). Duplicates are rejected and logged immediately.
- 05
PO Lookup
SAP / Odoo
The stated PO number is checked against SAP S/4HANA, Odoo, Business Central, or ERPNext. On missing reference: AI attempts to guess PO by supplier + period + amount.
- 06
Three-Way Match
Line-item three-way match: invoice lines vs. PO vs. goods receipt. Price, quantity, and VAT deviations computed.
- 07Branch
Deviation?
Gateway: are all deviations within tolerance (typically 2-5% price, exact quantity)? If yes: straight to AI account assignment. If no: clarification workflow.
- 08
Clarification Workflow
Procurement contacted
Clarification workflow: procurement owner receives structured Slack/email with all deviations at a glance and one-click options (Approve, Reject, Partial). Response flows back, process continues.
- 09
AI Account Suggestion
Claude / GPT-4
Claude or GPT-4 suggests G/L account and cost center – based on historical bookings, supplier, line text, and amount. Suggestion shown with confidence score.
- 10Human decides
Approval Cascade
Role + amount
Approval cascade by role + amount: functional by business unit, >€10k second signature by management, >€50k four-eyes. Deputy rule during absence, 48h escalation.
- 11
Post to ERP
DATEV / SAP / Odoo
After approval: automated posting in DATEV Rechnungswesen, SAP FI, Odoo Accounting, or Business Central with correct document type, tax code, and cost center.
- 12
GoBD Archive
10 years immutable
GoBD-compliant archive: original invoice, three-way-match log, approval trail, and posting document stored immutably for 10 years. Signature trail verifiable.
- 13
Discount Alert
When deadline < 5 days
In parallel a discount guardian runs: if payment deadline is < 5 days and early-payment discount is available, an alert is raised to ensure timely payment.
Our Solution
An incoming-invoice pipeline that covers three intake paths: classic PDF or scanned invoice (via OCR + AI structure recognition), digital PDF with embedded ZUGFeRD-XML (parse CII directly), and pure XRechnung (UBL/CII via Peppol or email import). All three land in a unified data model.
The pipeline runs an automatic three-way match against your ERP (SAP S/4HANA, Odoo, Business Central, ERPNext): assign PO number, reconcile line items against goods receipt, flag price and quantity deviations. For any deviation above tolerance (configurable, usually 2–5 %) the invoice enters a structured clarification workflow.
AI (Claude or GPT-4) suggests cost center and G/L account from historical bookings with high accuracy but flags low-confidence cases for manual review.
Approval is role-based: functional approval by the business unit, amount-based second signature by management (> €10,000 second signature, > €50,000 four-eyes principle).
After approval: automatic posting to DATEV Rechnungswesen, SAP FI, or Odoo, with GoBD-compliant archival including the signature trail.
Outcome: throughput from ~12 days to ~2, early-payment discount capture > 90 %, audit readiness becomes permanent instead of point-in-time.
- Three Intake Paths, One Pipeline
- Classic PDF (OCR + AI), ZUGFeRD PDF (XML parse), XRechnung (UBL/CII via Peppol or email). All three land in the same data model – no parallel process.
- Automated Three-Way Match
- Purchase order, goods receipt, and invoice reconciled line-by-line. Deviations above tolerance (configurable) routed into a structured clarification workflow.
- Role-Based Approval Cascade
- Functional by business unit, amount-based by management (>€10k second signature, >€50k four-eyes). Deputy coverage and escalation on delay.
- AI Cost Center Suggestion
- Claude/GPT-4 suggests G/L account and cost center from historical bookings. High hit rate, human confirms with one click.
- E-Invoice Without Migration
- XRechnung and ZUGFeRD 2.x ready. Validation per EN 16931, optional Peppol connectivity. Ready for the 2027 B2B mandate.
- Auto-Post to ERP After Approval
- Native integration with DATEV Rechnungswesen, SAP FI, Odoo Accounting, or Microsoft Business Central. Full document flow, no manual re-entry.
What comes out of it
Possible setup, not a packaged product
The figures shown are target values and expected magnitudes for a possible setup – based on industry benchmarks, public studies of comparable setups, and our own tests on a real stack. They are not measured outcomes from a specific customer project; actual results depend on company size, process maturity, and integration depth. We do not offer this setup as a packaged product. We help teams design, automate, and run such processes themselves – through architecture consulting, workshops, and implementation support with n8n. For regulated third-party systems with certification or license requirements (e.g. HIS, gematik, DATEV-certified), we partner with specialized providers.
- 12→2 days
- Throughput
- >90%
- Discount Capture
- -80%
- Manual Review Time
- < 0.5%
- Error Rate
Throughput from 12 to 2 days, >90% early-payment discount capture, 80% less manual review, ZUGFeRD/XRechnung ready
Before vs. After
| Aspect | Before | After |
|---|---|---|
| Throughput: intake → posting | ~12 days | ~2 days |
| Manual review per invoice | 12-18 min | 1-2 min (approval) |
| Early-payment discount capture | ~40% | >90% |
| Three-way match coverage | Sampled | 100% line-accurate |
| E-invoice (XRechnung/ZUGFeRD) | Manually converted | Natively parsed per EN 16931 |
| Audit readiness | ~2 weeks prep per audit | Permanent, one-click export |
Technical facts
Technology Stack
Integrations
Seamless connection to your existing infrastructure
- DATEV Rechnungswesen / Unternehmen OnlineERP / Accounting
- Native DATEVconnect integration for tax consultancies and mid-market
- SAP S/4HANA / Business OneERP
- OData and BAPI interfaces for PO matching and SAP FI posting
- Odoo / ERPNextERP (Open Source)
- REST API connection to Odoo Accounting and ERPNext for open stacks
- Microsoft Business CentralERP
- Microsoft Graph API for Dynamics 365 Business Central and legacy NAV
- Peppol Access PointE-Invoice
- Receive XRechnung via Peppol for public sector and the 2027 B2B mandate
- Google Cloud Vision / Azure Document IntelligenceOCR
- High-precision text recognition for classic PDF and scanned invoices
Security & Compliance
Enterprise-ready with highest security standards
- GoBD-Compliant Original Archive
- Incoming invoice hashed at intake, archived immutably for 10 years. BMF Nov 2019 compliant.
- EN 16931 / XRechnung Validation
- Automated schema validation per EN 16931, UBL 2.1, and CII D16B. Invalid invoices rejected with a concrete error report.
- Role-Based Access (RBAC)
- Granular rights by role, cost center, and amount threshold. Deputy mechanisms audit-trail-safe.
- GDPR & EU Hosting
- Processing in EU data centers, Art. 28 DPA, automated retention. Supplier data protected.
Frequently Asked Questions
Does this look like your setup?
If this workflow resembles yours, we will look at it together — and tell you honestly whether automating it pays off.
Related Showcases
AI-Powered Invoice Data Extraction
Extract invoice data automatically instead of retyping it: OCR plus AI reads invoice numbers, line items, and tax rates from any format, catches duplicates, and posts straight to SAP — 2 minutes instead of 24 hours per invoice.
Digital Document Approval
Automated approval workflows with 75% faster approval cycles
Automate Dunning – Cut DSO by 21 days
Cut DSO by 14-21 days with automated dunning for Lexoffice, DATEV, or sevDesk. 70% fewer collections cases, § 286/288 BGB compliant, approval gates.