Validation rules

BR-DE-26 — XRechnung rule

A corrected invoice (type_code 384) should reference the invoice it corrects (BT-25).

Rule: BR-DE-26 — official EN 16931 / XRechnung rule
Severity: warning
Business term: BT-25 — Preceding invoice number
Field in your JSON: invoice.preceding_invoice

How to fix it

Set invoice.preceding_invoice to the number of the invoice being corrected.

Cancellation, correction or credit note — which type code applies, and why a UBL Invoice rejects 381: see the guide on cancellations, corrections and credit notes.

BR-DE-26 auf Deutsch — was bedeutet der Fehler?

Eine Rechnungskorrektur (type_code 384) soll die korrigierte Rechnung referenzieren (BT-25). Der Validator meldet eine Warnung.

So beheben Sie den Fehler

Setzen Sie invoice.preceding_invoice auf die Nummer der korrigierten Rechnung.

Welcher Typcode für Storno, Korrektur oder Gutschrift gilt: Leitfaden zu Storno, Korrektur und Gutschrift.

Related rules

BR-55 — A preceding-invoice reference (BG-3) is present but the preceding invoice number (BT-25) is missing.
UBL-SR-07 — A cac:BillingReference is present but the preceding invoice number (BT-25, InvoiceDocumentReference/cbc:ID)…
BR-DE-27 — The seller contact phone number (BT-42) should contain at least three digits.
BR-DE-28 — The seller contact email (BT-43) does not look like an email address — exactly one @, at least two…
BR-DE-30 — Direct-debit information (BG-19) is present but the creditor identifier (BT-90) is missing.
BR-DE-22 — Two embedded attachments share the same filename — every attached document's filename must be unique within…

Official sources

Every 422 from the API lists the rule id, the path in your request JSON, a plain-language message and a suggested fix — see the docs overview for the report format.

Or try it live: drop any XRechnung XML on the free validator — same KoSIT-backed report, no account.