PEPPOL-EN16931-CL008:Electronic address identifier scheme must be from the codelist "Electronic...
The electronic address identifier scheme must be from the PEPPOL Electronic Address Identifier Scheme codelist. This identifies what type of endpoint ID is being used (GLN, PEPPOL ID, etc.).
Engine Classification
Suggest correct endpoint scheme based on identifier format. User must confirm because wrong scheme affects network routing and delivery.
Confidence: 85% · Applied automatically in pipeline
What is PEPPOL-EN16931-CL008?
PEPPOL-EN16931-CL008 is a fatal validation rule defined in the EN 16931 specification. It validates the @schemeID element under ram:URIID 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: ram:URIUniversalCommunication/ram:URIID/@schemeID
Why This Error Matters
Invoice will be rejected by PEPPOL validation. Endpoint scheme must match the actual identifier type for proper routing.
PEPPOL-EN16931-CL008 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
- ·Error returned: PEPPOL-EN16931-CL008
- ·Specification: EN 16931
Before / After
<Invoice> <!-- Issue: Electronic address identifier scheme must be from the Peppol --> </Invoice>
<Invoice> <!-- Issue resolved per EN 16931 --> </Invoice>
Technical Reference
ram:URIUniversalCommunication/ram:URIID/@schemeIDCommon Causes
- ·Invalid endpoint scheme code
- ·Using wrong scheme for the identifier type
- ·Scheme code not in PEPPOL allowed list
- ·Typo in scheme code
- ·Old or deprecated scheme code used
Seeing this in production? The API handles PEPPOL-EN16931-CL008 automatically. See the fix response →
See Also
Last updated: 27 February 2026
Handle PEPPOL-EN16931-CL008 Automatically in Your Pipeline
The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.