Blog · Category
Technical Guides
13 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.
About to start sending real e-invoices? Run through this checklist first. Each item has caught a production issue at least once.
Your Peppol access point just sent you an MLR rejection. Here's what that means, what the error codes tell you, and how to get your invoice through.
You've configured your ERP for e-invoicing. The invoices look fine. But they keep failing validation. Here's why — and what to actually do about it.
Factur-X and ZUGFeRD are technically the same format with different names. But the details matter when you're trying to pass validation. Here's what you need to know.
How to architect a production e-invoice validation pipeline — from single-invoice checks to batch processing with auto-remediation. Patterns, code, and deployment strategies.
Every EN 16931 validation rule categorized, explained, and cross-referenced. The definitive technical reference for e-invoice developers.
We analyzed thousands of invoice validations. These are the 10 errors that trip up European businesses most — with fix instructions for each.
Your invoice just bounced back with a validation error. Here's exactly what happened, why, and how to fix it in minutes.
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.