If you supply goods or services to public buyers anywhere in the EU, mandatory e-invoicing has moved from a future planning item to a live compliance obligation. Directive 2014/55/EU required central government authorities to receive structured electronic invoices by April 2019, with sub-central authorities following a year later. Since then, several member states have gone further, extending the obligation to suppliers and requiring them to issue machine-readable invoices rather than scanned PDFs. For a small manufacturer or service firm in Poland, Slovakia, Romania, or the Czech Republic, the question is no longer whether to adopt electronic invoicing: it is how quickly and how correctly.
The same period has seen procurement portals evolve from simple notice boards into full end-to-end digital systems. Tenders are published, clarifications exchanged, bids submitted, contracts awarded, and invoices processed, all inside a single electronic environment. That integration is efficient, but it adds a compliance layer on top of your existing obligations. Miss it and you do not simply face an accounting correction. You risk a rejected invoice, a delayed payment, or, in some cases, disqualification from a future bid round. This article sets out what you need to understand and what you need to do.
What the EU e-invoicing mandate actually requires
The foundation is Directive 2014/55/EU on electronic invoicing in public procurement. It standardised what contracting authorities must be able to receive: a structured invoice conforming to the European standard EN 16931. That standard defines the semantic data model, the fields that must appear, and the rules for how values are expressed. It does not mandate a single file format; it mandates a structured data syntax that machines can read and validate without human intervention.
The directive applies to above-threshold contracts, but member states have used it as a baseline for wider domestic rollouts. Several countries now require electronic invoices on below-threshold contracts too, and some are moving toward mandatory issuance for all business-to-government transactions. The pace varies significantly by country and by tier of buying authority. The local implementing regulation will govern your immediate obligations more precisely than the directive alone, so check your national transposition as a first step.
The formats and standards you need to support
- UBL (Universal Business Language): the XML format used in most Nordic countries, Belgium, and increasingly across CEE procurement portals. If your portal asks for a structured invoice file, UBL is frequently what it expects.
- CII (UN/CEFACT Cross-Industry Invoice): common in Germany and France, and the XML payload embedded inside hybrid formats such as ZUGFeRD and Factur-X, where a machine-readable layer sits inside a visible PDF.
- Peppol BIS Billing 3.0: the most widely adopted implementation profile in EU public procurement, built on UBL and distributed through the Peppol network. If your buyer is registered on Peppol, your invoice routes from your access point to theirs with no manual intervention on either side.
- CIUS (Core Invoice Usage Specification): the national or sector variant of EN 16931 that individual countries publish to handle local tax fields, identifier formats, or payment terms. Your invoicing software must apply the correct CIUS for each country you invoice into, not just the base standard.
Peppol deserves particular attention for CEE suppliers. It is the network infrastructure behind most new government e-procurement rollouts in the region, and it sits beneath several national portals that have modernised in the past three years. Registering a Peppol identifier through an accredited access-point provider is a one-time action that makes you discoverable and reachable for structured invoice delivery across every connected buyer in the network.
How digital procurement portals connect to e-invoicing
Modern e-procurement portals do not stop at bid submission. Once a contract is awarded, the same system often handles purchase orders, delivery confirmations, and invoices. The contract reference numbers and line-item codes generated at award stage must appear verbatim on every invoice you raise against that contract. A mismatch between the purchase order number recorded in the portal and the reference on your invoice is one of the most common rejection triggers, and it almost always happens when procurement and finance operate as separate workflows with no shared reference discipline.
Portal-embedded invoice submission also means your document is validated on upload. The portal checks EN 16931 conformance, the applicable CIUS variant, and cross-references your data against the contract record. A PDF that looks correct will be refused if the machine-readable data layer is missing or malformed. Getting this right before your first submission, rather than after a rejection on a 60-day payment-terms contract, matters directly for cash flow.
Setting up once: the practical steps
Getting e-invoicing right does not require enterprise-scale IT investment, but it does require a deliberate one-time setup. The effort is front-loaded and, once complete, largely invisible.
Choose accounting or invoicing software that holds a current EN 16931 certification, supports the Peppol network via a built-in or partnered access point, and lets you apply the correct CIUS variant for each country you invoice into. Most mid-market accounting packages used across CEE now offer this natively, or have a certified add-on that handles it.
Register on Peppol through your software provider's access-point service. You will receive a Peppol participant identifier tied to your VAT number or national company register number. Publish this identifier on your supplier profile in any procurement portal that requests it.
Store your standard document identifiers centrally: VAT number, national company register number, IBAN, and any sector-specific codes that appear in your contracts. Populate these once as defaults in your invoicing software so they carry through automatically to every invoice, eliminating the manual transcription errors that trigger validation failures.
Map your internal product and service codes to the CPV or commodity codes your public buyers use. Consistent line-item references make the invoice match the contract record at the portal's automated check, reducing the risk of a manual review queue that can hold payment for weeks.
Review the specific national CIUS for each new country you enter. The underlying EN 16931 semantic model is the same, but the local fields differ by member state. If you are expanding your tender activity into other EU markets, this country-specific preparation is the same kind of due diligence described in Cross-border tender: the CEE SME guide to bidding in Europe.
Avoiding the compliance gap that disqualifies bids
Digital procurement compliance reaches further back than the invoice stage. Before a payment is ever raised, your bid must pass a conformance check at submission. The ESPD (European Single Procurement Document) is the first line of that, and many suppliers discover their exclusion grounds declarations or self-certification fields are out of date precisely when they are trying to meet a submission deadline. The compliance vault in Tanax Edge stores your ESPD self-declarations and qualification documents so you update them once and reuse them across bids, rather than rebuilding a full compliance pack from scratch each time.
Beyond the ESPD, watch for portal-specific requirements: digital signatures on submitted documents, specific certificate file formats, and the buyer's required metadata schema for attachments. These vary by country and by buying authority. Missing a single mandatory field can invalidate an otherwise strong bid. It is one of several avoidable compliance failures detailed in The 7 reasons SMEs lose tenders, and it is also one of the easiest to prevent with a checklist run before each submission.
Practical takeaway
E-invoicing compliance for a CEE SME comes down to three durable actions: choose software that issues EN 16931-conformant structured invoices in the formats your target markets require, register once on Peppol so you are reachable by any connected buyer, and align your internal order-reference discipline so invoice data matches contract data precisely. Do this before you win your next public contract rather than after. A payment rejection on a 60-day public-sector contract is an expensive lesson, and the setup cost in most cases is under a few hundred euros and a day of configuration. That is a one-time investment that removes a compliance risk permanently, frees your finance team from manual corrections, and ensures that a correctly priced and correctly submitted bid is never undermined at the payment stage.