What it means
Each ram:ShipFromTradeParty under ram:ApplicableHeaderTradeDelivery may contain zero or one direct ram:URIUniversalCommunication child. This rule counts communication blocks, not the address values inside them.
Why it matters
The Extended profile allows one optional URI communication block for this party. Repeating the block does not match the required XML structure.
How to fix it
Check ram:ApplicableHeaderTradeDelivery/ram:ShipFromTradeParty in your XML or export mapping. Keep the intended ram:URIUniversalCommunication block and remove the extra blocks, or remove them all if you do not need this information. Export your invoice again and recheck it.
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:URIUniversalCommunication' 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-000796 still fails, and which other rules do.
Related rules
- FX-SCH-A-000797 Use at most one ship-from tax registration
- FX-SCH-A-000798 The ship-from contact email block needs one address field
- FX-SCH-A-000799 The ship-from contact fax block needs one number field
- FX-SCH-A-000800 The ship-from contact telephone block needs one number field
- FX-SCH-A-000801 The ship-from party's global ID needs a scheme attribute
- FX-SCH-A-000802 Use an allowed ship-from identifier scheme