einvoice / EN 16931 / XRechnung rule reference

BR-DE-27

So beheben Sie den Fehler

In BT-42 sollen mindestens drei Ziffern enthalten sein.

Deutsche Fassung: Amtlicher KoSIT-Text (official KoSIT assert text).

BT-42 should contain at least three digits. Evaluated per seller Contact; an ABSENT telephone normalizes to '' and fires too.

Requires
BT-42 should contain at least three digits. Evaluated per seller Contact; an ABSENT telephone normalizes to '' and fires too.
Business terms
BT-42
Syntax
Binds the UBL-2.1 Invoice / CreditNote syntax and the UN/CEFACT-CII syntax
Location (UBL-2.1 path)
/ubl:Invoice/cac:AccountingSupplierParty/cac:Party/cac:Contact
Fix (Deutsch)
Korrigieren Sie `/ubl:Invoice/cac:AccountingSupplierParty/cac:Party/cac:Contact`, sodass gilt: In BT-42 sollen mindestens drei Ziffern enthalten sein.
Fix
Correct `/ubl:Invoice/cac:AccountingSupplierParty/cac:Party/cac:Contact` so that BT-42 should contain at least three digits. Evaluated per seller Contact; an ABSENT telephone normalizes to '' and fires too.
Severity
warning
Provenance source
xrechnung-ubl
Provenance assert

In BT-42 sollen mindestens drei Ziffern enthalten sein.

The Location above is a UBL-2.1 path, and no UN/CEFACT-CII path for this rule is published here; Fix and Fix (Deutsch), verbatim from remediation_catalog.json and not reworded here; the UN/CEFACT-CII binding of this rule is differentially proven against the official KoSIT XRechnung 2.5.0 (XRechnung 3.0.2) Schematron.

Korrektur prüfen: Laden Sie die geänderte Rechnung in den Browser-Validator unter /einvoice/validate/ — er führt dieselbe Engine lokal im Browser aus, ohne Upload, und meldet BR-DE-27 nicht mehr, sobald die Korrektur greift.

Where to check the fix: paste the corrected invoice into the browser validator at /einvoice/validate/ — it runs this same engine locally in your browser, with no upload, and stops reporting BR-DE-27 once the edit lands.

The same invoice, failing and fixed

No vendored test suite ships a labelled example for this rule, so this pair was found rather than written. The engine was run over the vendored instance corpus/xrechnung-testsuite/src/test/technical-cases/cius/01.06_minimal_test_ubl.xml under --profile xrechnung, then re-run over the same file with one mechanical edit applied to one element, over and over, until the edit below changed the verdict: the text content of Telephone was deleted, leaving the element present but empty. The page publishes it because the engine reported BR-DE-27 for the edited document and did not report it for the untouched one.

UBL Invoice — fails

The vendored file around the change, verbatim:

<cac:Contact>
  <cbc:Name>Tim Tester</cbc:Name>
  <cbc:Telephone></cbc:Telephone>
  <cbc:ElectronicMail>tim.tester@test.com</cbc:ElectronicMail>
</cac:Contact>

UBL Invoice — passes

The same lines as 01.06_minimal_test_ubl.xml actually ships them — this block is the fix for the block above:

<cac:Contact>
  <cbc:Name>Tim Tester</cbc:Name>
  <cbc:Telephone>012 3456789</cbc:Telephone>
  <cbc:ElectronicMail>tim.tester@test.com</cbc:ElectronicMail>
</cac:Contact>

What the engine reports for the edited invoice

{
  "element": "cac:AccountingSupplierParty/cac:Party/cac:Contact/cbc:Telephone",
  "field": "cac:AccountingSupplierParty/cac:Party/cac:Contact/cbc:Telephone",
  "fix_hint": "Correct `/ubl:Invoice/cac:AccountingSupplierParty/cac:Party/cac:Contact` so that BT-42 should contain at least three digits. Evaluated per seller Contact; an ABSENT telephone normalizes to '' and fires too.",
  "location": "/ubl:Invoice/cac:AccountingSupplierParty/cac:Party/cac:Contact",
  "message": "'Seller contact telephone number' (BT-42) should contain at least three digits.",
  "rule": "BR-DE-27",
  "severity": "warning",
  "terms": [
    "BT-42"
  ],
  "title": "BT-42 should contain at least three digits. Evaluated per seller Contact; an ABSENT telephone normalizes to '' and fires too."
}

Rule ids the engine reports for 01.06_minimal_test_ubl.xml untouched: BR-DE-TMP-32. After the edit, BR-DE-27 BR-DE-6 are reported that were not before — one mechanical edit can break more than one rule at a time, and BR-DE-6 is the neighbour this one takes with it.

Two honest limits. This is an edit that provokes the rule, not the only one, and it is not a claim about how real exporters break it. And it is the reverse of the fix a reader needs: the passing block is the vendored file's own content, which is what a conformant invoice looks like here.

Reproduce it yourself: take corpus/xrechnung-testsuite/src/test/technical-cases/cius/01.06_minimal_test_ubl.xml from this repository, apply the one edit named above, and run einvoice validate 01.06_minimal_test_ubl.xml --profile xrechnung --format json, or paste the file into the browser validator, which runs this same engine locally with no upload.

Everything here is free and open source — pick up whatever helps, at your own pace: