This analysis distinguishes between enacted requirements under Act No. 385/2025 Coll. and changes still pending under legislative proposal LP/2026/282. Where final legislation, technical rules, or official guidance is unavailable, this is explicitly stated.

1. Introduction and Country Context

1.1 Tax-digitalisation journey

Slovakia’s move toward mandatory structured e-invoicing builds on:

• Transaction-level VAT control statements.
• The eKasa online cash-register system.
• B2G e-invoicing under Act No. 215/2019 Coll.
• Earlier work on the IS EFA public-sector invoicing platform.
• The EU VAT in the Digital Age, or ViDA, reforms adopted in March 2025.

The latest model replaces the earlier central-platform concept with a decentralised interoperability model based on Peppol, certified delivery-service providers, and direct invoice-data reporting to the Slovak Financial Administration. [mfsr.sk], [mfsr.sk], [financnasprava.sk]

1.2 Policy objectives

The stated objectives are:

• Reducing VAT fraud and the VAT gap.
• Giving the tax administration faster access to transaction-level data.
• Standardising invoicing data.
• Eliminating manual data entry and transcription errors.
• Automating accounts payable and accounts receivable processes.
• Supporting interoperability with other EU countries.
• Gradually replacing periodic VAT control reporting with digital transaction reporting.

The Slovak Financial Administration also identifies lower invoicing costs, faster payment, improved cash flow, better invoice traceability, and fewer processing errors as expected benefits. [financnasprava.sk], [mfsr.sk], [financnasprava.sk]

1.3 Position in the European landscape

Slovakia is implementing domestic B2B and B2G structured e-invoicing from 1 January 2027, ahead of ViDA’s compulsory EU cross-border digital reporting date of 1 July 2030. Its decentralised five-corner design is more closely aligned with European interoperability than central pre-clearance systems such as those used in some other Member States. [e-invoice.app], [taxation-c….europa.eu], [eur-lex.europa.eu]

1.4 EU authorization or derogation

No separate Council derogation comparable to pre-ViDA derogations appears necessary. Directive (EU) 2025/516 changed the EU legal framework so that Member States can introduce mandatory structured e-invoicing under the new conditions without relying on the previous customer-consent rule in Article 232. Slovakia’s legislation expressly transposes relevant parts of Directive (EU) 2025/516. [financnasprava.sk], [taxation-c….europa.eu], [eur-lex.europa.eu]

2. Regulatory Framework

2.1 Primary legislation

The central legislation is:

• Act No. 222/2004 Coll. on VAT, as amended.
• Act No. 385/2025 Coll., adopted on 9 December 2025 and published on 19 December 2025.
• The amendment also changes the Tax Procedure Code, Accounting Act, Income Tax Act, Public Procurement Act, Social Economy Act, and Act No. 215/2019 Coll. on guaranteed electronic invoicing and the Central Economic System. [slov-lex.sk], [static.slov-lex.sk], [financnasprava.sk]

Important provisions include:

• Section 76a, governing electronic-invoice delivery services and certified providers, effective from 1 January 2026.
• Section 85o, containing transitional e-invoicing and reporting rules, principally effective from 1 January 2027 and 1 July 2030.
• Sections 71 to 75 of the VAT Act, containing the underlying definitions, issuance, content, and correction requirements for VAT invoices. [efaktura.sk], [slov-lex.sk], [slov-lex.sk]

2.2 Pending amendment LP/2026/282

As of 26 September 2026, LP/2026/282 should still be treated as a legislative proposal, unless and until an adopted law is published in the Collection of Laws.

The proposal would:

• Postpone the buyer’s obligation to report data from received invoices until 1 July 2030.
• Preserve the buyer’s obligation to receive structured invoices from 1 January 2027.
• Preserve supplier-side reporting from 1 January 2027.
• Introduce a penalty soft-landing period from 1 January to 31 March 2027.
• Remove or narrow certain disproportionate obligations, including aspects affecting private landlords.

The proposal does not postpone the core 2027 e-invoicing mandate. [sovos.com], [vatupdate.com], [vatcalc.com], [slov-lex.sk]

2.3 Official guidance and FAQs

The most important official guidance includes:

• Financial Directorate Information No. 1/DPH/2026/I, explaining the provisions effective from 2027 and 2030.
• FAQ 9/DPH/2025/IM, substantially expanded in August 2026.
• The Financial Administration’s eFaktúra portal.
• Dedicated guides for businesses, municipalities, NGOs, software providers, and certified delivery-service providers.
• The Financial Administration Academy’s webinars and training material. [financnasprava.sk], [financnasprava.sk], [financnasprava.sk], [financnasprava.sk]

2.4 B2G legal framework

