What it means
This rule counts ram:URIID elements inside each ram:SellerTradeParty/ram:DefinedTradeContact/ram:EmailURIUniversalCommunication. Each email block must contain one ram:URIID. The test does not check its text or email format; an empty ram:URIID still counts. It applies to the EN 16931 and Extended profiles of Factur-X and ZUGFeRD.
Why it matters
A supplied contact email block has a defined structure with one address element. Missing or repeated address elements do not follow that structure.
How to fix it
Check the seller contact email (BT-43) in your source invoice. In the XML, put the intended email address in one ram:URIID inside the affected ram:EmailURIUniversalCommunication under the seller's ram:DefinedTradeContact. Remove extra ram:URIID elements. If you are not supplying a contact email, remove the whole email block rather than leaving an empty block. Export and recheck your invoice.
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:URIID' must occur exactly 1 times. Where this rule applies
| Rule set | Version |
|---|---|
| Factur-X 1.09 EN 16931 | 1.0.9-2 |
| Factur-X 1.09 EXTENDED | 1.0.9-2 |
| ZUGFeRD 2.5 EN 16931 | 2.5.2 |
| ZUGFeRD 2.5 EXTENDED | 2.5.2 |
Check your file
Drop your e-invoice to see whether FX-SCH-A-000577 still fails, and which other rules do.
Related rules
- FX-SCH-A-000578 The seller's contact phone must hold exactly one number
- FX-SCH-A-000579 The seller identifier scheme must be an ISO 6523 code
- FX-SCH-A-000580 Use a listed seller country code
- FX-SCH-A-000581 Use a listed seller registration scheme
- FX-SCH-A-000582 Use a listed seller electronic address scheme
- FX-SCH-A-000583 Use format 102 for the delivery date