BR-CO-26: no seller identifier (BT-29, BT-30 or BT-31)

BR-CO-26 in an e-invoice report: the file must carry at least one of the seller identifier (BT-29), legal registration identifier (BT-30) or VAT identifier (BT-31). What counts and what does not.

The file carries at least one of these for the seller: a seller identifier, BT-29, which has no fixed scheme, the seller's legal registration identifier, BT-30, or the seller's VAT identifier, BT-31. In CII the rule reads, in the ram:SellerTradeParty, ram:ID, ram:GlobalID, ram:SpecifiedLegalOrganization/ram:ID and the ram:SpecifiedTaxRegistration/ram:ID with schemeID="VA".

The rule text

A report names BR-CO-26 with this text from CEN's EN 16931 rules:

[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.

Source: EN 16931 UBL and CII validation artefacts, v1.3.16 (2026-03-30), © CEN, licensed under EUPL 1.2. Licence and notices

Source: ZUGFeRD / Factur-X schema and rules, ZF_250 code lists 1.09.2 (2026-08-04), © FeRD / FNFE-MPE, Apache-2.0. Licence and notices

CEN's rules list it as an error (fatal).

FeRD's ZUGFeRD rules give it no severity; for ZUGFeRD files the check reports it as an error.

Where in the file the rule looks

SyntaxElements
CIIram:SellerTradeParty/ram:ID, ram:SellerTradeParty/ram:GlobalID, ram:SpecifiedLegalOrganization/ram:ID, ram:SpecifiedTaxRegistration/ram:ID
UBLcac:PartyIdentification/cbc:ID, cac:PartyLegalEntity/cbc:CompanyID, cac:PartyTaxScheme/cbc:CompanyID

When the rule fails

  • The rule fails when none of them is in the file for the seller.
  • For example, the file holds only a Steuernummer (BT-32), which does not count for this rule.
  • The rule also fails when, in UBL, the seller's only identifier is a cac:PartyIdentification/cbc:ID with schemeID="SEPA"; such an identifier does not count.

How to fix it

  1. Add an identifier the seller really has: BT-29, BT-30 from an official register, or BT-31 if the seller has a VAT identifier.

Add or correct the data in the program that produces the file, and produce it again before you send the invoice. If the invoice has already been sent, ask your tax adviser whether and how to amend it; § 31 para. 5 UStDV governs amending an invoice. If you received the file, pass the code on to the invoice's issuer: the file is produced in their program.

Check the file again

Upload the corrected file to InkVoice's free e-invoice check (the page is in German). It shows the codes the rules report, with the rules' text.

Read on

Last updated 15 November 2026. This article is general orientation and is not tax or legal advice.