Attestwire › Rule reference › BR-DE-27

BR-DE-27 The seller telephone number must be diallable

noun · XRechnung · warning · BT-42

Your invoice carries a warning because the contact telephone number is not something anyone can dial: it has fewer than three digits. Text such as “Zentrale” satisfies the requirement to fill the field (BR-DE-6) but cannot be dialled. KoSIT rates this a warning, so the invoice is accepted. In the standard the field is BT-42, and BR-DE-27 is the rule that counts the digits.

Diese Regel auf Deutsch: BR-DE-27 — auf Deutsch erklärt.

Business term
BT-42 — Seller contact telephone number
Severity
warning
Applies to
xrechnung-ubl, xrechnung-cii

The fix

Write the full number in international format into seller.contact.phone, for example "+49 30 1234567".

What the rule requires

BT-42 must contain at least three digits. The rule starts where BR-DE-6 stops: that one only asks for the field to be filled, and BR-DE-27 asks for the content to be a telephone number.

Write the number in full and in international format: +49 30 1234567.

In this library the field is seller.contact.phone.

In BT-42 sollen mindestens drei Ziffern enthalten sein.

BR-DE-27 — KoSIT XRechnung Schematron 2.6.0 (XRechnung 3.0), XRechnung-UBL-validation.sch

A passing value

the shape this field expects
"phone": "+49 30 1234567"

Why it exists

A mandatory field that can be filled with anything will be filled with anything. This rule closes the gap: it does not check that anyone answers, but it does check that the number can be dialled. KoSIT rates it a warning: the invoice is accepted, it is just that nobody can call you.

What the library returns

The full error returned by @attestwire/en16931. It includes the rule ID, affected field and suggested correction. Developers can use this object in their application:

TeachingError
{
  "rule": "BR-DE-27",
  "field": "BT-42",
  "severity": "warning",
  "message": "The seller contact telephone number (BT-42) should contain at least three digits, but \"call us\" contains 0. KoSIT raises this as a warning rather than an error, so the invoice will be accepted — but the number as written cannot be dialled.",
  "fix": "Write the full number in international format, e.g. \"+49 30 1234567\".",
  "example": "\"phone\": \"+49 30 1234567\"",
  "xpath": "/ubl:Invoice/cac:AccountingSupplierParty/cac:Party/cac:Contact/cbc:Telephone",
  "docsUrl": "https://attestwire.com/rules/BR-DE-27"
}

xpath is always a UBL path. On a CII invoice, look for the matching CII field instead.

How our check differs

We count digits anywhere in the value, as KoSIT’s expression does, so "+49 30 1234567" and "030/1234567" pass, and so would "Room 101". If the field is empty, the finding is BR-DE-6 instead.

See also: BR-DE-6 — the rule that requires the field at all; BR-DE-28 — the same kind of shape check for the email address.