With mandatory B2B e-invoicing rolling out across Germany (§ 14 UStG — ZUGFeRD 2.3 / XRechnung 3.0), Belgium (Peppol BIS 3.0 B2B 2026), Poland (KSeF FA(2)), and France (Factur-X), developers integrating Stripe, Shopify, or custom ERPs keep running into the exact same Schematron rejections at Peppol Access Points.
Here are the 3 most common fatal errors and how to fix them cleanly.
- PEPPOL-EN16931-R008 — Empty XML Elements
Most ERP serializers output empty tags when an optional field (like AdditionalStreetName or Note) is null:
xml
cbc:AdditionalStreetName/cbc:AdditionalStreetName
Fix: Strip every self-closing or whitespace-only XML leaf node before signing or transmitting.
- BR-CO-10 — Line Extension Amount Rounding Drift
When converting Stripe cents or Shopify discounts into EN 16931 UBL 2.1, SUM(InvoiceLine/LineExtensionAmount) must match LegalMonetaryTotal/LineExtensionAmount to the exact cent. A 0.01 EUR drift causes an immediate fatal rejection.
- PEPPOL-EN16931-R020 — Missing Seller EndpointID with @schemeID
In Belgium and across Peppol, cbc:EndpointID is mandatory and must declare an ISO 6523 EAS scheme (e.g., 0208 for Belgian KBO, 9930 for German VAT):
xml
0123456789/cbc:EndpointID
Quick Local & Online Validation
To avoid fighting 200-page CEN PDFs, I built an open-source CLI and browser pre-flight studio:
Local CI/CD CLI: npx invoicespec-cli ./invoice.xml (GitHub)
Online Validator, XRechnung Visual Viewer & 1,150+ Rule Diffs: https://invoicespec.dev
Stripe/Shopify JSON → Peppol XML + n8n Workflow: https://invoicespec.dev/tools/stripe-to-peppol-xml
Hope this saves someone a few hours of debugging XPath expressions!
