What it means
For a supporting document reference with ram:TypeCode 916, ram:AttachmentBinaryObject (BT-125) must have a mimeCode attribute (BT-125-1). This rule checks that the attribute exists, not whether it is empty or its value is allowed. It applies to the EN 16931 and Extended profiles of Factur-X and ZUGFeRD.
Why it matters
The attribute records the embedded document's file format. It is required by this XML structure.
How to fix it
Check the actual format of the embedded file. If you create the XML yourself, add its MIME type to ram:AttachmentBinaryObject, such as mimeCode="application/pdf" for a PDF. Other rules may restrict which formats you can use. If your software omits the attribute, ask its supplier to correct the attachment export. 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
Attribute '@mimeCode' is required in this context. Where this rule applies
| Rule set | Version |
|---|---|
| Factur-X 1.09 EN 16931 | 1.0.9-2 |
| Factur-X 1.09 EXTENDED | 1.0.9-2 |
| ZUGFeRD 2.5 EN 16931 | 2.5.2 |
| ZUGFeRD 2.5 EXTENDED | 2.5.2 |
Check your file
Drop your e-invoice to see whether FX-SCH-A-000285 still fails, and which other rules do.
Related rules
- FX-SCH-A-000286 An attached document must have a file name
- FX-SCH-A-000287 The file type of an attachment must be an allowed one
- 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