Skip to main content

BR-DE-26 Corrected invoice should reference at least one preceding invoice

BR-DE-26 of the German XRechnung rules applies when the invoice type code (BT-3) is 384 (corrected invoice). The invoice should then contain at least one preceding invoice reference (BG-3) with the number of the invoice it corrects in BT-25; the issue date (BT-26) is optional.

Problem Description

WARNING

German XRechnung rule (KoSIT, BR-DE) · XRechnung 3.0

Interactive pipeline

Click a stage to see what it checks, or type a rule ID to light up the stage that reports it.

Try:

BR-DE-26 XRechnung rule (Germany)

Reported in stage 3: National rules (CIUS).

Level warning: on its own, the invoice is still accepted.

Stage 3 · What it checks

  • The specification identifier in BT-24 selects the rule set, for example XRechnung 3.0 or Peppol BIS Billing 3.0.
  • XRechnung adds the German BR-DE rules: buyer reference (BT-10), seller contact, payment instructions.
  • Peppol adds PEPPOL-EN16931 and country rules. XRechnung applies some PEPPOL-EN16931 rules too.

Example codes

Typical fix

Fill the fields the rule set requires in your master data, such as the Leitweg-ID in BT-10 or the seller contact.

A validator checks an e-invoice in stages. First the file must be well-formed XML that matches the UBL or CII schema (XSD). Then the EN 16931 business rules run: BR core rules, BR-CO calculations, BR-CL code lists, BR-DEC decimals and VAT-category rules such as BR-S. Next come the national or network rules that BT-24 selects: BR-DE for XRechnung, PEPPOL-EN16931 for Peppol BIS Billing. The report lists every failed rule: one error means reject, warnings alone still mean accept. BR-DE-26: XRechnung rule (Germany), reported in the stage “National rules (CIUS)”. Rule sets: KoSIT validator 1.6.3 with the XRechnung configuration of 31 Aug 2026 (EN 16931 artefacts 1.3.16), Peppol BIS Billing 3.0.21.

Solution

In your ERP billing module, when generating a corrected invoice (type 384), populate the preceding invoice reference with the original invoice number (BT-25) and optionally the issue date (BT-26). In UBL 2.1 syntax, populate <cac:BillingReference><cac:InvoiceDocumentReference><cbc:ID>INV-2025-001</cbc:ID><cbc:IssueDate>2025-12-15</cbc:IssueDate></cac:InvoiceDocumentReference></cac:BillingReference>. In UN/CEFACT CII syntax, populate <ram:InvoiceReferencedDocument><ram:IssuerAssignedID>INV-2025-001</ram:IssuerAssignedID><ram:FormattedIssueDateTime>...</ram:FormattedIssueDateTime></ram:InvoiceReferencedDocument> under <ram:ApplicableHeaderTradeSettlement>. If the document is a standard commercial invoice, set InvoiceTypeCode to 380 (Commercial invoice) instead.

Quick actions

Context and Significance

BR-DE-26 is a warning in the KoSIT configuration for XRechnung 3.0.2, so the validator does not reject the file for it alone. Without the reference, however, the buyer cannot match the correction to the original invoice.

Valid Examples

  • Corrected invoice (type 384) referencing preceding invoice "INV-2025-001" (BT-25)
  • Corrected invoice referencing preceding invoice with issue date 2025-11-30 (BT-26)

Invalid Examples

  • Invoice with cbc:InvoiceTypeCode = 384 completely omits cac:BillingReference
  • Corrected invoice declares cac:BillingReference without cbc:ID in InvoiceDocumentReference

Code Examples

Valid XML
<cbc:InvoiceTypeCode>384</cbc:InvoiceTypeCode>
<cac:BillingReference>
  <cac:InvoiceDocumentReference>
    <cbc:ID>INV-2025-001</cbc:ID>
    <cbc:IssueDate>2025-12-15</cbc:IssueDate>
  </cac:InvoiceDocumentReference>
</cac:BillingReference>
Invalid XML
<cbc:InvoiceTypeCode>384</cbc:InvoiceTypeCode>

Affected Fields

Validation Tools