E-invoicing for public sector bodies: receiving and set-up

E-invoicing for public sector bodies comes down to two questions: which e-invoices must your organisation be able to receive and process, and how do you set this up? This page covers receiving routes, the integration with your financial system, addressing and sending e-invoices yourself.

Back to Knowledge Base

A public sector body must be able to receive and process e-invoices. Two questions are then important: what counts as “being able to receive”, and which route do you use to set this up? On this page you can read which requirements apply, which two routes exist and how to determine whether a single Peppol ID is sufficient for your organisation.

What “receiving and processing” involves

“Receiving and processing” means more than opening a mailbox for PDF invoices. A public sector body must receive and process electronic invoices that comply with a recognised semantic standard. Such a standard defines which data an invoice contains and what that data means. This allows your systems to read the invoice automatically. In Europe, EN 16931 is the European standard for e-invoicing. The legal basis is Directive 2014/55/EU, adopted in 2014. This directive requires contracting authorities and contracting entities in the EU to receive and process e-invoices that comply with the European standard. Member states have transposed the directive into national legislation, and many countries go further:

  • Netherlands: the Dutch central government has made e-invoicing mandatory for all contracts, orders and agreements. Suppliers can invoice via a service provider, the Supplier Portal (Leveranciersportaal) or Digipoort.
  • Belgium: since 1 March 2024, e-invoicing via Peppol has been mandatory for public contracts. Contracts below EUR 3,000 may be exempt, except at the federal government.
  • Luxembourg: mandatory for suppliers on public contracts in phases: for large companies since 18 May 2022, for medium-sized companies since 18 October 2022 and for small companies since 18 March 2023. Suppliers invoice via Peppol or via forms on MyGuichet.lu.
  • France: since 1 January 2020, all suppliers to the government have invoiced electronically via Chorus Pro.
  • Germany: since 27 November 2020 for direct contracts of the federal government from EUR 1,000 net, in XRechnung or another EU-compliant standard. Suppliers invoice via the central platform OZG-RE, including via Peppol.
  • Other countries: in Italy, all invoices go through the SdI platform, and in Spain suppliers submit their invoices to the government through a central entry point, such as FACe.

Outside the EU, too, various jurisdictions have similar obligations for governments to receive e-invoices in a structured format. Which obligation applies in your situation depends on the jurisdiction your organisation falls under. Always verify this with the primary source: EUR-Lex or the competent national authority. Read more about the legal background on the Mandatory e-invoicing page.

Two receiving routes, and the integration behind them

There are two ways to receive e-invoices. Behind them, you always determine how they end up in your financial system.

Route 1: central government platform

A shared government facility where suppliers submit e-invoices or to which they are forwarded. Advantage: shared infrastructure and costs, and a quick connection. Disadvantage: less control of your own and dependence on the platform operator. In some countries, such a platform is mandatory.

Route 2: your own service provider

Your organisation connects to the network itself through a Peppol service provider. Advantage: your own control over document types, validation and integration. Disadvantage: your own implementation and management costs. Certification and maintenance of the connection lie with the service provider; sometimes this is the vendor of your financial software itself.

Behind it: the integration with your financial system

Directly via an API or via a middleware layer. Advantage: automatic processing without manual handover. Disadvantage: requires investment in integration and testing.

Addressing organisational units: one or multiple Peppol IDs

Many public sector bodies consist of several units, such as separate agencies, departments or locations. You then have to choose: is one central Peppol ID sufficient, or does each unit need its own Peppol ID?

That depends on how invoices need to be routed and processed within your organisation. One central Peppol ID suits an organisation with a single central accounts payable department; internal distribution is then based on data in the invoice, such as an order number or reference. Multiple Peppol IDs suit units with their own administration, their own financial system or their own responsibility for payment: invoices then arrive directly at the right unit.

You can read how a Peppol ID works and how to register one on the Peppol ID page.

In Peppol, a buyer reference or an order number is mandatory on every e-invoice. This is the most important tool for getting invoices to the right unit internally. So always ask suppliers to include that reference.

Sending e-invoices yourself

Public sector bodies also send invoices themselves, for example for rent, fees, secondment or recharges. Those that do so by e-invoice show that e-invoicing is the standard and increase support among suppliers and customers. Moreover, from 1 July 2030, European digital reporting will also affect governments that invoice across borders as suppliers. Read more about this in ViDA explained.

What this means for public sector bodies

Receiving route checklist

Use these points to set up the receipt, addressing and sending of e-invoices.
  • ✓ Determine the receiving route: central platform or your own service provider, matching the size and IT capacity of your organisation
  • ✓ Choose how e-invoices end up in your financial system
  • ✓ Determine whether you need one central Peppol ID or several, per unit
  • ✓ Make sure you can be found on the network, so that suppliers can reach you
  • ✓ Validate e-invoices automatically against the standard that applies to you, and agree on how you handle rejected invoices
  • ✓ Tell suppliers through which channel, in which format and with which mandatory reference they must invoice
  • ✓ Consider sending e-invoices yourself as well
  • ✓ Are you going to procure a Peppol service? Then read Procuring a Peppol service for the requirements framework
Compare providers for public sector bodies
Tip: in the comparison tool, filter by the sector "Government & Public Sector" and by your user group.

For software vendors

Do you have public sector bodies as customers? Then your software will have to deal with different routes. Some public sector customers receive via a central government platform and mainly need reliable forwarding to that platform. Others receive directly via Peppol and need support for Peppol document types, validation, mandatory references and addressing to one or multiple Peppol IDs. Software that supports both routes, as well as sending e-invoices, can serve more public sector customers without custom development.

Conclusion and next steps

For well-designed e-invoicing, you make four choices: the receiving route, the integration with your financial system, the addressing of your units, and whether you also send e-invoices yourself. Once you have made those choices, the next step is procuring the service. You can read more about this on the Procuring a Peppol service page. Want to see which providers match your requirements? Use the comparison tool on Peppol.now.

Ready to set up your receiving process?

Compare Peppol service providers that fit your route.

Peppol.now - Your guide in the world of electronic invoicing