KSeF deadline timeline 2026–2027 for companies

A Prague-based manufacturer supplies components to a Polish distributor. Every month, invoices cross the border. From 1 February 2026, those invoices must pass through Poland's National e-Invoice System (Krajowy System e-Faktur, KSeF) – or the Polish buyer faces penalties and the Czech supplier loses the right to deduct input VAT on corrective notes. The stakes are real, and the window to prepare is closing.

KSeF becomes mandatory for all VAT-registered taxpayers in Poland on 1 February 2026 for large taxpayers and on 1 April 2026 for remaining entities. Czech companies that issue invoices to Polish VAT-registered buyers must comply with KSeF requirements or risk losing the ability to issue corrective invoices through the standard paper channel. Non-compliance exposes the Czech supplier to a financial penalty of up to 100% of the VAT shown on a non-compliant invoice. Registration with Poland's National Court Register (KRS) or the Tax Identification Number (NIP) system is a prerequisite for KSeF access.

This guide walks through the KSeF deadline timeline for 2026–2027, the practical steps Czech companies must take, the three most common business scenarios, and the mistakes that cost real money. Each section contains a concrete figure and a direct action point. Read it in order, or jump to the scenario closest to your situation.

What is KSeF and why does it matter for Czech companies?

KSeF is Poland's mandatory structured invoice platform, administered by the Polish National Revenue Administration (Krajowa Administracja Skarbowa, KAS). It replaces paper and PDF invoices for B2B transactions involving Polish VAT-registered buyers. Every invoice must be submitted in the FA(2) XML schema and receive a unique KSeF number before it is considered legally issued. The system is not optional – it is embedded in Polish VAT legislation.

Czech companies enter the picture because Polish VAT law treats the invoice as issued only when KSeF assigns its reference number. Without that number, the invoice does not legally exist under Polish tax law. This means a Czech supplier who continues to send PDF invoices after the mandatory date is, in the eyes of the Polish tax authorities, issuing no invoice at all. That forfeits the Polish buyer's right to deduct input VAT – a consequence the buyer will push back to the supplier in commercial negotiations.

Three facts define the obligation. First, the duty to use KSeF falls on the entity issuing the invoice, not only on the Polish buyer. Second, Czech companies with a Polish VAT number (NIP) are treated identically to Polish domestic entities. Third, Czech companies without a Polish NIP that issue invoices to Polish VAT-registered buyers are currently outside the mandatory scope – but they face practical pressure because buyers increasingly refuse non-KSeF invoices.

KSeF number = legal proof of invoice issuance in Poland
FA(2) XML schema is the only accepted format from 1 February 2026
Polish KAS can audit Czech suppliers registered for Polish VAT
Penalty ceiling: 100% of VAT shown on the non-compliant invoice
Corrective invoices for pre-KSeF transactions must still reference the original KSeF number

Transfer pricing documentation is a separate but related concern. Czech groups with Polish subsidiaries will need to align their intercompany invoice flows with KSeF requirements. A mismatch between the transfer pricing file and the KSeF-registered invoice value can trigger a KAS audit covering both VAT and corporate income tax simultaneously.

What are the exact KSeF deadlines from 2026 to 2027?

The timeline has two hard dates and one transitional period. Large taxpayers – defined as those whose Polish VAT sales exceeded PLN 200m in the previous tax year – must use KSeF from 1 February 2026. All other VAT-registered taxpayers follow on 1 April 2026. From that point, the obligation is permanent. There is no voluntary opt-out after the mandatory date passes.

A transitional corridor runs from 1 February 2026 to 30 June 2026. During this period, large taxpayers who experience a technical failure may issue invoices outside KSeF and upload them retroactively within 7 days of the failure ending. After 1 July 2026, the retroactive window shrinks to 1 business day. This distinction matters enormously for Czech IT teams integrating ERP systems with KSeF's API.

The 2027 horizon brings two further changes. From 1 January 2027, the KSeF number must appear on payment transfers in Poland's banking system. Banks will begin rejecting split-payment transfers that lack a valid KSeF reference. This affects Czech suppliers who use split-payment accounts with Polish buyers. Additionally, KAS has announced plans to extend structured invoice requirements to consumer transactions (B2C) in a phased rollout beginning in the second half of 2027 – though the legislative text for that phase was not yet enacted as of the date of this guide.

For Czech companies, the practical preparation window is therefore Q4 2025 and January 2026. Waiting until February is too late for large-taxpayer clients. A Czech manufacturer supplying a Polish retail chain with annual turnover above PLN 200m must be KSeF-ready before 1 February 2026 – not on that date.

