# BR-DEC-20

Quoted from a public specification. This page is not a validator, and it is not tax, legal, or accounting advice.

- Country: EU
- Syntax: UBL
- Severity: fatal
- Statement language: en
- Last verified: 2026-10-18

## Official statement

> The allowed maximum number of decimals for the VAT category tax amount (BT-117) is 2.

Source: https://docs.peppol.eu/poacc/billing/3.0/rules/ubl-tc434/BR-DEC-20/

Peppol BIS Billing 3.0, May 2026 release, EN 16931 model bound to UBL

Severity note: fatal, from the Flag column of the Peppol BIS Billing 3.0 UBL rules index retrieved 2026-10-18.

## Plain-language reading

The VAT category tax amount (BT-117) may have at most 2 decimals. The statement says "allowed maximum number of decimals" and "is 2", and it ends with a period. It does not say shall. The context is cac:TaxTotal/cac:TaxSubtotal. This is a decimal limit, not the BR-46 presence check and not the BR-CO-17 calculation. The published test reads cbc:TaxAmount and writes <=2 with no space before <=. It does not call exists.

## What to change

Send the VAT category tax amount (BT-117) with at most 2 digits after the decimal point.

## Illustration

Illustration of the condition in the official statement. Not an example published by the source.

**Fails the stated condition.** A VAT category tax amount has 3 digits after the decimal point.

**Passes the stated condition.** That amount has 2 digits after the decimal point.

## Published context and test

Copied from the source. Not reimplemented on this page.

```
cac:TaxTotal/cac:TaxSubtotal
```

```
string-length(substring-after(cbc:TaxAmount,'.'))<=2
```

[All rule notes](https://einvoicegoblin.com/rules/index.md) · [JSON](https://einvoicegoblin.com/rules/BR-DEC-20.json) · [HTML](https://einvoicegoblin.com/rules/BR-DEC-20/) · [llms.txt](https://einvoicegoblin.com/llms.txt) · [Invoice page](https://einvoicegoblin.com/) · [Privacy](https://einvoicegoblin.com/privacy.html)