Slovakia: The Financial Administration Declares the eFaktúra Communication Infrastructure Complete and Fully Functional
Country Update — Slovakia | 25 August 2026 | Topic: E-Invoicing / Infrastructure Readiness
On August 21, 2026 the Slovak Financial Administration issued a press release headed “Infraštruktúra pre systém elektronickej fakturácie je kompletná a plne funkčná” — the infrastructure for the electronic invoicing system is complete and fully functional. By launching the communication infrastructure, the authority states that it has confirmed the full technical readiness of the system for automated transfer of tax data from eFaktúry. It also claims that Slovakia has become the first country in Europe to put into practice an electronic reporting model built entirely in line with the new EU VAT rules.
Background
Slovakia's mandatory e-invoicing and reporting regime was enacted by Act 385/2025 Z.z., amending the VAT Act (Act 222/2004 Z.z.). Domestic B2B and B2G invoicing and the associated data reporting become mandatory on January 1, 2027. Coverage extends to relevant intra-EU cross-border transactions from July 1, 2030, at which point the control statement (kontrolný výkaz) and the EC sales list (súhrnný výkaz) are abolished.
The Slovak design is decentralized rather than clearance-based. Invoices are exchanged over a Peppol-based network through certified delivery-service providers — the digitálni poštári, or digital postmen — with the Financial Administration acting as the Peppol Authority of the Slovak Republic. The tax data flows to the authority alongside the invoice rather than the invoice being cleared by the authority in advance.
That design has a consequence for readiness. In a clearance model the state platform is the system, and its availability is the milestone. In a decentralized model the state's contribution is the reporting channel that sits behind a network it does not itself operate, and it is much harder for taxpayers to tell whether that channel exists yet. Until this announcement, the authority's own eFaktúra FAQ — reference 9/DPH/2025/IM, reissued on August 17, 2026 — still described the reporting go-live in the future tense, stating in answer to Example 44 that reporting would follow “pokiaľ bude na to C2 a C5 pripravené” and that go-live was expected in the third quarter of 2026.
The Change
There is no legislative change. Act 385/2025 Z.z. and the amended VAT Act are untouched, no date has moved, and no obligation starts on August 21, 2026. What has changed is the state of the infrastructure and, just as importantly, the authority's public position on it.
The announcement is nonetheless operationally significant, because it converts the reporting channel from an expected component into a stated fact. The Financial Administration describes the mechanism as follows: the supplier issues an eFaktúra; a certified delivery-service provider transmits it to the buyer and at the same time automatically sends the statutory tax data to the Financial Administration; the authority receives and processes that data and returns a confirmation of receipt to the digital postman. The confirmation loop back to the provider is the part that had not previously been described as live.
The authority also makes an architectural argument: that exchange is deliberately not centralized in a single state system, and that resilience comes instead from a network of certified digital postmen. Read alongside the timing, this is best understood as the Financial Administration signaling that the technical prerequisites for January 1, 2027 are now in place on its side, and that the remaining risk sits with taxpayers and providers.
Scope
The announcement concerns the communication infrastructure for automated transfer of tax data from eFaktúry, and therefore the reporting leg of the regime rather than invoice exchange itself, which runs over the Peppol network between providers.
Two points of precision matter. First, the press release does not use the C2 to C5 corner terminology at all, and no official source states in terms that “the C2 to C5 reporting service has gone live.” The Financial Administration words it as a launch of the communication infrastructure together with confirmed full technical readiness. Since the FAQ of August 17, 2026 was still describing that reporting go-live as expected in the third quarter of 2026, the August 21 announcement is consistent with being that go-live, but the equation is an inference and is identified as such here.
Second, the Peppol testbed material published by the Financial Administration covers C2 to C3 test suites only, for Billing and Self-Billing. No C2 to C5 test suite is published there. Taxpayers should not assume that the availability of the reporting channel is matched by a published means of testing against it.
The “first in Europe” claim is the authority's own, and this update reports it as such rather than adopting it. The Financial Administration's formulation is narrower than the shorthand circulating in commentary: it says Slovakia is the first country to put into practice a reporting model created fully in accordance with the new EU VAT rules, not the first country to operate continuous transaction controls. Several Member States already run national reporting regimes. The press release also states that Slovakia was presented in this role at the eDelivery Interoperability Forum in March 2026 by OpenPeppol — not, as some secondary accounts have it, by the European Commission.
Timeline
- January 1, 2026 to December 31, 2026 — transition period; use of the new delivery services is voluntary.
- August 17, 2026 — eFaktúra FAQ 9/DPH/2025/IM reissued at 48 pages, still describing reporting go-live as expected in the third quarter of 2026.
- August 21, 2026 — Financial Administration announces that the communication infrastructure is complete and fully functional and that technical readiness is confirmed.
- August 25, 2026 — certified and in-accreditation provider registers replaced, listing 62 certified providers and 13 in accreditation.
- 7 to September 30, 2026 — seven regional eFaktúra conferences.
- January 1, 2027 — domestic B2B and B2G e-invoicing and the associated data reporting become mandatory.
- July 1, 2027 — ISO/IEC 27001 certification becomes mandatory for Peppol service providers.
- July 1, 2030 — extension to relevant intra-EU cross-border transactions; kontrolný výkaz and súhrnný výkaz abolished.
Businesses Affected
Every business that will issue or receive domestic Slovak B2B or B2G invoices from January 1, 2027 is affected, including foreign-established businesses holding a Slovak VAT registration. For most of them the practical effect of this announcement is that the excuse for waiting has gone: the reporting channel is stated to be operational, and the remaining four months of the transition period are now genuinely usable for end-to-end testing rather than for exchange testing alone.
Groups running SAP are the population with most to gain and most to lose from the timing. The infrastructure being live means a Slovak flow can now be exercised from document creation through provider transmission to authority confirmation, which is the only test that proves the design. It also means that a group which leaves this to the fourth quarter will be competing for the same provider and integrator capacity as everyone else, in a quarter that also carries Norway's January 1, 2027 mandate and Germany's 2027 issuance phase.
Delivery-service providers are directly implicated, since the confirmation loop described by the authority runs to them rather than to the taxpayer. A taxpayer's visibility of whether reporting succeeded depends entirely on what its provider exposes.
Required Actions
- Treat the transition period as a test window that is now fully usable, and schedule an end-to-end test in September or October 2026 rather than in the fourth quarter.
- Ask your delivery-service provider a specific question: does it receive and surface the Financial Administration's confirmation of receipt of the reported tax data, and how is that confirmation exposed to you? A provider that transmits successfully but does not pass the confirmation back leaves you unable to evidence compliance.
- Confirm your provider appears on the certified register of August 25, 2026 and note its EFSK identifier.
- Do not assume a published test route exists for the reporting leg. The Financial Administration's testbed material covers C2 to C3 Billing and Self-Billing only; establish with your provider how the reporting leg will be tested in practice.
- Design your exception handling around the confirmation, not around transmission. In a decentralized model the invoice can be delivered to the buyer while the reporting leg fails, and only the confirmation distinguishes the two.
- Record this announcement in your compliance evidence file with its date. It is the authority's own statement of technical readiness and it is the reference point against which any later slippage would be measured.
Practical Implications
The most useful thing about this announcement is what it removes. Until August 21, a group asking whether it could meaningfully test the Slovak reporting leg had no clear answer, because the authority's own FAQ four days earlier still framed reporting go-live as forthcoming. That ambiguity was a legitimate reason to defer work. It has now gone, and with it the defensible case for waiting.
The second implication concerns evidence. The Financial Administration has described a confirmation returning to the digital postman, not to the taxpayer. In a decentralized architecture this is the single most important operational detail, because it determines who holds proof that the reporting obligation was discharged. Groups should treat the provider's handling of that confirmation as a contractual matter, not a technical footnote, and should be wary of any provider that cannot demonstrate it today.
Third, the gap between exchange testing and reporting testing is real and is not closed by this announcement. Published testbed suites cover the invoice exchange corners. The reporting leg is now stated to be live but is not, so far as the published material shows, accompanied by an equivalent self-service test route. That asymmetry should be raised with providers explicitly rather than discovered in December.
Finally, a word on the “first in Europe” framing, which will circulate widely. It is the authority's own claim, it is narrower than it sounds, and it is not a compliance fact. What matters for planning is not whether Slovakia is first but that the Slovak model is deliberately unlike the clearance systems most groups have implemented elsewhere. A team whose mental model of a mandate is Poland's KSeF or Italy's SdI will design the wrong controls for Slovakia, because there is no central platform whose acceptance can be treated as proof.
Expected Next Steps
Further reissues of FAQ 9/DPH/2025/IM should be expected through the autumn, and one of them can reasonably be expected to update the answer that still describes reporting go-live in the future tense. The provider registers are updated continuously. The seven regional conferences between 7 and September 30, 2026 are the most likely venue for the authority to describe the reporting leg and its testing arrangements in more operational detail, and the question-and-answer segments are where transitional positions are usually stated first.
How Can KGT Support You?
KGT is a specialist indirect tax technology firm working exclusively inside the SAP landscape. We deliver SAP-integrated e-invoicing add-ons for countries where a local mandate outpaces the standard SAP roadmap, and we implement and run SAP Document and Reporting Compliance (SAP DRC) where the standard solution is the right answer. Because we build and operate both, our advice on which route to take for a given country is not a sales position.
For the development described above, KGT typically helps clients in four ways: assessing the impact on the existing SAP configuration and interface build; carrying out the mapping and regression work against the current official specification version; managing the platform, provider or registration dependency; and running the resulting flows as a managed service, so that each release, schema version and validation change is absorbed for you rather than by you. To discuss what this means for your SAP landscape, contact KGT at
This publication is provided for general informational purposes only and does not constitute tax, legal, or professional advice. Please consult your advisor before acting on any information contained in this update.
