What it means
Within the line's ram:SpecifiedLineTradeDelivery/ram:UltimateShipToTradeParty, the check allows zero or one ram:RoleCode child. It checks the number of elements, not their values.
Why it matters
The Extended profile provides one role-code field for this party. Repeating the element breaks that structural limit.
How to fix it
Check ram:RoleCode under the affected line's ram:UltimateShipToTradeParty. If you need a role code, retain the correct one in a single element. Otherwise, omit the field. Correct any export mapping that writes it repeatedly, then 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:RoleCode' 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-001109 still fails, and which other rules do.
Related rules
- FX-SCH-A-001110 Repeated electronic address entry for the final recipient
- FX-SCH-A-001111 Repeated tax registration for the final recipient
- FX-SCH-A-001112 The final recipient's contact email needs exactly one address
- FX-SCH-A-001113 The final recipient's contact fax entry needs one number element
- FX-SCH-A-001114 The final recipient's contact phone block needs a number
- FX-SCH-A-001115 The final recipient's global identifier needs a scheme