# BR-AG-01: No VAT breakdown for category M

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

When a line, an allowance or a charge uses category M (« IPSI »), the production, services and import tax of Ceuta and Melilla (Impuesto sobre la Producción, los Servicios y la Importación), category M, the VAT breakdown (BG-23) must contain at least one breakdown (one per rate) with category M; and a M breakdown needs something in that category to break down. 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-95, BT-102, BT-118, BT-151, BG-20, BG-21, BG-23, BG-25
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-AG-01 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-AG-01]-An Invoice that contains an Invoice line (BG-25), a Document level allowance (BG-20) or a Document level charge (BG-21) where the VAT category code (BT-151, BT-95 or BT-102) is "IPSI" shall contain in the VAT breakdown (BG-23) at least one VAT category code (BT-118) equal with "IPSI".
```

## What it checks

When a line, an allowance or a charge uses category M (« IPSI »), the production, services and import tax of Ceuta and Melilla (Impuesto sobre la Producción, los Servicios y la Importación), category M, the VAT breakdown (BG-23) must contain at least one breakdown (one per rate) with category M; and a M breakdown needs something in that category to break down.

## Why invoices fail it

The breakdown is built from a fixed list of rates rather than from the categories the lines actually use, or a line was changed to M after the totals were computed.

## How to fix it

Build the VAT breakdown from the lines, allowances and charges: one group per category and rate, with category M for these amounts.

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

| Rule | Severity | Where | Message |
|---|---|---|---|
| [BR-CO-18](/einvoice-rules/br-co-18) | error | `/ubl:Invoice` | An Invoice shall at least have one VAT breakdown group (BG-23). |
| **BR-AG-01** | error | `/ubl:Invoice` | An Invoice that contains an Invoice line (BG-25), a Document level allowance (BG-20) or a Document level charge (BG-21) where the VAT category code (BT-151, BT-95 or BT-102) is "IPSI" shall contain in the VAT breakdown (BG-23) at least one VAT category code (BT-118) equal with "IPSI". |

```diff
  …
    <cac:TaxTotal>
      <cbc:TaxAmount currencyID="EUR">96.34</cbc:TaxAmount>
+     <cac:TaxSubtotal>
+       <cbc:TaxableAmount currencyID="EUR">2408.40</cbc:TaxableAmount>
+       <cbc:TaxAmount currencyID="EUR">96.34</cbc:TaxAmount>
+       <cac:TaxCategory>
+         <cbc:ID>M</cbc:ID>
+         <cbc:Percent>4.00</cbc:Percent>
+         <cac:TaxScheme>
+           <cbc:ID>VAT</cbc:ID>
+         </cac:TaxScheme>
+       </cac:TaxCategory>
+     </cac:TaxSubtotal>
    </cac:TaxTotal>
    <cac:LegalMonetaryTotal>
  …
```

## 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:    ((count(//cac:AllowanceCharge/cac:TaxCategory[normalize-space(cbc:ID) = 'M'][cac:TaxScheme/normalize-space(upper-case(cbc:ID))='VAT']) + count(//cac:ClassifiedTaxCategory[normalize-space(cbc:ID) = 'M'][cac:TaxScheme/normalize-space(upper-case(cbc:ID))='VAT'])) > 0 and count(cac:TaxTotal/cac:TaxSubtotal/cac:TaxCategory[cbc:ID = 'M'][cac:TaxScheme/normalize-space(upper-case(cbc:ID))='VAT']) > 0) or ((count(//cac:AllowanceCharge/cac:TaxCategory[normalize-space(cbc:ID) = 'M'][cac:TaxScheme/normalize-space(upper-case(cbc:ID))='VAT']) + count(//cac:ClassifiedTaxCategory[normalize-space(cbc:ID) = 'M'][cac:TaxScheme/normalize-space(upper-case(cbc:ID))='VAT'])) = 0 and count(cac:TaxTotal/cac:TaxSubtotal/cac:TaxCategory[normalize-space(cbc:ID) = 'M'][cac:TaxScheme/normalize-space(upper-case(cbc:ID))='VAT']) = 0)
```

```xpath
context: /rsm:CrossIndustryInvoice
test:    ((count(//ram:SpecifiedLineTradeSettlement/ram:ApplicableTradeTax[ram:CategoryCode='M']) + count(//ram:ApplicableHeaderTradeSettlement/ram:ApplicableTradeTax[ram:CategoryCode='M'])) >=2 or not (//ram:SpecifiedLineTradeSettlement/ram:ApplicableTradeTax[ram:CategoryCode='M'])) and ((count(//ram:CategoryTradeTax[ram:CategoryCode='M']) + count(//ram:ApplicableHeaderTradeSettlement/ram:ApplicableTradeTax[ram:CategoryCode='M'])) >=2 or not (//ram:CategoryTradeTax[ram:CategoryCode='M']))
```

## 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-AG-02: Missing identifiers for category M (line)](https://veriport.io/einvoice-rules/br-ag-02)
- [BR-AG-03: Missing identifiers for category M (allowance)](https://veriport.io/einvoice-rules/br-ag-03)
- [BR-16: At least one invoice line (BG-25)](https://veriport.io/einvoice-rules/br-16)
- [BR-32: Document allowance VAT category (BT-95) missing](https://veriport.io/einvoice-rules/br-32)
- [BR-37: Document charge VAT category (BT-102) missing](https://veriport.io/einvoice-rules/br-37)
- [BR-47: VAT breakdown category code (BT-118) missing](https://veriport.io/einvoice-rules/br-47)
- [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)