Slovak B2G e-invoicing was already governed by Act No. 215/2019 Coll., implementing Directive 2014/55/EU. The new Peppol-based model is expected to supersede or integrate the earlier IS EFA architecture so that domestic B2B and B2G invoices use a common framework from 2027. [financnasprava.sk], [ec.europa.eu], [ec.europa.eu]

3. Scope of the Mandate

3.1 Domestic B2B

From 1 January 2027, a Slovak domestic VAT payer registered under Sections 4, 4b, or 4c must issue a structured electronic invoice for prescribed supplies of goods or services where:

• The place of supply is Slovakia.
• The customer is a domestic taxable person or non-taxable legal person.
• The supplier has an obligation to issue an invoice under the VAT Act.
• The transaction may include advance payments received before the supply.

A PDF, scanned invoice, Word file, or image is not a qualifying e-invoice. [financnasprava.sk], [danovky.sk], [financnasprava.sk]

3.2 Domestic B2G

Domestic B2G transactions are included in the 2027 framework where the supplier is a domestic VAT payer and the place of supply is Slovakia. Public-sector recipients must be capable of receiving the structured invoice. Public-procurement references may be required where applicable. [financnasprava.sk], [snitechnology.net], [ec.europa.eu]

3.3 Domestic B2C

Invoices to ordinary private consumers are outside the 2027 structured e-invoicing mandate. Consumer invoices can continue through existing channels, including paper, email, portals, and applicable eKasa processes. [financnasprava.sk], [financnasprava.sk], [financnasprava.sk]

3.4 Intra-EU supplies and acquisitions

The structured cross-border e-invoicing and ViDA digital-reporting regime is scheduled for 1 July 2030.

Until then:

• Intra-Community supplies and acquisitions remain subject to existing VAT invoicing, VAT return, EC Sales List, and control-statement rules.
• They are generally outside the mandatory domestic Peppol e-invoicing scope beginning in 2027.
• Voluntary structured invoicing via Peppol may remain commercially possible.
• Cross-border invoices must continue to contain applicable VAT numbers, exemption references, and reverse-charge wording. [kpmg.com], [efaktura.sk], [financnasprava.sk], [taxation-c….europa.eu]

3.5 Exports, imports, and other cross-border B2B supplies

Exports, imports, and supplies or services involving a foreign counterparty do not generally enter the mandatory domestic 2027 invoice-exchange regime merely because one party has a Slovak VAT registration. Their full integration is planned for 1 July 2030 under ViDA-aligned rules.

A foreign supplier’s commercial invoice, customs documentation, import VAT evidence, and reverse-charge accounting remain relevant under the existing rules. [kpmg.com], [efaktura.sk], [dynatos.com]

3.6 Self-billing

Self-billing remains permitted. The buyer creates the invoice in the supplier’s name and transmits it through the buyer’s certified delivery-service provider to the supplier’s provider. The reporting process is then handled through the applicable provider routing. Existing legal conditions for self-billing, including the prior agreement and acceptance procedure, continue to apply. [sovos.com], [financnasprava.sk], [vatupdate.com]

3.7 Triangulation and chain transactions

Slovakia has not published a separate eFaktúra exclusion specifically for triangulation or chain transactions.

The decisive test is the nature of each individual supply:

• A domestic leg satisfying the 2027 conditions can be in scope.
• An intra-EU or export leg generally remains outside the compulsory 2027 domestic exchange mandate.
• Existing evidence requirements for transport, VAT identification numbers, exemption, triangulation, and reverse charge continue to apply.
• The invoicing treatment must be determined separately for each link in the chain.

No dedicated technical transaction type for every chain-transaction variant has been identified in the publicly available official material. [financnasprava.sk], [efaktura.sk], [financnasprava.sk]

3.8 Special VAT schemes

There is no general published exemption for margin schemes, travel-agent schemes, second-hand goods, investment gold, or flat-rate farmers purely because a special VAT regime applies.

Where the underlying transaction otherwise falls within the domestic invoicing obligation:

• The invoice should normally be structured.
• The correct VAT category and VATEX exemption or special-treatment code must be used.
• VAT must not be shown separately where the relevant special scheme prohibits it.
• Existing statutory wording for the applicable margin scheme remains relevant.

Detailed national mappings should be checked against the latest VAT Category Code and VATEX section in the official FAQ. [financnasprava.sk], [comarch.com]

3.9 Explicit exclusions

Published guidance identifies or indicates exclusions for:

• B2C invoices.
• Pro forma invoices and payment requests that are not VAT invoices.
• Simplified invoices, including qualifying eKasa documents and certain fuel receipts.
• Certain invoices up to EUR 400 where the simplified-invoice conditions are met.
• Supplies involving classified information or specified intelligence bodies.
• Documents for transactions outside the scope of VAT.
• Internal documents between members of the same Slovak VAT group, because they are treated as transactions within one taxable person.

