Quick answer
e-Invoicing is the electronic exchange of invoice data between a supplier and a contracting authority in a structured machine-readable format, enabling automated processing, faster payment, and compliance with the European e-Invoicing standard EN 16931 mandated for public sector transactions.
e-Invoicing is the structured, automated exchange of invoice information between suppliers and public sector buyers. Unlike a PDF invoice sent by email (which a human must read and manually key into an accounting system), a true e-Invoice is a structured data file that can be processed automatically by the buyer's financial systems, reducing errors, accelerating payment, and producing a complete audit trail.
What is e-Invoicing?
e-Invoicing in the European public sector is defined and governed by the European e-Invoicing Standard EN 16931, which specifies the semantic data model that all compliant invoices must follow. EU Directive 2014/55/EU on electronic invoicing in public procurement required contracting authorities in EU member states to be capable of receiving and processing compliant e-Invoices. Central government bodies were required to meet this obligation by April 2019, and subnational authorities (regional and local) by April 2020.
In practice, e-Invoices are transmitted using established networks, most commonly Peppol, which connects suppliers and buyers through a network of certified access points. A supplier's accounting system sends the invoice data in Peppol BIS Billing 3.0 format (based on EN 16931) through its Peppol access point to the buyer's access point and then to the buyer's financial system, without manual intervention.
Key elements of an e-Invoice include:
- Structured identification of buyer and seller (including Peppol IDs or national identifiers).
- Purchase order reference linking the invoice to the original contract or order.
- Line-item detail at the level of granularity required by the buyer.
- Tax data in a machine-readable form compliant with EN 16931.
The UK adopted equivalent e-Invoicing obligations for central government under a phased programme aligned to EN 16931, with Peppol as the preferred transmission network.
Why it matters for bidders
For suppliers, e-Invoicing capability is becoming a prerequisite for doing business with public sector buyers. Buyers who have mandated e-Invoicing will reject PDF invoices submitted by email or require resubmission through the correct channel. The practical implications are:
- Suppliers need an accounting or ERP system capable of generating EN 16931-compliant invoice files, or a Peppol service provider who can convert their existing data.
- Faster processing translates directly into faster payment, which improves cash flow.
- Structured data reduces disputes caused by keying errors in the buyer's accounts payable system.
- Compliance with e-Invoicing requirements is often written into contract terms, so non-compliance can constitute a contract breach.
Connecting to Peppol through an access point provider is the most common solution for small and medium-sized suppliers who lack in-house EDI capability.
Example
A Swedish IT consultancy wins a services contract with a Swedish government agency. The contract specifies that invoices must be submitted via Peppol. The consultancy registers with a Peppol access point provider, enters its Peppol ID into its accounting software, and sends invoices in Peppol BIS Billing 3.0 format. The agency's financial system automatically validates the invoice against the contract purchase order, approves it within 24 hours, and schedules payment within the 30-day statutory deadline.
Frequently Asked Questions
Is e-Invoicing mandatory for all public contracts in Europe?
Receiving e-Invoices is mandatory for contracting authorities across EU member states and EEA countries that have implemented Directive 2014/55/EU. Sending e-Invoices is mandatory for suppliers in some member states (including Italy, which mandates B2G e-Invoicing broadly). Suppliers in other countries are not universally mandated to send e-Invoices but may be required to do so by individual contract terms.
Do I need to use Peppol specifically?
Peppol is the dominant transmission network for public sector e-Invoicing across Europe, but it is not the only legal channel. EN 16931 defines the data model; the transmission channel can be Peppol, a direct API connection, or a bilateral channel agreed with the buyer. In practice, Peppol is the safest default because it is accepted by virtually all European public sector buyers.
What if my accounting software does not support e-Invoicing?
Several intermediary service providers convert standard invoice data (CSV, PDF, Excel) into compliant Peppol BIS Billing 3.0 files and submit them on your behalf. This is a practical solution for smaller suppliers while upgrading accounting software. Costs vary but are typically modest relative to the payment speed benefits.
How Bidovate helps
Bidovate puts e-Invoicing to work inside your capture and proposal workflow.
Tender discoverySee Bidovate in action
Book a demo and we will show you the platform using your actual contract data.
Related terms
European e-Invoicing Standard (EN 16931)
EN 16931 is the European standard that defines the semantic data model and syntax bindings for electronic invoices in the public sector, enabling machine-readable invoice exchange between suppliers and contracting authorities across all EU member states and EEA countries.
ViewPeppol (Pan-European Public Procurement OnLine)
Peppol is an international network and set of technical specifications that enables the secure, standardised exchange of procurement documents including e-Invoices, e-Orders, and e-Catalogues between buyers and suppliers through certified access points, widely adopted across European and global public sector procurement.
Viewe-Procurement
e-Procurement is the use of electronic systems and platforms to conduct public purchasing processes, including publishing notices, managing tender documents, receiving bids, evaluating submissions, and awarding contracts, replacing paper-based workflows with secure digital equivalents.
ViewContract Lifecycle Management (CLM)
Contract Lifecycle Management (CLM) is the systematic administration of contracts from initial drafting and negotiation through execution, performance monitoring, variation management, and expiry or renewal, supported by dedicated software that centralises contract data, automates obligations tracking, and reduces the risk of missed deadlines or unauthorised spend.
ViewInteroperability in e-Procurement
Interoperability in e-Procurement is the ability of different electronic procurement systems, platforms, and data formats to exchange information accurately and automatically across organisational and national boundaries, enabling suppliers and buyers in different European countries to transact without bilateral integration agreements.
View