Telephone communication requires exactly one complete number

Error FX-SCH-A-000913 Factur-X

Element 'ram:CompleteNumber' must occur exactly 1 times.

Mandatory rule: As long as it is violated, the invoice is invalid and will be rejected by validators.
What is wrong

The ram:TelephoneUniversalCommunication element does not contain exactly one ram:CompleteNumber element. The complete number is either missing or the element occurs more than once.

What the rule means

The payee’s contact telephone number must be provided as exactly one complete number.

Please provide exactly one complete telephone number for the payee’s contact

The payee party’s contact telephone number is missing its complete number, or that number is entered more than once. This can be resolved by having a single ram:CompleteNumber.

What to do
  1. Find the payee party contact’s ram:TelephoneUniversalCommunication.
  2. Make sure it contains exactly one ram:CompleteNumber.
  3. Generate the invoice again and validate it.
What it looks like
✗ Triggers the message 
<ram:TelephoneUniversalCommunication/>
✓ Correct 
<ram:TelephoneUniversalCommunication>
  <ram:CompleteNumber>+33123456789</ram:CompleteNumber>
</ram:TelephoneUniversalCommunication>
Technical details

The XPath test requires exactly one direct ram:CompleteNumber child of ram:TelephoneUniversalCommunication.

Where the rule applies

The rule applies to the telephone number of the payee party’s contact in the invoice settlement.

Context (rule/@context)
/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ ram:PayeeTradeParty/ram:DefinedTradeContact/ram:TelephoneUniversalCommunication
Test expression (assert/@test)
count(ram:CompleteNumber)=1