How do I fix UBL-CR-633?

Invoice Navigator automatically removes the disallowed `cbc:AllowanceChargeReasonCode` element from your Invoice. You can also use Invoice Navigator's automatic Fixer tool to correct this instantly.

Is UBL-CR-633 a critical error?

Yes, UBL-CR-633 is a critical error that will cause invoice rejection. It must be fixed before submission to ensure your invoice is accepted.

Can UBL-CR-633 be automatically fixed?

Yes, UBL-CR-633 can be automatically corrected. The fix is applied without modifying financial fields.

Error codes · UBL 2.1

UBL-CR-633In your invoicing software

A UBL invoice should not include the InvoiceLine Item Price AllowanceCharge AllowanceChargeReasonCode

This is the rejection, word for word: „[UBL-CR-633] UBL 2.1 Invoice schema does not include `cac:Price/cac:AllowanceCharge/cbc:AllowanceChargeReasonCode`. This element must be removed for EN 16931 compliance.“

What to have readyNothing. The file has to be re-exported from your invoicing software; we check it again afterwards.

What we doInvoice Navigator automatically removes the disallowed `cbc:AllowanceChargeReasonCode` element from your Invoice.

Choose the rejected invoiceor drop it here

XRechnung XML or ZUGFeRD PDF. Checking is free · corrected file €1.90 · the first every 30 days is free · no sign-up.

If you enter it yourself in your invoicing software

Before

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

After

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

Element order is part of the rule: if the element sits in the wrong place, the validator rejects with UBL-CR-633.

What the finding looks likeExample

FindingStructure invalid · UBL-CR-633

Location/Invoice/cac:InvoiceLine/cac:Price/cac:AllowanceCharge/cbc:AllowanceChargeReasonCode

From youA re-exported file

ThenRe-export

ProofSHA-256 and /verify link after the check