Briefing document & Podcast: E-Invoicing and E-Reporting in Slovakia

Last update: June 6, 2026

Executive Summary

Slovakia is poised to introduce a mandatory structured B2B and B2G e-invoicing and near-real-time digital reporting regime, effective 1 January 2027. Enacted through Act No. 385/2025 Coll., this initiative represents a significant step in Slovakia’s tax digitalization journey, aiming to combat VAT fraud, reduce the VAT gap (historically one of the highest in the EU at ~29%), and modernize tax administration. The adopted model is a decentralized, 5-corner Peppol architecture, aligning with European standards (EN 16931, Peppol BIS 3.0, UBL 2.1) and positioning Slovakia as an early adopter within the EU, ahead of the 2030 EU-wide ViDA deadline. All domestic VAT payers, regardless of size, are in scope, facing substantial penalties for non-compliance.

Introduction & Country Context

2.1. Overview of Slovakia’s Tax Digitalization Journey Slovakia has progressively digitalized its tax system, having introduced transaction-level VAT reporting via the VAT Control Statement, retail fiscalization through eKasa, and an existing B2G e-invoicing framework (IS EFA) since 2022-2023 for public procurement invoices over €5,000. The upcoming mandate builds on these foundations.

2.2. Rationale Behind the Mandate The reform is primarily driven by “reducing the VAT gap” – which in Slovakia has historically been approximately 29%, equivalent to EUR 2.3 billion, according to PwC Slovakia. Other key objectives include “combating VAT fraud and evasion, reducing the administrative burden on businesses, standardizing invoice data for automation, and modernizing tax administration in line with EU digital developments.” [pwc.com], [vatupdate.com]

2.3. Position Within the Broader Regional and International Landscape Slovakia is an early adopter within the EU, implementing its regime well ahead of the EU-wide mandatory cross-border ViDA date of 1 July 2030. The system utilizes a “decentralized interoperability model based on the Peppol network and certified delivery service providers,” differing from centralized pre-clearance models like Italy’s SDI. It aligns with internationally recognized standards such as EN 16931, Peppol BIS 3.0, and UBL 2.1. [vatupdate.com], [marosavat.com]

2.4. Supranational Authorization or Derogation The legal basis for this mandate is primarily Act No. 385/2025 Coll., which transposes Article 1 and Article 5 of Council Directive (EU) 2025/516 (ViDA). This Directive itself provides the legal basis for Member States to mandate structured e-invoicing without requiring buyer consent, removing the previous Article 232 consent requirement. [forvismazars.com]

Regulatory Framework

3.1. Primary Legislation The central legislative instrument is Act No. 385/2025 Coll., an amendment to the core Slovak VAT Act (Act No. 222/2004 Coll.), published on 19 December 2025. It introduces mandatory e-invoicing and digital reporting. The existing B2G framework under Act No. 215/2019 Coll. will transition to the new Peppol-based solution by 2027. [forvismazars.com], [e-invoice.app]

3.2. Implementing Regulations, Decrees & Orders Implementation details are distributed across the law, Financial Administration guidance, Slovak Peppol materials, and technical specifications. Key documents include:

Informácia č. 1/DPH/2026/I (Financial Administration guidance, 14 Jan 2026) [kpmg.com]
SK Solution Architecture document v1.2 (19 March 2026) [financnasprava.sk]
Peppol BIS transposition rules v1.9 (2 June 2026) [e-invoice.app]
Accreditation Scheme for Service Providers [financnasprava.sk]

3.3. Circulars, Official Guidance, Administrative Rulings & FAQs The Financial Administration FAQ (eFaktúra FAQ), regularly updated (latest major update May 2026), is the “most comprehensive official guidance on the scope and technical requirements.” [sovos.com] A significant pending development is the 27 May 2026 Ministry of Finance proposal to remove the buyer-side reporting obligation for the interim period (2027–2030), though this is not yet final law. [vatupdate.com]

Scope of the Mandate

4.1. Transactions in Scope (Mandatory from 1 January 2027)

Domestic B2B: Mandatory for supplies where the issuer is a domestic VAT payer and the customer is a domestic taxable person or non-taxable legal person. “Standard paper/PDF invoices will no longer satisfy the legal definition of a compliant invoice for in-scope transactions.” [invoice-portal.de]
Domestic B2G: Already mandatory under Act No. 215/2019 Coll., transitioning to the new Peppol-based solution by 2027.
Self-billing: Explicitly in scope and must be reported to the Financial Administration no later than 5 days from issuance. A written agreement between parties is required. [forvismazars.com]

4.2. Excluded or Exempt Transactions (from 1 January 2027)

Domestic B2C: Covered primarily by the eKasa system. [invoice-portal.de]
Cross-border B2B (intra-EU and exports): Not in scope for 2027, but will be mandatory from 1 July 2030 (aligned with ViDA). [marosavat.com]
VAT-exempt supplies under §§ 28 to 43 and § 47 of the VAT Act (e.g., insurance, financial services, healthcare).
Simplified invoices under § 74 of the VAT Act.
Classified/security-related supplies.
Supplies by foreign taxable persons registered for VAT under § 5 (without a fixed establishment in Slovakia) are excluded from the issuance obligation until 30 June 2030. [snitechnology.net]
Transactions where the place of supply is outside Slovakia.
Summary electronic invoices for utilities (electricity, gas, water, heat) are abolished from 1 January 2027, as EN 16931 does not permit such arrangements. [forvismazars.com]

4.3. Taxable Persons in Scope

Established Domestic Entities: The obligation to issue e-invoices applies to all domestic VAT payers established in Slovakia. The obligation to receive e-invoices extends broadly to all domestic taxable persons (including non-VAT payers who are taxable persons or legal entities) and non-taxable legal persons. [marosavat.com], [forvismazars.com]
Non-Established Entities: Foreign entities with a fixed establishment in Slovakia are in scope. Foreign entities registered for VAT under § 5 (without a fixed establishment) are temporarily excluded from the issuance obligation until 30 June 2030. [kpmg.com]

Implementation Timeline

5.1. Key Dates

11 March 2025: ViDA Package (Directive (EU) 2025/516) published. [e-invoice.app]
19 December 2025: Act No. 385/2025 Coll. published. [forvismazars.com]
1 January 2026: Law enters into force; voluntary preparation and testing period begins.
May/June 2026: Voluntary use of the eFaktúra system opens for live exchange of valid XML e-invoices. [kpmg.com]
1 January 2027: Mandatory B2B and B2G e-invoicing and digital reporting for all domestic transactions. “No phase-in by company size or turnover threshold — the mandate applies to all in-scope taxpayers simultaneously.” [invoice-portal.de]
1 July 2030: Mandatory extension to cross-border intra-EU B2B transactions; invoice issuance deadline reduced to 10 days; elimination of VAT Control Statement and EC Sales List. [forvismazars.com]

5.2. Grace Periods & Transitional Provisions

2026 serves as the voluntary testing/transitional year. During this period, recipient consent is still required.
From 1 January 2027, recipient consent is no longer required.
No general post-1 January 2027 penalty-free grace period has been identified. However, penalties are not imposed if an obvious error is corrected promptly or if a technical failure of the contracted Digital Postman caused the delay. [e-invoice.app]
No official postponement of the 1 January 2027 go-live has been announced. [vatupdate.com]

How E-Invoicing & E-Reporting Work — The Operating Model

6.1. Overview of the Operating Model Slovakia has adopted a Decentralized / Interoperability Model using a 5-corner Peppol architecture:

