errorbusinessPeppol BIS 3.0

PEPPOL-EN16931-R010:Buyer electronic address required

Fix: Add buyer endpoint ID with scheme (e.g., GLN, DUNS, or national ID) Provide the required value in the free validator.

Peppol invoices MUST include a buyer electronic address (BT-49) with a valid EndpointID and schemeID for network routing.

Severity
Fatal
Rule set
Peppol BIS 3.0
Country
All EU
Fix type
INPUT REQUIRED
Category
identifier

Engine Classification

Business data required · Explicit input workflow · No assumptions made

Required input: Buyer Endpoint ID, Endpoint Scheme (EAS code)

What is PEPPOL-EN16931-R010?

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

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

Target path: XPath: /Invoice/cac:AccountingCustomerParty/cac:Party/cac:PartyName/cbc:Name

Fix this error

Why This Error Matters

Invoice will be rejected by PEPPOL validation. Electronic address is mandatory for PEPPOL network routing.

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

Validator Behavior

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

How to Fix It

1.

Add EndpointID element

Under buyer Party (cac:AccountingCustomerParty/cac:Party)

2.

Set endpoint value

Use buyer VAT number or PEPPOL participant ID

3.

Add schemeID attribute

Use appropriate scheme (9930 for DE VAT, 9944 for NL VAT, 0088 for GLN)

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

XPathXPath: /Invoice/cac:AccountingCustomerParty/cac:Party/cac:PartyName/cbc:Name
SpecPeppol BIS 3.0
StrategyRequires buyer Peppol participant ID from the invoice sender — this is the buyer registration that cannot be auto-generated

Common Causes

  • ·Buyer endpoint ID not provided
  • ·Customer master data missing PEPPOL identifier
  • ·Buyer not registered on PEPPOL network
  • ·Endpoint field not mapped in invoice export
  • ·Manual invoice without electronic address lookup

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

Frequently Asked Questions

Buyer party must have name specified.

Add buyer endpoint ID with scheme (e.g., GLN, DUNS, or national ID) Invoice Navigator detects this error and prompts for the required business data before applying a safe fix.

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

Related Errors

IN-UNIT-CODESUnit of measure codes validation

Related Content

Glossary
Evidence Packe-Reporting
Errors
Missing direct debit mandate referenceEndpoint identifier scheme identifier SHALL be chosen from the Electronic...
Answers
What is the difference between B2G and B2B e-invoicing?
Regulations
EN 16931

Last updated: 7 April 2026

Share this guide:

Validate your invoice

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

Fix PEPPOL-EN16931-R010 with guided input

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

Fix it nowAutomate via API