Peppol BIS Billing 3.0 · rule
UBL-CR-488
What does UBL-CR-488 mean? A UBL invoice should not include the AllowanceCharge TaxTotal
Why did my invoice fail UBL-CR-488?
EN 16931 defines a fixed set of business terms, and the UBL element cac:TaxTotal inside cac:AllowanceCharge is not mapped to any of them, so a core-compliant invoice should not contain it. This cardinality rule exists to keep invoices restricted to the EN 16931 semantic model: elements outside the model cannot be relied on by receivers and are flagged as warnings. Remove the element or move the information to a supported business term (e.g. cbc:Note) if it must be conveyed.
Official rule text
A UBL invoice should not include the AllowanceCharge TaxTotal
Common causes
- Emitting a nested TaxTotal per allowance/charge; VAT on allowances and charges is instead reflected in the document-level VAT breakdown (cac:TaxTotal/cac:TaxSubtotal)
- An ERP or invoicing tool exporting its full internal UBL model instead of the EN 16931 subset
- Reusing a UBL 2.1 template or mapping built for a richer profile than EN 16931
Related rules
UBL-CR-001 · UBL-CR-002 · UBL-CR-003 · UBL-CR-004 · UBL-CR-005 · UBL-CR-006 · UBL-CR-007 · UBL-CR-008
Paste it into the live demo, or call POST /v1/validate. See the quickstart.