What it means
The check covers all ram elements whose names end in ReferencedDocument. It passes if there is no ram:TypeCode child, or if the element is ram:AdditionalReferencedDocument and has a ram:TypeCode value of 50, 130 or 916. These codes represent a tender or lot reference (BT-17), an invoiced object identifier (BT-18) and a supporting document respectively. Purchase order references (BT-13) and contract references (BT-12) do not qualify for the exception.
Why it matters
This CII mapping uses these codes to distinguish the supported kinds of additional reference. Other reference elements identify their purpose through their element names rather than this child code.
How to fix it
Find the reference reported by the check. If it is not ram:AdditionalReferencedDocument, remove its ram:TypeCode child. If it is an additional reference, correct the code to match its purpose: 50 for a tender or lot, 130 for an invoiced object, or 916 for a supporting document such as a timesheet. Do not relabel an unrelated reference just to pass this check. Save or regenerate your CII file, then check it again.
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
TypeCode 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-018 still fails, and which other rules do.
Related rules
- CII-DT-019 Remove GlobalID from document references
- CII-DT-020 Remove RevisionID from document references
- CII-DT-021 Descriptions belong on supporting document references
- CII-DT-022 Only supporting document references may contain embedded attachments
- CII-DT-023 Remove Information from document references
- CII-DT-024 Reference type codes belong on invoiced object identifiers