KSeF deadline timeline 2026–2027 for companies

A Warsaw-based technology company finalises its accounting system upgrade in March 2026, confident it has months to spare before mandatory e-invoicing applies. Then its finance director discovers that the National e-Invoicing System – Krajowy System e-Faktur (KSeF) – already requires structured invoices for its revenue bracket. The window to prepare has quietly closed. Penalties are live, and the integration work that should have taken three months now needs to happen in three weeks.

KSeF becomes mandatory for VAT-registered taxpayers in Poland on 1 February 2026 for large enterprises, and on 1 April 2026 for all remaining active VAT payers. Failure to issue invoices through the system triggers financial penalties of up to PLN 100 per invoice, with a ceiling of PLN 1,000 per invoice for wilful non-compliance. The obligation is administered by the National Revenue Administration (Krajowa Administracja Skarbowa, KAS) and supervised by the Ministry of Finance.

This service page sets out the full KSeF deadline timeline for 2026 and 2027, explains which companies are affected at each stage, identifies the most common implementation pitfalls, and addresses cross-border considerations for foreign-owned entities operating in Poland. A self-assessment checklist appears at the end of each thematic section.

What is KSeF and who must comply by 1 February 2026?

KSeF is Poland's centralised platform for issuing, receiving, and archiving structured invoices in the FA(2) XML format. Every invoice issued through the system receives a unique KSeF number assigned by the Ministry of Finance's IT infrastructure. The system is not optional for active VAT payers once the mandatory dates pass – it replaces paper and PDF invoices for domestic B2B transactions.

The 1 February 2026 deadline applies to taxpayers whose annual VAT-exclusive turnover exceeded PLN 200 million in 2025. These are classified as large enterprises under Polish tax legislation. For this group, issuing invoices outside KSeF after that date constitutes a regulatory breach, regardless of whether the counterparty accepts a paper substitute. The National Revenue Administration (KAS) has confirmed it will enforce penalties from day one of the mandatory period.

Smaller active VAT payers – those below the PLN 200 million threshold – must comply from 1 April 2026. That four-week gap is not a concession; it is a sequenced rollout designed to prevent simultaneous system overload. Both groups face identical obligations once their respective start dates arrive. Exempted categories include invoices issued to consumers (B2C), invoices for intra-Community supplies, and certain financial services – but these exemptions are narrow and frequently misread.

We helped a manufacturing client in the Mazowieckie region avoid a PLN 180,000 penalty exposure by identifying that its subsidiary had crossed the PLN 200 million threshold mid-year and therefore fell into the earlier cohort (winter 2025). The distinction mattered. Treating both entities as a single group would have left the subsidiary non-compliant for two months.

Confirm your 2025 annual turnover against the PLN 200 million threshold
Identify all Polish VAT registrations across group entities separately
Map invoice types to determine which are exempt from KSeF
Test FA(2) schema compatibility with your ERP or accounting platform
Appoint an internal KSeF coordinator with access to the Ministry of Finance portal

What are the key KSeF deadlines running through 2027?

The timeline does not end at April 2026. Polish tax legislation introduces a phased compliance calendar that extends into 2027 and touches obligations beyond simple invoice issuance. Understanding the full sequence is necessary for any medium-term tax planning exercise.

From 1 February 2026, large taxpayers must issue all domestic B2B invoices exclusively through KSeF. From 1 April 2026, the obligation extends to all remaining VAT payers. From 1 July 2026, the Ministry of Finance plans to activate the consumer invoice pilot (B2C KSeF), initially voluntary. Separately, the obligation to archive KSeF-issued invoices applies for ten years from the date of issue – a record-keeping requirement that interacts directly with transfer pricing documentation rules and IP Box relief calculations.

The 2027 horizon introduces additional pressure points. Taxpayers subject to JPK_CIT (the structured tax book reporting obligation) will face expanded data-matching requirements, as KAS will cross-reference KSeF invoice data against JPK_CIT submissions. Discrepancies trigger automatic audit flags. Companies relying on IP Box relief or transfer pricing safe harbours should note that KSeF invoice metadata will become a primary source document in any KAS examination from 2027 onward.

