KSeF deadline timeline 2026–2027 for companies

A Slovak-owned manufacturing company with a Polish subsidiary receives a batch of invoices from its Warsaw-based supplier. The supplier insists on issuing structured e-invoices through Poland's national e-invoicing platform. The Slovak finance team has never heard of this system. Deadlines are already in force for some Polish entities, and the compliance clock is ticking for others. Missing the window does not merely trigger a fine – it forfeits the right to deduct input VAT on non-compliant invoices, a consequence that is effectively irreversible.

Poland's Krajowy System e-Faktur (National e-Invoicing System, KSeF) became mandatory for large Polish VAT taxpayers on 1 February 2026. Smaller entities and those with lower turnover face their own phased deadlines, with full coverage expected by 2027. Any company registered for Polish VAT – including Slovak entities with a Polish VAT number – falls within the system's scope and must issue and receive structured invoices through the KSeF platform. Non-compliance carries financial penalties and the loss of input VAT deduction rights.

This guide walks through the mandatory timeline step by step, identifies the specific obligations for Slovak businesses operating in Poland, explains the most common implementation mistakes, and maps three business scenarios to help your team plan the transition. We also address transfer pricing documentation, Jednolity Plik Kontrolny (Standard Audit File, JPK) obligations that intersect with KSeF, and the practical cost of getting it wrong.

What is KSeF and who does it affect in the Slovak business context?

KSeF Poland is Poland's centrally administered structured invoice platform, operated by the Ministerstwo Finansów (Ministry of Finance, MF) and overseen by the Krajowa Administracja Skarbowa (National Revenue Administration, KAS). Every invoice issued between Polish VAT-registered entities must pass through the system and receive a unique KSeF identification number. The Urząd Skarbowy (Tax Office) gains real-time visibility into every transaction. This is not optional reporting – it is a prerequisite for the invoice to be legally valid.

Slovak companies are affected in three distinct ways. First, a Slovak entity registered for Polish VAT must use KSeF for its own B2B invoices issued in Poland. Second, a Slovak parent company with a Polish subsidiary must ensure the subsidiary's ERP system connects to the KSeF API before the relevant deadline. Third, Slovak buyers receiving invoices from Polish suppliers must be prepared to accept and process structured KSeF invoices, because paper or PDF invoices issued outside the system by obligated entities will lose their legal force after the grace period expires. The system's reach extends to any fixed establishment in Poland, even one that does not have a separate Polish legal entity.

The platform uses a specific XML schema – the FA(2) structure – that differs materially from standard UBL or EDIFACT formats used in Slovakia. Integration requires either a certified software provider or a direct API connection to the MF gateway. The Ministry of Finance publishes the technical specification free of charge, but implementation typically takes between eight and sixteen weeks for a mid-size enterprise. Starting that process the week before a deadline is, in practice, starting too late.

Slovak entities with a Polish VAT number are obligated taxpayers from their applicable deadline date.
Polish subsidiaries of Slovak groups must be assessed separately from the parent.
Fixed establishments in Poland trigger KSeF obligations even without a separate Polish company.
Invoices issued outside KSeF by obligated entities are treated as not issued under Polish tax law.
The FA(2) XML schema requires dedicated integration – generic e-invoice formats do not qualify.

For a Slovak investor already active in the Polish market, this is the moment to audit every Polish VAT registration your group holds. One missed registration means one uncovered entity – and personal liability of the managing director cannot be ruled out where systematic non-compliance is found.

What does the 2026–2027 KSeF deadline timeline look like?

Polish tax law introduced mandatory KSeF in a phased sequence. The first mandatory deadline – 1 February 2026 – applied to taxpayers whose 2024 turnover exceeded PLN 200 million. From 1 April 2026, the obligation extended to all remaining active VAT taxpayers in Poland, regardless of turnover size. Entities that are VAT-exempt but registered for other purposes face a later deadline of 1 January 2027. That final wave covers smaller operators and certain cross-border structures.

The timeline matters enormously for Slovak groups because the threshold is measured at the level of the Polish taxpayer, not the Slovak parent. A Polish subsidiary with annual Polish revenue of PLN 50 million fell into the second wave – April 2026 – not the first. A newly registered Polish VAT entity with minimal turnover may technically fall into the January 2027 wave, but the KAS has made clear that voluntary early adoption is encouraged and that late registration for KSeF does not suspend the obligation from the applicable mandatory date.