The precise legal basis and conditions for each exclusion must be checked in Section 85o, the VAT Act’s simplified-invoice provisions, and the current official FAQ. [efaktura.sk], [fintua.com], [comarch.com]

4. Taxable Persons in Scope

4.1 Issuers

The 2027 issuance obligation generally applies to domestic VAT payers registered under:

• Section 4.
• Section 4b, including VAT groups.
• Section 4c, including groups registered ex officio.

It includes companies, sole traders, professionals, and other taxable persons that are Slovak VAT payers and make relevant domestic supplies. There is no general turnover-based SME exemption. [financnasprava.sk], [danovky.sk], [efaktura.sk]

4.2 Recipients

The obligation to be technically capable of receiving an e-invoice is broader than the issuance obligation. It covers:

• VAT-registered taxable persons.
• Non-VAT taxable persons.
• Legal entities that are not taxable persons.
• Municipalities and public institutions.
• NGOs and non-profit bodies.
• Sole traders and liberal professions.

Non-VAT persons are not generally required to issue structured invoices, but they must be able to receive them where an in-scope VAT payer is legally required to issue one. [financnasprava.sk], [vzdelavani…asprava.sk], [financnasprava.sk]

4.3 Non-established entities

The 2027 obligation focuses on domestic VAT payers and Slovak fixed establishments participating in domestic transactions.

• A foreign entity with a Slovak fixed establishment must assess whether that establishment intervenes in the supply.
• A foreign entity holding only a Slovak VAT registration, without establishment or fixed establishment, is generally outside the initial domestic issuer mandate.
• Broader coverage of non-established persons and cross-border supplies is planned from 1 July 2030.

The treatment of individual foreign registrations requires transaction-specific analysis under Sections 4 to 6 and Section 85o. [kpmg.com], [danovky.sk], [efaktura.sk], [dynatos.com]

4.4 Voluntary participation

Voluntary use is available during 2026, subject to provider onboarding and the ability of trading partners to exchange invoices through the network. This period is intended for testing connectivity, data mapping, validation, accounting integration, and operational processes. [financnasprava.sk], [financnasprava.sk], [e-invoice.app]

5. Implementation Timeline

5.1 Key dates

• 1 August 2019: Existing B2G framework under Act No. 215/2019 Coll. began.
• 11 March 2025: ViDA adopted by the Council.
• 9 December 2025: Slovak Parliament adopted Act No. 385/2025 Coll.
• 16 December 2025: Presidential signature reported.
• 19 December 2025: Publication in the Slovak Collection of Laws.
• 1 January 2026: Provider and delivery-service provisions became effective.
• 2026: Voluntary onboarding, testing, provider accreditation, and production preparation.
• 21 August 2026: Financial Administration confirmed the infrastructure was operational.
• 26 August 2026: Expanded official FAQ and business guidance published.
• 1 January 2027: Mandatory domestic B2B and B2G structured invoicing and supplier-side reporting.
• 1 July 2030: ViDA cross-border e-invoicing and digital reporting, broader taxpayer scope, and planned replacement of VAT control statements and EC Sales Lists. [sovos.com], [danovky.sk], [financnasprava.sk], [financnasprava.sk]

5.2 Proposed transitional relief

LP/2026/282 proposes:

• No administrative-offence treatment or financial penalty for certain e-invoicing failures during 1 January to 31 March 2027.
• Deferral of buyer-side reporting of received invoices until 1 July 2030.

This relief was still described by recent sources as proposed or pending. Businesses should not treat it as enacted until publication of the final amendment. [sovos.com], [sovos.com], [vatupdate.com], [vatcalc.com]

6. Operating Model

6.1 Model classification

Slovakia uses a decentralised five-corner Peppol model, not central tax-authority clearance.

The principal parties are:

1. Supplier.
2. Supplier’s certified delivery-service provider.
3. Buyer’s certified delivery-service provider.
4. Buyer.
5. Slovak Financial Administration, receiving reportable invoice data.

The tax authority does not approve every invoice before legal issuance or delivery. [vatupdate.com], [e-invoice.app], [vatcalc.com]

6.2 Invoice lifecycle

The expected process is:

1. The supplier’s ERP or accounting system creates a compliant structured invoice.
2. The invoice is submitted to the supplier’s certified provider.
3. The provider performs technical and schema validation.
4. The supplier-side provider resolves the buyer’s Peppol endpoint.
5. The invoice passes through the Peppol network to the buyer’s provider.
6. The buyer retrieves or automatically imports the invoice.
7. Required data is transmitted to the Financial Administration.
8. Both parties archive the authentic structured invoice and related evidence.

