Counterfoil rule note
Quoted from a public specification. This page is not a validator, and it is not tax, legal, or accounting advice.
Document level charge reason code (BT-105) and Document level charge reason (BT-104) shall indicate the same type of charge.
Source: https://docs.peppol.eu/poacc/billing/3.0/rules/ubl-tc434/BR-CO-06/
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.
The statement says a document-level charge reason code (BT-105) and a document-level charge reason (BT-104) shall indicate the same type of charge, and the published test is true(). The statement ends with a period and does not say MUST. The context is an invoice or a credit note charge whose charge indicator is true, with spaces around = and around the bar. The test does not compare the reason code with the reason text. It does not call exists.
When both the document-level charge reason code (BT-105) and the reason (BT-104) are present, make them name the same charge type. The published test is true().
Illustration of the condition in the official statement. Not an example published by the source.
Fails the stated condition. A document-level charge has a reason code and a reason text that name different charge types.
Passes the stated condition. A document-level charge has a reason code and a reason text that name the same charge type.
Copied from the source. Not reimplemented on this page.
/ubl:Invoice/cac:AllowanceCharge[cbc:ChargeIndicator = true()] | /cn:CreditNote/cac:AllowanceCharge[cbc:ChargeIndicator = true()]
true()
All rule notes · JSON · Markdown · llms.txt · Invoice page · Privacy