# BR-CO-18: At least one VAT breakdown (BG-23)

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

An invoice must contain at least one VAT breakdown, BG-23 (`cac:TaxTotal/cac:TaxSubtotal` in UBL, `ram:ApplicableTradeTax` in the header settlement in CII), even when no VAT is due. 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-23
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-CO-18 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-CO-18]-An Invoice shall at least have one VAT breakdown group (BG-23).
```

## What it checks

An invoice must contain at least one VAT breakdown, BG-23 (`cac:TaxTotal/cac:TaxSubtotal` in UBL, `ram:ApplicableTradeTax` in the header settlement in CII), even when no VAT is due.

## Why invoices fail it

A small business (Kleinunternehmer) or an exempt supplier writes no tax information at all.

## How to fix it

Write one breakdown per category and rate; without VAT, a breakdown in category E (exempt, with the reason) or O (not subject) with 0.00 tax.

## 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 CII. 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-CO-18 and 1 other rule, as a real file with this mistake would.

| Rule | Severity | Where | Message |
|---|---|---|---|
| **BR-CO-18** | error | `/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:IncludedSupplyChainTradeLineItem[1]` | An Invoice shall at least have one VAT breakdown group (BG-23). |
| **BR-CO-18** | error | `/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:IncludedSupplyChainTradeLineItem[2]` | An Invoice shall at least have one VAT breakdown group (BG-23). |
| [BR-CO-14](/einvoice-rules/br-co-14) | error | `/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradeSettlementHeaderMonetarySummation/ram:TaxTotalAmount` | Invoice total VAT amount (BT-110) = Σ VAT category tax amount (BT-117). |

```diff
  …
          </ram:PayeePartyCreditorFinancialAccount>
        </ram:SpecifiedTradeSettlementPaymentMeans>
+       <ram:ApplicableTradeTax>
+         <ram:CalculatedAmount>457.60</ram:CalculatedAmount>
+         <ram:TypeCode>VAT</ram:TypeCode>
+         <ram:BasisAmount>2408.40</ram:BasisAmount>
+         <ram:CategoryCode>S</ram:CategoryCode>
+         <ram:RateApplicablePercent>19.00</ram:RateApplicablePercent>
+       </ram:ApplicableTradeTax>
        <ram:SpecifiedTradePaymentTerms>
          <ram:DueDateDateTime>
  …
```

## 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:TaxTotal/cac:TaxSubtotal)
```

```xpath
context: //ram:IncludedSupplyChainTradeLineItem
test:    //rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:ApplicableTradeTax
```

## 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-CO-16: Amount due (BT-115) does not add up](https://veriport.io/einvoice-rules/br-co-16)
- [BR-CO-17: VAT amount (BT-117) ≠ taxable amount × rate](https://veriport.io/einvoice-rules/br-co-17)
- [BR-CO-19: Empty invoicing period (BG-14)](https://veriport.io/einvoice-rules/br-co-19)
- [BR-CO-20: Empty line period (BG-26)](https://veriport.io/einvoice-rules/br-co-20)
- [BR-45: VAT breakdown taxable amount (BT-116) missing](https://veriport.io/einvoice-rules/br-45)
- [BR-46: VAT breakdown tax amount (BT-117) missing](https://veriport.io/einvoice-rules/br-46)
- [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)