For Peppol delivery, the invoice is treated as issued when submitted to the delivery-service provider, not when merely generated in the supplier’s ERP. [sovos.com], [financnasprava.sk], [comarch.com]

6.3 Failed delivery

If the supplier submits the invoice within the statutory deadline but the buyer is not registered with a provider, official guidance indicates that the supplier’s issuance obligation can nevertheless be fulfilled. The same invoice may subsequently be supplied by email, with the recipient’s consent, without creating a second invoice. [sovos.com], [comarch.com]

6.4 Acceptance and rejection

Buyer approval is not tax-authority clearance and is not generally required to make the invoice legally issued. Commercial acceptance, dispute, or rejection workflows may be offered by providers, but no universal buyer approval is identified as a condition of invoice validity.

Detailed standardised rules for business rejection, dispute status messages, and the legal effect of each provider workflow are not yet comprehensively published. [sovos.com], [financnasprava.sk]

6.5 Authentication

Businesses select and authorize a certified provider through the Financial Administration portal. Access requires registration with the Financial Administration and authentication through the Slovak public-services environment or portal credentials. API keys, certificates, Peppol Access Point credentials, and other machine-authentication methods are provider-specific. [vpds.finan…asprava.sk], [e-invoice.app]

6.6 Offline and contingency processing

Public guidance recognises provider failure as a possible defence against penalties where:

• The provider’s failure can be demonstrated.
• The omitted data is transmitted without undue delay after restoration.

A comprehensive statutory offline mode, universal QR-code contingency process, and standard fallback upload deadline have not been identified in the current published materials. [efaktura.sk], [financnasprava.sk]

7. Acceptable E-Invoice Formats

7.1 Mandatory formats

A qualifying e-invoice must:

• Be issued, sent, and received in structured electronic form.
• Comply with EN 16931.
• Use an accepted syntax, principally UBL 2.1 or UN/CEFACT CII.
• In practical Peppol exchanges, comply with Peppol BIS Billing 3.0 and the Slovak implementation rules or CIUS.

PDF, scanned images, Word, Excel, and purely visual files do not qualify as the mandatory structured invoice. [financnasprava.sk], [e-invoice.app], [efaktura.sk]

7.2 EDIFACT and legacy EDI

EDIFACT is not itself the statutory EN 16931 invoice syntax. Businesses can retain EDI commercially, but the invoice data must be converted or mapped to the compliant UBL or CII structure for the statutory flow. [efaktura.sk], [efaktura.tools]

7.3 Structure

The invoice structure normally includes:

• Invoice header and identifier.
• Issue date and invoice type.
• Supplier and buyer identities.
• Tax and VAT identifiers.
• Delivery and supply information.
• Line-item descriptions, quantities, prices, and units.
• Discounts, charges, and allowances.
• VAT categories, rates, taxable amounts, and VAT amounts.
• Exemption or reverse-charge reason codes.
• Totals and payable amount.
• Payment information.
• References to orders, contracts, correcting documents, or public procurement, where applicable.

The binding field-by-field requirements derive from Section 74 of the VAT Act, EN 16931, Peppol BIS validation rules, and the national VAT/VATEX mappings. [financnasprava.sk], [eurofiscalis.com]

7.4 Attachments

Peppol BIS technically supports document references and certain attachments. However, an attachment does not replace the structured invoice. The exact permitted file types, size limits, and legal status of attachments depend on the applicable Peppol and provider specifications. No single comprehensive Slovak statutory attachment catalogue has been identified.

8. Technical and Functional Requirements

8.1 Mandatory invoice data

Core mandatory information includes:

• Unique invoice number.
• Issue date.
• Date of supply or advance payment where different.
• Supplier name, address, and VAT identification number.
• Customer name, address, and relevant identification.
• Description and quantity of goods or extent and nature of services.
• Unit price excluding VAT.
• Discounts or rebates not incorporated into the unit price.
• Taxable amount by VAT rate or exemption.
• VAT rate and VAT amount.
• Total payable amount.
• Reverse-charge, exemption, self-billing, margin-scheme, or other statutory wording when relevant.
• Reference to the original invoice for corrections.

Conditional data includes payment terms, bank account, purchase-order reference, contract reference, delivery location, public-procurement reference, tax representative information, and factoring details. [financnasprava.sk], [comarch.com], [eurofiscalis.com]

8.2 Validation rules

Validation is expected at several levels:

• XML syntax.
• EN 16931 semantic rules.
• Peppol BIS business rules.
• Slovak CIUS or domestic rule requirements.
• Tax identification and endpoint formats.
• VAT category and VATEX consistency.
• Mathematical reconciliation of line values, taxable bases, VAT, totals, allowances, and charges.
• Mandatory references for credit notes and special transactions.

