Counterfoil rule note

BR-CO-22

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 charge (BG-21) shall contain a Document level charge reason (BT-104) or a Document level charge reason code (BT-105), or both.

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

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 charge (BG-21) must contain a Document level charge reason (BT-104) or a Document level charge reason code (BT-105), or both. The statement says "shall contain", not "shall have", and it ends with a period. The context writes ChargeIndicator = true() with spaces around =. The published test is exists on the reason or exists on the reason code.

What to change

On each document-level charge, send a Document level charge reason (BT-104), a Document level charge reason code (BT-105), or both.

Illustration

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

Fails the stated condition. A document-level charge has neither a reason nor a reason code.

Passes the stated condition. A document-level charge has a reason code and no reason.

Published context and test

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