When does e-invoicing become mandatory in Slovakia?

On 1 January 2027, for domestic B2B and B2G supplies. Structured electronic invoicing and near-real-time reporting of invoice data both begin on that date. Calendar year 2026 is a voluntary transitional period in which both parties simply need an accredited provider. From 1 July 2030 the obligation extends to cross-border B2B supplies within the EU, the kontrolny vykaz (VAT control statement) and the suhrnny vykaz (EC Sales List) are abolished, and the period for issuing an invoice shortens from 15 days to 10. There is no turnover or size threshold and no phasing by company size.

Is a foreign company registered for Slovak VAT obliged to issue e-invoices?

Not until 2030 if it is registered only under par. 5 of the Slovak VAT Act, that is, as a person not established in Slovakia. The duty to issue falls on domestic VAT payers registered under par. 4, par. 4b or par. 4c for supplies whose place of supply is Slovakia. The Financial Administration FAQ of 26 August 2026 states expressly that the issuing provision does not apply to suppliers registered under par. 5. A foreign parent whose Slovak presence amounts to a seat, a place of business or a prevadzkaren (fixed establishment) is on the other side of that line and is caught.

Who must be able to receive an electronic invoice in Slovakia?

Every domestic legal person and every taxable person, from 1 January 2027 — including entities that are not registered for VAT at all: sole traders, farmers, landlords and non-profit organisations. The duty to receive therefore reaches a far wider population than the duty to issue. Roughly 58,000 non-profit organisations were assigned a tax identification number in June 2026 for this reason. An entity that concludes it is outside the regime because it is not a VAT payer has read only half of the rule.

Is there a penalty-free period for Slovak e-invoicing in early 2027?

No. It is drafted, not enacted. A Ministry of Finance draft amendment, LP/2026/282 of 27 May 2026, would defer the five-day buyer-side reporting duty to 1 July 2030 and introduce a penalty-free period from 1 January to 31 March 2027. As at 3 September 2026 it had not been approved, and the Financial Administration materials published in August 2026 mention no such period. It should not be built into an implementation plan.

How much are the fines for breaching the Slovak e-invoicing rules?

Up to EUR 10,000 for a first breach and up to EUR 100,000 for a repeated breach. No fine is imposed for an obvious error corrected without delay, or where the breach was caused by a technical failure on the provider side. The second relief does not operate by itself: to rely on it you must be able to show that the failure occurred and when, which means retaining records of attempts, responses and error states rather than outcomes alone.

Does Slovakia route invoices through a state clearance platform?

No. Slovakia adopted a Peppol 5-corner model. Corners one to four are the standard Peppol network — supplier, supplier access point, buyer access point, buyer — and the fifth corner is the Financial Administration, which receives a separate document, the SK Tax Data Document. The invoice itself never passes through a state system for acceptance, which is the structural difference from Poland's KSeF and from Italy's Sistema di Interscambio.

Slovak e-invoicing from 1 January 2027: who is in scope

One point of standing before anything else. The binding text is the Slovak one, published in the Zbierka zákonov. This page is a working guide for a reader who does not read Slovak; where a decision turns on the wording, read the instrument, and where this page and the Slovak text diverge, the Slovak text governs.

What exactly becomes mandatory on 1 January 2027?

The Slovak regime is known as e-faktúra — the electronic invoice — and it arrives in three steps.

Period	What applies
1 Jan – 31 Dec 2026	Voluntary transitional period. Both parties need an accredited provider; nothing else is required.
1 January 2027	Mandatory structured electronic invoicing and reporting of invoice data for domestic B2B and B2G supplies.
1 July 2030	Extension to cross-border B2B supplies within the EU. The kontrolný výkaz (VAT control statement) and the súhrnný výkaz (EC Sales List) are abolished. The period for issuing an invoice shortens from 15 days to 10.

The invoice format is XML conforming to EN 16931 — UBL 2.1 or UN/CEFACT CII — and specifically Peppol BIS Billing 3.0 with a Slovak CIUS, a national narrowing of the European core invoice. The Finančná správa (Financial Administration) announced full technical readiness on 24 August 2026 and published an updated FAQ and manual two days later, on 26 August 2026. There is no turnover or size threshold and no staged introduction by company size: every affected entity crosses on the same day.

Which entities in a group are actually caught?

This is the question a group tax function has to settle first, and in Slovakia it turns on a narrower and more mechanical test than the equivalent question in Poland.

The duty to issue falls on domestic VAT payers registered under § 4, § 4b or § 4c of the VAT Act, for supplies whose place of supply is Slovakia. A foreign entity registered for Slovak VAT only under § 5 — that is, a person not established in Slovakia — has no duty to issue until 2030. The Financial Administration's FAQ of 26 August 2026 states this in terms: the issuing provision does not concern suppliers registered for VAT in Slovakia under § 5. Registration alone therefore does not pull a foreign entity into the 2027 obligation.