Rejected documents must be corrected and retransmitted. Creation in the ERP is insufficient if the invoice is not successfully handed to the delivery service. [financnasprava.sk], [e-invoice.app], [comarch.com]

8.3 E-reporting data

Under enacted Act No. 385/2025:

• The supplier reports invoice data when issuing the e-invoice.
• The recipient reports data from a received invoice within five calendar days.
• In normal Peppol processing, the certified provider performs the reporting automatically.

LP/2026/282 proposes removing the buyer-side five-day obligation until 1 July 2030. Supplier reporting remains scheduled for 2027. [efaktura.sk], [efaktura.sk], [vatupdate.com], [deloitte.com]

8.4 Digital signature and integrity

No universal qualified electronic signature is required for every e-invoice. Authenticity, integrity, and readability may be supported through:

• Business process controls.
• Secure Peppol transmission.
• Electronic data interchange.
• Electronic signatures or seals where voluntarily used.
• Platform and provider audit trails.

The use of a certified provider and controlled network transmission is central to the future model. [financnasprava.sk], [podpora.fi…asprava.sk]

8.5 QR codes

No general requirement has been identified for a QR code on ordinary B2B or B2G e-invoices exchanged through Peppol. Separate eKasa receipt requirements should not be confused with the eFaktúra mandate.

9. Correction of Errors

9.1 Correcting e-invoices

An invoice that has already been issued should not normally be overwritten. Material errors should be corrected through a formal correcting document, credit note, or debit note, as appropriate.

The corrective invoice should contain:

• Its own unique identifier and issue date.
• A reference to the original invoice.
• The reason or nature of the correction.
• The affected tax base and VAT amounts.
• The corrected differences.
• Applicable VAT category and exemption information.

The correction must itself be sent as a compliant structured invoice where the original transaction falls within the mandatory scope. [financnasprava.sk], [vatupdate.com]

9.2 Technical rejection before issuance

Where an invoice fails schema or business-rule validation before valid transmission:

• Correct the source data.
• Regenerate the XML.
• Retransmit it through the provider.
• Preserve logs showing that the rejected file was not the legally issued invoice.

No credit note should be required solely to cancel a file that never became a valid issued invoice, although this depends on the exact processing status.

9.3 Reporting corrections

Incorrect reported data must be corrected promptly. The available guidance indicates possible protection from penalties for an obvious error corrected immediately or for a demonstrable provider failure remedied without delay.

If the incorrect invoice affected a VAT return, VAT control statement, or EC Sales List, the taxpayer must separately assess whether an amended filing is required under the existing reporting rules. No separate public correction form dedicated solely to every eFaktúra reporting error has been identified. [efaktura.sk], [financnasprava.sk]

10. Transmission and Workflow

10.1 Platform architecture

There is no central clearance portal through which every invoice must be approved. Slovakia operates:

• Peppol eDelivery.
• Certified delivery-service providers, commonly called “Digital Postmen.”
• A Slovak Financial Administration reporting component as the fifth corner.
• Service Metadata Publisher and endpoint-discovery infrastructure. [mfsr.sk], [e-invoice.app], [vatcalc.com]

10.2 Transmission channels

Expected channels include:

• ERP or accounting-system connection via a certified provider.
• Provider API.
• Provider web or mobile application.
• Peppol Access Point.
• Alternative delivery outside Peppol with recipient consent in legally permitted circumstances.

The official provider registry is available through the Financial Administration. [vpds.finan…asprava.sk], [sovos.com]

10.3 Certified providers

Provider use is central to the statutory delivery service. Providers are accredited or certified and must comply with:

• Slovak delivery-service requirements.
• Peppol operational rules.
• Security and identity requirements.
• Reporting obligations.
• Technical interoperability standards.

The official registry already includes Slovak and foreign providers and their intermediaries. ISO/IEC 27001 requirements are reported to apply to certified providers from 1 July 2027. [vpds.finan…asprava.sk], [vatupdate.com]

10.4 Timing

• General invoice-issuance deadlines continue to apply, commonly 15 calendar days in relevant cases.
• Submission to the provider within the statutory period is essential.
• Supplier reporting occurs at issuance.
• Buyer reporting is five calendar days under the enacted rules, but proposed for deferral until July 2030.
• Existing VAT returns and control statements remain periodic until their planned replacement in 2030. [sovos.com], [comarch.com], [vatcalc.com]

11. Self-Billing

• Self-billing remains legally permitted.
• A prior agreement between supplier and customer and an acceptance procedure continue to be required.
• The buyer issues the invoice in the supplier’s name.
• The buyer transmits it through its own Digital Postman to the supplier’s provider.
• The invoice must contain the statutory self-billing indication and all normal VAT invoice information.
• The applicable invoice type, party roles, supplier/customer identifiers, and routing must be correctly mapped.
• Foreign buyers without an appropriate Slovak or Peppol identity may require specific provider configuration.
• Public guidance does not establish a general requirement for the supplier to approve every self-billed invoice through a government portal.
• Commercial and contractual acceptance controls remain necessary, especially for pricing, quantities, VAT treatment, and correction workflows. [sovos.com], [financnasprava.sk], [vatupdate.com]