Corner 1: Sender (supplier).
Corner 2: Sender’s Digital Postman (certified Peppol Access Point).
Corner 3: Receiver’s Digital Postman (certified Peppol Access Point).
Corner 4: Receiver (buyer).
Corner 5: Financial Administration (tax authority), receiving the Tax Data Document (TDD) for each invoice.

Crucially, this is not a centralized clearance (CTC) model. “There is no pre-clearance requirement. Invoices do not need government approval before they are issued.” The tax authority receives reporting data (SK TDD) in near-real-time without blocking the invoice flow. [e-invoice.app], [marosavat.com]

6.2. Step-by-Step Invoice Lifecycle

Invoice Creation: Seller’s ERP generates structured XML e-invoice (EN 16931, UBL 2.1 or CII).
Submission: Transmitted to seller’s Digital Postman.
Validation: Digital Postman performs syntax, schema, and business-rule validation.
Reporting (no clearance): Digital Postman generates and transmits a Tax Data Document (SK TDD) to the Financial Administration’s Access Point (C5) at or near the time of invoice issuance.
Delivery to Buyer: E-invoice transmitted across Peppol network to buyer’s Digital Postman. “The supplier’s legal duty is met upon proper issuance and sending via the delivery service, even if the buyer fails to connect.” [marosavat.com]
Retrieval by Buyer: Buyer retrieves e-invoice.
Buyer Reporting: Buyer’s Digital Postman reports received invoice data to FA within 5 calendar days of receipt (subject to pending MoF proposal).
Archiving: Taxpayers must archive e-invoices in original structured XML.

6.3. Buyer-Side Workflow Buyers must be technically capable of receiving structured e-invoices through a contracted Digital Postman. “Buyer acceptance is not required for the invoice’s legal validity.” Invoice rejection by the recipient must be handled bilaterally. [marosavat.com]

6.4. Accredited Service Providers / Certified Intermediaries Use of accredited providers (Digital Postmen) is effectively mandatory. These providers must have valid OpenPeppol certification, a legal personality in an EU Member State, and complete Slovak-specific onboarding tests. The Financial Administration publishes and updates a list of certified Digital Postmen. [marosavat.com], [financnasprava.sk]

Technical & Functional Requirements

7.1. Mandatory Format(s) The legally required format is a structured XML file compliant with the European standard EN 16931, in either UBL 2.1 or UN/CEFACT CII (D16B) syntax. “Unstructured formats are explicitly not accepted as valid e-invoices for in-scope transactions: PDF invoices, scanned documents, images, Word documents, Excel files, and EDIFACT files do not qualify.” [marosavat.com]

7.2. E-Invoice Specifications

Mandatory Data Fields: Must contain all data elements required by EN 16931 and Slovak VAT law, including seller/buyer identification, tax identification numbers (DIČ and IČ DPH), Peppol participant identifiers (scheme ID 0245:XXXXXXXXXX).
Data Validation Rules: Performed by the Digital Postman against EN 16931 schema rules, Peppol BIS business rules, and Slovak CIUS national validation rules (latest v1.9). [financnasprava.sk]

7.3. E-Reporting Specifications

Format: The SK TDD (Slovak Republic Tax Data Document), a structured data message generated by the Digital Postman for each invoice.
Filing frequency: Near-real-time for supplier-side reporting (at invoice issuance). Buyer-side reporting within 5 calendar days of receipt (pending MoF proposal). [marosavat.com]

7.4. Digital Signature & Integrity Requirements No per-invoice qualified electronic signature is required. Integrity and authenticity are ensured via the structured data format and controlled delivery/reporting through the certified Peppol network. [vatupdate.com]

Correction of Errors & Archiving

8.1. E-Invoice Corrections “Direct modification of a transmitted e-invoice is not possible.” Errors discovered post-transmission must be corrected through formal credit notes (corrective invoices) and, where necessary, a new corrected invoice. Invoice rejection by the recipient is handled bilaterally. [marosavat.com]

8.2. Archiving & Retention E-invoices must be archived in their original structured electronic XML format for a general retention period of 10 years (20 years for immovable property). Conversion to other formats (e.g., PDF) is not sufficient. Tax authorities must be granted immediate and free access to archived invoices upon request. [snitechnology.net], [basware.com]

Penalties & Enforcement

No general post-1 January 2027 penalty-free grace period.
Penalties can be up to EUR 10,000 per infraction for failure to report, late reporting, incomplete reporting, or incorrect data.
Up to EUR 100,000 for repeated violations. [forvismazars.com]
Penalties are fixed monetary fines, escalated by seriousness and repetition.
Mitigating factors include prompt correction of obvious errors or technical malfunction of the contracted Digital Postman.

Readiness for VAT in the Digital Age (ViDA)

Slovakia is “ahead of the minimum EU ViDA timetable” by implementing its domestic mandate by 1 January 2027, well before the EU’s 1 July 2030 cross-border ViDA deadline. The national system’s reliance on EN 16931, Peppol BIS 3.0, and UBL 2.1 makes it “broadly future-proof and compatible with future ViDA obligations.” Businesses complying with the 2027 mandate are building infrastructure that will align with future ViDA requirements, though additional adjustments will likely be needed for the 2030 cross-border phase. [vatupdate.com]

Impact on SMEs and Startups

No formal phase-in by company size or turnover has been legislated; all in-scope VAT-registered taxpayers must comply from 1 January 2027. [vatupdate.com]
Government support includes the Financial Administration’s eFaktúra portal, FAQs, webinars, and demo tools. Free third-party tools are also available.
Compliance costs for basic Digital Postman services are estimated at EUR 5 to 12 per month, with transaction fees of EUR 0.05 to 0.50 per invoice. No government subsidies have been identified. [forvismazars.com]
While there is an “initial compliance burden,” the long-term policy aims for “simplification and automation.” [vatupdate.com]

Key Takeaways & Critical Dates

Mandatory Domestic E-Invoicing & Digital Reporting: Applies to all B2B and B2G transactions involving domestic VAT payers from 1 January 2027.
Technology: Decentralized 5-corner Peppol model, using structured XML (EN 16931, UBL 2.1/CII) via certified Digital Postmen.
No Pre-Clearance: The tax authority receives a “Tax Data Document (SK TDD)” in near-real-time without blocking invoice flow.
Penalties: Significant fines (up to EUR 10,000 per infraction, EUR 100,000 for repeated violations) underscore the importance of compliance.
ViDA Readiness: Slovakia’s system is highly aligned with future EU ViDA requirements, making the investment largely future-proof.
No Phase-in by Size: All in-scope businesses must be ready from Day 1.

Recommended Immediate Next Steps for Businesses (as of June 2026):

Map All Invoicing Flows: Identify domestic B2B and B2G transactions in scope.
ERP/Accounting System Readiness: Confirm capabilities for EN 16931 XML generation.
Select & Contract Digital Postman: Choose a certified delivery service provider.
Begin Testing: Utilize the voluntary phase (May/June 2026 onwards) for testing.
Monitor Updates: Closely track the Financial Administration’s eFaktúra portal and official FAQs, particularly regarding the pending MoF proposal on buyer-side reporting.

Disclaimer: This briefing is based on publicly available sources as of June 6, 2026. Businesses should consult local specialist counsel for company-specific implementation advice and regularly monitor official channels for the latest updates.

INDEPTH ANALYSIS

Introduction & Country Context

1.1. Overview of Slovakia’s Tax Digitalization Journey

