What it means
For each ram:URIUniversalCommunication under ram:ShipToTradeParty in the header delivery section, this rule requires exactly one direct ram:URIID child. It counts address elements; it does not check whether the address text is empty or correct.
Why it matters
The Extended profile uses one ram:URIID field for the address within each communication block. A missing or repeated field does not match that structure.
How to fix it
For the delivery party's electronic address, keep one ram:URIID containing the intended address inside each ram:URIUniversalCommunication block. Remove extra ram:URIID elements. If an electronic-address block is not required for your invoice, remove the whole block rather than leaving it incomplete. Export and recheck.
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-000829 still fails, and which other rules do.
Related rules
- FX-SCH-A-000830 The delivery party's electronic address needs a scheme
- FX-SCH-A-000831 The delivery party's electronic address scheme must be allowed
- FX-SCH-A-000832 The final delivery party can have only one ID
- FX-SCH-A-000833 The final delivery party can have only one role code
- FX-SCH-A-000834 Keep at most one electronic-address block for the final delivery party
- FX-SCH-A-000835 The final delivery party can have only one tax registration