Top Up Credits โ†’
InvoiceSpec / Rules Registry / peppol-bis-3 / PEPPOL-EN16931-CL008
fatal ASSERTION ยท PEPPOL-EN16931-CL008 Peppol BIS Billing 3.0 (UBL-2.1) Jurisdiction: EU

PEPPOL-EN16931-CL008: Electronic address identifier scheme must be from the codelist "Electronic Address Identifier Scheme"

Official Peppol BIS Billing 3.0 Spec โ†—
01. Technical Specification & XPath Evaluation Context

Schematron rule PEPPOL-EN16931-CL008 (FATAL) enforces the EN 16931 / OpenPeppol assertion "Electronic address identifier scheme must be from the codelist "Electronic Address Identifier Scheme"". During validation at context node `cbc:EndpointID[@schemeID]`, the XSLT/Schematron engine evaluates the XPath boolean expression `some $code in $eaid satisfies @schemeID = $code`. If this expression evaluates to false, the receiving Peppol Access Point or tax authority gateway rejects the UBL-2.1 document immediately.

Evaluated XPath Location:
cbc:EndpointID[@schemeID]
Deterministic Remediation Steps

1. Inspect the UBL 2.1 node at XPath `cbc:EndpointID[@schemeID]`. 2. Ensure the XML payload satisfies the Schematron assertion `some $code in $eaid satisfies @schemeID = $code` (Electronic address identifier scheme must be from the codelist "Electronic Address Identifier Scheme"). 3. Validate that all required child tags, @currencyID / @schemeID attributes, and decimal totals match EN 16931-1 before dispatching to the Peppol network.

02. Side-by-Side UBL-2.1 Payload Diff (Rejected vs. Compliant)
--- a/invoice-rejected.xml (PEPPOL-EN16931-CL008) FAIL
1 <Invoice xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2"
2 xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"
3 xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">
4 <cbc:CustomizationID>urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0</cbc:CustomizationID>
5 - <cbc:ID>INV-PEPPOL-EN16931-CL008-FAIL</cbc:ID>
6 - <!-- ERROR [PEPPOL-EN16931-CL008]: Electronic address identifier scheme must be from the codelist "Electronic Address Identifier Scheme" -->
7 <!-- Evaluated at XPath: cbc:EndpointID[@schemeID] -->
8 <cac:InvoiceLine>
9 <cbc:EndpointID></cbc:EndpointID>
10 </cac:InvoiceLine>
11 </Invoice>
+++ b/invoice-compliant.xml (EN 16931 VALID)
PASS
1 <Invoice xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2"
2 xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"
3 xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">
4 <cbc:CustomizationID>urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0</cbc:CustomizationID>
5 + <cbc:ID>INV-PEPPOL-EN16931-CL008-VALID</cbc:ID>
6 + <!-- COMPLIANT [PEPPOL-EN16931-CL008]: Satisfies cbc:EndpointID[@schemeID] -->
7 <cac:InvoiceLine>
8 + <cbc:EndpointID>EN16931-VERIFIED-VALUE</cbc:EndpointID>
9 </cac:InvoiceLine>
10 </Invoice>
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: PASS (0 FATAL)ยท 1ms
Peppol BIS Billing 3.0
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 โ†’