What it means
The seller must not have a LogoAssociatedSpecifiedBinaryFile element. That element stores a logo image inside the structured data of the invoice. EN 16931 has no field for a logo. The same restriction applies in the CII rules for XRechnung, NLCIUS and the French CTC rules.
Why it matters
This is a warning, so the file is still accepted. The recipient's software is not required to read or show the image, and it makes the file larger without adding anything the check can use. Fix it if you want a clean file, or if the recipient or a government e-invoicing portal limits file size.
How to fix it
Look in your invoicing software for an option such as include logo in the e-invoice or embed logo, and switch it off. The logo still appears on the invoice layout in the PDF, which is the right place for it. If you need to send a file with the invoice, add it as an attachment, because the standard has a separate place for those.
The rule as published
LogoAssociatedSpecifiedBinaryFile 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-SR-248 still fails, and which other rules do.
Related rules
- CII-SR-249 Leave out the buyer's role code
- CII-SR-250 Leave out the buyer's free-text description
- CII-SR-251 Leave out the buyer's legal form code
- CII-SR-252 Leave out the name inside the buyer's legal organisation
- CII-SR-254 Leave out the address inside the buyer's legal organisation
- CII-SR-255 Leave out the buyer's legal registration details block