What it means
For ram:AttachmentBinaryObject inside a supporting document reference with ram:TypeCode 916, a non-empty mimeCode (BT-125-1) must be application/pdf, image/png, image/jpeg, text/csv, application/vnd.openxmlformats-officedocument.spreadsheetml.sheet or application/vnd.oasis.opendocument.spreadsheet. An empty value passes this particular test. FX-SCH-A-000285 separately checks attribute presence. This rule applies to the EN 16931 profiles of Factur-X and ZUGFeRD.
Why it matters
The profile defines a permitted list of MIME codes for embedded supporting documents. A non-empty code outside that list fails this check, regardless of what formats a particular recipient's software supports.
How to fix it
Use an attachment in PDF, PNG, JPEG, CSV, XLSX or OpenDocument spreadsheet format. If the file uses another format, convert it to an allowed format before attaching it; do not just change its extension or MIME code. If it is already a PDF, make sure the export writes application/pdf rather than an incorrect value such as application/octet-stream. Export again and recheck.
Once the file is corrected, check it again for free: Validate a ZUGFeRD invoice
Or fix the invoice in a form and download the corrected file, for 1 credit: Fix a rejected e-invoice Beta
The rule as published
Value of '@mimeCode' is not allowed. Where this rule applies
| Rule set | Version |
|---|---|
| Factur-X 1.09 EN 16931 | 1.0.9-2 |
| ZUGFeRD 2.5 EN 16931 | 2.5.2 |
Check your file
Drop your e-invoice to see whether FX-SCH-A-000287 still fails, and which other rules do.
Related rules
- FX-SCH-A-000288 The buyer can have only one contact
- FX-SCH-A-000289 A buyer telephone entry must contain exactly one number
- FX-SCH-A-000290 Only one rounding amount is allowed
- FX-SCH-A-000291 A payment instruction can have only one text
- FX-SCH-A-000292 A bank entry must contain exactly one BIC
- FX-SCH-A-000293 Only one object reference is allowed in a line's settlement details