Reference
Markdown exportPEPPOL-EN16931-R020 Seller electronic address and scheme must be provided for Peppol identification
Under the Peppol BIS Billing 3.0 specification, every electronic invoice transmitted across the Peppol network must state the seller electronic address in BT-34 (EndpointID) with a valid electronic address identification scheme in BT-34-1 (schemeID attribute) from the official EAS (ISO 6523 / ICD) code list (e.g. "0088" for GLN, "9930" for Leitweg-ID, "0192" for Norwegian Org.nr, "9944" for Dutch KvK, "0208" for Belgian CBE, or "0009" for French SIRET). In OpenPeppol network exchange, the seller EndpointID verifies the authorized origin of the message and provides the return transmission channel for electronic dispatch advices and invoice response messages (MLR / IMR).
Problem Description
Under the Peppol BIS Billing 3.0 specification, every electronic invoice transmitted across the Peppol network must state the seller electronic address in BT-34 (EndpointID) with a valid electronic address identification scheme in BT-34-1 (schemeID attribute) from the official EAS (ISO 6523 / ICD) code list (e.g. "0088" for GLN, "9930" for Leitweg-ID, "0192" for Norwegian Org.nr, "9944" for Dutch KvK, "0208" for Belgian CBE, or "0009" for French SIRET). In OpenPeppol network exchange, the seller EndpointID verifies the authorized origin of the message and provides the return transmission channel for electronic dispatch advices and invoice response messages (MLR / IMR).
ERROR
XRechnung 3.0
Context and Significance
Without BT-34 and schemeID, Peppol Access Points reject the invoice before transmission, raising Schematron error PEPPOL-EN16931-R020.
Solution
In your company master data and e-invoicing settings, maintain your registered Peppol participant identifier and EAS scheme. In UBL 2.1 syntax, populate <cbc:EndpointID schemeID="0088">4012345000018</cbc:EndpointID> under <cac:AccountingSupplierParty><cac:Party>. In UN/CEFACT CII syntax, populate <ram:URIID schemeID="0088">4012345000018</ram:URIID> under <ram:SellerTradeParty><ram:URIUniversalCommunication>.
Quick actions
Valid Examples
Use these points as the practical checks for this section.
- Seller electronic address with BT-34 = "4012345000018" and schemeID = "0088" (GS1 Global Location Number)
- Seller electronic address with BT-34 = "987654321" and schemeID = "0192" (Norwegian Organization Number)
Invalid Examples
Use these points as the practical checks for this section.
- cac:AccountingSupplierParty/cac:Party contains party name and address but completely omits cbc:EndpointID
- Seller EndpointID tag present with address value but missing the mandatory schemeID attribute (<cbc:EndpointID>4012345000018</cbc:EndpointID>)
Code Examples
<cac:Party>
<cbc:EndpointID schemeID="0088">4012345000018</cbc:EndpointID>
<cac:PartyName><cbc:Name>Lieferant GmbH</cbc:Name></cac:PartyName>
</cac:Party><cac:Party>
<!-- Missing cbc:EndpointID (BT-34) with schemeID (BT-34-1) -->
<cac:PartyName><cbc:Name>Lieferant GmbH</cbc:Name></cac:PartyName>
</cac:Party>