What it means
In a CII file, the seller's contact telephone (BT-42) is held in TelephoneUniversalCommunication, in its CompleteNumber element. This rule warns when that same block also has a URIID element.
Why it matters
The invoice is still accepted. EN 16931 only reads the phone number from this block, so the buyer's software will normally ignore the URIID. If it held something the buyer needed, it does not arrive.
How to fix it
Check what the URIID holds. If it is the phone number, move it into CompleteNumber. If it is an email address, it belongs in the separate email element (BT-43). Then delete the URIID from the telephone block, or ask your software supplier to stop writing it.
The rule as published
URIID should not be present Where this rule applies
| Rule set | Version |
|---|---|
| EN 16931 (CII) | 1.3.17 |
| XRechnung 3.0 (CII) | 3.0.2 |
| NLCIUS (CII) | 1.0.3.13 |
| France CTC (CII) | 1.4.0-04 |
Check your file
Drop your e-invoice to see whether CII-SR-232 still fails, and which other rules do.
Related rules
- CII-SR-233 Seller phone number should not have a channel code
- CII-SR-234 Seller contact should not have a direct phone number
- CII-SR-235 Seller contact should not have a mobile phone number
- CII-SR-236 Seller contact should not have a fax number
- CII-SR-237 Seller email should not have a channel code
- CII-SR-238 Seller's email block should not contain a phone number field