InvoiceSpec / Rules Registry / peppol-bis-3 / PEPPOL-EN16931-R010
fatal ASSERTION · PEPPOL-EN16931-R010 Peppol BIS Billing 3.0 (UBL-2.1) Jurisdiction: EU

PEPPOL-EN16931-R010: Buyer electronic address (BT-49) MUST be provided with a valid EAS schemeID

Official Peppol BIS Billing 3.0 Spec ↗
01. Technical Specification & XPath Evaluation Context

Every Peppol invoice requires a routable Buyer electronic address (cbc:EndpointID, BT-49) inside cac:AccountingCustomerParty/cac:Party with a valid EAS @schemeID attribute.

Evaluated XPath Location:
/ubl:Invoice/cac:AccountingCustomerParty/cac:Party/cbc:EndpointID
Deterministic Remediation Steps

Include the mandatory @schemeID attribute (e.g., schemeID="9957" for French VAT or "0009" for SIRET) on the buyer <cbc:EndpointID> element.

02. Side-by-Side UBL-2.1 Payload Diff (Rejected vs. Compliant)
--- a/invoice-rejected.xml (PEPPOL-EN16931-R010) FAIL
1 <cac:AccountingCustomerParty>
2 <cac:Party>
3 - <!-- ERROR [PEPPOL-EN16931-R010]: EndpointID present without required EAS @schemeID -->
4 <cbc:EndpointID>FR40303265045</cbc:EndpointID>
5 <cac:PartyName>
6 <cbc:Name> Lyon Logistics SAS</cbc:Name>
7 </cac:PartyName>
8 </cac:Party>
9 </cac:AccountingCustomerParty>
+++ b/invoice-compliant.xml (EN 16931 VALID)
PASS
1 <cac:AccountingCustomerParty>
2 <cac:Party>
3 + <cbc:EndpointID schemeID="9957">FR40303265045</cbc:EndpointID>
4 <cac:PartyName>
5 + <cbc:Name>Lyon Logistics SAS</cbc:Name>
6 </cac:PartyName>
7 </cac:Party>
8 </cac:AccountingCustomerParty>
03. Interactive Peppol BIS Billing 3.0 Validation & Auto-Fix Workbench
1 CREDITS
invoice.xmlUBL-2.1
DETECTED SOURCECustom ERP / Billing Engine
BT-131 LINE SUM0.00 EUR
BT-106 HEADER0.00 EUR
SCHEMATRON: 2 FATAL, 1 WARN· 1ms
Peppol BIS Billing 3.0
BR-01An Invoice shall have a valid EN 16931 Specification identifier (BT-24)
Spec & Diff
xpath: /ubl:Invoice/cbc:CustomizationID

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

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

PEPPOL-EN16931-R010Buyer electronic address (BT-49) MUST include a valid EAS @schemeID attribute
Spec & Diff
xpath: /ubl:Invoice/cac:AccountingCustomerParty/cac:Party/cbc:EndpointID

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

fix: 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
Spec & Diff
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.

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

Automate Custom ERP / Billing Engine → Peppol BIS Billing 3.0 AP Delivery

Deploy certified Peppol Access Point & ZUGFeRD ERP connector

04. Adjacent Peppol BIS Billing 3.0 Assertions Browse All Rules →