Peppol BIS Billing 3.0 · rule
UBL-CR-646
What does UBL-CR-646 mean? A UBL invoice should not include the InvoiceLine SubInvoiceLine
Why did my invoice fail UBL-CR-646?
A UBL invoice should not include the InvoiceLine SubInvoiceLine. The UBL 2.1 element InvoiceLine SubInvoiceLine has no corresponding business term in the EN 16931 semantic model, so it lies outside the core invoice content and should not be sent. Compliant invoices restrict themselves to elements that map to EN 16931 business terms; remove this element from the document.
Official rule text
A UBL invoice should not include the InvoiceLine SubInvoiceLine
Common causes
- Invoice generated from a full UBL 2.1 schema/template rather than the EN 16931 subset
- ERP export includes extra product, price, or logistics data not covered by the standard
- Data copied over from orders, catalogues, or despatch documents that use richer UBL structures
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
Check your invoice against this rule
Paste it into the live demo, or call POST /v1/validate. See the quickstart.