What it means
Within the payee (BG-10), each ram:DefinedTradeContact/ram:EmailURIUniversalCommunication must contain exactly one ram:URIID child element. An empty ram:URIID still counts as one; this rule does not check whether the email address is populated or valid.
Why it matters
The contact's email entry has a defined structure with one element for the address.
How to fix it
In ram:PayeeTradeParty/ram:DefinedTradeContact/ram:EmailURIUniversalCommunication, add the missing ram:URIID with the correct email address or remove extra ram:URIID elements. If you are not supplying an email address, remove the whole email entry rather than just its child element. Regenerate and recheck your file.
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 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-000911 still fails, and which other rules do.
Related rules
- FX-SCH-A-000912 The payee contact's fax entry needs one number element
- FX-SCH-A-000913 The payee contact's phone entry needs one number element
- FX-SCH-A-000914 The payee's global identifier needs a valid scheme code
- FX-SCH-A-000915 The payee's address needs exactly one country element
- FX-SCH-A-000916 The payee's address may contain one region element
- FX-SCH-A-000917 The payee's address needs a valid country code