Slovakia’s path toward tax digitalization has evolved through several stages: the introduction of transaction-level VAT reporting via the VAT Control Statement (kontrolný výkaz), retail fiscalization through the eKasa system, and the existing B2G e-invoicing framework under the Information System for Electronic Invoicing (IS EFA), operational since 2022–2023 for public procurement invoices exceeding €5,000. The current programme represents the next logical step — mandatory structured B2B and B2G e-invoicing and near-real-time digital reporting to the Financial Administration, effective 1 January 2027, enacted through Act No. 385/2025 Coll. amending the VAT Act (Act No. 222/2004 Coll.). [vatupdate.com] [invoice-portal.de], [forvismazars.com]

1.2. Rationale Behind the Mandate

The reform is driven by several core objectives: reducing the VAT gap (Slovakia has historically had one of the highest VAT gaps in the EU — approximately 29%, equivalent to EUR 2.3 billion, according to PwC Slovakia), combating VAT fraud and evasion, reducing the administrative burden on businesses, standardizing invoice data for automation, and modernizing tax administration in line with EU digital developments. The Ministry of Finance has further linked the initiative to “stronger risk detection, better control of VAT leakage, and a more predictable and fairer VAT system.” [pwc.com], [vatupdate.com] [vatupdate.com]

1.3. Position Within the Broader Regional and International Landscape

Slovakia is positioned as an early adopter within the EU. It is implementing its domestic e-invoicing and e-reporting regime ahead of the EU-wide mandatory cross-border ViDA date of 1 July 2030. The adopted model is a decentralized interoperability model based on the Peppol network and certified delivery service providers, differing from centralized pre-clearance models such as Italy’s SDI. The system aligns with EN 16931, Peppol BIS 3.0, and UBL 2.1 standards, reflecting a growing international consensus among countries such as France, Germany, and Romania that are also adopting Peppol-based architectures. [vatupdate.com] [marosavat.com]

1.4. Supranational Authorization or Derogation

The primary aim of Act No. 385/2025 is the transposition of Article 1 and Article 5 of Council Directive (EU) 2025/516 of 11 March 2025, which amends Directive 2006/112/EC as regards VAT rules for the digital age (ViDA). The existing B2G framework was aligned with Directive 2014/55/EU. No separate EU Council Implementing Decision or special derogation was required because the ViDA Directive itself provides the legal basis for Member States to mandate structured e-invoicing without requiring buyer consent (removal of the Article 232 consent requirement). No WTO notification or other non-EU supranational legal basis has been identified in public materials. [forvismazars.com] [vatupdate.com] [vatupdate.com]

Regulatory Framework

2.1. Primary Legislation

Act No. 222/2004 Coll. on Value Added Tax (VAT Act) — the core Slovak VAT law, as amended. [financnasprava.sk]
Act No. 385/2025 Coll. — the amendment to the VAT Act introducing mandatory e-invoicing and digital reporting, published in the Collection of Laws of the Slovak Republic on 19 December 2025, following parliamentary approval on 9 December 2025. This is the central legislative instrument for the B2B/B2G e-invoicing mandate. [forvismazars.com], [e-invoice.app]
Act No. 215/2019 Coll. — governing the existing B2G e-invoicing framework (IS EFA), effective from 1 August 2019. This framework is being transitioned to the new Peppol-based solution by 2027. [ec.europa.eu], [vatupdate.com]

2.2. Implementing Regulations, Decrees & Orders

Slovakia has not enacted a single consolidated implementing decree. Instead, implementation details are distributed across the law itself, Financial Administration guidance, Slovak Peppol materials, and technical specifications: [vatupdate.com]

Informácia č. 1/DPH/2026/I (issued 14 January 2026) — Financial Administration guidance on structured invoice formats, certified delivery services, reporting deadlines, exceptions, and penalties. [kpmg.com]
SK Solution Architecture document v1.2 (published 19 March 2026) — defining the technical architecture of Slovakia’s Peppol-based e-invoicing system. [financnasprava.sk]
Peppol BIS transposition rules v1.8 (published April 2026) — specifying the Slovak validation rules for Peppol BIS. Latest version v1.9 was published on 2 June 2026. [e-invoice.app], [financnasprava.sk]
Accreditation Scheme for Service Providers — published by the Financial Administration, specifying requirements for Digital Postmen certification. [financnasprava.sk]
Slovakia – Peppol Authority Specific Requirements — published by the Financial Administration as the Slovak Peppol Authority. [financnasprava.sk]

2.3. Circulars, Official Guidance, Administrative Rulings & FAQs

Financial Administration FAQ (eFaktúra FAQ) — published and regularly updated (initial version March 2026; latest major update May 2026 adding 29 new Q&As — 8 for taxpayers and 21 for ERP vendors/service providers). This represents the most comprehensive official guidance on the scope and technical requirements of Slovakia’s e-invoicing framework. [sovos.com], [snitechnology.net]
Webinars and presentations — the Financial Administration has conducted multiple public webinars (29 October 2025, 26 November 2025, 10 December 2025, 17 December 2025, 5 March 2026) with recordings publicly available. [financnasprava.sk]
27 May 2026 Ministry of Finance proposal — a significant pending development proposing to remove the buyer-side reporting obligation for the interim period (2027–2030). This is not yet final law. [vatupdate.com]

2.4. Supranational / International Legal Basis

EU Directive 2014/55/EU — for B2G/public procurement e-invoicing. [vatupdate.com]
EU Directive (EU) 2025/516 (ViDA) — for the ViDA-related VAT changes transposed by Act No. 385/2025. [forvismazars.com], [e-invoice.app]
EN 16931 plus the syntax list under Commission Implementing Decision (EU) 2017/1870 — for structured e-invoice standards. [vatupdate.com], [snitechnology.net]

Scope of the Mandate

3.1. Transactions in Scope

Domestic B2B: Mandatory from 1 January 2027 for supplies where the issuer is a domestic VAT payer and the customer is a domestic taxable person or non-taxable legal person. Standard paper/PDF invoices will no longer satisfy the legal definition of a compliant invoice for in-scope transactions. [invoice-portal.de], [forvismazars.com]
Domestic B2G: Already mandatory under Act No. 215/2019 Coll. via the IS EFA system; transitioning to the new Peppol-based national solution by 2027. Public entities must accept and process e-invoices; public contracts must include procurement reference numbers. [ec.europa.eu], [snitechnology.net]
Domestic B2C: Explicitly excluded from the mandate. B2C transactions are covered primarily by the eKasa retail fiscalization system. [invoice-portal.de], [vatupdate.com]
Cross-border B2B (intra-EU): Not in scope for the 2027 mandate. The obligation will extend to cross-border intra-EU transactions from 1 July 2030, aligned with ViDA. [marosavat.com], [forvismazars.com]
Cross-border B2B (exports outside the EU): Not in scope for 2027. [vatupdate.com]
Intra-community acquisitions: Not part of the mandatory 2027 system; planned for the broader 2030 phase. [vatupdate.com]

3.2. Special Transactions in Scope

Self-billing: Explicitly in scope. Where a customer issues an invoice on behalf of and for the account of the supplier, the data must be reported to the Financial Administration no later than 5 days from the date the electronic invoice is issued, or from the expiry of the deadline for issuing the electronic invoice. A written agreement between parties is required. Self-billing is included among documents exchanged via the eFaktúra system. [forvismazars.com], [e-invoice.app], [financnasprava.sk]
Triangulation and chain transactions: Detailed public operational rules for these scenarios are not yet available. The law does not explicitly exclude them, but specific guidance is pending. [vatupdate.com]
Special VAT regimes (margin schemes, flat-rate farmers, etc.): No detailed public guidance has been published on the treatment of these special regimes under the e-invoicing mandate. [vatupdate.com]

3.3. Excluded or Exempt Transactions

The following are explicitly excluded from the e-invoicing obligation from 1 January 2027: [forvismazars.com], [vatupdate.com]

