What it means
The test allows at most one ram:URIUniversalCommunication directly inside ram:BuyerTradeParty (BG-7). This block holds the buyer's electronic address (BT-49). The test counts blocks, not their address elements, and does not check the address or delivery. It applies to the Basic WL, Basic, EN 16931 and Extended profiles of Factur-X 1.09 and ZUGFeRD 2.5.
Why it matters
One block gives your buyer's electronic address a single place in the structured invoice. This structural check does not establish whether an address can receive e-invoices.
How to fix it
Check the electronic address the buyer asked you to use. Make sure your XML export puts it in one ram:URIUniversalCommunication directly under ram:BuyerTradeParty, rather than creating repeated blocks. Remove duplicates, export again 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:URIUniversalCommunication' may occur at maximum 1 times. Where this rule applies
| Rule set | Version |
|---|---|
| Factur-X 1.09 BASIC WL | 1.0.9-2 |
| Factur-X 1.09 BASIC | 1.0.9-2 |
| Factur-X 1.09 EN 16931 | 1.0.9-2 |
| Factur-X 1.09 EXTENDED | 1.0.9-2 |
| ZUGFeRD 2.5 BASIC WL | 2.5.2 |
| ZUGFeRD 2.5 BASIC | 2.5.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-000165 still fails, and which other rules do.
Related rules
- FX-SCH-A-000166 The buyer can have at most one tax registration block
- FX-SCH-A-000167 The buyer's address can have at most one region field
- FX-SCH-A-000168 The buyer's electronic address block needs one address element
- FX-SCH-A-000169 A tax representative needs one tax registration block
- FX-SCH-A-000171 A delivery event needs one date element
- FX-SCH-A-000172 The invoice can have at most one payment reference