What it means
Each ram:ProductEndUserTradeParty under ram:ApplicableHeaderTradeAgreement may contain zero or one direct ram:URIUniversalCommunication child. This does not count email blocks inside ram:DefinedTradeContact.
Why it matters
The Extended profile allows at most one electronic address block directly within each product end user block.
How to fix it
In your CII XML, keep the intended ram:URIUniversalCommunication block directly inside ram:ProductEndUserTradeParty and remove additional blocks at that location. Do not remove the contact person's email block to fix this rule. Export the corrected file 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-000711 still fails, and which other rules do.
Related rules
- FX-SCH-A-000712 Use at most one end user tax registration block
- FX-SCH-A-000713 Put one address field in each end user contact email block
- FX-SCH-A-000714 Put one number field in each end user contact fax block
- FX-SCH-A-000715 Put one number field in each end user contact telephone block
- FX-SCH-A-000716 Add a scheme to the end user's global identifier
- FX-SCH-A-000717 Use an allowed scheme for the end user's global identifier