B2C transactions — supplies to final consumers (private individuals).
VAT-exempt supplies under §§ 28 to 43 and § 47 of the VAT Act (e.g., insurance, financial services, healthcare, education).
Simplified invoices under § 74 of the VAT Act.
Classified/security-related supplies — supplies where the recipient is the Slovak Information Service (Slovenská informačná služba) or Military Intelligence (Vojenské spravodajstvo), or where the supply involves classified information.
Supplies by foreign taxable persons registered for VAT under § 5 of the VAT Act (i.e., foreign entities registered for VAT in Slovakia without a fixed establishment) — excluded until 30 June 2030.
Transactions where the place of supply is outside Slovakia.
Summary electronic invoices in the form of payment agreements for electricity, gas, water, or heat are abolished from 1 January 2027, as the EN 16931 standard does not permit such arrangements. [forvismazars.com]

Taxable Persons in Scope

4.1. Established Domestic Entities

The obligation to issue e-invoices applies to all domestic VAT payers — registered pursuant to § 4, § 4b, and § 4c of the VAT Act — who have their registered seat, place of business, or fixed establishment in Slovakia. This includes corporations, partnerships, sole traders, liberal professionals (lawyers, notaries, architects, artists), self-employed farmers, and landlords. [marosavat.com], [forvismazars.com]

The obligation to receive e-invoices extends broadly to all domestic taxable persons (including non-VAT payers who are taxable persons or legal entities) and non-taxable legal persons. [deloitte.com], [kpmg.com]

4.2. Non-Established Entities

Foreign entities with a fixed establishment in Slovakia: In scope from 1 January 2027 — they must issue and receive e-invoices. [kpmg.com], [invoice-portal.de]
Foreign entities registered for VAT under § 5 (without a fixed establishment): Temporarily excluded from the issuance obligation until 30 June 2030. The updated FAQ confirms that § 5-registered persons are not obliged to receive e-invoices via service providers during the 2027–2030 phase-in period. [snitechnology.net], [sovos.com]
Foreign entities without Slovak VAT registration: Outside the scope of the mandate entirely.

4.3. Voluntary Participation

2026 is a voluntary preparation and testing year. From May/June 2026, businesses can voluntarily issue and exchange e-invoices through the Peppol network. E-invoices issued during this phase are treated as valid tax documents. Non-VAT payers have no legal obligation to issue e-invoices even if they voluntarily join the Peppol network. [marosavat.com], [financnasprava.sk] [snitechnology.net], [europe.tho…euters.com]

4.4. Sector-Specific Rules & Exemptions

No general sector-by-sector exemption matrix has been identified. The scope is driven by VAT status, establishment status, domestic vs. cross-border nature, and whether the transaction is exempt, simplified, B2C, or security-sensitive. [vatupdate.com]

Implementation Timeline

5.1. Legislative History

1 June 2022: B2G e-invoicing phase began for selected B2G transactions exceeding €5,000 via IS EFA. [cleartax.com]
31 January 2025: Public consultation launched on new e-invoicing rules. [cleartax.com]
11 March 2025: ViDA Package (Directive (EU) 2025/516) published in the EU Official Journal. [e-invoice.app]
9 December 2025: Slovak National Council approved Act No. 385/2025 Coll. [vatupdate.com], [forvismazars.com]
19 December 2025: Act No. 385/2025 Coll. published in the Collection of Laws of the Slovak Republic. [forvismazars.com]
1 January 2026: Law enters into force; legal basis for delivery service framework and provider accreditation becomes effective. [e-invoice.app]

5.2. Voluntary or Pilot Phases

January 2026 onwards: Voluntary preparation and testing period begins. The Financial Administration published Access Point accreditation requirements on 14 January 2026. [e-invoice.app]
May/June 2026: Voluntary use of the eFaktúra system opens for live exchange of valid XML e-invoices. [kpmg.com], [marosavat.com]
Q3 2026 (September): Projected availability of digital reporting through the tax authority’s corner 5 system. [e-invoice.app]
No formal incentives such as faster VAT refunds or reduced audit risk have been identified for voluntary participants. [vatupdate.com]

5.3. Mandatory Go-Live Dates

1 January 2027: Mandatory B2B and B2G e-invoicing and digital reporting for all domestic transactions involving domestic VAT payers. No phase-in by company size or turnover threshold — the mandate applies to all in-scope taxpayers simultaneously. [invoice-portal.de], [forvismazars.com]
1 July 2030: Mandatory extension to cross-border intra-EU B2B transactions; invoice issuance deadline reduced to 10 days; elimination of VAT Control Statement (kontrolný výkaz) and EC Sales List (súhrnný výkaz). [forvismazars.com], [marosavat.com]

5.4. Grace Periods & Transitional Provisions

2026 serves as the voluntary testing/transitional year. During this period, the recipient’s consent to receive an e-invoice is still required (unless the recipient is already connected to the Peppol delivery system). [forvismazars.com]
From 1 January 2027, consent is no longer required; the issuance and sending of an electronic invoice does not require the consent of the recipient. [forvismazars.com]
No general post-1 January 2027 penalty-free grace period has been identified. However, no penalty is imposed if an obvious error is corrected promptly or if a technical failure of the contracted Digital Postman caused the delay. [e-invoice.app], [forvismazars.com]

5.5. Pre-Mandate Milestones

14 January 2026: Accreditation requirements published. [e-invoice.app]
March 2026: First list of certified Digital Postmen published; first list of providers in accreditation process published; expanded FAQ guidance published; SK Solution Architecture v1.2 published. [e-invoice.app], [financnasprava.sk]
April 2026: Peppol BIS transposition rules v1.8 published. [e-invoice.app]
May 2026: Updated lists of certified and accrediting providers published. As of 26 May 2026: 30 accredited providers and 20 in process. [vatupdate.com]
June 2026: Transposition rules v1.9 published (2 June 2026). [financnasprava.sk]

5.6. Known or Anticipated Postponements

No official postponement of the 1 January 2027 domestic go-live has been announced or publicly discussed. [vatupdate.com]

How E-Invoicing & E-Reporting Really Work — The Operating Model

6.1. Overview of the Operating Model

Slovakia has adopted a Decentralized / Interoperability Model using a 5-corner Peppol architecture: [e-invoice.app], [marosavat.com]

Corner 1: Sender (supplier).
Corner 2: Sender’s Digital Postman (certified Peppol Access Point).
Corner 3: Receiver’s Digital Postman (certified Peppol Access Point).
Corner 4: Receiver (buyer).
Corner 5: Financial Administration (tax authority), receiving the Tax Data Document (TDD) for each invoice.

This is not a centralized clearance (CTC) model — there is no pre-clearance requirement. Invoices do not need government approval before they are issued. The tax authority sits at corner 5 to receive reporting data, providing visibility into transactions without blocking the invoice flow. [e-invoice.app], [marosavat.com]

6.2. Step-by-Step Invoice Lifecycle

