E-Invoicing for Public Sector Clients: A Complete Compliance Guide

Why Public Sector E-Invoicing Is Now Mandatory Across the EU

EU Directive 2014/55/EU requires all public sector entities to be able to receive and process structured electronic invoices. Most EU member states have gone further, making it mandatory for suppliers to send e-invoices to government clients. In Slovenia, the e-SLOG format via the UJP portal has been required since 2015. In Croatia, the eSEF system became mandatory for B2G invoices from 2019. Across the EU, the Peppol network has become the common infrastructure.

Paper invoices to government bodies are increasingly rejected or processed with significant delays. Suppliers who have not yet switched to e-invoicing frequently report payment delays of 2 to 4 weeks compared to their peers who send structured e-invoices. The business case for compliance is straightforward: faster payment and less administrative overhead on both sides.

Key E-Invoice Formats and Networks to Know

The most important formats depend on your target market. Peppol BIS Billing 3.0 is the EU-wide standard used across 38 countries and is based on UBL 2.1 XML. It is the format to target if you sell to public bodies in multiple EU countries. National variants exist: e-SLOG in Slovenia, eSEF/eRačun HR in Croatia, FatturaPA in Italy, and XRechnung in Germany.

The Peppol network uses a four-corner model: your software (corner 1) sends the invoice to your Peppol access point provider (corner 2), which routes it to the recipient's access point (corner 3) and on to the buyer's system (corner 4). Choosing an accredited Peppol access point provider means you do not need to manage XML generation or network connectivity yourself - your invoicing software handles both.

The Most Common E-Invoice Submission Errors and How to Avoid Them

The leading causes of e-invoice rejection are: missing purchase order reference (most public bodies require a PO number or contract reference on every invoice), incorrect buyer identifier (each public entity has a unique GLN or Peppol ID - using the wrong one routes the invoice to the wrong destination), and invalid tax data (wrong VAT rate, missing tax breakdown, or mismatched totals). A fourth common issue is sending to an entity that is not registered on the Peppol network, which results in a failed delivery with no error message to the supplier.

Validation before submission is the most reliable prevention. Good invoicing software validates the XML against the schema and business rules before sending, and shows you any errors in plain language. Manual validation using the online tools published by national tax authorities works for low volumes but does not scale.

How Software Simplifies E-Invoicing for Public Sector Suppliers

Modern invoicing platforms like Entexia generate structured e-invoices directly from your sales data, without any manual XML editing. You create the invoice in the familiar interface, select the public sector recipient from a validated directory, and send. The system handles format conversion, network routing, and delivery confirmation. You see the status of every invoice in a single dashboard.

For businesses that send 20 or more invoices per month to public sector clients, the time saved on formatting, validation, and postal handling typically exceeds the subscription cost of a good invoicing system by a factor of 4 to 8. The Entexia Finance module supports Peppol BIS 3.0, e-SLOG, and eSEF, covering the key markets in the region. Try it free for 7 days.