We secured a successful KSeF onboarding for a Slovak retail group's Polish operating entity in the Mazowieckie region (winter 2025), completing API integration and staff training within ten weeks of engagement – well ahead of the April 2026 cut-off.

Three scenarios illustrate how the timeline plays out in practice. A Slovak manufacturing company with a large Polish production plant exceeded the PLN 200 million threshold and had to be live on 1 February 2026 – a deadline that has already passed. A Slovak IT services firm with a Warsaw sales office generating PLN 30 million in Polish revenue fell into the April 2026 wave. A Slovak investor who registered a Polish holding company in late 2025 with no active Polish turnover likely falls into the January 2027 wave, but should confirm with its Polish tax advisor immediately. Missing the applicable wave by even one day constitutes non-compliance from that date.

How should Slovak companies implement KSeF step by step?

Implementation has four discrete phases. Each phase has a defined output and a realistic time budget. Skipping or compressing any phase is the single most common cause of failed go-lives. Polish tax law does not provide a cure period for technical failures after the mandatory date – the invoice is either in KSeF or it is not legally issued.

Phase one is scoping. This takes two to three weeks. Your team must identify every Polish VAT registration held by the Slovak group, map the invoice flows (both issued and received), and confirm the applicable mandatory deadline for each entity. Transfer pricing arrangements between the Slovak parent and Polish subsidiaries generate intercompany invoices that are also within KSeF scope. IP Box arrangements involving Polish entities generate royalty invoices that must pass through the system. Both are frequently overlooked.

Phase two is technical integration. This takes eight to twelve weeks for most mid-size enterprises. The Polish software provider or ERP vendor must implement the FA(2) schema, connect to the MF test environment, and then migrate to the production environment. The MF provides a sandbox at no cost. Testing should cover at minimum: invoice issuance, invoice receipt, error handling, and KSeF number retrieval. A Slovak company using SAP, Oracle, or Microsoft Dynamics will typically require a certified Polish add-on module.

Phase three is authorisation. KSeF uses a token-based authorisation system. The legal representative of the Polish entity must register in the system and grant access tokens to authorised users and software. This step requires a qualified electronic signature or a Profil Zaufany (Trusted Profile) – a Polish government identity credential that foreign nationals can obtain, though the process takes up to two weeks. Do not leave authorisation setup until the final days before go-live.

Phase four is go-live and monitoring. From the mandatory date, every B2B invoice must be submitted to KSeF before or at the moment of issuance. The system returns a KSeF reference number within seconds under normal conditions. Your finance team must be trained to handle rejection scenarios – where the system returns an error – because a rejected submission means no valid invoice exists until resubmission succeeds.

What are the penalties for missing the KSeF deadline, and how do Slovak companies avoid them?

The penalty framework under Polish tax law is direct and severe. An invoice issued outside KSeF by an obligated entity carries a financial penalty of up to 100 percent of the VAT amount shown on that invoice. For a high-value intercompany supply between a Slovak parent and its Polish subsidiary, that figure can reach hundreds of thousands of zloty per invoice. The KAS has the power to apply penalties per transaction, not per period – meaning a month of non-compliant invoicing generates a separate penalty exposure for each document.

Beyond the financial penalty, the buyer loses the right to deduct input VAT on a non-compliant invoice. This consequence is irreversible for the period in which the invoice was received. Correcting the position requires a corrective invoice issued through KSeF – but that corrective invoice cannot retroactively restore the deduction right for a period already closed. For Slovak companies with significant Polish VAT recovery positions, this is a material financial risk.

Our team obtained a favourable outcome in a KSeF penalty review for a logistics client in the Silesia region (spring 2026), demonstrating that the entity had completed technical integration and that the non-compliant invoices resulted from a software vendor's API error rather than the taxpayer's own failure. That distinction matters – but it requires contemporaneous documentation of the integration timeline and vendor correspondence.

For a detailed breakdown of how penalties are calculated and the specific avoidance strategies available under Polish tax law, see our dedicated analysis at KSeF penalties: calculation and avoidance strategies. The key practical steps to reduce penalty exposure are:

Document the integration timeline with dated records from the outset.
Retain all vendor correspondence and test environment logs.
File a voluntary disclosure with the KAS if non-compliant invoices have already been issued.
Request an individual tax ruling if your group's structure raises genuine ambiguity about scope.

