What does BR-CO-26 mean?
The seller needs at least an identifier, a legal registration identifier or a VAT identifier. That lets the buyer identify him automatically.
Common causes of BR-CO-26
- The seller has only a name, but no identifier, no legal registration identifier and no VAT identifier.
- The VAT identifier was written without schemeID='VA' and therefore was not recognised as BT-31.
- The legal registration identifier (BT-30) is missing because 'ram:SpecifiedLegalOrganization' was not filled in.
How to fix BR-CO-26
- Find the faulty spot in the XML. Open the XML of the invoice and go to field BT-29 along this XPath:
//ram:SellerTradeParty - Apply the fix. For the buyer to identify the supplier automatically, the seller needs at least one identifier. In 'ram:SellerTradeParty', add one of: Seller identifier 'ram:ID' (BT-29), legal registration identifier 'ram:SpecifiedLegalOrganization/ram:ID' (BT-30) or Seller VAT identifier 'ram:SpecifiedTaxRegistration/ram:ID' with schemeID='VA' (BT-31).
- Validate again. Save the file and validate it again to check that BR-CO-26 is no longer reported.
For the buyer to identify the supplier automatically, the seller needs at least one identifier. In 'ram:SellerTradeParty', add one of: Seller identifier 'ram:ID' (BT-29), legal registration identifier 'ram:SpecifiedLegalOrganization/ram:ID' (BT-30) or Seller VAT identifier 'ram:SpecifiedTaxRegistration/ram:ID' with schemeID='VA' (BT-31).
//ram:SellerTradePartyBefore / after: the XML example
This is the spot in question before and after the fix (Cross Industry Invoice, ZUGFeRD/Factur-X).
<ram:SellerTradeParty>
<ram:Name>Musterfirma GmbH</ram:Name>
</ram:SellerTradeParty>
<ram:SellerTradeParty>
<ram:Name>Musterfirma GmbH</ram:Name>
<ram:SpecifiedTaxRegistration>
<ram:ID schemeID="VA">DE123456789</ram:ID>
</ram:SpecifiedTaxRegistration>
</ram:SellerTradeParty>
Frequent questions about BR-CO-26
Do I have to give all three identifiers?
Why is my VAT identifier not accepted as an identifier?
Related error codes
Check BR-CO-26 automatically
Instead of digging through the XML by hand you can validate your ZUGFeRD or XRechnung file online – upload the PDF or the XML and you get every error with rule ID, affected field, fix and XPath, as a readable report or as JSON through the API.