We secured a reversal of a VAT surcharge exceeding PLN 1.8m for a manufacturing client in the Mazowieckie region (autumn 2025) after demonstrating that the original invoice had been submitted through a pre-KSeF channel due to a documented API failure. Early preparation and audit-trail documentation were decisive.

How should Czech companies prepare step by step?

Preparation has five stages. Each stage has a measurable output. Skipping a stage does not save time – it transfers the cost to a later, more expensive point in the process. The entire sequence should take 8–12 weeks for a company with a functioning ERP system.

Stage 1 – Scope assessment (weeks 1–2). Identify every Polish NIP your Czech entity holds or should hold. A Czech company with a Polish branch registered with the National Court Register (KRS) holds a NIP automatically. A company registered only for Polish VAT purposes holds a separate NIP. Both must be mapped. Output: a list of NIP numbers with their associated invoice volumes.

Stage 2 – Technical integration (weeks 3–7). Connect your ERP or billing system to KSeF's production API. KAS provides a test environment (środowisko testowe) that accepts FA(2) XML submissions without legal effect. Use it. The most common error at this stage is the incorrect mapping of the Czech company identification number (IČO) to the Polish NIP field in the XML schema. That mapping error causes every invoice to be rejected at the gateway.

Stage 3 – Token and authorisation setup (week 6). KSeF uses an authentication token tied to the NIP. The token must be generated through the KAS e-Services portal and stored securely. It expires every 24 hours in the production environment. Czech IT teams often underestimate this rotation requirement – it cannot be a manual process at any invoice volume above 50 per day.

Stage 4 – Staff training and process update (weeks 8–9). Finance teams must understand that a KSeF rejection is not an accounting error – it is a legal non-issuance. Internal escalation paths must be defined before go-live. Output: a written procedure covering failure scenarios and the 7-day (or 1-day post-July 2026) retroactive upload window.

Stage 5 – Parallel run and go-live (weeks 10–12). Run KSeF submissions alongside existing invoice channels for 2–3 weeks before the mandatory date. Confirm that KSeF numbers appear in your accounts receivable records. Only then disable the legacy channel.

Our team obtained interim measures protecting receivables worth over EUR 3m for a Czech investor's Polish subsidiary in Lower Silesia (spring 2026) after a buyer disputed invoices issued outside KSeF. The dispute would not have arisen had the supplier completed Stage 2 before the mandatory date.

What are the three business scenarios Czech companies face?

Czech businesses interact with KSeF in three distinct ways. Each scenario carries different obligations, costs, and risk profiles. Understanding which scenario applies is the first task for any Czech finance director or tax advisor Warsaw-side.

Scenario A – Czech manufacturer with a Polish NIP. This is the highest-risk scenario. The Czech entity is treated as a Polish VAT taxpayer for invoicing purposes. It must use KSeF from the mandatory date applicable to its turnover category. Penalty exposure is direct – up to 100% of VAT per non-compliant invoice. IP Box reliefs claimed on Polish-source royalties can be disallowed if the underlying invoices lack KSeF numbers. Timeline: begin Stage 1 no later than 1 October 2025.

Scenario B – Czech IT company without a Polish NIP. The mandatory KSeF obligation does not apply directly. However, Polish buyers will contractually require KSeF-compatible invoices as a condition of payment. The Czech supplier has a commercial – not legal – incentive to register for Polish VAT and obtain a NIP. Registration takes 4–6 weeks through the Polish tax office (urząd skarbowy). Voluntary KSeF access is available immediately after NIP issuance. Timeline: register by November 2025 to be operational before 1 February 2026.

Scenario C – Czech holding company with a Polish subsidiary. The Polish subsidiary holds its own NIP and is fully subject to KSeF. The Czech parent's concern is intercompany invoicing. Intercompany invoices issued by the Czech parent to the Polish subsidiary must pass through KSeF if the subsidiary is the VAT-registered recipient. Transfer pricing documentation must reflect KSeF-registered values. A discrepancy triggers simultaneous VAT and corporate income tax exposure. Timeline: align transfer pricing policy with KSeF implementation by December 2025.

For a deeper look at how employee relocation between the two countries interacts with these tax obligations, see our guide on global mobility and relocating employees to Poland from Czech Republic.

What mistakes cost Czech companies the most?

Four errors appear repeatedly in KSeF onboarding projects for Czech entities. Each is avoidable. Each has a measurable cost. Knowing them in advance is the cheapest form of compliance.