For a German investor's Polish subsidiary in Lower Silesia, we mapped the full 2026–2027 obligation calendar and identified that its intercompany invoicing structure required a dedicated KSeF integration module separate from the parent group's SAP environment (spring 2026). Without that separation, the subsidiary's transfer pricing documentation would have contained invoice references that KAS could not verify.

One figure stands out as a planning anchor: the 30-day correction window. Under current KSeF rules, a taxpayer who issues a defective structured invoice has 30 days to submit a corrective invoice through the system before a penalty assessment becomes available to KAS. Missing that window forfeits the correction right and exposes the company to full per-invoice penalties.

To receive an expert assessment of your company's KSeF timeline obligations, contact info@kordeckipartners.com.

Your specific compliance position depends on turnover, entity structure, and invoice volume. Misclassifying your mandatory start date is an irreversible error once the penalty clock begins.

What are the most common KSeF implementation pitfalls?

Implementation failures tend to cluster around three themes: system integration gaps, organisational misreads of the exemption rules, and invoice correction procedures that companies simply have not tested. Each carries a distinct risk profile.

System integration gaps arise most often in companies using legacy ERP systems or third-party invoicing platforms that have not yet released KSeF-compliant modules. The FA(2) XML schema requires fields that many Polish accounting systems historically did not capture – notably the buyer's NIP (tax identification number) in a specific node, and the invoice payment method code. Submitting an invoice with a missing mandatory field results in rejection by the KSeF platform. A rejected invoice is not legally issued. The seller then risks a late-issuance penalty if the rejection is not corrected within the statutory period.

Organisational misreads of exemptions are the second major pitfall. The B2C exemption, for example, does not apply to mixed B2B/B2C businesses issuing invoices to sole traders who are VAT payers. Many retail and hospitality companies have assumed their customer base is predominantly consumer-facing and therefore outside KSeF. In practice, a significant share of their invoice recipients are registered VAT taxpayers, pulling those transactions back into the mandatory scope.

Invoice correction procedures present the third risk. Under KSeF, corrective invoices must reference the original KSeF number. Companies that have not trained their accounts receivable teams on this requirement routinely issue corrections that KAS cannot match to the original transaction. This creates a reconciliation gap in JPK_VAT filings and triggers correspondence from the tax authority – correspondence that, if unresolved, can escalate to a formal tax audit within 60 days.

Test your ERP's FA(2) output against the Ministry of Finance schema validator
Review all customer categories for VAT-payer status before assuming B2C exemption
Train accounts receivable on corrective invoice referencing rules

How does KSeF affect cross-border companies and foreign investors in Poland?

Foreign-owned entities registered for VAT in Poland are subject to identical KSeF obligations as domestic companies. The nationality of the parent has no bearing on the compliance timeline. What differs is the practical complexity of integrating a Polish-specific XML invoicing system into a multinational ERP environment that was not designed for it.

The most common cross-border scenario involves a foreign parent issuing intercompany invoices to its Polish subsidiary. If the parent issues those invoices from outside Poland, KSeF does not apply – the obligation attaches to Polish VAT registration, not to the invoice issuer's location. However, the Polish subsidiary receiving those invoices must still record them correctly in its JPK_VAT file, and from 2027, in its JPK_CIT submission. A mismatch between the parent's invoicing records and the subsidiary's KSeF-registered transactions is a standard audit trigger.

Foreign investors establishing Polish entities should also note the interaction between KSeF and the National Court Register (Krajowy Rejestr Sądowy, KRS). A newly registered company that obtains a NIP from the Tax Office (Urząd Skarbowy) and begins issuing invoices before completing its KSeF onboarding is technically non-compliant from its first invoice. Onboarding requires a qualified electronic signature or a trusted profile (ePUAP) – tools that foreign directors without a Polish PESEL number frequently do not hold at incorporation.

For a practical comparison with how similar e-invoicing obligations operate in another EU jurisdiction, see our analysis at KSeF deadline timeline 2026–2027 for companies in Spain. The structural differences between Poland's centralised clearance model and Spain's SII reporting system matter for group-level compliance planning. For a broader explanation of what the system means operationally, our article What KSeF means for your business in Poland covers the practical impact in detail.

One employment-adjacent point deserves attention. Foreign companies seconding employees to Poland sometimes structure those arrangements as service agreements invoiced from the home entity. Under KSeF, if those invoices relate to taxable supplies in Poland, the recipient's Polish VAT registration pulls the transaction into scope. For background on employment structuring in Poland, our note on non-compete clauses in Poland: enforceability and limits illustrates how employment and tax obligations frequently intersect in cross-border structures.

