Skip to content

Fatal

CII-DT-030: Use the supported attachment element

In short

Fatal: fails the selected checks.

CII-DT-030 means a CII document reference contains ram:AttachedSpecifiedBinaryFile. Remove this element. If you need the file as a supporting attachment, recreate it using ram:AttachmentBinaryObject on ram:AdditionalReferencedDocument with ram:TypeCode 916.

On this page

What it means

Every CII reference element whose name ends in ReferencedDocument must be free of ram:AttachedSpecifiedBinaryFile, including supporting document references. Supporting attachments use ram:AttachmentBinaryObject (BT-125) on ram:AdditionalReferencedDocument with ram:TypeCode 916 instead.

Why it matters

These are different XML structures. The supporting attachment field used by this CII mapping is ram:AttachmentBinaryObject, not ram:AttachedSpecifiedBinaryFile.

How to fix it

Remove ram:AttachedSpecifiedBinaryFile from the affected reference. If you need to retain the attachment, recreate it as BT-125 in ram:AttachmentBinaryObject on the correct supporting document reference, including the file name and MIME type. Do not assume that renaming the old element will produce the correct structure. 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

AttachedSpecifiedBinaryFile 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
Rule text from phive-rules 4.6.4.

Check your file

Drop your e-invoice to see whether CII-DT-030 still fails, and which other rules do.

Updated 6 November 2026