What it means
The check applies to all CII reference elements whose names end in ReferencedDocument. They may contain ram:ReferenceTypeCode only when the reference is ram:AdditionalReferencedDocument with a ram:TypeCode value of 130. In that structure, ram:ReferenceTypeCode identifies the scheme of the invoiced object identifier, BT-18-1 at invoice level or BT-128-1 on a line.
Why it matters
This scheme field describes an invoiced object identifier. It is not a general reference type field for contracts, orders or other referenced documents.
How to fix it
Remove ram:ReferenceTypeCode from the affected reference. If you are providing an invoiced object identifier, such as a subscription number, use the correct ram:AdditionalReferencedDocument with ram:TypeCode 130 and put its scheme in ram:ReferenceTypeCode. Do not change an unrelated reference's type just to retain the element. Export the corrected file and recheck it.
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
ReferenceTypeCode should not be present Where this rule applies
| Rule set | Version |
|---|---|
| EN 16931 (CII) | 1.3.17 |
| XRechnung 3.0 (CII) | 3.0.2 |
| NLCIUS (CII) | 1.0.3.13 |
| France CTC (CII) | 1.4.0-04 |
Check your file
Drop your e-invoice to see whether CII-DT-024 still fails, and which other rules do.
Related rules
- CII-DT-025 Remove SectionName from document references
- CII-DT-026 Remove previous revision identifiers from document references
- CII-DT-027 Only invoice references may use this date field
- CII-DT-028 Remove effective periods from document references
- CII-DT-029 Remove IssuerTradeParty from document references
- CII-DT-030 Use the supported attachment element