What it means
This rule checks whether mimeCode exists on ram:AttachmentBinaryObject inside a line's ram:SpecifiedLineTradeAgreement/ram:AdditionalReferencedDocument. An empty attribute satisfies this presence check. The test does not inspect the MIME value or the attachment's contents.
Why it matters
The mimeCode attribute declares the embedded attachment's file type.
How to fix it
Check the attachment's actual format. Add its corresponding allowed MIME type to mimeCode, such as application/pdf for a PDF. If your software omits the attribute, have its export corrected. Export 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 EXTENDED | 1.0.9-2 |
| ZUGFeRD 2.5 EXTENDED | 2.5.2 |
Check your file
Drop your e-invoice to see whether FX-SCH-A-001019 still fails, and which other rules do.
Related rules
- FX-SCH-A-001020 A line attachment needs an allowed file-type code
- FX-SCH-A-001021 A line attachment needs a file-name attribute
- FX-SCH-A-001022 A line's referenced document date needs a format attribute
- FX-SCH-A-001023 The date format code on a line document reference is not allowed
- FX-SCH-A-001024 The reference type code on a line document is not allowed
- FX-SCH-A-001025 The document type code on a line document is not allowed