# BR-09: Seller country code (BT-40) missing

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

The seller’s address must contain a country code, BT-40, from ISO 3166-1 alpha-2: `cac:PostalAddress/cac:Country/cbc:IdentificationCode` in UBL, `ram:PostalTradeAddress/ram:CountryID` in CII. 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-40, BG-5
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-09 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-09]-The Seller postal address (BG-5) shall contain a Seller country code (BT-40).
```

## What it checks

The seller’s address must contain a country code, BT-40, from ISO 3166-1 alpha-2: `cac:PostalAddress/cac:Country/cbc:IdentificationCode` in UBL, `ram:PostalTradeAddress/ram:CountryID` in CII.

## Why invoices fail it

The country is written as a name (« Deutschland ») in an address line, or omitted for domestic invoices.

## How to fix it

Add the two-letter ISO code (DE, FR, BE…) in BT-40, even for a domestic invoice.

## 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-09.

| Rule | Severity | Where | Message |
|---|---|---|---|
| **BR-09** | error | `/ubl:Invoice/cac:AccountingSupplierParty/cac:Party/cac:PostalAddress` | The Seller postal address (BG-5) shall contain a Seller country code (BT-40). |

```diff
  …
          <cbc:CityName>Berlin</cbc:CityName>
          <cbc:PostalZone>10969</cbc:PostalZone>
+         <cac:Country>
+           <cbc:IdentificationCode>DE</cbc:IdentificationCode>
+         </cac:Country>
        </cac:PostalAddress>
        <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/cac:Party/cac:PostalAddress
test:    normalize-space(cac:Country/cbc:IdentificationCode) != ''
```

```xpath
context: /rsm:CrossIndustryInvoice
test:    normalize-space(rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:PostalTradeAddress/ram:CountryID) != ''
```

## 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-07: Buyer name (BT-44) missing](https://veriport.io/einvoice-rules/br-07)
- [BR-08: Seller postal address (BG-5) missing](https://veriport.io/einvoice-rules/br-08)
- [BR-10: Buyer postal address (BG-8) missing](https://veriport.io/einvoice-rules/br-10)
- [BR-11: Buyer country code (BT-55) missing](https://veriport.io/einvoice-rules/br-11)
- [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)
