BR-DE-27In BT-42 sollen mindestens drei Ziffern enthalten sein.

Why does BR-DE-27 happen?

The field holds a placeholder ("-", "0", "n/a") because BR-DE-6 demands some value and the source system has no phone number on file. The expression behind it is .*([0-9].*){3,}.* against the value after normalize-space: three digits anywhere in the text, in any order, with anything between them. "+49" and "0" fail it; "extension 123" passes, and so does "2026".

What the validator checks

The expression the official KoSIT rule set evaluates — not paraphrased, but read from the Schematron file it ships. UBL and CII address different document trees, so the same rule reads differently in each.

UBL

matches(normalize-space(cbc:Telephone), $XR-TELEPHONE-REGEX)

Variables in it

$XR-TELEPHONE-REGEX

'.*([0-9].*){3,}.*'

CII

matches(normalize-space(ram:TelephoneUniversalCommunication/ram:CompleteNumber), $XR-TELEPHONE-REGEX)

Variables in it

$XR-TELEPHONE-REGEX

'.*([0-9].*){3,}.*'

Source: rule set v2026-08-31

How do you fix BR-DE-27?

Enter a real, reachable number (cac:Contact/cbc:Telephone in UBL, ram:DefinedTradeContact/ram:TelephoneUniversalCommunication/ram:CompleteNumber in CII). The format is free — +49 30 1234567 is fine; it just must not consist of fewer than three digits.

<cac:Contact>
  <cbc:Name>Buchhaltung</cbc:Name>
  <cbc:Telephone>-</cbc:Telephone>
</cac:Contact>

<cac:Contact>
  <cbc:Name>Buchhaltung</cbc:Name>
  <cbc:Telephone>+49 30 1234567</cbc:Telephone>
</cac:Contact>