Invoice
The Invoice subset is designed for validating invoicing data conforming to the EDIFACT standard (Electronic Data Interchange for Administration, Commerce and Transport).
Overview
| Property | Value |
|---|---|
| # Records | 78 |
| # Node Shapes | 78 |
| # Property Shapes | 113 |
| Avg. NL Length | 75.1 words |
| Avg. Shapes per Record | 2.45 |
| Raw Records | 84 |
| Filtered Records | 6 |
Domain
The shapes specify constraints for invoice data exchange, covering both header-level and item-level information. This subset is notable for its use of logical constraint components to express alternative and negation constraints.
Constraint patterns in this subset include:
- Required fields and data formats
- Identifier structure constraints
- Logical constraints via
sh:orandsh:not - Conditional constraints based on party roles (buyer, supplier, invoicee, delivery party)
The subset covers entities such as invoice details, line items, and organizational parties (buyers, suppliers, and invoice recipients).
Ontologies
The Invoice subset draws on the following ontologies:
- EDIFACT-O (
https://purl.org/edifact/ontology) - models EDIFACT invoice structures - P2P-O (
https://purl.org/p2p-o) - models procure-to-pay processes
Source
This subset is derived from prior work on EDIFACT-based invoice validation using SHACL shapes.