The line is drawn at establishment. The Finančné riaditeľstvo SR (Financial Directorate of the Slovak Republic) frames the transitional rules by reference to a person that has in Slovakia a sídlo (seat), a place of business or a prevádzkareň (fixed establishment). A foreign parent whose Slovak footprint amounts to one of those is on the issuing side of the line from 1 January 2027, whatever the group considers the entity to be for other purposes. Two further points matter for a group:

Supplies inside a single VAT group are outside the obligation, because transactions between members of one VAT group are not subject to tax. That removes a great deal of intercompany traffic from scope — but only for entities that are actually in the group registration, which is a question of fact worth confirming rather than assuming.
§ 4c is not a voluntary category. It is the provision under which the tax administration may impose a registration on formally independent persons that are financially, economically and organisationally linked. A registration imposed under it carries the issuing duty with it, which makes it a scoping risk that sits outside the e-invoicing project entirely.

It is worth naming the contrast with the neighbouring regime this library also covers, because a group that has already done the Polish analysis will be tempted to reuse it. Poland's test under art. 106ga ust. 2 of its VAT Act asks whether a fixed establishment participates in the supply, an assessment of what local people and equipment actually do. Slovakia's test is closer to the registration provision itself. The same group, with the same operating model, can therefore land differently in the two countries, and the reasoning is not transferable. See KSeF penalties from 1 January 2027 for how the Polish version of the question is answered.

Who has to be able to receive an electronic invoice?

Here the population is much wider, and this is the single most commonly missed point in the whole regime. From 1 January 2027, every domestic legal person and every taxable person must be able to receive an electronic invoice — including entities that are not VAT payers at all: sole traders, farmers, landlords, non-profit organisations. This is why roughly 58,000 non-profit organisations were assigned a tax identification number in June 2026.

If you take one thing from this page, take this: a large number of entities that will never have to issue an electronic invoice will have to be able to receive one. For a group, that means the inventory cannot be built from the list of trading subsidiaries. Dormant companies, property-holding vehicles, a foundation, a works council entity, an SPV kept alive for a financing arrangement — each is a domestic legal person, and each needs a route by which a supplier's invoice can reach it. An entity that concludes we are not a VAT payer, this does not apply to us has read half of the rule.

What is outside the scope?

B2C supplies. The regime covers business-to-business and business-to-government invoicing.
Simplified invoices — eKasa cash-register documents up to €400, and other simplified documents up to €100.
Supplies exempt from VAT.
Classified supplies and supplies to the intelligence services.

Is there a penalty-free period in the first quarter of 2027?

It is drafted, not enacted, and should not be planned around. A draft amendment from the Ministry of Finance — LP/2026/282, of 27 May 2026 — would defer the five-day buyer-side reporting duty to 1 July 2030 and introduce a penalty-free period from 1 January to 31 March 2027. As at the position date of this page it had not been approved, it remained in the legislative process, and the Financial Administration's official materials published in August 2026 describe no such period.

This is worth stating plainly because the proposal circulates in advisory material as though it were settled law, and a group that builds a three-month buffer into its cutover plan on the strength of it will discover the error in the same month the fines begin. If a Slovak adviser or a vendor tells you the first quarter of 2027 is free of penalties, ask which instrument that comes from and whether it has been published in the Zbierka zákonov. The library's register of corrections tracks this one alongside the equivalent errors in other markets.

How large are the fines, and when are they not imposed?

Up to €10,000 for a first breach and up to €100,000 for a repeated breach. An invoice must be issued within 15 days of the tax point; from July 2030, within 10.

Two reliefs exist. No fine is imposed for an obvious error corrected without delay, and none is imposed where the breach was caused by a technical failure on the provider's side. The second is more valuable than it looks and it does not operate by itself: to rely on it, you have to be able to demonstrate that the failure occurred and when. That means retaining records of transmission attempts, responses and error states — not merely of outcomes. A system that records invoice sent on 3 March offers no defence at all. A system that records three failed attempts with error codes and timestamps offers one.

What does a group finance function have to do differently?

A Slovak filer and a group finance function in London, New York or Frankfurt face the same statute and a different problem. Six differences are worth planning around.

Scope is decided entity by entity, by registration provision. There is no group filing and no consolidated discharge. The field that decides whether an entity issues from 2027 or from 2030 is which paragraph it is registered under, and that field usually lives in a local tax file rather than in the ERP.
The receiving obligation reaches entities no one has put on the project list. It is a different test, applied to a different population, and it should be run as a separate exercise rather than as a column on the issuing inventory.
There is no state platform to tell you that you have failed. The invoice flow and the reporting flow are separate; nothing reconciles them on your behalf. Period-end controls have to compare both, which is a control design question rather than an integration question. The architecture is set out in the Peppol 5-corner model and the digitálni poštári.
Receiving has exactly one provider, per entity. The registration in the SMP is unique to a ParticipantID, so a group-wide provider decision still has to be executed once per Slovak entity, and a provider outage on the receiving side means invoices cannot reach you at all. This belongs in the business continuity plan.
The buyer-side reporting duty lands outside the billing team. When your provider receives an invoice, the data from it must be reported within five days. That is an accounts payable and procurement obligation, and it is the part of the regime most often left unowned in a cross-border implementation plan.
Evidence has to survive translation. An inspection is conducted in Slovak. A control description and audit trail that exist only in English are usable, but they will be read by someone reconstructing your process from field names they have never seen. Bilingual definitions cost little now.

