# BR-DE-1: Payment instructions (BG-16) required

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

An XRechnung must contain payment instructions, BG-16: at least one `cac:PaymentMeans` in UBL, `ram:SpecifiedTradeSettlementPaymentMeans` in CII, with a payment means code (BT-81). Below: the message, the cause and the fix, and an invoice our validator checked, failing and fixed.

- **Specification:** [XRechnung 3.0 rules](/einvoice-rules/xrechnung), XRechnung 3.0.2 schematron 2.6.0
- **Severity:** error
- **Business terms:** BG-16
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-DE-1 is a rule of the XRechnung 3.0 rules (xrechnung-schematron 2.6.0 (XRechnung 3.0.2)) for UBL and CII. It is an error (fatal): a validator rejects the invoice.

```text
[BR-DE-1] Eine Rechnung (INVOICE) muss Angaben zu "PAYMENT INSTRUCTIONS" (BG-16) enthalten.
```

## What it checks

An XRechnung must contain payment instructions, BG-16: at least one `cac:PaymentMeans` in UBL, `ram:SpecifiedTradeSettlementPaymentMeans` in CII, with a payment means code (BT-81). EN 16931 leaves the group optional; XRechnung makes it mandatory.

## Why invoices fail it

The invoice is already paid (card, cash, direct debit agreed elsewhere) and the generator writes no payment group, or the bank details are printed only on the PDF.

## How to fix it

Write a payment means group with its code: 58 with the seller’s IBAN for a SEPA transfer, 59 for a direct debit, 48 or 54 for a card, 10 for cash, 1 when no means is specified.

## 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 XRechnung 3.0 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-DE-1.

| Rule | Severity | Where | Message |
|---|---|---|---|
| **BR-DE-1** | error | `/ubl:Invoice` | Eine Rechnung (INVOICE) muss Angaben zu "PAYMENT INSTRUCTIONS" (BG-16) enthalten. |

```diff
  …
      <cbc:ActualDeliveryDate>2026-10-15</cbc:ActualDeliveryDate>
    </cac:Delivery>
+   <cac:PaymentMeans>
+     <cbc:PaymentMeansCode>58</cbc:PaymentMeansCode>
+     <cac:PayeeFinancialAccount>
+       <cbc:ID>DE02120300000000202051</cbc:ID>
+     </cac:PayeeFinancialAccount>
+   </cac:PaymentMeans>
    <cac:TaxTotal>
      <cbc:TaxAmount currencyID="EUR">457.60</cbc:TaxAmount>
  …
```

## The rule as published

Where the rule applies (`context`) and what must hold (`test`), unmodified from XRechnung 3.0.2 schematron 2.6.0. An `assert` fails when its test is false.

Text and test: © KoSIT, Apache License 2.0. Quoted unmodified; the explanations on this page are Veriport’s.

```xpath
context: /ubl:Invoice | /cn:CreditNote
test:    cac:PaymentMeans
```

```xpath
context: /rsm:CrossIndustryInvoice
test:    rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradeSettlementPaymentMeans
```

## 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-DE-2: Seller contact (BG-6) required](https://veriport.io/einvoice-rules/br-de-2)
- [BR-DE-3: Seller city (BT-37) required](https://veriport.io/einvoice-rules/br-de-3)
- [BR-49: Payment means type code (BT-81) missing](https://veriport.io/einvoice-rules/br-49)
- [BR-50: Payment account (BT-84) for a credit transfer](https://veriport.io/einvoice-rules/br-50)
- [All XRechnung 3.0 rules](https://veriport.io/einvoice-rules/xrechnung)
- [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

- XRechnung — the German CIUS of EN 16931 (standard, versions and bundles; version 3.0.2 in force) — https://xeinkauf.de/xrechnung/ (2026-10-28)
- Validator configuration XRechnung v2026-08-31 (XRechnung 3.0.2, CEN schematron 1.3.16, xrechnung-schematron 2.6.0) — https://github.com/itplr-kosit/validator-configuration-xrechnung/releases/tag/v2026-08-31 (2026-10-28)
- XRechnung schematron (xrechnung-schematron) and the XRechnung validator configuration: licence, Apache License 2.0 (LICENSE files; NOTICE of the configuration: « Copyright 2020 Koordinierungsstelle für IT-Standards ») — https://github.com/itplr-kosit/xrechnung-schematron/blob/master/LICENSE (2026-11-17)
