What it means
Every attachment embedded in the invoice (BT-125) must carry a file name attribute (BT-125-2), for example filename="timesheet.pdf". In UBL this is the filename attribute on the cbc:EmbeddedDocumentBinaryObject element. The check looks at every element whose name ends in BinaryObject and fails when the filename attribute is missing. It does not check whether the value is non-empty or includes a file extension.
Why it matters
The standard requires the filename attribute, and an embedded attachment without one fails the check.
How to fix it
Give the attachment a file name in your invoicing software and export again. If you build the XML yourself, add filename="timesheet.pdf" to cbc:EmbeddedDocumentBinaryObject, next to the mimeCode attribute. If you do not need the attachment, remove it and export again. Recheck the file.
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
Binary object elements shall contain the file name attribute Where this rule applies
| Rule set | Version |
|---|---|
| EN 16931 (UBL) | 1.3.17 |
| EN 16931 (UBL credit note) | 1.3.17 |
| XRechnung 3.0 (UBL) | 3.0.2 |
| XRechnung 3.0 (UBL credit note) | 3.0.2 |
| Peppol BIS Billing 3.0 (invoice) | 2026.5 |
| Peppol BIS Billing 3.0 (credit note) | 2026.5 |
| SI-UBL 2.0 / NLCIUS (invoice) | 2.0.3.13 |
| SI-UBL 2.0 / NLCIUS (credit note) | 2.0.3.13 |
| France CTC (UBL invoice) | 1.4.0-04 |
| France CTC (UBL credit note) | 1.4.0-04 |
| CIUS-RO UBL Invoice 1.0.9 | 1.0.9 |
| CIUS-RO UBL Credit Note 1.0.9 | 1.0.9 |
Check your file
Drop your e-invoice to see whether UBL-DT-07 still fails, and which other rules do.