PEPPOL-EN16931-CL003:Reason code MUST be according to UNCL 7161 D.16B.
Fix: 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. Upload your invoice to fix this automatically.
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 rejected by Peppol access points and never reaches 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 — the invoice must be corrected and re-sent before it can reach the recipient.
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
How to Fix It
Find the incorrectly formatted value
Check @schemeID at //cbc:EndpointID/@schemeID. The current value does not match the required format.
Apply the correct format
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.
Update your export settings
If this occurs consistently, check your invoicing software's locale and format settings for XML export. Re-validate to confirm PEPPOL-EN16931-CL003 is resolved.
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 →
Frequently Asked Questions
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.
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. You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.
Yes, PEPPOL-EN16931-CL003 is a critical error that will cause invoice rejection. It must be fixed before submission.
Many instances of PEPPOL-EN16931-CL003 can be automatically corrected using Invoice Navigator's compliance engine. The fix is applied in your pipeline with full audit evidence.
Related Content
Last updated: 14 April 2026
Validate your invoice
Drop your XML here to check for PEPPOL-EN16931-CL003
Auto-fix PEPPOL-EN16931-CL003 in seconds
Upload your invoice and we fix this error automatically. Financial fields are never touched.