Slovakia E-Invoicing Requirements: 2027 Guide

Slovakia's e-invoicing legislation becomes legally valid on January 1, 2026, but the main operational rules for domestic B2B and B2G structured e-invoicing plus real-time reporting start on January 1, 2027. A compliant e-invoice is not a PDF. It must be a structured XML invoice aligned to EN 16931, typically exchanged through a Peppol-based model, and taxable persons must be able to receive those invoices through a certified service provider. The next major step, expanded cross-border EU reporting, begins on July 1, 2030. There is no B2C e-invoicing mandate in this reform.

For teams researching Slovakia e-invoicing requirements, that timing distinction matters because many will otherwise confuse enactment with go-live. In plain English, 2026 is the legal foundation year and 2027 is the operational start date for the domestic model. For AP, accounting, and ERP owners, that makes 2026 the preparation window, not the year to wait for the first compliance impact. If you are searching for Slovakia e-invoice requirements 2027, the key point is that issuance, receipt capability, and reporting obligations do not all begin in 2026 simply because the law is already on the books.

At a high level, this reform sits within Slovakia's VAT framework under VAT Act No. 222/2004 Coll., with implementation overseen through the Financial Administration of the Slovak Republic. This guide is written as a finance-team transition reference, not a legal alert. The rest of this Slovakia electronic invoicing guide explains who is in scope, what file format counts, why receipt capability matters, how the current IS EFA environment connects to the new model, and what practical workstreams finance teams should complete during 2026.

Who Must Issue And Receive E-Invoices In Slovakia

From January 1, 2027, Slovakia mandatory e-invoicing moves beyond a supplier-side formatting rule. For domestic invoice flows, the key split is this: taxable persons issuing in-scope domestic invoices need compliant issuing capability, and recipients in scope need compliant receiving capability. In practice, that means the rule is relevant for both sides of the transaction, not just the company creating the invoice.

Fast scope check: domestic B2B and B2G taxable persons should prepare for the January 1, 2027 domestic go-live; B2C stays out of scope; and broader cross-border EU digital reporting comes later, from July 1, 2030.

For finance teams, the easiest way to think about it is:

• Issue-side obligation: if your organization is a Slovak taxable person issuing invoices for domestic supplies that fall within the mandate, you need to generate the invoice in the required structured format.
• Receive-side obligation: if your organization is the kind of customer that should receive that invoice under the domestic model, you need to be able to accept it in that structured format when it arrives.

That second point is where many teams underestimate the change. The Slovakia e-invoice receiving obligation means a company that sends only a small number of invoices, or hardly any at all, may still need to get ready. If suppliers, contractors, or service providers will send you structured domestic B2B e-invoices, your AP process has to be able to take them in. This is why the mandate is an operational issue for accounts payable, controllers, ERP owners, and outsourced accounting partners, not just a tax manager's concern.

The scope is aimed at domestic B2B e-invoicing and B2G flows, not consumer invoicing. In plain English, this is about invoices exchanged between businesses and between businesses and public-sector bodies in Slovakia. B2C is not part of the mandate, so consumer receipts and ordinary retail customer invoices are not the focus here.

Receive-side readiness also means more than simply having a file arrive somewhere. Your organization needs a workable process to:

• accept the structured invoice through the mandated delivery model
• validate that the invoice can be processed and contains the expected business data
• route it into AP, bookkeeping, approval, and posting workflows
• retain it in a way that supports matching, reconciliation, audit trail, and downstream reporting

So the real question is not only, "Do we need to send e-invoices?" It is also, "If a supplier sends us one on January 1, 2027, can our AP and accounting workflow actually receive, process, and retain it without manual workarounds?" For many Slovak taxable persons, that is the more immediate compliance gap.

Why A PDF Does Not Meet Slovakia's E-Invoice Rules

A PDF invoice can still help a person read, approve, or archive a bill. But once Slovakia's mandate applies, the legal e-invoice is not the PDF attachment. It is the structured XML invoice that your systems can validate and process automatically. That distinction matters because a PDF or image only shows information visually, while the Slovak model expects invoice data to sit in machine-readable fields that software can parse, check, and route without rekeying. If your current process is "generate PDF, email it, and let AP type it in," that is document sharing, not compliant e-invoicing.

For system owners, the practical rule is this: EN 16931 defines what the invoice means, and Peppol BIS Billing defines how that invoice is packaged for exchange.

EN 16931 is the European semantic standard for electronic invoices. It sets the core business fields and logic, such as supplier and buyer identifiers, dates, tax categories, totals, payment details, and line-level relationships.

In a Slovakia EN 16931 invoice format context, Peppol BIS Billing is the format profile many teams are most likely to encounter because it applies those semantic rules in a specific structured XML syntax, with validation constraints that let different ERPs and AP systems interpret the same invoice consistently. If you need a broader primer, what structured e-invoicing means beyond sending a PDF explains the shift in more detail.

That is also why Slovakia Peppol e-invoicing is about both format and routing. In plain English, businesses generally do not meet the mandate by attaching XML to a normal email and hoping the other side can use it. Each party is expected to connect through a certified service provider so invoices can be transmitted, received, validated, and logged through an accredited channel.

For Slovakia certified service provider e-invoicing, the provider is not just a mailbox. In practice, businesses need to choose their provider or access-point setup, complete onboarding and addressing, and test send-and-receive flows before the 2027 deadline. That is what turns a compliant XML format into a working operational process.

For finance and ERP teams, the technical rule should translate into a short systems checklist:

• Can your billing system generate the required structured XML, not just a PDF render?
• Can your AP flow receive that XML from a certified service provider and map it into the right ERP fields?
• Can you validate EN 16931 and Peppol BIS Billing rules before posting, so rejects are caught early?
• Can you manage exceptions, such as missing identifiers, tax mismatches, or invoices that fail validation?
• Can you keep a usable audit trail showing what was sent, what was received, what was accepted or rejected, and what human-readable version staff reviewed?

If the answer to any of those questions is no, the gap is not cosmetic. It means the business is still treating invoices as files for people, while the Slovak mandate expects invoices to move as structured data between systems.

How IS EFA Fits Into Slovakia's 2027 And 2030 Roadmap

The cleanest way to read Slovakia's roadmap is as three separate stages, not one continuous rule set. That matters because a lot of older Slovakia IS EFA e-invoicing guidance still reflects the current public-sector environment, while newer compliance planning has to account for a much broader domestic mandate.

1. Stage 1: the current IS EFA and B2G context. Slovakia already has a B2G e-invoicing environment through IS EFA, which is why many older references to Slovakia eFaktura requirements sound tied to public bodies, state suppliers, or earlier implementation phases. If you have been reading advisory notes that focus mainly on government invoicing, that is not necessarily wrong. It is just describing the current baseline rather than the full domestic model now scheduled to follow.

Existing IS EFA experience is useful, but it is only a starting point. It does not automatically mean your business is ready for 2027 domestic B2B receipt, routing, ERP mapping, and reporting.

2. Stage 2: January 1, 2027, domestic B2B and B2G structured e-invoicing plus reporting. From that date, the regime becomes much broader than today's IS EFA context. The change is not only about sending structured invoices to the public sector. It extends into domestic B2B and B2G flows, with a Peppol-based exchange model and Slovakia real-time invoice reporting layered into the compliance design. In practical terms, finance teams should think beyond invoice creation alone: receiving, validating, routing, status handling, and reporting controls all become part of the operating model. The voluntary rollout planned for the second quarter of 2026 sits between legal validity and mandatory effectiveness, giving businesses a useful window to test receiving and routing processes before the hard go-live. Teams comparing regional transitions may also want to look at Latvia's phased Peppol e-invoicing rollout, because it shows how public-sector and domestic phases can be easy to confuse when dates shift across multiple reforms.

3. Stage 3: July 1, 2030, cross-border expansion. This is the next major step, when cross-border EU digital reporting expands under the wider VAT modernization agenda. It is a different milestone from the 2027 domestic launch: 2027 is about Slovakia's domestic B2B and B2G framework, while July 1, 2030 brings broader cross-border reporting alignment across the EU. B2C remains outside the mandate, so this later phase is about business transactions, not consumer sales invoicing. For the wider policy context, the European Commission's 2021 VAT Gap update says member states lost around EUR 61 billion in VAT in 2021, which helps explain the wider push toward digital reporting and e-invoicing reforms across the EU.

If you keep those three stages separate, the roadmap becomes much easier to follow: today's IS EFA and B2G environment, January 1, 2027 domestic go-live with structured invoicing and reporting, then July 1, 2030 cross-border expansion.

What Finance Teams Should Do During 2026

For most teams, the real value of a Slovakia electronic invoicing guide is turning fixed legal dates into a work plan for 2026. The priority is not just issuing compliant invoices on time. It is making sure your business can receive, validate, route, approve, store, reconcile, and report on structured invoices before the first mandatory inbound document arrives.

A practical 2026 checklist should cover five areas:

• Check system readiness early. Confirm whether your ERP, accounting platform, AP tools, archive, and middleware can ingest structured invoice data, map required fields correctly, and preserve references needed for downstream posting, approval, and audit.
• Choose your connectivity model. Decide whether you will connect through a certified provider, a Peppol access point, an ERP partner, or another supported routing setup. That choice affects onboarding, message flow, testing, support responsibility, and how quickly you can react to failed deliveries or validation errors.
• Design inbound workflow rules. Map how compliant invoices will enter the business, who validates them, what happens when mandatory fields fail checks, how exceptions are escalated, and where approvals sit once the intake channel is no longer just PDF by email.
• Prepare storage and evidence controls. Structured invoicing changes what you need to retain. Make sure you can store the invoice data, message status, validation results, routing history, and any human intervention in a way that supports audits and internal controls.
• Update reconciliation and reporting processes. Review VAT reporting, purchase reconciliation, supplier statement checks, and month-end controls so they work with structured source data rather than manual rekeying from attachments.

Receive-side readiness matters as much as issue-side readiness. If your team waits until the first compliant inbound invoice lands on January 1, 2027, you are already in reactive mode. Use the voluntary rollout opportunities expected from the second quarter of 2026 to test real invoices, real suppliers, and real handoffs between finance and IT. Those pilots usually surface the hard parts quickly: missing supplier identifiers, incomplete master data, weak tax-code mapping, approval bottlenecks, and unclear ownership when a message fails validation.

Supplier and customer onboarding also needs a plan. Update vendor communication, confirm master-data fields, document who owns connection details, and decide how you will handle counterparties that are not ready on the same timeline. If your wider compliance scope also includes retail receipts, Slovakia's eKasa receipt and QR-code requirements sit alongside this transition, but they do not replace invoice-readiness work for B2B flows.

The operational priorities are straightforward: confirm your provider model, define routing and validation rules, clean up master data, and assign reporting ownership across finance and IT. That is the work that turns legal awareness into 2027 readiness.