12. Triangulation and Special Scenarios

12.1 Triangulation

The e-invoicing system does not change the substantive VAT conditions for triangulation. The intermediary must continue to:

• Use the correct VAT identification number.
• Apply the triangulation simplification only where all statutory conditions are satisfied.
• Include the required reverse-charge wording.
• Report the transaction through the existing VAT return and EC Sales List until the 2030 model applies.

Whether a specific invoice is subject to the 2027 eFaktúra mandate depends on the place of supply and domestic status of the parties.

12.2 Chain transactions

Each transaction in a chain must be assessed separately. The structured invoice should document the commercial supply, while transport attribution and exemption evidence remain outside the invoice itself and must be retained in the audit file.

12.3 Reverse charge

For domestic or cross-border reverse-charge scenarios:

• VAT category and VATEX or exemption codes must be correctly populated.
• The legally required reverse-charge wording must be included.
• No Slovak output VAT should be shown where the reverse charge applies.
• Inbound foreign invoices remain subject to purchaser-side VAT accounting and existing reporting until the ViDA cross-border system begins. [financnasprava.sk], [comarch.com], [eurofiscalis.com]

12.4 Zero-rated and exempt supplies

The XML must distinguish:

• Taxable supplies at the applicable rate.
• Exempt supplies with right to deduct.
• Exempt supplies without right to deduct.
• Intra-Community supplies.
• Exports.
• Reverse-charge supplies.
• Transactions outside VAT scope.

The official FAQ’s Slovak VAT Category Code and VATEX mapping should be used rather than free-text descriptions alone. [financnasprava.sk], [comarch.com]

12.5 VAT grouping

Transactions between members of the same Slovak VAT group are internal to one taxable person and do not normally create a statutory VAT invoice obligation. Voluntary Peppol documents may nevertheless be exchanged for accounting purposes, using the correct “not subject to VAT” treatment and participant identifiers. [comarch.com]

13. Archiving and Retention

13.1 Retention period

Invoices must generally be retained for 10 years for Slovak VAT purposes. This applies to issued and received invoice records and supporting evidence. [vatupdate.com], [snitechnology.net]

13.2 Format

For mandatory e-invoices, the safest compliance approach is to retain:

• The original structured XML.
• Any human-readable rendition.
• Provider transmission and delivery evidence.
• Validation results and status messages.
• Correction and cancellation links.
• Supporting commercial documents.

Keeping only a PDF rendering would create risk because the legally relevant structured invoice is the XML document. [vatupdate.com], [efaktura.sk]

13.3 Central storage

Provider or platform storage does not automatically relieve the supplier and customer of their statutory retention duties. Businesses should contractually verify:

• Retention duration.
• Data export rights.
• Retrieval after contract termination.
• Evidence availability.
• Disaster recovery.
• Audit support.

No official rule has been identified stating that tax-authority receipt of invoice data replaces taxpayer archiving.

13.4 Storage location

Electronic storage outside Slovakia may be possible where the invoice remains immediately accessible online to the Slovak tax authorities and the authenticity, integrity, and readability requirements are satisfied. Businesses should verify third-country hosting, GDPR, tax-authority access, and contractual exit provisions before relying on non-EU storage.

13.5 Integrity, authenticity, and readability

These must be maintained from issuance until the end of retention. Permitted methods include business controls establishing a reliable audit trail, EDI, electronic signatures, and other technologies ensuring authenticity and integrity. [podpora.fi…asprava.sk]

14. Penalties and Enforcement

14.1 E-reporting penalties

Reported maximum penalties are:

• Up to EUR 10,000 for a first breach.
• Up to EUR 100,000 for repeated breaches.

Potential triggers include:

• Failure to report invoice data.
• Late reporting.
• Reporting data inconsistent with the invoice.
• Issuing only a PDF where structured XML is mandatory.
• Failure to meet prescribed transmission requirements. [efaktura.sk], [snitechnology.net]

14.2 Mitigation

Penalties may not apply where:

• An obvious error is corrected immediately.
• The certified provider demonstrably failed.
• The data is reported without undue delay after the failure is resolved.
• Proposed Q1 2027 transitional relief is ultimately enacted and its conditions are met. [sovos.com], [efaktura.sk]

14.3 Other exposures

Separate sanctions may arise under the VAT Act, Tax Procedure Code, or Accounting Act for:

