# BR-DE-26: Corrected invoice (384) without a preceding invoice

Source: https://veriport.io/einvoice-rules/br-de-26 (published 2026-11-17)

When the invoice type code (BT-3) is 384 (corrected invoice), the invoice should reference the invoice it corrects in BG-3 (`cac:BillingReference/cac:InvoiceDocumentReference` in UBL, `ram:InvoiceReferencedDocument` in CII). Below: the message, the cause and the fix, and an invoice our validator checked, failing and fixed.

- **Specification:** [XRechnung 3.0 rules](/einvoice-rules/xrechnung), XRechnung 3.0.2 schematron 2.6.0
- **Severity:** warning
- **Business terms:** BT-3, BG-3
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-DE-26 is a rule of the XRechnung 3.0 rules (xrechnung-schematron 2.6.0 (XRechnung 3.0.2)) for UBL and CII. It is a warning: the invoice stays valid, but should be corrected.

```text
[BR-DE-26] Wenn im Element "Invoice type code" (BT-3) der Code 384 (Corrected invoice) übergeben wird, soll PRECEDING INVOICE REFERENCE BG-3 mind. einmal vorhanden sein.
```

```text
[BR-DE-26] Wenn im Element Invoice type code (BT-3) der Code 384 (Corrected invoice) übergeben wird, soll PRECEDING INVOICE REFERENCE BG-3 mind. einmal vorhanden sein.
```

## What it checks

When the invoice type code (BT-3) is 384 (corrected invoice), the invoice should reference the invoice it corrects in BG-3 (`cac:BillingReference/cac:InvoiceDocumentReference` in UBL, `ram:InvoiceReferencedDocument` in CII). It is a warning.

## Why invoices fail it

A corrected invoice is generated from a copy of the original without the reference to it.

## How to fix it

Add the number (BT-25) and date (BT-26) of the invoice being corrected.

## A failing invoice and its fix, checked

We start from our sample invoice (two lines at 19 %, Berlin to Stuttgart), written by our own generator as XRechnung 3.0 in UBL. The change below (`-` the failing version, `+` the fixed one) makes the rule fail. Both versions went through our validator on 2026-11-17 (the XML schema and the official rule files, as `POST /einvoice/validate` runs them): the fixed one is valid, the failing one reports BR-DE-26.

| Rule | Severity | Where | Message |
|---|---|---|---|
| **BR-DE-26** | warning | `/ubl:Invoice` | Wenn im Element "Invoice type code" (BT-3) der Code 384 (Corrected invoice) übergeben wird, soll PRECEDING INVOICE REFERENCE BG-3 mind. einmal vorhanden sein. |

```diff
  …
    <cbc:DocumentCurrencyCode>EUR</cbc:DocumentCurrencyCode>
    <cbc:BuyerReference>EK-2026-0345</cbc:BuyerReference>
+   <cac:BillingReference>
+     <cac:InvoiceDocumentReference>
+       <cbc:ID>2026-011</cbc:ID>
+       <cbc:IssueDate>2026-09-30</cbc:IssueDate>
+     </cac:InvoiceDocumentReference>
+   </cac:BillingReference>
    <cac:AccountingSupplierParty>
      <cac:Party>
  …
```

## The rule as published

Where the rule applies (`context`) and what must hold (`test`), unmodified from XRechnung 3.0.2 schematron 2.6.0. An `assert` fails when its test is false.

Text and test: © KoSIT, Apache License 2.0. Quoted unmodified; the explanations on this page are Veriport’s.

```xpath
context: /ubl:Invoice | /cn:CreditNote
test:    ((not(normalize-space(cbc:InvoiceTypeCode) = '384' or normalize-space(cbc:CreditNoteTypeCode) = '384') or (cac:BillingReference/cac:InvoiceDocumentReference)))
```

```xpath
context: /rsm:CrossIndustryInvoice
test:    not(normalize-space(rsm:ExchangedDocument/ram:TypeCode) = '384') or (rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:InvoiceReferencedDocument)
```

## Check your own invoice

Drop your XRechnung, ZUGFeRD or Peppol file into a free validator ([Peppol BIS](/tools/peppol-validator), [XRechnung](/tools/xrechnung-pruefen), [Factur-X](/tools/valider-factur-x)): each runs the same rule files and links every finding to its rule page. From your own code, `POST /einvoice/validate` ([reference](/docs/einvoice)) returns the same check as JSON, each finding with an `explanation` field pointing here (5 calls a check, anonymous within the daily allowance).

## Read next

- [BR-DE-25-a: Direct debit group (BG-19) for code 59](https://veriport.io/einvoice-rules/br-de-25-a)
- [BR-DE-25-b: Transfer or card data with code 59](https://veriport.io/einvoice-rules/br-de-25-b)
- [BR-DE-27: Seller telephone (BT-42) with fewer than 3 digits](https://veriport.io/einvoice-rules/br-de-27)
- [BR-DE-28: Seller e-mail (BT-43) malformed](https://veriport.io/einvoice-rules/br-de-28)
- [BR-04: Invoice type code (BT-3) missing](https://veriport.io/einvoice-rules/br-04)
- [BR-55: Preceding invoice reference (BT-25) missing](https://veriport.io/einvoice-rules/br-55)
- [All XRechnung 3.0 rules](https://veriport.io/einvoice-rules/xrechnung)
- [All e-invoice rules, search](https://veriport.io/einvoice-rules)
- [Check an e-invoice free (XRechnung prüfen)](https://veriport.io/tools/xrechnung-pruefen)
- [Create a valid e-invoice free (German form)](https://veriport.io/tools/e-rechnung-erstellen)

## Sources

- XRechnung — the German CIUS of EN 16931 (standard, versions and bundles; version 3.0.2 in force) — https://xeinkauf.de/xrechnung/ (2026-10-28)
- Validator configuration XRechnung v2026-08-31 (XRechnung 3.0.2, CEN schematron 1.3.16, xrechnung-schematron 2.6.0) — https://github.com/itplr-kosit/validator-configuration-xrechnung/releases/tag/v2026-08-31 (2026-10-28)
- XRechnung schematron (xrechnung-schematron) and the XRechnung validator configuration: licence, Apache License 2.0 (LICENSE files; NOTICE of the configuration: « Copyright 2020 Koordinierungsstelle für IT-Standards ») — https://github.com/itplr-kosit/xrechnung-schematron/blob/master/LICENSE (2026-11-17)