Step 1 — Invoice Creation: Seller’s ERP or accounting system generates a structured XML e-invoice compliant with EN 16931 in UBL 2.1 or CII syntax. [marosavat.com]
Step 2 — Submission: The e-invoice is transmitted to the seller’s Digital Postman (certified delivery service provider) via API, web application, or mobile application. [financnasprava.sk], [forvismazars.com]
Step 3 — Validation: The Digital Postman performs syntax, schema, and business-rule validation. If validation fails, the system flags format or data errors for correction before sending. [marosavat.com]
Step 4 — Reporting (no clearance): The Digital Postman generates a Tax Data Document (SK TDD) and transmits it to the Financial Administration’s Access Point (C5). This occurs at or near the time of invoice issuance. No unique fiscal validation code or government stamp is assigned. [marosavat.com], [vatupdate.com]
Step 5 — Delivery to Buyer: The e-invoice is transmitted across the Peppol network to the buyer’s Digital Postman. The supplier’s legal duty is met upon proper issuance and sending via the delivery service, even if the buyer fails to connect. [marosavat.com], [vatupdate.com]
Step 6 — Retrieval by Buyer: The buyer retrieves the e-invoice via their Digital Postman’s software, web portal, or mobile application. [financnasprava.sk]
Step 7 — Buyer Reporting: The buyer’s Digital Postman reports the received invoice data to the Financial Administration within 5 calendar days of receipt (subject to the pending MoF proposal to remove this obligation for 2027–2030). [marosavat.com], [vatupdate.com]
Step 8 — Archiving: Taxpayers must archive e-invoices in their original structured XML format for the statutory retention period. [snitechnology.net]

6.3. Authentication & Access Methods

Provider onboarding via Peppol and Slovak accreditation process. [financnasprava.sk]
Provider operation through accounting/ERP software integration, web applications, and mobile applications. [forvismazars.com]
PKI/AP test certificates for provider testbed access. [vatupdate.com]
The participant identifier on the Peppol network uses the scheme ID 0245:XXXXXXXXXX, where the ten-digit number is the Slovak Tax Identification Number (DIČ). [marosavat.com]
For third-party authorization, the Financial Administration publishes a Letter of Authorization template. Providers must obtain user authorization through a Financial Administration application. [financnasprava.sk]

6.4. Offline / Contingency Mode

A comprehensive taxpayer-facing contingency manual has not yet been publicly provided. However, the law provides that no penalty is imposed if the taxpayer fails to report data within the statutory deadline due to a proven technical malfunction on the part of the certified delivery service provider, provided the taxpayer reports the data immediately after the malfunction is remedied. [forvismazars.com], [e-invoice.app]

6.5. Buyer-Side Workflow

Buyers must be technically capable of receiving structured e-invoices through a contracted Digital Postman. Buyer acceptance is not required for the invoice’s legal validity — the invoice is legally deemed issued once the supplier sends it through the delivery service. Invoice rejection by the recipient must be handled bilaterally between supplier and buyer; it is not possible to reject an invoice through the Peppol network itself. [marosavat.com], [vatupdate.com]

6.6. QR Code or Verification Code Requirements

No mandatory QR code or specific verification code on B2B/B2G e-invoices has been identified in the current framework. [vatupdate.com]

Acceptable E-Invoice Formats — Mandatory & Voluntary

7.1. Mandatory Format(s)

The legally required e-invoice format is a structured XML file compliant with the European standard EN 16931, in either UBL 2.1 or UN/CEFACT CII (D16B) syntax. UBL 2.1 is the practical default for transmission via the Peppol network. [marosavat.com], [e-invoice.app]

Unstructured formats are explicitly not accepted as valid e-invoices for in-scope transactions: PDF invoices, scanned documents, images, Word documents, Excel files, and EDIFACT files do not qualify. [marosavat.com], [invoice-portal.de]

7.2. Relationship to International / Regional Standards

EN 16931: Full alignment — the Slovak e-invoice must comply with the EN 16931 semantic standard. [ec.europa.eu]
Peppol BIS 3.0: Slovakia will use a CIUS (Core Invoice Usage Specification) within the scope of Peppol BIS 3 format after January 2027, compliant with EN 16931 semantics. [ec.europa.eu], [ec.europa.eu]
UBL 2.1 / UN/CEFACT CII: Both syntaxes are accepted. [e-invoice.app]
National extensions: The SK TDD (Slovak Republic Tax Data Document) is a national specification for tax reporting data transmitted to the Financial Administration. [vatupdate.com], [marosavat.com]
EDIFACT: Not sufficient on its own. Businesses using EDI systems such as EDIFACT must convert their invoicing data into an EN 16931-compliant structured format. [snitechnology.net], [europe.tho…euters.com]

7.3. Voluntary / Legacy / Transitional Formats

During the 2026 voluntary phase, businesses can still use legacy invoicing methods alongside testing of the new system.
For transactions outside the mandate scope (B2C, cross-border, exempt transactions), traditional invoicing methods (including PDF and paper) remain legally valid. [invoice-portal.de]
No dual-format or hybrid format options (such as Factur-X/ZUGFeRD) are referenced in the Slovak framework.

7.4. Attachments

Detailed public policy on attachments within the e-invoice format has not yet been published. The Peppol BIS standard generally allows for embedded binary objects (e.g., PDF attachments), but specific Slovak rules on permitted attachment types and their legal status are pending clarification. [vatupdate.com]

Technical & Functional Requirements

8.1. E-Invoice Specifications

Mandatory Data Fields: The e-invoice must contain all data elements required by the EN 16931 standard and Slovak VAT law, including: seller/buyer identification, tax identification numbers (DIČ and IČ DPH), invoice number, issue date, line item descriptions, quantities, unit prices, net/gross amounts, VAT rates and amounts, payment terms, delivery details, and Peppol participant identifiers (scheme ID 0245). [marosavat.com], [snitechnology.net]
Public procurement invoices must include procurement reference numbers. [snitechnology.net]
Simplified invoices under § 74 of the VAT Act are limited to transactions under €100 or e-kasa receipts up to €400, but these are excluded from the e-invoicing mandate. [snitechnology.net]
Data Validation Rules: Validation is performed by the Digital Postman against EN 16931 schema rules, Peppol BIS business rules, and Slovak CIUS national validation rules. The latest version (v1.9) of the Slovak transposition rules is published on the Financial Administration’s portal. [financnasprava.sk]

8.2. E-Reporting Specifications

Format: The SK TDD (Slovak Republic Tax Data Document) — a structured data message generated by the Digital Postman for each invoice. [vatupdate.com], [marosavat.com]
Filing frequency: Near-real-time. Supplier-side reporting occurs at the time of invoice issuance. Buyer-side reporting must occur within 5 calendar days of receipt (pending the MoF proposal to remove this obligation for 2027–2030). [marosavat.com], [vatupdate.com]
From 1 July 2030: The VAT Control Statement (kontrolný výkaz) and EC Sales List (súhrnný výkaz) are expected to be abolished and replaced by automated reporting through the e-invoicing system. [forvismazars.com], [marosavat.com]

8.3. Digital Signature & Integrity Requirements

No per-invoice qualified electronic signature is required. Integrity and authenticity are ensured via the structured data format and the controlled delivery/reporting through the certified Peppol network. [vatupdate.com]

8.4. Real-Time or Near-Real-Time Processing

The system is designed for near-real-time exchange and reporting. There is no batch reporting model — the SK TDD is transmitted to the tax authority at or near the time of invoice issuance. [vatupdate.com], [globalindi…gement.com]

Correction of Errors in E-Invoices and E-Reporting

9.1. E-Invoice Corrections

Pre-transmission errors: Caught by the Digital Postman during validation. The system flags format or data errors for correction before sending. [marosavat.com]
Post-transmission corrections: Direct modification of a transmitted e-invoice is not possible. Errors discovered after successful sending must be corrected through formal credit notes (corrective invoices) and, where necessary, a new corrected invoice. Document type 384 (corrective invoice) is confirmed for inclusion in the autumn 2026 Peppol BIS release. [marosavat.com], [sovos.com]
Invoice rejection by recipient: Handled bilaterally between supplier and buyer — it is not possible to reject an invoice through the Peppol network itself. If the recipient identifies an error (e.g., wrong amount), they should contact the supplier and request a corrective document or credit note. [marosavat.com], [europe.tho…euters.com]
Suspected fraudulent invoices should be reported to the tax administration. [snitechnology.net]

