# BR-AE-10: No exemption reason for category AE

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

A VAT breakdown with category AE (« Reverse charge ») must state why no VAT is charged: an exemption reason code (BT-121) or an exemption reason text (BT-120): VATEX-EU-AE, or the text « Reverse charge ». 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-118, BT-120, BT-121, BG-23
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-AE-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-AE-10]-A VAT breakdown (BG-23) with VAT Category code (BT-118) "Reverse charge" shall have a VAT exemption reason code (BT-121), meaning "Reverse charge" or the VAT exemption reason text (BT-120) "Reverse charge" (or the equivalent standard text in another language).
```

```text
[BR-AE-10]-A VAT Breakdown (BG-23) with VAT Category code (BT-118) "Reverse charge" shall have a VAT exemption reason code (BT-121), meaning "Reverse charge" or the VAT exemption reason text (BT-120) "Reverse charge" (or the equivalent standard text in another language).
```

## What it checks

A VAT breakdown with category AE (« Reverse charge ») must state why no VAT is charged: an exemption reason code (BT-121) or an exemption reason text (BT-120): VATEX-EU-AE, or the text « Reverse charge ».

## Why invoices fail it

The legal mention is printed on the PDF but not written in the XML breakdown.

## How to fix it

Add the VATEX code or the reason text to the AE breakdown (`cbc:TaxExemptionReasonCode` / `cbc:TaxExemptionReason` in UBL, `ram:ExemptionReasonCode` / `ram:ExemptionReason` in CII).

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

| Rule | Severity | Where | Message |
|---|---|---|---|
| **BR-AE-10** | error | `/ubl:Invoice/cac:TaxTotal/cac:TaxSubtotal/cac:TaxCategory` | A VAT breakdown (BG-23) with VAT Category code (BT-118) "Reverse charge" shall have a VAT exemption reason code (BT-121), meaning "Reverse charge" or the VAT exemption reason text (BT-120) "Reverse charge" (or the equivalent standard text in another language). |

```diff
  …
          <cbc:ID>AE</cbc:ID>
          <cbc:Percent>0.00</cbc:Percent>
+         <cbc:TaxExemptionReasonCode>VATEX-EU-AE</cbc:TaxExemptionReasonCode>
          <cac:TaxScheme>
            <cbc:ID>VAT</cbc:ID>
  …
```

## 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:TaxTotal/cac:TaxSubtotal/cac:TaxCategory[normalize-space(cbc:ID) = 'AE'][cac:TaxScheme/normalize-space(upper-case(cbc:ID))='VAT']
test:    exists(cbc:TaxExemptionReason) or (exists(cbc:TaxExemptionReasonCode) )
```

```xpath
context: //rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:ApplicableTradeTax/ram:CategoryCode[. = 'AE'][upper-case(../ram:TypeCode) = 'VAT']
test:    (../ram:ExemptionReason) or (../ram:ExemptionReasonCode)
```

## 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-AE-08: Taxable amount of category AE wrong](https://veriport.io/einvoice-rules/br-ae-08)
- [BR-AE-09: AE VAT amount not zero](https://veriport.io/einvoice-rules/br-ae-09)
- [BR-47: VAT breakdown category code (BT-118) missing](https://veriport.io/einvoice-rules/br-47)
- [BR-AF-10: Exemption reason given for category L](https://veriport.io/einvoice-rules/br-af-10)
- [BR-AG-10: Exemption reason given for category M](https://veriport.io/einvoice-rules/br-ag-10)
- [BR-CO-18: At least one VAT breakdown (BG-23)](https://veriport.io/einvoice-rules/br-co-18)
- [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)
