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

PEPPOL-EN16931-R020: Seller electronic address (BT-34) MUST be provided with a valid EAS schemeID

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

In Peppol BIS 3.0, the Seller must provide an electronic routing address (cbc:EndpointID, BT-34) inside cac:AccountingSupplierParty/cac:Party, including a valid Electronic Address Scheme (@schemeID) from CEF EAS code list (e.g., 9930 for German VAT, 0088 for GLN, 0204 for Leitweg-ID).

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

Add <cbc:EndpointID schemeID="9930"> (or the appropriate EAS code for the seller country) as the first child of <cac:Party> inside <cac:AccountingSupplierParty>.

02. Side-by-Side UBL-2.1 Payload Diff (Rejected vs. Compliant)
--- a/invoice-rejected.xml (PEPPOL-EN16931-R020) FAIL
1 <cac:AccountingSupplierParty>
2 <cac:Party>
3 - <!-- ERROR [PEPPOL-EN16931-R020]: Missing cbc:EndpointID or missing @schemeID attribute -->
4 <cac:PartyIdentification>
5 <cbc:ID>DE123456789</cbc:ID>
6 </cac:PartyIdentification>
7 <cac:PartyLegalEntity>
8 <cbc:RegistrationName>Nordic Cloud AB</cbc:RegistrationName>
9 </cac:PartyLegalEntity>
10 </cac:Party>
11 </cac:AccountingSupplierParty>
+++ b/invoice-compliant.xml (EN 16931 VALID)
PASS
1 <cac:AccountingSupplierParty>
2 <cac:Party>
3 + <cbc:EndpointID schemeID="9930">DE123456789</cbc:EndpointID>
4 <cac:PartyIdentification>
5 + <cbc:ID schemeID="0088">7300010000001</cbc:ID>
6 </cac:PartyIdentification>
7 <cac:PartyLegalEntity>
8 <cbc:RegistrationName>Nordic Cloud AB</cbc:RegistrationName>
9 </cac:PartyLegalEntity>
10 </cac:Party>
11 </cac:AccountingSupplierParty>
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-R020Seller electronic address (BT-34) MUST be provided with a valid EAS @schemeID
Spec & Diff
xpath: /ubl:Invoice/cac:AccountingSupplierParty/cac:Party/cbc:EndpointID

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

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

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 →