Skip to main content

PEPPOL-EN16931-R010 Buyer electronic address must be provided for Peppol routing

Under Peppol rule PEPPOL-EN16931-R010, every invoice in Peppol BIS Billing 3.0 must contain the buyer electronic address in BT-49 (cbc:EndpointID). R010 checks only that this address is present; the schemeID attribute (BT-49-1) is checked by BR-63, and its value must come from the Electronic Address Scheme (EAS) code list (BR-CL-25). Examples are "0088" for a GS1 Global Location Number (GLN), "0204" for a German Leitweg-ID, "0192" for a Norwegian organisation number, "9944" for a Dutch VAT number, "0208" for a Belgian enterprise number or "0009" for a French SIRET. Peppol access points use the buyer EndpointID to query the SML and SMP and locate the recipient’s access point.

Problem Description

ERROR

Peppol BIS Billing 3.0 rule (OpenPeppol)

Interactive pipeline

Click a stage to see what it checks, or type a rule ID to light up the stage that reports it.

Try:

PEPPOL-EN16931-R010 Peppol BIS Billing rule

Reported in stage 3: National rules (CIUS).

Level error: the report recommends rejecting the invoice.

Stage 3 · What it checks

  • 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.

A validator checks an e-invoice in stages. First the file must be well-formed XML that matches the UBL or CII schema (XSD). Then the EN 16931 business rules run: BR core rules, BR-CO calculations, BR-CL code lists, BR-DEC decimals and VAT-category rules such as BR-S. Next come the national or network rules that BT-24 selects: BR-DE for XRechnung, PEPPOL-EN16931 for Peppol BIS Billing. The report lists every failed rule: one error means reject, warnings alone still mean accept. PEPPOL-EN16931-R010: Peppol BIS Billing rule, reported in the stage “National rules (CIUS)”. Rule sets: KoSIT validator 1.6.3 with the XRechnung configuration of 31 Aug 2026 (EN 16931 artefacts 1.3.16), Peppol BIS Billing 3.0.21.

Solution

In your customer master data, store the buyer Peppol participant identifier and its EAS scheme. In UBL 2.1, add <cbc:EndpointID schemeID="0204">04011000-12345-03</cbc:EndpointID> (or schemeID="0088" for a GLN) under <cac:AccountingCustomerParty><cac:Party>. Peppol BIS Billing 3.0 is exchanged as UBL 2.1.

Quick actions

Context and Significance

Without BT-49 the sending Peppol access point cannot look up the recipient in the SML and SMP, so the invoice fails validation before transmission. A missing schemeID on an existing EndpointID is reported separately by BR-63. The error usually appears when the buyer’s Peppol identifier is not maintained in the customer master data.

Valid Examples

  • Buyer electronic address with BT-49 = "04011000-12345-03" and schemeID = "0204" (German Leitweg-ID)
  • Buyer electronic address with BT-49 = "4012345000016" and schemeID = "0088" (GS1 Global Location Number)

Invalid Examples

  • cac:AccountingCustomerParty/cac:Party contains party name and address but completely omits cbc:EndpointID
  • The buyer Peppol identifier is not maintained in the customer master data, so no cbc:EndpointID is exported (an EndpointID without schemeID, such as <cbc:EndpointID>04011000-12345-03</cbc:EndpointID>, is reported by BR-63 instead)

Code Examples

Valid XML
<cac:Party>
  <cbc:EndpointID schemeID="0204">04011000-12345-03</cbc:EndpointID>
  <cac:PartyName><cbc:Name>Bundesministerium des Innern</cbc:Name></cac:PartyName>
</cac:Party>
Invalid XML
<cac:Party>
  <cac:PartyName><cbc:Name>Bundesministerium des Innern</cbc:Name></cac:PartyName>
</cac:Party>

Affected Fields

Validation Tools