What it means
The check applies to all CII reference elements whose names end in ReferencedDocument. A ram:AttachmentBinaryObject is allowed only when its parent is ram:AdditionalReferencedDocument with a ram:TypeCode value of 916. It holds the supporting document attachment (BT-125).
Why it matters
An embedded supporting document has a specific place in the CII mapping. Other reference types do not provide this attachment field.
How to fix it
Remove ram:AttachmentBinaryObject from the affected reference. If you need to include the file, attach it to a supporting document reference using ram:AdditionalReferencedDocument with ram:TypeCode 916. Keep the contract, order or other original reference in its proper form. 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
AttachmentBinaryObject 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-022 still fails, and which other rules do.
Related rules
- CII-DT-023 Remove Information from document references
- CII-DT-024 Reference type codes belong on invoiced object identifiers
- 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