errorPeppol BIS 3.0

IN-SELLER-ENDPOINT-SCHEME:Seller endpoint scheme ID validation

Electronic address schemeID must be from Peppol participant identifier schemes. Invoice Navigator can auto-derive the correct scheme based on country.

Severity
Fatal
Rule set
Peppol BIS 3.0
Country
All EU
Fix type
AUTO-FIX
Confidence
90%
Category
identifier

Engine Classification

Derive schemeID from country code or endpoint pattern

Confidence: 90% · Applied automatically in pipeline

What is IN-SELLER-ENDPOINT-SCHEME?

IN-SELLER-ENDPOINT-SCHEME is a fatal validation rule defined in the Peppol BIS 3.0 specification. It validates the @schemeID element under Party > EndpointID 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/@schemeID

Why This Error Matters

Peppol network requires valid scheme IDs for message routing.

IN-SELLER-ENDPOINT-SCHEME 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.

Invoice Navigator can automatically correct this error in your pipeline. The fix is applied with full audit evidence, so your compliance trail remains intact.

Validator Behavior

  • ·Causes invoice rejection
  • ·Rejected by PEPPOL Access Points
  • ·Error returned: IN-SELLER-ENDPOINT-SCHEME
  • ·Specification: Peppol BIS 3.0

How to Fix It

1.

Check scheme

Must be from ISO 6523 ICD list

2.

Common schemes

0088 (GLN), 0184 (Peppol), 0106 (NL KVK), 0190 (NL OIN)

3.

Country-specific

0208 (BE), 9906 (IT), 9914 (AT)

Before / After

Failing XML
<Invoice>
  <!-- Issue: Seller EndpointID must have a schemeID attribute from EAS co -->
</Invoice>
Corrected XML
<Invoice>
  <!-- Issue resolved per Peppol BIS 3.0 -->
</Invoice>

Technical Reference

XPath//cac:AccountingSupplierParty/cac:Party/cbc:EndpointID/@schemeID
SpecPeppol BIS 3.0
Operationderive
StrategyDerive schemeID from country code or endpoint pattern

Code Example

<cbc:EndpointID schemeID="0088">5790000435975</cbc:EndpointID>

Common Causes

  • ·Unknown scheme ID
  • ·Wrong code for country
  • ·Missing schemeID attribute

Seeing this in production? The API handles IN-SELLER-ENDPOINT-SCHEME automatically. See the fix response →

Commonly Seen In

Peppol-enabled systems

Frequently Asked Questions

Electronic address schemeID must be from Peppol participant identifier schemes.

Use valid Peppol participant scheme identifier. Invoice Navigator can help identify and fix this issue.

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

See Also

Related Errors

Last updated: 27 February 2026

Share this guide:

Handle IN-SELLER-ENDPOINT-SCHEME Automatically in Your Pipeline

The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.