# BR-DE-16: Seller VAT ID, tax number or tax representative

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

When an XRechnung uses any of the VAT categories S, Z, E, AE, K, G, L or M, it must contain the seller’s VAT identifier (BT-31), the seller’s tax number (BT-32, the Steuernummer) or a seller tax representative (BG-11). § 14 (4) UStG requires one of them on every invoice. 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:** error
- **Business terms:** BT-31, BT-32, BG-11
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-DE-16 is a rule of the XRechnung 3.0 rules (xrechnung-schematron 2.6.0 (XRechnung 3.0.2)) for UBL and CII. It is an error (fatal): a validator rejects the invoice.

```text
[BR-DE-16] Wenn in einer Rechnung die Steuercodes S, Z, E, AE, K, G, L oder M verwendet werden, muss mindestens eines der Elemente "Seller VAT identifier" (BT-31), "Seller tax registration identifier" (BT-32) oder "SELLER TAX REPRESENTATIVE PARTY" (BG-11) übermittelt werden.
```

## What it checks

When an XRechnung uses any of the VAT categories S, Z, E, AE, K, G, L or M, it must contain the seller’s VAT identifier (BT-31), the seller’s tax number (BT-32, the Steuernummer) or a seller tax representative (BG-11). § 14 (4) UStG requires one of them on every invoice.

## Why invoices fail it

A small business without a VAT identifier writes its Steuernummer only in a note or the PDF footer.

## How to fix it

Write the USt-IdNr. in BT-31, or the Steuernummer in BT-32 (`cac:PartyTaxScheme` with a tax scheme other than VAT in UBL, `ram:SpecifiedTaxRegistration/ram:ID` with `schemeID="FC"` in CII).

## 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-16 and 2 other rules, as a real file with this mistake would.

| Rule | Severity | Where | Message |
|---|---|---|---|
| [BR-S-02](/einvoice-rules/br-s-02) | error | `/ubl:Invoice` | An Invoice that contains an Invoice line (BG-25) where the Invoiced item VAT category code (BT-151) is "Standard rated" shall contain the Seller VAT Identifier (BT-31), the Seller tax registration identifier (BT-32) and/or the Seller tax representative VAT identifier (BT-63). |
| [BR-CO-26](/einvoice-rules/br-co-26) | error | `/ubl:Invoice/cac:AccountingSupplierParty` | In order for the buyer to automatically identify a supplier, the Seller identifier (BT-29), the Seller legal registration identifier (BT-30) and/or the Seller VAT identifier (BT-31) shall be present. |
| **BR-DE-16** | error | `/ubl:Invoice` | Wenn in einer Rechnung die Steuercodes S, Z, E, AE, K, G, L oder M verwendet werden, muss mindestens eines der Elemente "Seller VAT identifier" (BT-31), "Seller tax registration identifier" (BT-32) oder "SELLER TAX REPRESENTATIVE PARTY" (BG-11) übermittelt werden. |

```diff
  …
          </cac:Country>
        </cac:PostalAddress>
+       <cac:PartyTaxScheme>
+         <cbc:CompanyID>DE136695976</cbc:CompanyID>
+         <cac:TaxScheme>
+           <cbc:ID>VAT</cbc:ID>
+         </cac:TaxScheme>
+       </cac:PartyTaxScheme>
        <cac:PartyLegalEntity>
          <cbc:RegistrationName>Lena Hartmann — Webdesign</cbc:RegistrationName>
  …
```

## 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( ($BT-95-UBL-Inv = $supportedVATCodes or $BT-95-UBL-CN = $supportedVATCodes) or ($BT-102 = $supportedVATCodes) or ($BT-151 = $supportedVATCodes) ) or (cac:TaxRepresentativeParty, $BT-31orBT-32Path))
```

```xpath
context: /rsm:CrossIndustryInvoice
test:    not((rsm:SupplyChainTradeTransaction/ram:IncludedSupplyChainTradeLineItem/ram:SpecifiedLineTradeSettlement/ram:ApplicableTradeTax/ram:TypeCode = 'VAT' and rsm:SupplyChainTradeTransaction/ram:IncludedSupplyChainTradeLineItem/ram:SpecifiedLineTradeSettlement/ram:ApplicableTradeTax/ram:CategoryCode = ('S', 'Z', 'E', 'AE', 'K', 'G', 'L', 'M')) or (rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradeAllowanceCharge/ram:CategoryTradeTax = 'VAT' and rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradeAllowanceCharge/ram:CategoryTradeTax/ram:CategoryCode = ('S', 'Z', 'E', 'AE', 'K', 'G', 'L', 'M')) or (rsm:SupplyChainTradeTransaction/ram:IncludedSupplyChainTradeLineItem/ram:SpecifiedLineTradeSettlement/ram:ApplicableTradeTax/ram:TypeCode = 'VAT' and rsm:SupplyChainTradeTransaction/ram:IncludedSupplyChainTradeLineItem/ram:SpecifiedLineTradeSettlement/ram:ApplicableTradeTax/ram:CategoryCode = ('S', 'Z', 'E', 'AE', 'K', 'G', 'L', 'M'))) or ((rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:SpecifiedTaxRegistration/ram:ID[normalize-space(@schemeID)='VA' or normalize-space(@schemeID)='FC'][boolean(normalize-space(.))], rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTaxRepresentativeTradeParty))
```

## 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-14: VAT category rate (BT-119) required](https://veriport.io/einvoice-rules/br-de-14)
- [BR-DE-15: Buyer reference (BT-10) required](https://veriport.io/einvoice-rules/br-de-15)
- [BR-DE-17: Invoice type code outside the XRechnung list](https://veriport.io/einvoice-rules/br-de-17)
- [BR-DE-18: Skonto in payment terms (BT-20) malformed](https://veriport.io/einvoice-rules/br-de-18)
- [BR-56: Tax representative VAT identifier (BT-63)](https://veriport.io/einvoice-rules/br-56)
- [BR-Z-02: Missing identifiers for category Z (line)](https://veriport.io/einvoice-rules/br-z-02)
- [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)
