# BR-10: Buyer postal address (BG-8) missing

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

The buyer must have a postal address group, BG-8: `cac:PostalAddress` under the customer party in UBL, `ram:PostalTradeAddress` under `ram:BuyerTradeParty` 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:** BG-8
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-10 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-10]-An Invoice shall contain the Buyer postal address (BG-8).
```

## What it checks

The buyer must have a postal address group, BG-8: `cac:PostalAddress` under the customer party in UBL, `ram:PostalTradeAddress` under `ram:BuyerTradeParty` in CII.

## Why invoices fail it

The buyer is identified only by its electronic address or a customer number, and the generator writes no address.

## How to fix it

Write the buyer’s postal address as BG-8 with at least the country code (BT-55).

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

| Rule | Severity | Where | Message |
|---|---|---|---|
| **BR-10** | error | `/ubl:Invoice` | An Invoice shall contain the Buyer postal address (BG-8). |

```diff
  …
      <cac:Party>
        <cbc:EndpointID schemeID="EM">buchhaltung@mustermann.example</cbc:EndpointID>
+       <cac:PostalAddress>
+         <cbc:StreetName>Industrieweg 7</cbc:StreetName>
+         <cbc:CityName>Stuttgart</cbc:CityName>
+         <cbc:PostalZone>70565</cbc:PostalZone>
+         <cac:Country>
+           <cbc:IdentificationCode>DE</cbc:IdentificationCode>
+         </cac:Country>
+       </cac:PostalAddress>
        <cac:PartyLegalEntity>
          <cbc:RegistrationName>Mustermann Maschinenbau GmbH</cbc:RegistrationName>
  …
```

## 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: /ubl:Invoice | /cn:CreditNote
test:    exists(cac:AccountingCustomerParty/cac:Party/cac:PostalAddress)
```

```xpath
context: /rsm:CrossIndustryInvoice
test:    rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:BuyerTradeParty/ram:PostalTradeAddress
```

## 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-08: Seller postal address (BG-5) missing](https://veriport.io/einvoice-rules/br-08)
- [BR-09: Seller country code (BT-40) missing](https://veriport.io/einvoice-rules/br-09)
- [BR-11: Buyer country code (BT-55) missing](https://veriport.io/einvoice-rules/br-11)
- [BR-12: Sum of line net amounts (BT-106) missing](https://veriport.io/einvoice-rules/br-12)
- [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)
