What it means
The delivery party on an invoice line can carry an electronic address (ram:URIUniversalCommunication), for example an email address or a Peppol ID. When that entry is present, it must contain exactly one ram:URIID.
Why it matters
The recipient's software reads the entry as a single address. An entry with none or two does not fit the structure of the Extended profile, so the file fails the schema check and is reported as invalid.
How to fix it
In your invoicing software, open the delivery party of the line and check its email or electronic address field. Enter one address, or clear the field so that nothing is written. If you build the XML yourself, put a single ram:URIID inside ram:URIUniversalCommunication, or leave the element out.
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-001105 still fails, and which other rules do.
Related rules
- FX-SCH-A-001106 The delivery party's electronic address needs a scheme (Extended)
- FX-SCH-A-001107 Unsupported electronic address scheme for the delivery party
- FX-SCH-A-001108 Repeated identifier for the final recipient on a line
- FX-SCH-A-001109 Repeated role code for the final recipient on a line
- FX-SCH-A-001110 Repeated electronic address entry for the final recipient
- FX-SCH-A-001111 Repeated tax registration for the final recipient