PEPPOL-EN16931-CL003:Reason code MUST be according to UNCL 7161 D.16B.
The charge reason code must be from the UNCL 7161 D.16B list. This code explains why a surcharge or additional charge is being applied.
Engine Classification
Normalize electronic address scheme to valid EAS code
Confidence: 80% · Applied automatically in pipeline
What is PEPPOL-EN16931-CL003?
PEPPOL-EN16931-CL003 is a fatal validation rule defined in the PEPPOL_BIS specification. It validates the @schemeID element 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: //cbc:EndpointID/@schemeID
Why This Error Matters
Invoice will be rejected by PEPPOL validation. Charge reasons must use standard codes for proper processing.
PEPPOL-EN16931-CL003 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: PEPPOL-EN16931-CL003
- ·Specification: PEPPOL_BIS
XML Example
Generic example based on the rule's target XPath. Your actual XML structure may differ.
<!-- Triggers validation error --> <@schemeID></@schemeID>
<!-- Corrected --> <@schemeID>VALID_VALUE</@schemeID>
Technical Reference
//cbc:EndpointID/@schemeIDCommon Causes
- ·Invalid or unknown charge reason code
- ·Using old version of code list
- ·Custom code not in standard list
- ·Typo in charge code
- ·Code from wrong code list used
Seeing this in production? The API handles PEPPOL-EN16931-CL003 automatically. See the fix response →
Last updated: 21 February 2026
Handle PEPPOL-EN16931-CL003 Automatically in Your Pipeline
The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.