Counterfoil rule note
Quoted from a public specification. This page is not a validator, and it is not tax, legal, or accounting advice.
Each Document level charge (BG-21) shall have a Document level charge reason (BT-104) or a Document level charge reason code (BT-105).
Source: https://docs.peppol.eu/poacc/billing/3.0/rules/ubl-tc434/BR-38/
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.
Each Document level charge (BG-21) must have a Document level charge reason (BT-104) or a Document level charge reason code (BT-105). The message says "shall have" and starts with "Each". It ends with a period. The context is the document charge, and the charge indicator comparison has spaces around =. The published test checks that an allowance-charge reason or an allowance-charge reason code exists.
On each document charge, send a Document level charge reason (BT-104) or a Document level charge reason code (BT-105).
Illustration of the condition in the official statement. Not an example published by the source.
Fails the stated condition. A document charge has neither a reason nor a reason code.
Passes the stated condition. That charge has a reason or a reason code.
Copied from the source. Not reimplemented on this page.
/ubl:Invoice/cac:AllowanceCharge[cbc:ChargeIndicator = true()] | /cn:CreditNote/cac:AllowanceCharge[cbc:ChargeIndicator = true()]
exists(cbc:AllowanceChargeReason) or exists(cbc:AllowanceChargeReasonCode)
All rule notes · JSON · Markdown · llms.txt · Invoice page · Privacy