9.2. E-Reporting Corrections

The Tax Office will not impose a penalty if the taxpayer corrects incorrectly reported data and it is evident that the incorrect information was provided due to an obvious mistake. [forvismazars.com]
Specific procedures, forms, or timelines for formal corrections of e-reporting files have not been detailed in the currently available public guidance beyond the general penalty exemption for prompt corrections.

Transmission & Workflow

10.1. Central Platform

There is no central government clearance platform in the traditional sense. The Financial Administration of the Slovak Republic (Finančná správa) operates as the Slovak Peppol Authority and as Corner 5 of the 5-corner model, receiving SK TDD reporting data. [e-invoice.app], [marosavat.com]

The existing IS EFA (B2G) platform is being replaced by the new Peppol-based national solution. [ec.europa.eu]

10.2. Transmission Channels

All e-invoices must be transmitted through certified delivery service providers (Digital Postmen) via the Peppol network. The delivery service may be provided in the form of: [forvismazars.com], [financnasprava.sk]

Accounting/ERP software with integrated Peppol Access Point connectivity.
Web applications provided by certified service providers.
Mobile applications provided by certified service providers.

Alternative delivery channels (non-Peppol) are permissible only where the recipient’s consent is obtained, according to the latest FAQ guidance. The DRR reporting obligation for consent-based alternative delivery channels remains unresolved pending further discussion with the Ministry of Finance. [sovos.com]

10.3. Accredited Service Providers / Certified Intermediaries

Use of accredited providers is effectively mandatory — businesses must select and contract with a certified Digital Postman. [kpmg.com], [marosavat.com]
Accreditation requirements: Valid OpenPeppol certification for e-invoicing and e-reporting; legal personality and headquarters or place of business in an EU Member State; clean criminal record for the entity and its statutory representatives; completion of the Slovak-specific onboarding test on the Peppol Testbed. [marosavat.com], [financnasprava.sk]
The Financial Administration publishes and regularly updates the list of certified Digital Postmen and providers in the accreditation process on its portal. As of 26 May 2026: 30 accredited providers and 20 in process. [vatupdate.com], [kpmg.com]
Intermediaries may operate on behalf of certified providers. [financnasprava.sk]
A 3-working-day deadline applies to SMP deregistration when switching service providers. [sovos.com]

10.4. Interoperability

The system is designed for interoperability with the Peppol network (connecting with 21+ countries across Europe), B2G exchange, and future ViDA cross-border reporting from 1 July 2030. [financnasprava.sk], [vatupdate.com]

10.5. Deadlines & Timing

Invoice issuance deadline: 15 calendar days from the tax point (date of supply, date of advance payment, or end of the calendar month for adjustments/summary invoices). [forvismazars.com], [invoice-portal.de]
Supplier reporting: At the time of invoice issuance (real-time via the Digital Postman). [forvismazars.com]
Buyer reporting: Within 5 calendar days of receipt (subject to the pending MoF proposal for removal during 2027–2030). [marosavat.com], [vatupdate.com]
From 1 July 2030: Invoice issuance deadline reduced to 10 days. [forvismazars.com]
Certified providers must store logs of invoice delivery and receipt for at least 6 months. [financnasprava.sk]

Self-Billing

11.1. Self-billing is explicitly permitted under the e-invoicing mandate and is included among the document types exchanged via the eFaktúra system. [e-invoice.app], [financnasprava.sk]

11.2. Self-billed invoices must be processed through the e-invoicing platform (Peppol network via a Digital Postman). The Financial Administration publishes separate testing guides for self-billing (Slovak Republic C2-C3 BIS Self-Billing testing user guide and environment description). [financnasprava.sk]

11.3. A written (prior) agreement between the parties is required. [e-invoice.app]

11.4. Self-billed invoices must comply with the same mandatory content rules as standard e-invoices under EN 16931.

11.5. The Peppol BIS standard includes specific document type and process identifiers for self-billing.

11.6. Specific restrictions for foreign buyers without a domestic tax number have not been detailed in the available guidance beyond the general exclusion of non-established entities until 2030.

11.7. When a self-billed invoice is issued by the customer on behalf of the supplier, the data must be reported to the Financial Administration no later than 5 days from the date of issuance or from the expiry of the deadline for issuance. [forvismazars.com]

Triangulation & Special Scenarios

12.1. Triangulation Transactions

Detailed public operational rules for how invoices issued by domestically registered entities as part of triangular transactions are handled under the mandate are not yet available. [vatupdate.com]

12.2. Chain Transactions

Documentation and reporting requirements for multi-party chain transactions have not been specifically addressed in the published guidance. [vatupdate.com]

12.3. Cross-Border Reverse Charge

Outbound invoices with reverse-charge notation for cross-border transactions are not in scope of the 2027 mandate (domestic only).
Inbound reverse-charge invoices from foreign suppliers are not part of the mandatory 2027 system. These are planned for the broader 2030 phase. [vatupdate.com]

12.4. Zero-Rated and Exempt Supplies

VAT-exempt supplies under §§ 28–43 and § 47 of the VAT Act are excluded from the e-invoicing obligation. For these transactions, where there is no obligation to issue an invoice, there is also no related obligation to issue, receive, or report an e-invoice. Voluntary e-invoice exchange remains possible. [snitechnology.net], [forvismazars.com]
Zero-rated intra-community supplies are part of the cross-border phase (from 1 July 2030).

12.5. Local Nuances & Special Cases

VAT groups: The reform introduces obligations for VAT groups, but detailed operational guidance is limited. [snitechnology.net]
Summary invoices for utilities: The option to issue summary electronic invoices in the form of payment agreements for electricity, gas, water, or heat is abolished from 1 January 2027, as EN 16931 does not permit such arrangements. [forvismazars.com]
Fiscal representatives, consignment/call-off stock, construction reverse charge: No specific guidance under the e-invoicing framework has been published.
VAT deductions: From 1 July 2030, e-invoices become a substantive condition for domestic VAT deductions. [kpmg.com]

Archiving & Retention

13.1. Central Archiving by the Platform

The government platform does not centrally store invoices for archiving purposes. Taxpayers retain separate archiving obligations; the central platform does not relieve this duty. [vatupdate.com]

13.2. Mandatory Archiving Format

E-invoices must be archived in their original structured electronic XML format. Conversion into another format (e.g., PDF) is not sufficient to meet the archiving obligation. [snitechnology.net], [europe.tho…euters.com]

13.3. Retention Period

General retention: 10 years from the end of the year to which the supply relates. [tradeshift.com], [forvismazars.com], [basware.com]
Immovable property: 20 years. [e-invoice.app]

13.4. Storage Location Requirements

Storage location is flexible — archiving abroad is permitted. However, authorities must be granted immediate and free access to archived invoices upon request. [basware.com], [e-invoice.app]

13.5. Integrity, Authenticity & Readability

Integrity, authenticity (credibility of origin), and readability must be maintained throughout the retention period. Readability of invoices in XML BIS format must be ensured (i.e., the format must enable clear and comprehensible display of data). No specific technology (e.g., digital signatures, timestamps) is mandated for archiving beyond maintaining the original XML format. [financnasprava.sk], [basware.com]

13.6. Audit Accessibility

Tax authorities must have immediate and free access to archived invoices upon request. The system does not provide real-time access by authorities to archived invoices (as distinct from the near-real-time reporting via SK TDD). [basware.com]

