Blog · Tag
#en16931
12 articles
A complete developer reference for Factur-X — the hybrid PDF/A-3 + CII XML format used across France, Germany, and Luxembourg. XML anatomy, profile hierarchy, EN 16931 rule mapping, validation errors, and code samples.
EN 16931 supports two XML syntaxes: UBL 2.1 and UN/CEFACT CII. Here's when to use each, how they differ technically, and why it matters for validation.
Every EN 16931 validation rule categorized, explained, and cross-referenced. The definitive technical reference for e-invoice developers.
FeRD and FNFE-MPE will release ZUGFeRD 2.5 / Factur-X on May 20, 2026 — adding native gross invoice support, refreshed EN 16931 code lists, and ViDA-ready fields. Here's what changes, what breaks, and what to ship before customers start sending 2.5 invoices into your ERP.
We analyzed thousands of invoice validations. These are the 10 errors that trip up European businesses most — with fix instructions for each.
Belgium's 3-month e-invoicing grace period ended March 31, 2026. Penalties are now active. Here's what changed, what the fines look like, and what ERP vendors need to do right now.
EN 16931 defines ~65 business rules, Peppol adds ~80, and each country CIUS adds more. Here's how the four validation layers work, what they check, and which errors you'll see most.
ZUGFeRD and XRechnung are Germany's two e-invoice formats — but they solve different problems. This guide covers the XML structures, validation rules, profile mappings, and integration patterns ERP developers need to choose the right format.
A practical guide to Schematron validation in EU e-invoicing. Understand the three validation layers, read real rule examples, debug common errors, and see how EN16931, Peppol, and country-specific rules work together.
Fix every BR-DE validation error in your XRechnung invoices. Covers BR-DE-1 through BR-DE-29 with XML examples, root causes, and tested solutions for XRechnung 3.0.
Three approaches to e-invoice validation in your pipeline: build your own, use open-source tools, or call an API. Code examples for each.
Belgium requires structured e-invoicing for all domestic B2B transactions since January 1, 2026. Peppol BIS 3.0 is the standard. The grace period ends March 31. Here's what you need.