Counterfoil rule note

BR-33

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
Last verified
2026-10-18

Official statement

Each Document level allowance (BG-20) shall have a Document level allowance reason (BT-97) or a Document level allowance reason code (BT-98).

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

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

Each Document level allowance (BG-20) must have a Document level allowance reason (BT-97) or a Document level allowance reason code (BT-98). The message says "shall have" and starts with "Each". It ends with a period. The context is the document allowance, and the charge indicator comparison has spaces around =. The published test checks that an allowance-charge reason or an allowance-charge reason code exists.

What to change

On each document allowance, send a Document level allowance reason (BT-97) or a Document level allowance reason code (BT-98).

Illustration

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

Fails the stated condition. A document allowance has neither a reason nor a reason code.

Passes the stated condition. That allowance has a reason or a reason code.

Published context and test

Copied from the source. Not reimplemented on this page.

/ubl:Invoice/cac:AllowanceCharge[cbc:ChargeIndicator = false()] | /cn:CreditNote/cac:AllowanceCharge[cbc:ChargeIndicator = false()]
exists(cbc:AllowanceChargeReason) or exists(cbc:AllowanceChargeReasonCode)

All rule notes · JSON · Markdown · llms.txt · Invoice page · Privacy