EN 16931 / PEPPOL 3.0.17 ENGINE LIVE DE E-Rechnung (§ 14 UStG) & FR Factur-X 2026 Ready
InvoiceSpec Hub / ERP Integrations / woocommerce-to-xrechnung
SOURCE: WOOCOMMERCE → TARGET: XRECHNUNG 3.0 (UBL-2.1) Mandate Deadline: 2025-01-01 (DE)

WooCommerce to XRechnung 3.0 Integration & Schema Crosswalk

Converting WooCommerce REST API Orders to German XRechnung 3.0

German public-sector (B2G) and enterprise (B2B) buyers require **XRechnung 3.0.2** compliance. Standard WooCommerce PDF plugins fail KoSIT validation because:

1. **Mandatory Leitweg-ID / BuyerReference (BR-DE-15):** You must capture a custom checkout meta field (`_billing_leitweg_id` or `_billing_buyer_reference`) and map it to `/ubl:Invoice/cbc:BuyerReference`.

2. **Seller Contact Point (BR-DE-2):** XRechnung strictly requires `cac:AccountingSupplierParty/cac:Party/cac:Contact` with `cbc:Name`, `cbc:Telephone`, and `cbc:ElectronicMail`.

REST Webhook Bridge: POST /api/v1/normalize
Target Specification: 3.0.2

Mandatory WooCommerce to XRechnung 3.0 Field Crosswalk Matrix

Deterministic attribute mapping from WooCommerce payloads to EN 16931 Business Terms (BT) and UBL-2.1 XPaths.

WooCommerce Source Field EN 16931 Business Term Target UBL-2.1 XPath Card. Transformation & Normalization Rule Schematron Rule
meta_data["_billing_leitweg_id"] string ("991-12849-74") BT-10 (Buyer Reference) /ubl:Invoice/cbc:BuyerReference 1..1 Fallback to order.number if B2B buyer omits cost center BR-DE-15 ↗
billing.address_2 string ("") BT-51 (Buyer Address Line 2) /ubl:Invoice/cac:AccountingCustomerParty/cac:Party/cac:PostalAddress/cbc:AdditionalStreetName 0..1 Omit XML node completely if empty string PEPPOL-EN16931-R008 ↗
line_items[].subtotal string ("149.9500") BT-131 (Invoice Line Net) /ubl:Invoice/cac:InvoiceLine/cbc:LineExtensionAmount 1..n Round 4-decimal WooCommerce internal floats to 2 decimals BR-CO-10 ↗

Test Your WooCommerce XRechnung 3.0 XML Export Live

Validate your generated UBL-2.1 payload against EN 16931 & XRechnung 3.0 rules directly in your browser.

100% Client-Side Privacy
invoice-payload.xmlUBL-2.1
DETECTED SOURCEShopify
LINE SUM (BT-131)199.95 EUR
HEADER NET (BT-106)200.00 EUR
8 FATAL SCHEMATRON ERRORS
Invoice ID: SHPFY-2026-8841 · Validated in 1ms
XRechnung 3.0 (UBL)
BR-01An Invoice shall have a valid EN 16931 Specification identifier (BT-24)
Fix Guide
XPath: /ubl:Invoice/cbc:CustomizationID

Missing <cbc:CustomizationID> or value does not declare EN 16931 CIUS compliance.

Remediation: Insert <cbc:CustomizationID>urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0</cbc:CustomizationID>.

BR-CL-01Document currency code (BT-5) MUST belong to ISO 4217 uppercase code list
Fix Guide
XPath: /ubl:Invoice/cbc:DocumentCurrencyCode

Found invalid or lowercase currency code "eur". Expected uppercase ISO 4217 (e.g. "EUR").

Remediation: Replace <cbc:DocumentCurrencyCode>eur</cbc:DocumentCurrencyCode> with uppercase "EUR".

PEPPOL-EN16931-R008Document MUST NOT contain empty XML elements (found 1: <cbc:AdditionalStreetName>)
Fix Guide
XPath: //cbc:AdditionalStreetName[not(node())]

Peppol Schematron forbids empty elements such as <cbc:AdditionalStreetName></cbc:AdditionalStreetName> serialized from null ERP fields.

Remediation: Strip empty <cbc:AdditionalStreetName> nodes prior to XML serialization.

PEPPOL-EN16931-R020Seller electronic address (BT-34) MUST be provided with a valid EAS @schemeID
Fix Guide
XPath: /ubl:Invoice/cac:AccountingSupplierParty/cac:Party/cbc:EndpointID

Missing <cbc:EndpointID schemeID="..."> inside <cac:AccountingSupplierParty>/<cac:Party>.

Remediation: Add <cbc:EndpointID schemeID="9930">DE123456789</cbc:EndpointID> as the first child of Seller <cac:Party>.

PEPPOL-EN16931-R010Buyer electronic address (BT-49) MUST include a valid EAS @schemeID attribute
Fix Guide
XPath: /ubl:Invoice/cac:AccountingCustomerParty/cac:Party/cbc:EndpointID

Buyer <cbc:EndpointID> is either missing or lacks the mandatory EAS @schemeID attribute.

Remediation: Add schemeID="9930" (or "0088" for GLN / "0204" for Leitweg-ID) to Buyer <cbc:EndpointID>.

BR-DE-15Buyer reference / Leitweg-ID (BT-10) is missing
Fix Guide
XPath: /ubl:Invoice/cbc:BuyerReference

No <cbc:BuyerReference> (BT-10) found. Mandatory in XRechnung 3.0 (BR-DE-15) and required in Peppol BIS 3.0 (PEPPOL-EN16931-R003) when OrderReference is absent.

Remediation: Insert <cbc:BuyerReference>991-12849-74</cbc:BuyerReference> in the document header.

BR-CO-10Sum of Invoice line net amount (BT-106 = 200.00) != sum of lines (BT-131 = 199.95)
Fix Guide
XPath: /ubl:Invoice/cac:LegalMonetaryTotal/cbc:LineExtensionAmount

Mathematical discrepancy of 0.05 EUR between InvoiceLine sum (199.95) and LegalMonetaryTotal/LineExtensionAmount (200.00).

Remediation: Set cbc:LineExtensionAmount and cbc:TaxExclusiveAmount to 199.95.

BR-S-08Standard rate VAT TaxableAmount (BT-116 = 200.00) does not match S-rated lines (199.95)
Fix Guide
XPath: /ubl:Invoice/cac:TaxTotal/cac:TaxSubtotal/cbc:TaxableAmount

TaxSubtotal/TaxableAmount reports 200.00, but Standard rated ("S") lines total 199.95.

Remediation: Recalculate BT-116 = 199.95, VAT BT-117 = 37.99, and PayableAmount BT-115 = 237.94.

AP
Automate XRechnung 3.0 (UBL) directly in WooCommerce

Try Certified Peppol Access Point & ZUGFeRD ERP Integration — Zero XML coding

Try Certified Integration

Other ERP to E-Invoicing Compliance Bridges

Unlock Pro Batch XML / PDF Converter ($29/mo) →