What it means
This rule counts ram:AttachmentBinaryObject children of each ram:AdditionalReferencedDocument under a line's ram:SpecifiedLineTradeAgreement. Zero or one passes. The limit applies separately to each document reference.
Why it matters
The Extended profile provides a single optional embedded attachment element within each additional document reference.
How to fix it
Find the affected reference and remove duplicate attachment elements. If you need separate references for additional files, include the required ram:IssuerAssignedID and ram:TypeCode in each new reference and keep at most one ram:AttachmentBinaryObject in each. 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
Element 'ram:AttachmentBinaryObject' may occur at maximum 1 times. 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-001018 still fails, and which other rules do.
Related rules
- FX-SCH-A-001019 A line attachment needs a file-type attribute
- 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