Peppol BIS 3.0.21 (May 2026) · UBL · Severity: ERROR
Peppol buyer electronic address is missing
The buyer party must include an electronic address (BT-49) with a valid EAS schemeID in the published Peppol BIS syntax.
- Rule ID & Severity
PEPPOL-EN16931-R010· ERROR- Standard & Scope
- Peppol BIS 3.0.21 (May 2026) · UBL
- XPath Condition
exists(cac:AccountingCustomerParty/cac:Party/cbc:EndpointID)- Target XML Path
cac:AccountingCustomerParty/cac:Party/cbc:EndpointID
Find the source field
cac:AccountingCustomerParty/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
- The buyer electronic address was left empty.
- The address was written into a contact field instead of EndpointID.
Invalid and corrected fragments
<!-- Buyer EndpointID missing -->
<cbc:EndpointID schemeID="9930">DE987654321</cbc:EndpointID>
Obtain the real buyer electronic address and its scheme from source records or the recipient. The fictional example does not prove registration, reachability or delivery.
Open PEPPOL-EN16931-R010 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-R010 source ↗
Explanation record: 2026-10-14 · Local WebAssembly / SaxonJS validation. No invoice-derived report is published as a search page.