What is an invoice data model and why does it matter for e-invoicing?
An invoice data model is a structured definition of all data elements that can appear in an invoice, their data types, cardinality (mandatory vs. optional), and relationships. A shared invoice data model enables interoperability between different e-invoicing systems and trading partners. The EN 16931 core invoice data model is the EU standard that underpins UBL, CII, and Factur-X invoice formats.
What does the EN 16931 core invoice data model define?
The EN 16931 semantic data model defines: (1) Business Terms (BT): named data elements (e.g., BT-1 Invoice number, BT-2 Invoice issue date, BT-9 Payment due date, BT-25 Invoice total VAT amount, BT-84 Payment account identifier); (2) Business Groups (BG): logical groupings of related terms (BG-4 Seller, BG-7 Buyer, BG-25 Invoice line); (3) Cardinality: which terms are mandatory (1..1), conditional (0..1), or repeatable (0..n); (4) Allowed values: code lists for currency, country, VAT category, and unit codes.
Frequently Asked Questions
- How does the invoice data model relate to ERP configuration?
- ERP invoice data model alignment is critical for e-invoicing compliance. Businesses must map their ERP's internal invoice data fields to the EN 16931 Business Terms to ensure all mandatory elements are captured and exportable in the required format. Common gaps: ERP systems may not natively store Peppol endpoint IDs, IBAN in required format, or VAT category codes in the exact code list values required. ERP configuration or middleware mapping must bridge these gaps before e-invoicing goes live.
- What is a CIUS (Core Invoice Usage Specification)?
- A CIUS is a national or sector-level restriction and extension of the EN 16931 core invoice model. A CIUS can: restrict optional fields to mandatory, further restrict allowed values from EN 16931 code lists, and add national extension elements not in EN 16931. Examples: NLCIUS (Netherlands), CIUS-PT (Portugal), Peppol BIS Billing 3.0. A CIUS cannot remove mandatory EN 16931 fields or contradict EN 16931 business rules.