How do I fix UBL-CR-669?

Invoice Navigator automatically removes the disallowed `cbc:AllowanceChargeReasonCode` element from your Invoice (UBL-CR-669). You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.

Is UBL-CR-669 a critical error?

Yes, UBL-CR-669 is a critical error that will cause invoice rejection. It must be fixed before submission.

Can UBL-CR-669 be automatically fixed?

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

errorUBL 2.1

`UBL-CR-669`:A UBL invoice should not include a Price Allowance Reason Code

UBL 2.1 Invoice schema does not include `cac:Price/cac:AllowanceCharge/cbc:AllowanceChargeReasonCode`. This element must be removed for EN 16931 compliance (rule UBL-CR-669).

Severity

Fatal

Rule set

UBL 2.1

Country

All EU

Fix type

AUTO-FIX

Confidence

90%

Engine Classification

Remove disallowed UBL element per EN16931 specification

Confidence: 90% · Applied automatically in pipeline

What is UBL-CR-669?

UBL-CR-669 is a fatal validation rule defined in the UBL 2.1 specification. It validates the AllowanceChargeReasonCode element under AllowanceCharge 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: //cac:Price/cac:AllowanceCharge/cbc:AllowanceChargeReasonCode

Get API Access Test This Error ↓

Why This Error Matters

Invoice will be rejected by EN16931 validators. These conformance rules prohibit UBL attributes and element combinations not in the EN16931 e-invoicing profile. Remove the disallowed attribute or restructure the element.

UBL-CR-669 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
·Fails UBL schema validation
·Error returned: UBL-CR-669
·Specification: UBL 2.1

Before / After

Failing XML

<cac:AllowanceCharge>
  <cbc:AllowanceChargeReasonCode>value</cbc:AllowanceChargeReasonCode>
</cac:AllowanceCharge>

Corrected XML

<cac:AllowanceCharge>
  <!-- cbc:AllowanceChargeReasonCode removed for EN 16931 compliance -->
</cac:AllowanceCharge>

Technical Reference

XPath//cac:Price/cac:AllowanceCharge/cbc:AllowanceChargeReasonCode

SpecUBL 2.1

Operationremove

StrategyRemove disallowed UBL element per EN16931 specification

Common Causes

·Price contains AllowanceCharge ReasonCode element
·Price AllowanceChargeReasonCode not in EN16931
·Reason code for price discount not permitted
·Use BaseAmount only for price allowances
·ERP exports coded reason for price adjustment

Seeing this in production? The API handles UBL-CR-669 automatically. See the fix response →

Handle UBL-CR-669 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

UBL-CR-669:A UBL invoice should not include a Price Allowance Reason Code