PEPPOL-EN16931-R020:Seller electronic address missing
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.
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 non-compliant and will be rejected by Peppol access points and national validation services. The sending system receives a rejection response and the invoice does not reach 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. Invoices that trigger this rule are rejected at the access point and never reach the recipient. In Peppol networks, this means your sending system receives an MLR (Message Level Response) with a rejection status. The invoice must be corrected and re-sent, adding delay to your payment cycle.
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
<cac:Party> <!-- cbc:EndpointID is missing --> </cac:Party>
<cac:Party> <cbc:EndpointID>valid-value</cbc:EndpointID> </cac:Party>
Technical Reference
//cac:AccountingSupplierParty/cac:Party/cbc:EndpointIDCommon 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
Frequently Asked Questions
If TaxCurrencyCode present, second TaxTotal required.
Add second TaxTotal with tax currency amount. Invoice Navigator can help identify and fix this issue.
Yes, PEPPOL-EN16931-R020 is a critical error that must be fixed.
See Also
Related Errors
Last updated: 27 February 2026
Handle PEPPOL-EN16931-R020 Automatically in Your Pipeline
The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.