errorbusinessPeppol BIS 3.0

PEPPOL-EN16931-R020: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.

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

How to Fix It

.

.

.

.

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.

Related Errors

Related Content

Last updated: 7 April 2026

Share this guide:

Validate your invoice

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

Fix PEPPOL-EN16931-R020 with guided input

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