What it means
This rule checks mimeCode on ram:AttachmentBinaryObject inside a line's ram:SpecifiedLineTradeAgreement/ram:AdditionalReferencedDocument against file-type list 19. An empty value passes. FX-SCH-A-001019 checks attribute presence only. Neither test verifies the attachment's actual format.
Why it matters
The profile restricts the declared MIME types of embedded attachments. An unlisted type does not establish what software the recipient can use.
How to fix it
Check the actual file format. If it is allowed, use its exact MIME value, such as application/pdf for a PDF. Otherwise, convert the file to an allowed format and update the embedded data, mimeCode and filename. Changing only the label or file extension does not convert the file. 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
Value of '@mimeCode' is not allowed. 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-001020 still fails, and which other rules do.
Related rules
- 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
- FX-SCH-A-001026 Line delivery terms need exactly one delivery terms code