Comply with Germany B2B e-invoicing receive mandate effective January 2025
domain: ecosio.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm your ERP or accounting system can ingest EN 16931-compliant XML formats: XRechnung (UBL 2.1 or CII D16B) and ZUGFeRD 2.1 (hybrid PDF/XML)
Configure an inbound channel (email, SFTP, or Peppol) that accepts structured invoices from domestic B2B suppliers
Validate incoming invoices against EN 16931 schematron rules and the XRechnung CIUS schematron before posting to the AP ledger
Archive the original XML alongside any human-readable PDF for the GoBD-required 10-year retention period
For issuing mandates: prepare for companies over EUR 800K turnover to issue e-invoices from January 2027, and all remaining businesses from January 2028
Known gotchas
Since January 1, 2025, all German domestic B2B businesses must be technically capable of receiving structured e-invoices — issuance mandates are phased through 2028
ZUGFeRD 2.1 and XRechnung are both EN 16931-compliant but structurally different; your parser must handle both
Paper invoices and simple PDF-only invoices remain temporarily permissible for issuance during transition, but the recipient's duty to accept structured invoices is already in force
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?