What it means
A credit note in UBL states its document type (BT-3) in cbc:CreditNoteTypeCode, for example 381. The code list is fixed by the standard, so the code is written as plain text with no list identifier. This rule checks that the element has no listID attribute. It only looks at cbc:CreditNoteTypeCode, not at cbc:InvoiceTypeCode.
Why it matters
This is a warning. It is worth fixing when you can.
How to fix it
Export again in the standard EN 16931, XRechnung or Peppol BIS UBL format, and update the software if the attribute is still there. If you build the XML yourself, delete the listID attribute from cbc:CreditNoteTypeCode.
Once the file is corrected, check it again for free: Validate an invoice against EN 16931
Or fix the invoice in a form and download the corrected file, for 1 credit: Fix a rejected e-invoice
The rule as published
A UBL credit note should not include the CreditNoteTypeCode listID Where this rule applies
| Rule set | Version |
|---|---|
| EN 16931 (UBL) | 1.3.17 |
| EN 16931 (UBL credit note) | 1.3.17 |
| XRechnung 3.0 (UBL) | 3.0.2 |
| XRechnung 3.0 (UBL credit note) | 3.0.2 |
| Peppol BIS Billing 3.0 (invoice) | 2026.5 |
| Peppol BIS Billing 3.0 (credit note) | 2026.5 |
| SI-UBL 2.0 / NLCIUS (invoice) | 2.0.3.13 |
| SI-UBL 2.0 / NLCIUS (credit note) | 2.0.3.13 |
| France CTC (UBL invoice) | 1.4.0-04 |
| France CTC (UBL credit note) | 1.4.0-04 |
| CIUS-RO UBL Invoice 1.0.9 | 1.0.9 |
| CIUS-RO UBL Credit Note 1.0.9 | 1.0.9 |
Check your file
Drop your e-invoice to see whether UBL-CR-672 still fails, and which other rules do.
Related rules
- UBL-CR-673 An invoiced object reference must not have a description
- UBL-CR-674 The payment card number must not have a scheme attribute
- UBL-CR-675 The card network identifier must not have a scheme attribute
- UBL-CR-676 The direct debit mandate reference must not have a scheme
- UBL-CR-677 The account to be debited must not have a scheme attribute
- UBL-CR-678 The VAT category code must have no scheme