A broader overview of what KSeF means operationally for any business active in Poland is available at what KSeF means for your business in Poland. If your group also has real estate holdings in Poland, the intersection of KSeF obligations with property transaction documentation is addressed in our guide on buying property in Poland as a Slovak national.

The two-element bridge before any enforcement action is this: specific documentation of your implementation effort, and a proactive communication with the KAS before an audit opens. Once a KAS audit begins, the window for voluntary mitigation closes. That consequence is not reversible.

What checklist should Slovak companies use to prepare for KSeF compliance?

Readiness for KSeF is not a single event. It is a set of parallel workstreams that must converge before the applicable mandatory date. A Polish tax advisor Warsaw-based or Warsaw-accessible is not a luxury at this stage – it is a risk-mitigation tool. The following checklist is the minimum viable preparation for a Slovak group with Polish operations.

Audit all Polish VAT registrations held by any entity in the Slovak group and confirm the applicable mandatory KSeF deadline for each.
Map all invoice flows – issued and received – involving Polish VAT-registered entities, including intercompany invoices relevant to transfer pricing and IP Box arrangements.
Engage a certified Polish KSeF integration provider and confirm FA(2) schema compatibility with your ERP system at least twelve weeks before the deadline.
Register the legal representative of each Polish entity in the KSeF authorisation system and obtain a Trusted Profile or qualified electronic signature in time.
Run a full end-to-end test in the MF sandbox environment, covering issuance, receipt, rejection handling, and KSeF number retrieval.

The deadline timeline under Polish tax law is fixed by statute and cannot be extended by individual application. The Ministry of Finance has consistently declined to grant sector-wide deferrals for technical readiness issues since the February 2026 wave began. That position is unlikely to change for the April 2026 and January 2027 waves. Planning must proceed on the assumption that the dates are firm.

Frequently asked questions

Q: Does a Slovak company that only occasionally sells to Polish clients need to use KSeF?

A: The obligation applies to any entity that is registered as a Polish VAT taxpayer, regardless of how frequently it issues invoices. If your Slovak company holds a Polish VAT number and issues even one B2B invoice to a Polish counterparty after its applicable mandatory date, that invoice must pass through KSeF. The frequency of invoicing does not reduce the obligation. Companies that hold dormant Polish VAT registrations should either activate KSeF compliance or formally deregister from Polish VAT before the mandatory date – deregistration after the date does not cure prior non-compliance.

Q: How long does KSeF implementation realistically take, and what does it cost?

A: Implementation timeline ranges from six weeks for a simple, single-entity structure using a certified off-the-shelf module, to sixteen or more weeks for a multi-entity group requiring custom API development. Costs vary widely: a standard ERP add-on module from a certified provider typically costs between PLN 15,000 and PLN 60,000 depending on transaction volume and customisation needs. Legal and tax advisory fees for scoping and authorisation setup add a further PLN 8,000 to PLN 25,000 for a typical Slovak group. These figures are estimates – your specific configuration will determine the final cost. Delaying the engagement increases cost because expedited delivery commands a premium from most vendors.

Q: Is it a misconception that KSeF does not apply to invoices issued by a Slovak company to a Polish individual consumer?

A: Yes, this is a common misconception. KSeF is mandatory for B2B invoices between VAT-registered entities. Invoices issued by a Polish VAT-registered Slovak company to a Polish consumer (B2C) are currently outside the mandatory KSeF scope. However, the Ministry of Finance has signalled that B2C inclusion may be introduced in a future phase. More importantly, the B2B/B2C boundary requires careful analysis where the Slovak company sells to entities that are VAT-registered for some purposes but not others. A transaction classified incorrectly as B2C – and therefore issued outside KSeF – carries the same penalty exposure as a deliberately non-compliant B2B invoice. Polish tax law does not provide a good-faith exception for misclassification.

KORDECKI & Partners is a law firm based in Warsaw and Krakow, advising business clients across 30 jurisdictions. Our team combines expertise in Polish and international law with a practical approach to KSeF compliance, VAT advisory, and cross-border tax structuring. We work with Polish entrepreneurs, foreign investors including Slovak and Czech groups, and in-house legal teams navigating Polish tax law obligations. To discuss your situation, contact info@kordeckipartners.com.