• Missing or incorrect invoice information.
• Late VAT returns.
• Incorrect VAT control statements.
• Inadequate accounting records.
• Failure to retain documents.
• Obstruction of an audit.
• Intentional tax evasion or fraud.

The eFaktúra penalties do not replace these wider tax and accounting sanctions.

14.4 Important status qualification

The proposed 1 January to 31 March 2027 penalty holiday should not yet be built into compliance planning as a certainty. It remains dependent on final legislative adoption and publication. [sovos.com], [sovos.com], [slov-lex.sk]

15. Pre-Filled VAT Returns

Slovakia does not currently appear to offer a fully pre-filled periodic VAT return generated from eFaktúra data.

The strategic direction is nevertheless clear:

• Supplier-side invoice reporting starts in 2027.
• Broader domestic and cross-border digital reporting is planned for 2030.
• VAT control statements and EC Sales Lists are intended to be withdrawn or replaced from July 2030.
• Transaction-level eFaktúra data could subsequently support pre-population, automated reconciliation, and risk analysis.

No final official publication has yet specified:

• A confirmed launch date for pre-filled VAT returns.
• Which VAT return boxes would be populated.
• Whether taxpayers would accept, edit, or merely reconcile a draft.
• How non-invoice adjustments, imports, partial exemption, corrections, bad debt, or capital-goods adjustments would be handled. [kpmg.com], [vatupdate.com], [financnasprava.sk]

Accordingly, pre-filled VAT returns should be treated as a future policy possibility, not a currently enacted 2027 deliverable.

16. ViDA Readiness

16.1 Alignment

The Slovak system is strongly aligned with ViDA through:

• Structured e-invoices.
• EN 16931.
• UBL/CII syntax capability.
• Peppol interoperability.
• Transaction-level reporting.
• Expansion to cross-border transactions on 1 July 2030.
• Planned replacement of EC Sales Lists by digital reporting. [financnasprava.sk], [taxation-c….europa.eu], [eur-lex.europa.eu]

16.2 Potential gaps

Areas requiring continued alignment include:

• Final Slovak reporting data sets.
• EU harmonised cross-border validation and status rules.
• Reporting deadlines and correction mechanics.
• Treatment of invoices received from non-Peppol jurisdictions.
• Integration with the future EU central VIES information-exchange architecture.
• Reconciliation between domestic reporting and EU DRR.
• Removal of unnecessary duplicate buyer and supplier reporting.

16.3 Business implications

Businesses implementing Slovakia in 2027 should avoid a country-specific point solution. A future-proof architecture should support:

• EN 16931 semantic data.
• UBL and CII.
• Peppol BIS.
• Centralised VAT determination.
• Country extensions.
• Supplier and buyer reporting.
• Cross-border DRR from 2030.
• Full audit trails and correction chains.

This will reduce the cost of adapting the same ERP landscape to ViDA and other national mandates. [e-invoice.app], [taxation-c….europa.eu]

17. Impact on SMEs and Startups

17.1 Scope and thresholds

There is no general exemption based only on low turnover or SME status. Small VAT payers in scope must issue structured invoices, while non-VAT businesses and legal entities must generally be able to receive them.

Simplified-invoice exclusions reduce the burden for certain low-value retail and eKasa transactions, but they do not provide a broad SME exemption. [financnasprava.sk], [fintua.com]

17.2 Support and free tools

The Financial Administration provides:

• A central eFaktúra information portal.
• Business and sector-specific manuals.
• FAQs and webinars.
• A provider-selection service.
• A registry of certified providers.
• Training through the Financial Administration Academy.

Actual invoicing interfaces, web applications, mobile tools, and pricing depend substantially on the selected Digital Postman. [financnasprava.sk], [vzdelavani…asprava.sk], [vpds.finan…asprava.sk]

17.3 Costs

Likely one-time costs include:

• Accounting-software upgrades.
• ERP and master-data changes.
• Peppol integration.
• VAT code mapping.
• Testing.
• Staff training.
• Supplier and customer onboarding.

Ongoing costs may include:

• Provider subscription or transaction fees.
• Technical support.
• Certificate and security maintenance.
• Monitoring, reconciliation, and archiving.
• Exception and correction management.

No general government subsidy or tax credit dedicated specifically to private-sector eFaktúra implementation has been identified in the current public material.

17.4 Benefits

Potential benefits include:

• Automated posting.
• Fewer manual errors.
• Faster invoice delivery.
• Earlier detection of invalid VAT data.
• Better payment tracking.
• Reduced paper and handling costs.
• Improved cash flow from faster processing.

The Financial Administration has referred to possible processing-cost reductions of up to 80% for medium and large enterprises, but this should be treated as a policy estimate rather than a guaranteed saving for each taxpayer. [mfsr.sk], [vzdelavani…asprava.sk]