Penalties & Enforcement

14.1. Grace Period / Transitional Enforcement

2026 is the voluntary testing year; no penalties apply during this period. [vatupdate.com]
No general post-1 January 2027 penalty-free grace period has been identified. [vatupdate.com]
Mitigating factors: No penalty is imposed if (a) the taxpayer corrects incorrectly reported data and it is evident the error was due to an obvious mistake; or (b) the failure was caused by a proven technical malfunction on the part of the contracted Digital Postman, provided the taxpayer reports the data immediately after the malfunction is remedied. [forvismazars.com], [e-invoice.app]

14.2. & 14.3. Penalties for Non-Compliance & Amounts

Up to EUR 10,000 per infraction for: failure to report data, late reporting, incomplete reporting, or reporting incorrect data. [forvismazars.com], [e-invoice.app]
Up to EUR 100,000 for repeated violations of e-invoicing and reporting obligations. [forvismazars.com], [snitechnology.net]
Penalties are fixed monetary fines, escalated by seriousness and repetition — not based on a percentage of VAT or invoice value. [vatupdate.com]
When determining the specific amount, the Tax Office considers the seriousness of the infringement and the duration of the unlawful conduct. [forvismazars.com]

14.4. Article References & Official Sources

Penalty provisions are contained in the amended VAT Act (Act No. 222/2004 Coll. as amended by Act No. 385/2025 Coll.), specifically the new § 76a and related provisions. [financnasprava.sk], [forvismazars.com]

Pre-Filled VAT Returns

15.1. Slovakia does not currently offer pre-filled periodic VAT returns. [vatupdate.com]

15.2. Not applicable at present.

15.3. No specific timeline for introducing pre-filled returns has been announced. However, the data infrastructure being built (near-real-time SK TDD reporting) could potentially support pre-filled returns in the future. [vatupdate.com]

15.4. From 1 July 2030, the elimination of the VAT Control Statement and EC Sales List (replaced by automated reporting through the e-invoicing system) represents a step toward potential pre-filled returns, as all relevant data will be available to the Financial Administration in real time. [forvismazars.com]

15.5. The ViDA framework envisions potential pre-filled return functionalities for EU Member States, and Slovakia’s investment in near-real-time reporting infrastructure positions it to align with such developments.

Readiness for VAT in the Digital Age (ViDA) — Digital Reporting Requirements

16.1. Country Position Relative to ViDA

Slovakia is ahead of the minimum EU ViDA timetable. It is implementing mandatory domestic e-invoicing and reporting by 1 January 2027, well before the EU’s 1 July 2030 cross-border ViDA deadline. [vatupdate.com], [marosavat.com]

16.2. Alignment of the National System with ViDA / International Requirements

The national system aligns strongly with ViDA’s envisioned Digital Reporting Requirements: [vatupdate.com]

EN 16931 standard for e-invoice format.
Peppol BIS 3.0 / UBL 2.1 for transmission.
SK TDD for structured tax reporting.
The CIUS within Peppol BIS 3 is compliant with EN 16931 semantics. [ec.europa.eu]
Potential gaps: Detailed rules for cross-border transaction handling, final buyer-side reporting rules, and special-case mappings may require adjustment before the 2030 phase.

16.3. Cross-Border Digital Reporting

From 1 July 2030, the national system is expected to extend to cross-border intra-EU B2B transactions. At that point, the VAT Control Statement and EC Sales List will be abolished, and the e-invoicing system will provide real-time data to support intra-EU VAT information exchange. [forvismazars.com], [marosavat.com]

16.4. Implications for Businesses

Businesses complying with Slovakia’s 2027 mandate are building infrastructure (Peppol connectivity, EN 16931 compliance, structured XML invoicing) that is broadly future-proof and compatible with future ViDA obligations. [vatupdate.com]
Additional adjustments will likely be needed for the 2030 cross-border phase, including extended scope, shorter issuance deadlines (10 days), and any final ViDA technical specifications.
Early adopters gain experience with structured e-invoicing, provider integration, and data quality, reducing risk when the cross-border mandate arrives. [marosavat.com]

Impact on SMEs and Startups

17.1. Phased Onboarding

No formal phase-in by company size or turnover has been legislated. The mandate applies from 1 January 2027 to all in-scope VAT-registered taxpayers simultaneously, regardless of size. [vatupdate.com]

17.2. Government Support & Free Tools

Financial Administration eFaktúra portal — central information hub with FAQs, webinar recordings, technical documentation. [financnasprava.sk]
Demo tools: The Financial Administration references demo tools such as zrobefakturu.sk and peppolbox.sk for testing and familiarization. [vatupdate.com]
Free third-party tools: The efaktura.tools website offers free browser-based tools (viewer, validator, generator) for Slovak e-invoices, running entirely in the browser with no data uploaded. [efaktura.tools]
Webinar programme: Multiple public webinars conducted by the Financial Administration. [financnasprava.sk]

17.3. Simplified Regimes & Threshold-Based Exemptions

No specific SME turnover threshold exemption has been identified. Simplified invoices under § 74 are excluded from the mandate, but this applies to specific transaction types (under €100 or e-kasa receipts up to €400), not to SME status. [snitechnology.net], [forvismazars.com]

17.4. Subsidies or Financial Support Programs

No government grants, tax credits, or subsidies to offset e-invoicing compliance costs have been identified in the available materials. [vatupdate.com]

17.5. Compliance Costs

Subscription fees for basic Digital Postman services are estimated at approximately EUR 5 to 12 per month (not exceeding the EU average), with transaction fees of approximately EUR 0.05 to 0.50 per invoice. [forvismazars.com], [vatupdate.com]
One-time costs: ERP/accounting software upgrades, connection to certified providers, data mapping, employee training. [vatupdate.com]
Ongoing costs: Provider subscription or per-invoice fees, maintenance.

17.6. Cash Flow & Operational Benefits

Official guidance promotes: automated invoice processing, elimination of manual data entry and transcription errors, time savings and reduced errors, more secure and traceable delivery, easier exchange of invoices across the broader European Peppol ecosystem. [financnasprava.sk], [vatupdate.com]

17.7. Administrative Burden vs. Simplification

Short-term, SMEs will face an initial compliance burden (provider selection, system integration, process changes). Long-term, the policy aims for simplification and automation, especially as current reporting layers (Control Statement, EC Sales List) are streamlined by 2030. [vatupdate.com]

17.8. Market Impact

The open market for accredited providers (30+ certified, 20+ in process) offers choice and competitive pricing. However, SMEs must actively select and onboard a provider, which represents an additional administrative step. [vatupdate.com]

17.9. Official Assessments of SME Readiness

No specific government or independent assessment of SME preparedness for the Slovak e-invoicing mandate has been identified in the available materials.

Official References & Sources

18.1. Government Portals

Financial Administration e-Invoicing portal: https://www.financnasprava.sk/en/businesses/taxes-businesses/value-added-tax/e-invoicing
Financial Administration main portal: https://www.financnasprava.sk
Ministry of Finance of the Slovak Republic: https://www.mfsr.sk

18.2. Legislative Texts

Act No. 222/2004 Coll. on VAT (as amended): Available via Slov-Lex (Slovak legislative portal).
Act No. 385/2025 Coll.: Published 19 December 2025 in the Collection of Laws. [forvismazars.com]
Act No. 215/2019 Coll. (B2G e-invoicing). [ec.europa.eu]

18.3. Technical Specifications

