How do I fix PEPPOL-EN16931-CL002?

The allowance reason code must be from the UNCL 5189 D.16B subset. This code explains why a discount or allowance is being applied. You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.

Is PEPPOL-EN16931-CL002 a critical error?

Yes, PEPPOL-EN16931-CL002 is a critical error that will cause invoice rejection. It must be fixed before submission.

Can PEPPOL-EN16931-CL002 be automatically fixed?

Many instances of PEPPOL-EN16931-CL002 can be automatically corrected using Invoice Navigator's compliance engine. The fix is applied in your pipeline with full audit evidence.

errorPEPPOL_BIS

`PEPPOL-EN16931-CL002`:Reason code MUST be according to subset of UNCL 5189 D.16B.

The allowance reason code must be from the UNCL 5189 D.16B subset. This code explains why a discount or allowance is being applied.

Severity

Fatal

Rule set

PEPPOL_BIS

Country

All EU

Fix type

AUTO-FIX

Confidence

90%

Engine Classification

Set Peppol BIS 3.0 profile identifier

Confidence: 90% · Applied automatically in pipeline

What is PEPPOL-EN16931-CL002?

PEPPOL-EN16931-CL002 is a fatal validation rule defined in the PEPPOL_BIS specification. It validates the ProfileID 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: /Invoice/cbc:ProfileID

Get API Access

Why This Error Matters

Invoice will be rejected by PEPPOL validation. Allowance reasons must use standard codes for interoperability.

PEPPOL-EN16931-CL002 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-CL002
·Specification: PEPPOL_BIS

XML Example

Generic example based on the rule's target XPath. Your actual XML structure may differ.

Before

<!-- Missing or empty element triggers cbc:ProfileID error -->
<cbc:ProfileID></cbc:ProfileID>

After

<!-- Provide the required value -->
<cbc:ProfileID>VALID_VALUE</cbc:ProfileID>

Technical Reference

XPath/Invoice/cbc:ProfileID

SpecPEPPOL_BIS

Operationset_value

StrategySet Peppol BIS 3.0 profile identifier

Common Causes

·Invalid or unknown allowance reason code
·Using old version of code list
·Custom code not in standard list
·Typo in reason code
·Code from wrong code list used

Seeing this in production? The API handles PEPPOL-EN16931-CL002 automatically. See the fix response →

Last updated: 21 February 2026

Share this guide:

Handle PEPPOL-EN16931-CL002 Automatically in Your Pipeline

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

Get API Access View API Documentation

PEPPOL-EN16931-CL002:Reason code MUST be according to subset of UNCL 5189 D.16B.