Directive 2014/55/EU on electronic invoicing in public procurement
Directive 2014/55/EU establishes a European standard approach for electronic invoicing in public procurement and acceptance of covered compliant invoices.
What the authority record establishes
Directive 2014/55/EU establishes a European standard approach for electronic invoicing in public procurement and acceptance of covered compliant invoices.
Binding on Member States as to the result; operative requirements depend on implementation and transaction scope
The exact official title, issuing body, jurisdiction, version or application record, and linked source define the scope of this page. Readers should not transfer the authority's status to a commercial product or infer transaction-, patient-, system-, site-, or organization-specific applicability from this summary.
Why it matters to this market
Product evaluation needs jurisdiction, invoice standard, format, transport, validation, supplier enablement, exception, and archive boundaries instead of one undifferentiated e-invoicing label.
Affected operating stages
- Invoice Creation
- Format And Semantic Validation
- Transmission
- Receipt
- Processing
- Retention
Capabilities to examine
Supplier Onboarding And Master-Data Governance
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for supplier onboarding and master-data governance.
Supplier Network, Portal, And Transaction Collaboration
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for supplier network, portal, and transaction collaboration.
Receiving, Matching, And Exception Management
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for receiving, matching, and exception management.
Invoice Capture, Validation, And Approval Workflow
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for invoice capture, validation, and approval workflow.
Electronic Invoicing And Interoperability
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for electronic invoicing and interoperability.
ERP Integration, Data Lineage, And Access Governance
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for ERP integration, data lineage, and access governance.
Affected buyer audiences
- EU public buyers
- suppliers to government
- accounts-payable teams
- e-invoicing and procurement providers
Implementation questions
- Which entities, products, populations, transactions, systems, sites, or jurisdictions are actually within scope?
- What is binding, what is guidance, and what is a technical or consensus standard?
- Which publication, adoption, effective, application, transition, and enforcement dates differ?
- Who owns legal, clinical, quality, regulatory, policy, or operational interpretation?
- How will a source revision affect open work and historical decisions?
Interpretation boundary
The publication does not determine whether an invoice or entity is within scope or whether a transaction satisfies national tax and accounting requirements.