# BR-17: Payee name (BT-59) when a payee is given

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

When the invoice names a payee different from the seller (BG-10: `cac:PayeeParty` in UBL, `ram:PayeeTradeParty` in CII), the payee’s name, BT-59, must be present (`cac:PartyName/cbc:Name`, `ram:Name`). 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-59, BG-4, BG-10
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-17 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-17]-The Payee name (BT-59) shall be provided in the Invoice, if the Payee (BG-10) is different from the Seller (BG-4)
```

```text
[BR-17]-The Payee name (BT-59) shall be provided in the Invoice, if the Payee (BG-10) is different from the Seller (BG-4).
```

## What it checks

When the invoice names a payee different from the seller (BG-10: `cac:PayeeParty` in UBL, `ram:PayeeTradeParty` in CII), the payee’s name, BT-59, must be present (`cac:PartyName/cbc:Name`, `ram:Name`).

## Why invoices fail it

A factoring or collection account is added as payee with only an identifier or a bank account.

## How to fix it

Give the payee’s name in BT-59, or remove the payee group when the seller is paid directly.

## 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-17 and 3 other rules, as a real file with this mistake would.

| Rule | Severity | Where | Message |
|---|---|---|---|
| **BR-17** | error | `/ubl:Invoice/cac:PayeeParty` | The Payee name (BT-59) shall be provided in the Invoice, if the Payee (BG-10) is different from the Seller (BG-4) |
| [UBL-SR-19](/einvoice-rules/ubl-sr-19) | error | `/ubl:Invoice/cac:PayeeParty` | Payee name shall occur maximum once, if the Payee is different from the Seller |
| [UBL-SR-20](/einvoice-rules/ubl-sr-20) | error | `/ubl:Invoice/cac:PayeeParty` | Payee identifier shall occur maximum once, if the Payee is different from the Seller |
| [UBL-SR-21](/einvoice-rules/ubl-sr-21) | error | `/ubl:Invoice/cac:PayeeParty` | Payee legal registration identifier shall occur maximum once, if the Payee is different from the Seller |

```diff
  …
        <cbc:ID>FACT-77</cbc:ID>
      </cac:PartyIdentification>
+     <cac:PartyName>
+       <cbc:Name>Nordfactoring GmbH</cbc:Name>
+     </cac:PartyName>
    </cac:PayeeParty>
    <cac:Delivery>
  …
```

## 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:PayeeParty
test:    exists(cac:PartyName/cbc:Name) and (not(cac:PartyName/cbc:Name = ../cac:AccountingSupplierParty/cac:Party/cac:PartyName/cbc:Name) and not(cac:PartyIdentification/cbc:ID = ../cac:AccountingSupplierParty/cac:Party/cac:PartyIdentification/cbc:ID) )
```

```xpath
context: //ram:PayeeTradeParty
test:    (ram:Name) and (not(ram:Name = ../../ram:ApplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:Name) and not(ram:ID = ../../ram:ApplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:ID) and not(ram:SpecifiedLegalOrganization/ram:ID = ../../ram:ApplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:SpecifiedLegalOrganization/ram:ID))
```

## 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-15: Amount due for payment (BT-115) missing](https://veriport.io/einvoice-rules/br-15)
- [BR-16: At least one invoice line (BG-25)](https://veriport.io/einvoice-rules/br-16)
- [BR-18: Tax representative name (BT-62)](https://veriport.io/einvoice-rules/br-18)
- [BR-19: Tax representative address (BG-12)](https://veriport.io/einvoice-rules/br-19)
- [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)
