Navigating the New E-Invoicing Obligation in Slovakia: What You Need to Know

Slovakia’s e-invoicing law applies from 1 January 2027 with different duties for issuance, receipt and reporting. Domestic VAT payers under sections 4, 4b and 4c issue and report; the legally defined broader domestic recipient population must be able to receive. B2C is excluded, and section 5 foreign registrations remain excluded through 30 June 2030. The implementation design must therefore classify each legal entity and transaction instead of treating VAT registration as a universal scope test.

Compliance Summary

Area	Status (as of July 2026)
Mandate	Slovakia B2B e-invoicing and e-reporting for domestic transactions
Legal status	From 1 January 2027, domestic VAT payers under sections 4, 4b and 4c issue and report; the legally defined broader domestic recipient population must be able to receive.
Exchange model	Certified Digital Postman/Peppol is the default. Parties may agree another structured exchange method in advance if legal format and reporting requirements remain satisfied.
Format	EN 16931-compliant XML (UBL 2.1 or CII)
Reporting deadline	The 15-day rule is the invoice-issuance deadline, not the reporting deadline. A Digital Postman must notify the invoice data within five days after receiving the invoice.
Penalties	Late, incomplete, or inaccurate reporting: fines up to €10,000; repeated violations up to €100,000
Next phase	1 July 2030: extends to intra-Community B2B transactions in line with the EU ViDA digital reporting requirements

What Is the Slovakia E-Invoicing Requirement?

Invoices normally flow through certified Digital Postmen using Peppol, but parties may agree another legally compliant structured exchange method in advance. The Financial Administration receives the statutory data through the five-corner reporting model. Issuance and receipt scope differ, so SAP routing must be driven by the parties’ legal status and transaction type.

Business Impact for Finance and Tax Teams

• Invoice process control: manual invoice corrections and offline workarounds become harder to govern once invoice issuance and five-day Digital Postman reporting deadlines are monitored separately.
• Master data quality: tax identifiers, addresses, customer setup, and company-code data need to support structured exchange and routing.
• Exception handling: rejected or incomplete invoice data needs a clear owner and follow-up process on both AR and AP sides.
• Audit readiness: teams need traceability between the SAP source document, the exchanged invoice, and the reported record.

How This Impacts Your SAP Environment

SAP area	Preparation question
FI / SD	Can required invoice and tax values be derived consistently from source documents?
Master data	Are customer, vendor, company, and tax identifiers clean enough for Peppol routing and reporting?
E-document output	Can the system generate EN 16931 XML (UBL 2.1 / CII) without manual rekeying?
Integration	Which Digital Postman or agreed exchange method will be used, and how are the five-day reporting window and the separate 15-day invoice-issuance rule monitored?
Operations	Who resolves rejected records and how are corrections tracked?

Practical Steps for SAP Teams

1. Map affected company codes, invoice flows, and domestic transaction scenarios.
2. Review master data fields needed for structured invoice exchange and reporting.
3. Identify gaps in tax-code mapping, invoice-type handling, and correction logic.
4. Define how SAP will generate, validate, transmit, and monitor the invoice record.
5. Confirm final technical specifications against the Financial Administration’s published guidance before design freeze.

Official sources

• Financial Administration of Slovakia — eFaktúra FAQ, 26 March 2026

Regulatory content verified: 10 July 2026.

Verified on: 10 July 2026. Confirm the current legal scope, authority technical package and SAP-supported scenario before implementation.