Peppol BIS Billing 3.0 · rule
UBL-CR-634
What does UBL-CR-634 mean? A UBL invoice should not include the InvoiceLine Item Price AllowanceCharge AllowanceChargeReason
Why did my invoice fail UBL-CR-634?
EN 16931 does not define a business term for the AllowanceChargeReason element inside the Price AllowanceCharge structure (cac:InvoiceLine/cac:Item ... cac:Price/cac:AllowanceCharge). In the core standard the price allowance-charge group is only used to express the price discount (BaseAmount and Amount relationship), so the extra UBL element AllowanceChargeReason is outside the semantic model and must not be sent. Remove the element; a compliant invoice carries only the data covered by EN 16931 business terms.
Official rule text
A UBL invoice should not include the InvoiceLine Item Price AllowanceCharge AllowanceChargeReason
Common causes
- Invoice generator emits the full UBL 2.1 AllowanceCharge structure instead of only the fields EN 16931 allows
- ERP export copies purchase-order pricing structures into the invoice line price
- Template reused from a non-EN 16931 UBL profile
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.