On this page
The short answer
UBL-CR-502 is a warning raised when cbc:TierRange appears in the VAT breakdown (cac:TaxTotal/cac:TaxSubtotal). EN 16931 has no business term for it, so remove the element.
The warning on its own does not make the document invalid, though other rules still check what is there. Removing the element keeps the XML inside the EN 16931 model, which is what a receiver maps the invoice from.
What the rule checks
The rule checks one thing: whether cac:TaxTotal/cac:TaxSubtotal/cbc:TierRange exists. Its value is not read.
It runs once against the whole document, so it is reported once however many times the document has the element, and the finding points at the document root rather than at the element: look for cac:TaxTotal/cac:TaxSubtotal/cbc:TierRange in the XML.
| Term | Meaning | UBL element |
|---|---|---|
| - | TierRange (UBL only, no business term) | cac:TaxTotal/cac:TaxSubtotal/cbc:TierRange |
| BG-23 | VAT breakdown | cac:TaxTotal/cac:TaxSubtotal |
How an integration ends up here
Possible causes, from the shape of the rule rather than from measured usage:
- The source system holds the value, and the mapping writes it because UBL 2.1 has a place for it.
- A general UBL 2.1 library writes every element and attribute it has a value for, whether or not EN 16931 uses it.
- A mapping built for another UBL-based document, such as an order, a despatch advice or a national profile, is reused for Peppol BIS Billing.
How to fix it
- Stop writing
cac:TaxTotal/cac:TaxSubtotal/cbc:TierRange. - If you need the information, keep it in your own records: EN 16931 has no business term for it, so a receiver has no agreed place to read it from.
- Validate again: the warning goes. If the element was the only thing in its parent, remove the parent too: Peppol refuses empty elements (PEPPOL-EN16931-R008).
Validate your corrected invoice
Before and after
These are fragments, not complete documents. The complete synthetic documents they come from are linked below.
Fragment of the invoice with the warning: TierRange in the VAT breakdown
<cac:TaxSubtotal>
<cbc:TaxableAmount currencyID="GBP">58.50</cbc:TaxableAmount>
<cbc:TaxAmount currencyID="GBP">11.70</cbc:TaxAmount>
<cbc:TierRange>Example</cbc:TierRange>
<cac:TaxCategory>
<cbc:ID>S</cbc:ID>
<cbc:Percent>20</cbc:Percent>
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:TaxCategory>
</cac:TaxSubtotal>Fragment of the corrected invoice: the same lines without it
<cac:TaxSubtotal>
<cbc:TaxableAmount currencyID="GBP">58.50</cbc:TaxableAmount>
<cbc:TaxAmount currencyID="GBP">11.70</cbc:TaxAmount>
<cac:TaxCategory>
<cbc:ID>S</cbc:ID>
<cbc:Percent>20</cbc:Percent>
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:TaxCategory>
</cac:TaxSubtotal>The invoice with the warning has <cbc:TierRange>Example</cbc:TierRange> in the VAT breakdown, and the corrected invoice is the same document without it. It reports only this warning and is valid on every layer, so it would be accepted as it stands.
What the validator reported
- The invoice with the warning is valid, and reports the warning UBL-CR-502. The corrected document passes every layer with no findings.Download the XML with the warningDownload the corrected XML
Recorded on phive 12.1.0 / phive-rules-peppol 4.5.6 / Saxon-HE 12.10, the engine behind the free validator, using synthetic data. A recorded result is regression evidence for these documents; it is not a certification.
Where it applies
- Applies to UBL
InvoiceandCreditNotealike; the recorded example is an invoice. - The warning comes from the EN 16931 layer's rules for the UBL syntax. In the recorded example the schema layer passes: the element is valid UBL 2.1 and is only outside the EN 16931 model.
Related rules
- UBL-CR-500: BaseUnitMeasure in the VAT breakdown
- UBL-CR-501: PerUnitAmount in the VAT breakdown
- UBL-CR-503: TierRatePercent in the VAT breakdown
- Browse every rule in the reference
- Background: Understanding EN 16931 validation errors
Scope and source
Written for Peppol BIS Billing 3.0.21 (May 2026), EN 16931 1.3.16, as applied to UBL 2.1 Invoice and CreditNote documents. Other profiles, syntaxes and releases can define this identifier differently. Guidance version 2026-09-29.1: source checked 2026-09-29, explanation last updated 2026-09-29.
The official definition of UBL-CR-502 carries the normative wording and test. This page is our explanation of it, not a copy.
Guidance does not change the engine verdict. Fixing this finding does not mean the document passes every layer, and validation does not certify legal or tax compliance or transmit a document over Peppol.

