How do I fix UBL-CR-662?

Invoice Navigator automatically removes the disallowed `@listID` element from your Invoice (UBL-CR-662). You can also use Invoice Navigator's automatic Fixer tool to correct this instantly.

Is UBL-CR-662 a critical error?

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

Can UBL-CR-662 be automatically fixed?

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

Error codes · UBL 2.1

UBL-CR-662In your invoicing software

A UBL invoice should not include the AllowanceChargeReasonCode listID

This is the rejection, word for word: „[UBL-CR-662] UBL 2.1 Invoice schema does not include `cbc:AllowanceChargeReasonCode/@listID`. 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 `@listID` element from your Invoice (UBL-CR-662).

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

<cbc:AllowanceChargeReasonCode>
  <@listID>value</@listID>
</cbc:AllowanceChargeReasonCode>

After

<cbc:AllowanceChargeReasonCode>
  <!-- @listID removed for EN 16931 compliance -->
</cbc:AllowanceChargeReasonCode>

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

What the finding looks likeExample

FindingStructure invalid · UBL-CR-662

Location//cbc:AllowanceChargeReasonCode/@listID

From youA re-exported file

ThenRe-export

ProofSHA-256 and /verify link after the check