PEPPOL-EN16931-R020Peppol BIS 3.0fatalbusiness

Seller electronic address missing

Fix: This requires user input to resolve. Provide the correct value for `cbc:EndpointID` (BT-34). Provide the required value in the free validator.

Your invoice is missing the seller electronic address (EndpointID). This is required for Peppol network routing — without it, the invoice cannot be delivered to the buyer.

Where is this in my invoice?

Shown on a sample invoice. The marked row is the field this rule checks; on your own invoice it sits in the same place.

Sample invoice · not your document

Invoice

SAMPLE-INV-001 · issued 4 Jan 2026 · due 4 Feb 2026 · EUR

Seller

Seller nameSample Supplier B.V.

Seller streetHerengracht 100

Seller postcode1015 BS

Seller cityAmsterdam

Seller countryNL

Seller VAT numberNL123456789B01

Seller registration number12345678

Seller electronic addressNL123456789B01 PEPPOL-EN16931-R020

Buyer

Buyer nameSample Buyer NV

Buyer streetRue de la Loi 42

Buyer postcode1000

Buyer cityBrussels

Buyer countryBE

Buyer VAT numberBE0123456789

Buyer electronic addressBE0123456789

Invoice details

Invoice numberSAMPLE-INV-001

Issue date4 Jan 2026

Due date4 Feb 2026

Invoice type380

CurrencyEUR

Buyer referencePO-12345

Payment

Payment method30

Payment IBANNL91ABNA0417164300

Line items

No.	Item	Quantity	Unit price	VAT rate (%)	Line amount
1	Consulting Services	1	€100.00	21%	€100.00

Totals

Sum of line amounts€100.00

Total without VAT€100.00

Total VAT€21.00

Total with VAT€121.00

Amount due€121.00

VAT breakdown

VAT category	VAT rate (%)	Taxable amount	VAT amount
S	21%	€100.00	€21.00

How to Fix It

See this rule against your own invoice: every finding is pinned to the row it concerns.

Check your invoice Run this check in CI

Severity

Fatal

Rule set

Peppol BIS 3.0

Country

All EU

Fix type

Input required

Confidence

80%

Engine Classification

Business data required · Explicit input workflow · No assumptions made

Required input: Seller Electronic Address (EndpointID), Scheme ID

What is PEPPOL-EN16931-R020?

PEPPOL-EN16931-R020 is a fatal validation rule defined in the Peppol BIS 3.0 specification. It validates the EndpointID element under Party in the UBL invoice XML.

When this rule fires, the invoice is rejected by Peppol access points and never reaches the buyer.

Target path: //cac:AccountingSupplierParty/cac:Party/cbc:EndpointID

Why This Error Matters

Invoice will be rejected by PEPPOL validation. Seller electronic address is mandatory for PEPPOL network identification.

PEPPOL-EN16931-R020 is a hard failure — the invoice must be corrected and re-sent before it can reach the recipient.

Without a seller electronic address, the invoice cannot be routed through the Peppol network. The buyer's Access Point needs this identifier to verify the sender. The invoice will be rejected at the network level.

Validator Behavior

·Causes invoice rejection
·Rejected by PEPPOL Access Points
·Error returned: PEPPOL-EN16931-R020
·Specification: Peppol BIS 3.0

Before / After

Failing XML

<cac:Party>
  <!-- cbc:EndpointID is missing -->
</cac:Party>

Corrected XML

<cac:Party>
  <cbc:EndpointID>valid-value</cbc:EndpointID>
</cac:Party>

Technical Reference

XPath//cac:AccountingSupplierParty/cac:Party/cbc:EndpointID

SpecPeppol BIS 3.0

Operationderive

StrategyDerive EndpointID from seller VAT number or legal entity ID, with country-based scheme mapping. User must confirm because EndpointID is a high-risk routing field.

Common Causes

·Seller endpoint ID not configured
·Company PEPPOL registration not linked to invoicing
·Endpoint field not populated in company settings
·ERP does not export seller endpoint
·Multi-entity setup with missing endpoint for this entity

Seeing this in production? The API handles PEPPOL-EN16931-R020 automatically. See the fix response →

Commonly Seen In

All invoicing software

Frequently Asked Questions

If TaxCurrencyCode present, second TaxTotal required.

This requires user input to resolve. Provide the correct value for `cbc:EndpointID` (BT-34). Invoice Navigator detects this error and prompts for the required business data before applying a safe fix.

Yes, PEPPOL-EN16931-R020 is a critical error that must be fixed.

Validate your invoice

Drop your XML here to check for PEPPOL-EN16931-R020

Upload XML

Fix PEPPOL-EN16931-R020 with guided input

Upload your invoice and we'll ask for the missing data, then apply a safe, auditable fix.

Fix it now Automate via API