Skip to content

Warning: worth checking

CII-SR-325: Delivery event must not carry an embedded file

In short

CII-SR-325 means the delivery event in the file has a file embedded in it (DescriptionBinaryObject), which EN 16931 does not use. It is a warning, so the invoice is still accepted; remove the embedded file from the delivery event.

On this page

What it means

The delivery event (ActualDeliverySupplyChainEvent) carries the delivery date (BT-72). This rule checks that it has no DescriptionBinaryObject, a file such as an image or PDF stored inside the event as binary data.

Why it matters

EN 16931 has one place for files that go with an invoice, the attachments (BG-24). Anything embedded in the delivery event is outside that, so the recipient's software is unlikely to show it. The invoice is not rejected, but the file makes it larger.

How to fix it

Remove the file from the delivery event. If the buyer needs the document, for example a signed delivery note, add it as an attachment to the invoice in your invoicing software, which writes it to the right place. Check the export settings if the software keeps embedding it.

The rule as published

DescriptionBinaryObject 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-SR-325 still fails, and which other rules do.