# BR-CO-26: No seller identifier, registration or VAT ID

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

So that the buyer can identify the supplier automatically, the seller must have at least one of: an identifier (BT-29, `cac:PartyIdentification/cbc:ID` or `ram:ID` / `ram:GlobalID`), a legal registration identifier (BT-30, `cac:PartyLegalEntity/cbc:CompanyID` or `ram:SpecifiedLegalOrganization/ram:ID`), or a VAT identifier (BT-31). Below: the message, the cause and the fix, and an invoice our validator checked, failing and fixed.

- **Specification:** [EN 16931 business rules](/einvoice-rules/en16931), CEN EN 16931 validation artefacts 1.3.16
- **Severity:** error
- **Business terms:** BT-29, BT-30, BT-31
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-CO-26 is a rule of the EN 16931 business rules (CEN validation artefacts 1.3.16) for UBL and CII. It is an error (fatal): a validator rejects the invoice.

```text
[BR-CO-26]-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.
```

## What it checks

So that the buyer can identify the supplier automatically, the seller must have at least one of: an identifier (BT-29, `cac:PartyIdentification/cbc:ID` or `ram:ID` / `ram:GlobalID`), a legal registration identifier (BT-30, `cac:PartyLegalEntity/cbc:CompanyID` or `ram:SpecifiedLegalOrganization/ram:ID`), or a VAT identifier (BT-31).

## Why invoices fail it

A seller without a VAT number (a small business with only a tax number) writes the tax number in BT-32, which does not count.

## How to fix it

Write the VAT identifier when there is one; otherwise a register number in BT-30, or repeat the tax number as seller identifier (BT-29), as German small businesses commonly do.

## 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 EN 16931 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-CO-26.

| Rule | Severity | Where | Message |
|---|---|---|---|
| **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. |

```diff
  …
        </cac:PostalAddress>
        <cac:PartyTaxScheme>
-         <cbc:CompanyID>21/815/08150</cbc:CompanyID>
+         <cbc:CompanyID>DE136695976</cbc:CompanyID>
          <cac:TaxScheme>
-           <cbc:ID>FC</cbc:ID>
+           <cbc:ID>VAT</cbc:ID>
          </cac:TaxScheme>
        </cac:PartyTaxScheme>
  …
```

## The rule as published

Where the rule applies (`context`) and what must hold (`test`), unmodified from CEN EN 16931 validation artefacts 1.3.16. An `assert` fails when its test is false.

Text and test: © CEN/TC 434, EN 16931 validation artefacts, EUPL 1.2. Quoted unmodified; the explanations on this page are Veriport’s.

```xpath
context: cac:AccountingSupplierParty
test:    exists(cac:Party/cac:PartyTaxScheme[cac:TaxScheme/normalize-space(upper-case(cbc:ID))='VAT']/cbc:CompanyID) or exists(cac:Party/cac:PartyIdentification/cbc:ID[not(@schemeID = 'SEPA')]) or exists(cac:Party/cac:PartyLegalEntity/cbc:CompanyID)
```

```xpath
context: //ram:SellerTradeParty
test:    (ram:ID) or (ram:GlobalID) or (ram:SpecifiedLegalOrganization/ram:ID) or (ram:SpecifiedTaxRegistration/ram:ID[@schemeID='VA'])
```

## 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-CO-23: Line allowance without a reason](https://veriport.io/einvoice-rules/br-co-23)
- [BR-CO-24: Line charge without a reason](https://veriport.io/einvoice-rules/br-co-24)
- [BR-DE-16: Seller VAT ID, tax number or tax representative](https://veriport.io/einvoice-rules/br-de-16)
- [BR-G-02: Missing identifiers for category G (line)](https://veriport.io/einvoice-rules/br-g-02)
- [BR-G-03: Missing identifiers for category G (allowance)](https://veriport.io/einvoice-rules/br-g-03)
- [BR-G-04: Missing identifiers for category G (charge)](https://veriport.io/einvoice-rules/br-g-04)
- [All EN 16931 business rules](https://veriport.io/einvoice-rules/en16931)
- [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

- EN 16931 validation artefacts 1.3.16 (UBL and CII schematron, the business rules BR-*) — https://github.com/ConnectingEurope/eInvoicing-EN16931/releases/tag/validation-1.3.16 (2026-10-28)
- EN 16931 validation artefacts: licence, European Union Public Licence (EUPL) v1.2 (LICENSE.txt, the README « License » section and the release notes of validation-1.3.16) — https://github.com/ConnectingEurope/eInvoicing-EN16931/blob/master/LICENSE.txt (2026-11-17)