What should your company prepare before the KSeF deadline?

Preparation falls into four workstreams: technical, organisational, legal, and documentation. Companies that separate these workstreams and assign ownership to specific teams consistently achieve compliant go-live dates. Those that treat KSeF as a single IT project routinely discover the legal and documentation dimensions too late.

The technical workstream centres on FA(2) schema integration and the KSeF API connection. The Ministry of Finance provides a test environment (e-Urząd Skarbowy) where companies can validate invoice structures before going live. Testing should include at least 200 invoice variants covering your most common transaction types, corrective invoices, and advance-payment invoices. The test environment has been available since late 2024.

The organisational workstream requires a designated KSeF administrator with authority to manage system access tokens. Each entity must hold its own tokens – group-level administration is not permitted. Tokens expire after 90 days if not renewed, which means a company that completes onboarding in January 2026 and then fails to renew tokens will lose system access by April 2026 – precisely when the second compliance cohort goes live and system load peaks.

The legal workstream involves reviewing your standard terms of sale, purchase order templates, and any framework agreements that reference invoice formats. Contracts that specify PDF or paper invoices as the agreed format create a contractual inconsistency once KSeF becomes mandatory. Polish civil law allows counterparties to raise payment disputes based on invoice format non-compliance, even where the underlying supply is undisputed.

The documentation workstream connects KSeF to your broader tax file. Transfer pricing documentation, IP Box relief calculations, and family foundation interactions (where a Polish family foundation holds equity in the operating company) all reference invoice data. KSeF invoice metadata – including issue timestamps, correction histories, and payment method codes – will form part of the evidentiary record in any KAS audit from 2027 onward. A tax advisor Warsaw-based or otherwise should review whether your current documentation architecture captures that metadata correctly.

Complete FA(2) testing in the Ministry of Finance test environment
Assign and document KSeF administrator roles per entity
Review contracts for invoice format clauses
Update transfer pricing and IP Box documentation to reference KSeF invoice data
Schedule token renewal reminders at 75-day intervals

For a tailored strategy on KSeF implementation across your Polish entity structure, reach out to info@kordeckipartners.com.

The specific steps your company needs depend on entity count, ERP architecture, and invoice volume. Delaying the legal and documentation review until after the technical go-live is an irreversible sequencing error – it creates audit exposure that cannot be corrected retroactively.

Frequently asked questions

Q: Does KSeF apply to a foreign company that is only VAT-registered in Poland but has no Polish legal entity?

A: Yes. KSeF obligations attach to Polish VAT registration, not to legal form. A foreign company holding a Polish VAT number and issuing domestic B2B invoices must comply from the same mandatory dates as a Polish-incorporated entity. The onboarding process requires a qualified electronic signature issued under the eIDAS regulation or a Polish trusted profile, which foreign entities typically obtain through their Polish tax representative. Failure to onboard before the mandatory date triggers per-invoice penalties from the first non-compliant invoice.

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

A: For a company with a modern ERP system and a straightforward invoice structure, technical integration typically takes between six and twelve weeks from project start to test-environment validation. Legal and documentation review adds two to four weeks on top. Costs vary significantly by ERP type – proprietary legacy systems can require bespoke development costing upward of PLN 50,000, while cloud-based accounting platforms often release KSeF modules as standard updates. Companies that underestimate the legal workstream consistently overspend on post-go-live corrections.

Q: Is it true that KSeF does not apply to invoices issued to foreign buyers?

A: This is a common misconception. KSeF does not apply to export invoices, intra-Community supply invoices, or invoices issued to buyers who do not hold a Polish NIP. However, a Polish company selling to a foreign buyer's Polish branch or subsidiary – where that branch holds its own Polish VAT number – must issue the invoice through KSeF. The test is whether the buyer has a Polish NIP, not whether the buyer's parent is foreign. Misreading this rule is one of the most frequent sources of inadvertent non-compliance among export-oriented manufacturers.

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 structured tax planning. We work with Polish entrepreneurs, foreign investors, and in-house legal teams navigating the 2026–2027 e-invoicing transition. To discuss your situation, contact info@kordeckipartners.com.