SK Solution Architecture v1.2: Published on the Financial Administration portal. [financnasprava.sk]
Peppol BIS transposition rules (v1.9): Published on the Financial Administration portal (last update 2 June 2026). [financnasprava.sk]
Accreditation scheme: Published on the Financial Administration portal. [financnasprava.sk]
Peppol Testbed documentation: Slovak Republic C2-C3 testing guides published on the portal. [financnasprava.sk]
OpenPeppol: https://peppol.org/

18.4. Tax Authority Publications

Financial Administration FAQ (eFaktúra FAQ): Regularly updated, latest major update May 2026. [sovos.com]
Informácia č. 1/DPH/2026/I (14 January 2026). [kpmg.com]
Webinar recordings: Available on the Financial Administration portal. [financnasprava.sk]

18.5. Advisory Firm Newsletters & Analysis

KPMG TaxNewsFlash (11 May 2026): https://kpmg.com/us/en/taxnewsflash/news/2026/05/slovakia-vat-e-invoicing-implementation-2027.html
Deloitte Slovakia — E-invoicing and e-reporting in Slovakia: https://www.deloitte.com/cz-sk/en/services/tax/services/vat-online.html
Forvis Mazars (15 April 2026): https://www.forvismazars.com/sk/en/insights/publications-and-events/newsletters/electronic-invoicing-in-slovakia-from-1.1.2027
Sovos (26 May 2026): https://sovos.com/regulatory-updates/trr/slovakia-issues-and-updated-version-of-e-invoicing-faq/
Tradeshift (21 May 2026): https://tradeshift.com/resources/compliance/slovakia-b2b-e-invoicing-mandate-2027-tradeshift/
Marosa VAT — Complete Guide: https://marosavat.com/vat-news/e-invoicing-slovakia
SNI Technology (21 May 2026): https://snitechnology.net/slovakia-clarifies-e-invoicing-and-e-reporting-obligations-ahead-of-2027-mandate/
Fonoa (13 April 2026): https://www.fonoa.com/resources/blog/slovakia-e-invoicing-mandate
Thomson Reuters Regulatory Atlas: https://europe.thomsonreuters.com/fi/compliance/regulatory-updates/slovakia
PwC Slovakia — Protection against VAT fraud: https://www.pwc.com/sk/en/tax-services/value-added-tax/protection-against-vat-fraud.html
VATupdate.com — Briefing document (6 June 2026): https://www.vatupdate.com/2026/06/06/briefing-document-podcast-e-invoicing-in-slovakia/
Invoice-Portal (1 June 2026): https://invoice-portal.de/slovakia-moves-toward-mandatory-e-invoicing/
e-Invoice.app (4 April 2026): https://www.e-invoice.app/guides/slovakia-e-invoicing
EU Commission eInvoicing Country Fact Sheet: https://ec.europa.eu/digital-building-blocks/sites/spaces/einvoicingCFS/pages/956171304
Basware Compliance Map: https://www.basware.com/en/compliance-map/slovakia

18.6. Link Verification

All links referenced above were accessible as of June 2026 based on the source crawl dates. Readers are advised to verify current accessibility, as government portals and advisory publications are periodically updated.

Summary & Key Takeaways

19.1. Scope

Covered: All domestic B2B and B2G transactions where the supplier is a domestic VAT payer and the customer is a domestic taxable person or non-taxable legal person established in Slovakia. Excluded: B2C transactions, VAT-exempt supplies (§§ 28–43, § 47), simplified invoices (§ 74), classified/security-related supplies, cross-border transactions (until 1 July 2030), and foreign entities without a Slovak fixed establishment (until 30 June 2030). [forvismazars.com], [vatupdate.com]

19.2. Format

Mandatory: Structured XML compliant with EN 16931 in UBL 2.1 or CII syntax, exchanged via the Peppol network. Not valid: PDF, paper, scanned documents, Word, Excel, EDIFACT (unless converted). Legacy formats remain valid only for out-of-scope transactions. [marosavat.com], [e-invoice.app]

19.3. Timeline

1 January 2026: Law in force; voluntary testing begins.
May/June 2026: Voluntary e-invoice exchange opens.
1 January 2027: Mandatory domestic B2B/B2G e-invoicing and digital reporting.
1 July 2030: Extension to cross-border intra-EU transactions; issuance deadline shortened to 10 days; Control Statement and EC Sales List abolished.
No grace period after 1 January 2027 (with exceptions for obvious errors and provider technical failures). [e-invoice.app], [forvismazars.com]

19.4. How It Works

Decentralized 5-corner Peppol model. No pre-clearance. Invoices exchanged peer-to-peer through certified Digital Postmen (Peppol Access Points). Tax authority receives SK TDD reporting data at corner 5 in near-real-time. Buyer consent is not required for invoice delivery. [e-invoice.app], [marosavat.com]

19.5. Key Obligations

Issuance: Within 15 days of the tax point (reducing to 10 days from July 2030).
Reporting (supplier side): At the time of issuance via Digital Postman.
Reporting (buyer side): Within 5 calendar days of receipt (pending MoF proposal for removal during 2027–2030).
Receipt: All domestic taxable persons must be capable of receiving e-invoices.
Correction: Via formal credit notes/correcting invoices; no direct modification of transmitted invoices.
Archiving: Original XML format, 10 years (20 years for immovable property). [forvismazars.com], [marosavat.com], [snitechnology.net]

19.6. Main Risks

Penalties of up to EUR 10,000 per infraction and EUR 100,000 for repeated violations.
Loss of VAT deduction rights for domestic supplies from 1 July 2030 if e-invoice requirements are not met.
Operational disruption from failure to select and onboard a Digital Postman before the deadline.
Data quality issues from inadequate ERP/data mapping preparation.
Abolition of summary invoices for utilities requiring process changes. [forvismazars.com], [kpmg.com]

19.7. SME Implications

No phase-in by size; all in-scope taxpayers must comply from 1 January 2027. Low-cost provider options are expected (EUR 5–12/month). Free tools and webinars are available from the Financial Administration and third parties. No government subsidies identified. Initial compliance burden offset by long-term automation and simplification benefits. [vatupdate.com], [forvismazars.com]

19.8. ViDA / International Readiness

Slovakia is well-aligned with ViDA. The Peppol-based, EN 16931-compliant infrastructure is broadly future-proof. The 2030 cross-border phase will require scope extension and adjustment to final ViDA technical specifications, but the core technology investment made for 2027 will carry forward. [vatupdate.com], [marosavat.com]

19.9. Critical Dates & Next Steps

Now (June 2026): Map all Slovak domestic invoicing flows and identify in-scope transactions. Confirm ERP/accounting system capabilities for EN 16931 XML generation. Select and contract a certified Digital Postman. Begin testing during the voluntary phase.
Q3 2026: Digital reporting (C5) availability projected; end-to-end testing recommended.
1 January 2027: Mandatory go-live — no further delay expected.
1 July 2030: Cross-border expansion, shorter deadlines, elimination of legacy reporting.
Monitor: The status of the 27 May 2026 MoF proposal on buyer-side reporting removal, further FAQ updates from the Financial Administration, and any additional technical specification releases. [vatupdate.com], [e-invoice.app]

This analysis is based on publicly available sources as of 6 June 2026. Given the pace of developments, businesses should monitor the Financial Administration’s eFaktúra portal and official FAQ for the latest updates. For company-specific implementation advice, local specialist counsel should be consulted.

Legal texts:

The mandate is embedded in the amended VAT Act (Law No. 222/2004), as modified by Act No. 385/2025 Coll. which was passed in December 2025. Implementation details are further clarified by Financial Administration’s Guide 1/DPH/2026/I (Jan 14, 2026). These implement EU Council Directive 2025/516 (the “VAT in the Digital Age” amendments) for Slovakia.