There is a seventh point that is not a task but a warning. A group that has implemented Poland's KSeF, or Italy's Sistema di Interscambio, has built against a state platform that accepts, validates and returns an identifier. Slovakia has nothing of that shape, and the operating assumptions carried over from those projects — that acceptance is the compliance event, that the platform deduplicates, that an outage is a defined legal state — are all wrong here. The comparison is worked through in the companion article on the architecture, and the Polish treatment of platform outages, which has no Slovak equivalent, is in offline24, awaria and niedostępność.

What has to be ready before 31 December 2026?

Classify every Slovak entity by registration provision: § 4, § 4b, § 4c or § 5. Record the answer and the date it was reached.
Run the receiving test separately, across every domestic legal person and taxable person in the structure — including the entities that do not trade.
Appoint an accredited digitálny poštár for each entity and confirm it covers the whole scenario: sending, receiving and the reporting leg. Not every provider covers all three equally well.
Verify the SMP registration for every ParticipantID. Without it, invoices do not arrive, and you find out when they do not.
Move real traffic in the voluntary period during 2026. It is the only window in which a mistake is free.
Implement an idempotency control: a durable operation identifier assigned before the first attempt, so that a retry after a timeout cannot put a second document into circulation.
Reconcile both flows at period end — invoices issued, deliveries confirmed, reporting documents confirmed.
Retain attempts, responses and error states, not only outcomes. This is the evidence a provider-failure claim rests on.
Define approval thresholds for automated issuing, and decide which operations require a human decision before they run.

In practice

Where invoices are issued by automated processes or by AI agents rather than by a person, the question after the format question is who authorised the operation and how that is demonstrated later. BarzelVault applies policy and approval thresholds ahead of execution and issues signed audit receipts. BarzelOps runs the cross-system workflow with durable state, approval checkpoints and tenant isolation, so each Slovak entity's operations remain attributable to that entity.

How Barzel applies here

Frequently asked questions

When does the mandate start?

1 January 2027, for domestic B2B and B2G supplies. 2026 is voluntary. Cross-border EU B2B follows on 1 July 2030.

Is a foreign company with a Slovak VAT number obliged to issue?

Not if it is registered only under § 5 as a person not established in Slovakia — that duty begins in 2030. A seat, place of business or prevádzkareň in Slovakia puts the entity in scope from 2027.

Who has to be able to receive?

Every domestic legal person and every taxable person, including entities that are not VAT payers. This is much wider than the issuing population.

Is there a turnover threshold?

No. No turnover or size threshold, and no phasing by company size.

Will there be a penalty-free first quarter?

Proposed but not enacted. LP/2026/282 remained a draft as at 3 September 2026, and the August 2026 official materials describe no such period.

What are the fines?

Up to €10,000 for a first breach, up to €100,000 for a repeated breach, with reliefs for an obvious error corrected without delay and for a technical failure on the provider's side.

Where this leads

The Slovak mandate is unusually clean on its face — one date, no threshold, no phasing — and unusually easy to under-scope. The work that decides whether a group is ready is not the integration. It is the entity-by-entity classification, the separate receiving inventory, and the recognition that no state system is standing behind the process to tell you when something has gone wrong. Those three things are cheap in 2026 and expensive in 2027.

In practice

The control has to run before the invoice becomes irreversible.

An accepted structured invoice can be corrected but never deleted, and from the penalty date every defect has a price. Barzel puts the approval threshold, the duplicate check and the signed record in front of submission, so the process can be defended on the day an auditor or the tax authority asks.

94 days leftMandatory e-invoicing in Slovakia from 1 January 2027

BarzelVault

The AI action firewall: decide what an agent may do before it does it.

Approval thresholds and policy checks enforced before execution; human approvals that expire and escalate.
Cryptographically signed audit receipts: trigger, inputs, policy version, approver, outcome.
Credential isolation, spend and action limits, and an emergency kill switch.

Free tier: 10,000 calls a monthPaid plans from $199 a monthLive on MCPize

Start free Ask by email Product page Documentation

BarzelOps

Governed workflow automation across the systems that run the business.

Durable, idempotent execution: a timeout is retried once, never filed twice.
Human approval checkpoints that pause the workflow and resume it.
Isolation per entity or client, signed evidence receipts and a portable manifest; HubSpot, Xero, Gmail, Google Drive and Slack.

Free tier: 100 calls a dayPaid plans from $19 a monthLive on MCPize