Peppol BIS 3.0.21 (May 2026) · UBL · Severity: ERROR
Peppol seller electronic address is missing
The seller party must provide an electronic address (BT-34) with an EAS schemeID attribute in Peppol BIS Billing 3.0.21.
- Rule ID & Severity
PEPPOL-EN16931-R020· ERROR- Standard & Scope
- Peppol BIS 3.0.21 (May 2026) · UBL
- XPath Condition
exists(cac:AccountingSupplierParty/cac:Party/cbc:EndpointID)- Target XML Path
cac:AccountingSupplierParty/cac:Party/cbc:EndpointID
Find the source field
cac:AccountingSupplierParty/cac:Party/cbc:EndpointID
Match namespace URI and element name, not a particular prefix spelling. The validator reports the full expanded-name source path when the published rule supplies a location.
Common causes
- Seller EndpointID was omitted by the ERP export.
- Seller VAT number was placed only in PartyTaxScheme without an EndpointID.
Invalid and corrected fragments
<!-- Seller EndpointID missing -->
<cbc:EndpointID schemeID="9930">DE123456789</cbc:EndpointID>
Add the seller electronic address and EAS schemeID (such as 0208 for Belgian BCE/KBO or 9930 for German VAT) in AccountingSupplierParty/Party/EndpointID.
Open PEPPOL-EN16931-R020 in peppol-validator →
Verify the whole document
These are fragments, not complete invoices. The exact rule is exercised by synthetic mutation tests against the stated package. Correcting one field does not prove conformance; run the full selected validator again. Published messages and severity remain authoritative.
Official PEPPOL-EN16931-R020 source ↗
Explanation record: 2026-10-14 · Local WebAssembly / SaxonJS validation. No invoice-derived report is published as a search page.