Reference
Markdown exportPEPPOL-EN16931-R020 Seller electronic address must be provided for Peppol identification
Under Peppol rule PEPPOL-EN16931-R020, every invoice in Peppol BIS Billing 3.0 must contain the seller electronic address in BT-34 (cbc:EndpointID). R020 checks only that this address is present; the schemeID attribute (BT-34-1) is checked by BR-62, and its value must come from the EAS code list (BR-CL-25), for example "0088" for a GLN, "0192" for a Norwegian organisation number, "9944" for a Dutch VAT number, "0208" for a Belgian enterprise number or "0009" for a French SIRET. The seller EndpointID identifies the seller in the Peppol network and is the address to which invoice responses and message level responses (MLR) are sent.
Problem Description
ERROR
Peppol BIS Billing 3.0 rule (OpenPeppol)
Interactive pipeline
Where PEPPOL-EN16931-R020 is checked
Click a stage to see what it checks, or type a rule ID to light up the stage that reports it.
PEPPOL-EN16931-R020 Peppol BIS Billing rule
Reported in stage 3: National rules (CIUS).
Level error: the report recommends rejecting the invoice.
Stage 3 · What it checks
National rules (CIUS)
- The specification identifier in BT-24 selects the rule set, for example XRechnung 3.0 or Peppol BIS Billing 3.0.
- XRechnung adds the German BR-DE rules: buyer reference (BT-10), seller contact, payment instructions.
- Peppol adds PEPPOL-EN16931 and country rules. XRechnung applies some PEPPOL-EN16931 rules too.
Example codes
Typical fix
Fill the fields the rule set requires in your master data, such as the Leitweg-ID in BT-10 or the seller contact.
Solution
In your company master data and e-invoicing settings, maintain your registered Peppol participant identifier and EAS scheme, for example 0088 for a GLN or 0106 for a Dutch KvK number. In UBL 2.1, add <cbc:EndpointID schemeID="0088">4012345000016</cbc:EndpointID> under <cac:AccountingSupplierParty><cac:Party>. Peppol BIS Billing 3.0 is exchanged as UBL 2.1.
Quick actions
Context and Significance
Without BT-34 the Peppol validation fails before transmission, and responses to the invoice would have no Peppol address. A missing schemeID on an existing EndpointID is reported separately by BR-62. The error usually appears when the company’s own Peppol identifier is not set in the e-invoicing settings.
Valid Examples
- Seller electronic address with BT-34 = "4012345000016" and schemeID = "0088" (GS1 Global Location Number)
- Seller electronic address with BT-34 = "987654325" and schemeID = "0192" (Norwegian Organization Number)
Invalid Examples
- cac:AccountingSupplierParty/cac:Party contains party name and address but completely omits cbc:EndpointID
- The company Peppol identifier is not set, so no seller cbc:EndpointID is exported (an EndpointID without schemeID, such as <cbc:EndpointID>4012345000016</cbc:EndpointID>, is reported by BR-62 instead)
Code Examples
<cac:Party>
<cbc:EndpointID schemeID="0088">4012345000016</cbc:EndpointID>
<cac:PartyName><cbc:Name>Lieferant GmbH</cbc:Name></cac:PartyName>
</cac:Party><cac:Party>
<cac:PartyName><cbc:Name>Lieferant GmbH</cbc:Name></cac:PartyName>
</cac:Party>