17.5 Readiness risk

SMEs relying on email PDFs, spreadsheets, or basic accounting tools face the highest relative transition risk. Their essential minimum preparation is:

• Select a certified provider.
• Confirm receipt capability.
• Upgrade invoice software.
• Clean customer and tax-ID master data.
• Test credit notes and self-billing.
• Establish fallback and support procedures.
• Retain XML and transmission evidence.

18. Official References and Sources

18.1 Government and tax-authority sources

• Slovak Financial Administration eFaktúra portal
• English eInvoicing portal
• Official August 2026 eFaktúra FAQ
• Official business implementation manual
• Financial Administration eFaktúra Academy
• Certified provider selection and register
• Financial Directorate Guidance No. 1/DPH/2026/I

18.2 Legislation

• Act No. 385/2025 Coll.
• Official Gazette PDF of Act No. 385/2025 Coll.
• Act No. 222/2004 Coll. on VAT
• Legislative proposal LP/2026/282

18.3 European Union sources

• European Commission: ViDA overview
• Council Directive (EU) 2025/516
• European Commission eInvoicing country sheet for Slovakia

18.4 Advisor and technology sources

• KPMG: Slovak e-invoicing implementation from 2027
• KPMG Slovakia: approval of mandatory e-invoicing
• Deloitte: e-invoicing and e-reporting in Slovakia
• Sovos: expanded September 2026 FAQ analysis
• Sovos: infrastructure readiness
• Comarch: August 2026 FAQ changes
• VATupdate: Slovakia briefing document
• VATupdate: proposed buyer-reporting deferral

19. Summary and Key Takeaways

19.1 Scope

• Mandatory structured invoicing begins on 1 January 2027 for prescribed domestic B2B and B2G supplies by Slovak VAT payers.
• Recipients include a broader population of taxable persons and legal entities, including non-VAT businesses.
• B2C is excluded.
• Most cross-border transactions remain outside the mandatory 2027 exchange model and move into the ViDA-aligned framework from 1 July 2030. [financnasprava.sk], [financnasprava.sk], [financnasprava.sk]

19.2 Format

• EN 16931-compliant structured XML.
• UBL or CII syntax.
• Peppol BIS Billing 3.0 is the practical transmission standard.
• PDF, Word, scanned images, and standalone EDIFACT do not satisfy the mandatory structured-invoice requirement. [financnasprava.sk], [e-invoice.app], [efaktura.sk]

19.3 Operating model

• Decentralised five-corner Peppol model.
• Certified Digital Postmen exchange invoices and transmit reportable data.
• No central pre-clearance before issuance.
• The supplier reports at issuance.
• Buyer reporting within five days is enacted but proposed for postponement until July 2030. [sovos.com], [vatupdate.com], [vatcalc.com]

19.4 Main risks

• Selecting a provider too late.
• Treating a PDF as the legal e-invoice.
• Incorrect VAT categorisation or VATEX mapping.
• Missing statutory invoice deadlines.
• Failed customer endpoint resolution.
• Incomplete self-billing and correction processes.
• Failure to retain original XML and status evidence.
• Relying prematurely on the proposed Q1 2027 penalty relief.
• Assuming buyer reporting has already been legally postponed. [financnasprava.sk], [efaktura.sk], [vatupdate.com]

19.5 Critical dates

• Now through 31 December 2026: onboarding, voluntary transmission, data mapping, testing, and process redesign.
• 1 January 2027: mandatory domestic B2B/B2G e-invoicing, receipt capability, and supplier reporting.
• 1 January to 31 March 2027: proposed penalty soft landing, not yet a safe assumption until enacted.
• 1 July 2027: reported ISO/IEC 27001 deadline for certified providers.
• 1 July 2030: ViDA cross-border e-invoicing and reporting, proposed buyer-side reporting start, broader scope, and planned withdrawal of VAT control statements and EC Sales Lists. [sovos.com], [vatupdate.com], [vatcalc.com], [taxation-c….europa.eu]

19.6 Recommended next steps

• Confirm the exact Slovak entities and fixed establishments in scope.
• Map domestic, cross-border, B2G, B2C, self-billing, triangulation, and special-scheme flows.
• Select a certified Digital Postman.
• Validate UBL/CII and Peppol BIS capability.
• Map VAT codes to Slovak VAT Category and VATEX values.
• Test issuance, receipt, rejected invoices, credit notes, self-billing, attachments, and fallback scenarios.
• Build reconciliations between eFaktúra, VAT returns, VAT control statements, EC Sales Lists, and general-ledger data.
• Preserve XML files, provider acknowledgements, error messages, and correction chains for the full retention period.
• Monitor LP/2026/282 closely, particularly the proposed buyer-reporting deferral and Q1 2027 penalty relief.