BR-DE-27: what it means and how to fix it

The seller's telephone number should contain at least three digits.

RuleBR-DE-27
StandardXRechnung 3.0 (the German CIUS of EN 16931, published by KoSIT)
SeverityWarning
ConcernsBT-42: Seller contact telephone number

How to fix it

Give a real telephone number.

Where the field is in the XML

TermCII (XRechnung-CII, ZUGFeRD, Factur-X)UBL (XRechnung-UBL, Peppol)
BT-42
Seller contact telephone number
ram:SellerTradeParty/ram:DefinedTradeContact/ram:TelephoneUniversalCommunication/ram:CompleteNumbercac:AccountingSupplierParty/cac:Party/cac:Contact/cbc:Telephone

Check your own file for this rule

Up to 5 MB. Read in memory for this one request and not stored.

From your code

curl -H "Authorization: Bearer $API_KEY" -H "Content-Type: application/xml" \
  --data-binary @invoice.xml "https://tools.funwords.eu/einvoice/validate"

The answer lists every broken rule with its number, the field, a message with the figures from your file and the fix. E-invoice API: validate, convert to JSON, and create XRechnung or ZUGFeRD XML from JSON.

Questions

What does BR-DE-27 mean?

The seller's telephone number should contain at least three digits. It is a rule of XRechnung 3.0 (the German CIUS of EN 16931, published by KoSIT).

How do I fix BR-DE-27?

Give a real telephone number.

Is BR-DE-27 an error or a warning?

A warning: the invoice is still conformant, but the value should be corrected.

Does BR-DE-27 apply to ZUGFeRD and Factur-X too?

Only when the file declares the XRechnung specification identifier (the ZUGFeRD profile "XRECHNUNG" does). Files in the plain EN 16931 profile are checked against the European rules, not the German additions.

Related rules

Rule numbers are those of XRechnung 3.0 (KoSIT); the explanation is ours. Not tax or legal advice.