IN-BUYER-ENDPOINT-SCHEME:Buyer endpoint is missing its scheme identifier
Fix: Invoice Navigator automatically fixes this Invoice compliance issue by updating the relevant XML elements (IN-BUYER-ENDPOINT-SCHEME). Upload your invoice to fix this automatically.
The buyer's electronic address (EndpointID) in your invoice does not have a schemeID attribute. The schemeID tells the Peppol network what type of identifier is being used — for example, whether it is a GLN number, a VAT registration number, or a chamber of commerce number. Without this, the invoice cannot be delivered.
Engine Classification
Derives the correct EAS scheme code from the buyer endpoint value pattern and buyer country code using inferSchemeFromEndpoint()
Confidence: 95% · Applied automatically in pipeline
What is IN-BUYER-ENDPOINT-SCHEME?
IN-BUYER-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 rejected by Peppol access points and never reaches the buyer.
Target path: cac:AccountingCustomerParty/cac:Party/cbc:EndpointID/@schemeID
Why This Error Matters
Peppol requires standardized endpoint schemes.
IN-BUYER-ENDPOINT-SCHEME is a hard failure — the invoice must be corrected and re-sent before it can reach the recipient.
The Peppol network requires a scheme identifier on every electronic address to route invoices correctly. Without it, the Access Point rejects the invoice because it cannot determine whether the address is a GLN, VAT number, or other identifier type. Your invoice will not be delivered to the buyer.
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-BUYER-ENDPOINT-SCHEME
- ·Specification: Peppol BIS 3.0
How to Fix It
Check the buyer address type
Look at the value in the buyer EndpointID element. What type of number is it? A VAT number starts with a country code (e.g. DE, NL, FR). A GLN is exactly 13 digits. A Dutch KvK number is 8 digits.
Look up the scheme code
Each address type has a 4-digit scheme code. Common ones: 0088 (GLN), 0106 (Dutch KvK), 9930 (German VAT), 9944 (Dutch BTW), 0007 (Swedish org), 0009 (French SIRET).
Add the schemeID to your invoice
In your invoicing software, ensure the buyer EndpointID field includes the schemeID attribute. Example: schemeID="0088" for a GLN. If your software does not support this, contact the vendor.
Before / After
<Invoice> <!-- Issue: Buyer EndpointID must have a schemeID attribute from EAS cod --> </Invoice>
<Invoice> <!-- Issue resolved per Peppol BIS 3.0 --> </Invoice>
Technical Reference
cac:AccountingCustomerParty/cac:Party/cbc:EndpointID/@schemeIDCommon Causes
- ·Invoicing software exports EndpointID without the schemeID attribute
- ·ERP field mapping does not include the schemeID
- ·Invoice was created from a template missing the @schemeID
- ·Buyer's electronic address was entered manually without specifying the scheme
Seeing this in production? The API handles IN-BUYER-ENDPOINT-SCHEME automatically. See the fix response →
Commonly Seen In
Frequently Asked Questions
Electronic address scheme must be 4 digits.
Use valid 4-digit EAS scheme code. Invoice Navigator can help identify and fix this issue.
Yes, PEPPOL-EN16931-R005 is a critical error that must be fixed.
Related Errors
Related Content
Last updated: 27 February 2026
Validate your invoice
Drop your XML here to check for IN-BUYER-ENDPOINT-SCHEME
Auto-fix IN-BUYER-ENDPOINT-SCHEME in seconds
Upload your invoice and we fix this error automatically. Financial fields are never touched.