# BR-53: VAT total in accounting currency (BT-111)

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

When the invoice names a VAT accounting currency (BT-6, `cbc:TaxCurrencyCode` / `ram:TaxCurrencyCode`) different from the invoice currency, it must also give the total VAT in that currency, BT-111: a second `cac:TaxTotal/cbc:TaxAmount` in that currency in UBL, a second `ram:TaxTotalAmount` with that `currencyID` in CII. 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-6, BT-111
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-53 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-53]-If the VAT accounting currency code (BT-6) is present, then the Invoice total VAT amount in accounting currency (BT-111) shall be provided.
```

## What it checks

When the invoice names a VAT accounting currency (BT-6, `cbc:TaxCurrencyCode` / `ram:TaxCurrencyCode`) different from the invoice currency, it must also give the total VAT in that currency, BT-111: a second `cac:TaxTotal/cbc:TaxAmount` in that currency in UBL, a second `ram:TaxTotalAmount` with that `currencyID` in CII.

## Why invoices fail it

An invoice in USD or GBP to an EU buyer declares EUR as tax currency but carries VAT amounts only in the invoice currency.

## How to fix it

Add the total VAT converted into the accounting currency, or drop BT-6 when the VAT is accounted in the invoice currency.

## 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-53.

| Rule | Severity | Where | Message |
|---|---|---|---|
| **BR-53** | error | `/ubl:Invoice` | If the VAT accounting currency code (BT-6) is present, then the Invoice total VAT amount in accounting currency (BT-111) shall be provided. |

```diff
  …
      </cac:TaxSubtotal>
    </cac:TaxTotal>
+   <cac:TaxTotal>
+     <cbc:TaxAmount currencyID="DKK">3413.70</cbc:TaxAmount>
+   </cac:TaxTotal>
    <cac:LegalMonetaryTotal>
      <cbc:LineExtensionAmount currencyID="EUR">2408.40</cbc:LineExtensionAmount>
  …
```

## 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:    every $taxcurrency in cbc:TaxCurrencyCode satisfies exists(//cac:TaxTotal/cbc:TaxAmount[@currencyID=$taxcurrency])
```

```xpath
context: //ram:SpecifiedTradeSettlementHeaderMonetarySummation
test:    not(/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:TaxCurrencyCode) or (/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:TaxCurrencyCode and (ram:TaxTotalAmount/@currencyID = /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:TaxCurrencyCode) and not(/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:TaxCurrencyCode = /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:InvoiceCurrencyCode))
```

## 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-51: Full card number (BT-87) on the invoice](https://veriport.io/einvoice-rules/br-51)
- [BR-52: Supporting document reference (BT-122) missing](https://veriport.io/einvoice-rules/br-52)
- [BR-54: Item attribute name and value (BT-160/BT-161)](https://veriport.io/einvoice-rules/br-54)
- [BR-55: Preceding invoice reference (BT-25) missing](https://veriport.io/einvoice-rules/br-55)
- [BR-DEC-15: More than 2 decimals in BT-111 (Invoice total VAT amount in accounting currency)](https://veriport.io/einvoice-rules/br-dec-15)
- [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)
