TL;DR
2026 is the sweet spot to fix e‑invoicing pragmatically: centralized intake, validation, approvals, and auditable archiving. Don’t turn it into a massive ERP project — build a small internal app that covers the 80% cleanly.
The legal baseline (primary sources)
- From 2025‑01‑01, e‑invoices are mandatory in German B2B transactions — accompanied by transition provisions.
- An e‑invoice means a structured electronic format that enables electronic processing (e.g. EN 16931).
Primary sources:
- Federal info page (Germany): https://e-rechnung-bund.de/e-rechnung/e-rechnung-zwischen-unternehmen-b2b/
- German MoF (BMF) FAQ + documents: https://www.bundesfinanzministerium.de/Content/DE/FAQ/e-rechnung.htm
Not legal advice. Use the BMF docs / your tax advisor for binding interpretation.
The real problem: the invoice isn’t the bottleneck — the workflow is
What we see in 2026:
- Invoices arrive via email, portals, EDI — fragmented.
- Approvals happen in chat tools and hallway conversations.
- Evidence is scattered; audit trails are weak.
- Accounting ends up doing manual reconciliation.
Target state: a lean, enforceable process that’s provably auditable.
A minimal setup that actually works
Four building blocks:
- Inbox & intake
- Dedicated email alias (e.g. invoice@), portal downloads, optional EDI
- Automated import into one system
- Validation & risk checks
- Format/schema validation (XRechnung/ZUGFeRD/EN16931)
- Mandatory fields, VAT rates, IBAN, vendor match, duplicates
- Flagging: anomalies (new vendor, amount spikes)
- Approval workflow
- Ownership by cost center / project
- Two‑step approvals above threshold X
- SLA reminders (stuck approvals)
- Archive & export
- Compliant archiving (document + structured data)
- Export into ERP/DATEV/accounting
- Audit trail (who saw/approved what and when)
Why a small internal app is often the sweet spot
A lightweight internal app beats “let’s contort the ERP” when:
- You have multiple intake channels (email + portal + EDI)
- You need strict approvals, not just booking
- You need a clean audit trail
- Your ERP is good at posting, but bad at controlling workflows
The app can stay simple:
- UI: inbox with statuses (New / In review / Approved / Posted)
- Rules: validation + routing
- Integrations: email, storage, ERP/DATEV
Checklist 1: Operational compliance basics
E‑invoicing: minimum operational requirements
- Central intake + defined import (no lost invoices in inboxes)
- Structured data validation (schema + mandatory fields)
- Clear approval rules (thresholds, owners, delegation)
- Compliant archiving + unique document IDs
- Auditability: event trail (who/what/when)
- ERP/accounting export including structured data
Checklist 2: Build vs buy (pragmatic)
Decision guide: internal app vs tool/ERP module
- More than one intake channel (email/portal/EDI)? → integration layer helps
- Need approvals by cost center/project? → workflow layer required
- Many exceptions (credit notes, partial deliveries, discounts)? → rules + UI
- Is “posting” enough, or do you need “control + evidence”? → audit trail
- Monthly volume? → set automation level accordingly
A realistic 14‑day plan
- Days 1–2: map intake channels + approval rules + export target
- Days 3–5: intake + storage + baseline validation
- Days 6–9: approvals + roles + reminders
- Days 10–12: ERP/DATEV export + duplicate logic
- Days 13–14: audit trail + tests + 1‑page SOP
CTA: We build the internal app (without ERP drama)
A short brief is enough
Send us:
- Your ERP/accounting stack (DATEV, SAP, Navision, …)
- How invoices arrive (email/portal/EDI)
- Who approves what (roles + thresholds)
We’ll propose a small internal app that imports, validates, routes, and archives e‑invoices with a clean audit trail.