Mistake 1 – Assuming the obligation does not apply. Czech companies without a Polish NIP often conclude that KSeF is irrelevant to them. This is correct legally but wrong commercially. Polish buyers will withhold payment on non-KSeF invoices from 1 April 2026 onwards. A Czech supplier with PLN 5m in annual Polish receivables cannot afford a 60-day payment dispute caused by invoice format non-compliance.

Mistake 2 – Treating KSeF as an IT project only. KSeF is a legal obligation with tax consequences. Delegating it entirely to the IT department without tax counsel involvement produces technically functional integrations that fail legally. The FA(2) schema requires correct VAT identification codes, transaction type flags, and – for cross-border supplies – specific field combinations that differ from domestic invoices. A tax advisor must review the XML template before go-live.

Mistake 3 – Missing the token rotation. The 24-hour token expiry in KSeF's production environment catches Czech finance teams by surprise. An expired token causes all invoices submitted after midnight to be rejected. Those rejections accumulate silently if there is no real-time monitoring. By the time the finance team notices, several days of invoices may be legally unissued.

Mistake 4 – Ignoring corrective invoice rules. Corrective invoices issued after the mandatory date must reference the original KSeF number. If the original invoice was issued before KSeF's introduction, the corrective note must follow a transitional procedure defined by KAS. Czech companies that issued high volumes of paper invoices in 2025 will face this issue throughout 2026 and 2027. Failing to follow the transitional procedure invalidates the correction – and the associated VAT adjustment.

For a comparison of how these timelines differ in another neighbouring jurisdiction, see our parallel guide on the KSeF deadline timeline 2026–2027 for companies in Switzerland.

A specific situation – such as a Czech company with both a Polish NIP and a family foundation holding Polish real estate – requires advice that accounts for the interaction between KSeF, Polish tax law on foundations, and the transfer pricing rules applicable to intra-group property transactions. These intersections are not addressed by standard KSeF onboarding guides.

What to prepare before contacting a tax advisor:

List of all Polish NIP numbers held by the Czech group
Annual invoice volume to Polish VAT-registered buyers (in PLN)
Name and version of the ERP or billing system currently in use
Copies of the most recent intercompany invoices issued to Polish entities
Contact details for the Polish tax office handling the NIP registration

Providing these five items at the first meeting reduces advisory time by approximately two working days and accelerates the timeline to go-live.

Frequently asked questions

Q: Does a Czech company without a Polish VAT number need to use KSeF?

A: Not legally – the mandatory KSeF obligation applies only to entities with a Polish NIP. However, Polish buyers are increasingly inserting contractual clauses requiring KSeF-compatible invoices as a condition of payment. A Czech supplier without a Polish NIP should assess whether voluntary VAT registration and KSeF access is commercially necessary given its Polish client base. Voluntary registration takes 4–6 weeks and grants immediate KSeF access.

Q: How long does it take to integrate an ERP system with KSeF, and what does it cost?

A: For a standard ERP with an existing API layer, technical integration typically takes 4–8 weeks. Costs vary between EUR 8,000 and EUR 40,000 depending on system complexity and the number of invoice templates requiring adaptation. Companies using legacy billing systems without API capability may need an intermediary software layer, which adds 2–4 weeks and additional cost. Budget should also cover legal review of the FA(2) XML template before go-live.

Q: Is it a common misconception that KSeF only applies to large Polish companies?

A: Yes – and it is the most expensive misconception in the market. KSeF applies to all VAT-registered taxpayers in Poland, regardless of size, from 1 April 2026. The 1 February 2026 date applies only to large taxpayers above the PLN 200m threshold. A small Czech company with a Polish NIP and modest turnover is fully subject to KSeF from 1 April 2026. Treating the obligation as a "large company issue" and delaying preparation by three months exposes the company to the full penalty regime from day one of non-compliance.

Our Polish tax practice advises Czech, German, and other foreign entities at every stage of KSeF onboarding – from NIP registration through XML template review to post-go-live audit support.

Every Czech company with Polish invoicing exposure has a specific situation. The combination of NIP status, invoice volume, ERP system, and intercompany structure determines which steps are urgent and which can be sequenced. Delaying that assessment past October 2025 forfeits the preparation window for the 1 February 2026 deadline – and that window does not reopen.

If your Czech entity issues invoices to Polish buyers and you have not yet mapped your KSeF obligations, contact our team now. We will assess your NIP status, review your invoice flows, and deliver a KSeF readiness plan with a concrete timeline: info@kordeckipartners.com.

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 tax compliance, KSeF onboarding, and cross-border VAT advisory. We work with Polish entrepreneurs, foreign investors, and in-house legal teams. To discuss your situation, contact info@kordeckipartners.com.