KSeF deadline timeline 2026–2027 for companies in Switzerland

A Swiss-based trading company invoices its Polish subsidiary every month. The arrangement runs smoothly – until a Polish tax audit flags every invoice issued outside the Krajowy System e-Faktur (National e-Invoice System, KSeF) as potentially non-compliant. The exposure is not abstract. Under Polish tax legislation, buyers who receive invoices outside the mandatory KSeF channel may lose the right to deduct input VAT. That consequence is irreversible once the assessment period closes.

KSeF becomes mandatory for large Polish taxpayers on 1 February 2026 and for all remaining VAT-registered entities on 1 April 2026. Swiss companies with a Polish VAT registration or a permanent establishment in Poland fall within scope from the relevant date. Failure to issue structured invoices through KSeF after the applicable deadline triggers penalties of up to PLN 100 per invoice and, more significantly, exposes the buyer to loss of VAT deduction rights.

This guide walks through the full KSeF deadline timeline for 2026 and 2027, explains which Swiss entities are caught, and sets out a practical compliance roadmap. The article also covers three business scenarios, common mistakes, and a step-by-step checklist. Where relevant, it flags how KSeF interacts with transfer pricing documentation and IP Box arrangements – two areas where Swiss groups frequently have Polish exposure.

What is KSeF and which Swiss entities does it cover?

KSeF is a centralised government platform operated by the Krajowa Administracja Skarbowa (National Revenue Administration, KAS). It receives, validates, and stores structured XML invoices in real time. Every invoice issued through KSeF receives a unique identification number. That number is the only proof of issue recognised by Polish tax authorities after the mandatory start date.

A Swiss company falls within mandatory KSeF scope if it holds a Polish VAT registration number (NIP) – regardless of whether it has a physical presence in Poland. This includes Swiss entities registered solely for VAT purposes, for example to account for goods stored in a Polish warehouse. A Swiss company with a permanent establishment registered with the Krajowy Rejestr Sądowy (National Court Register, KRS) is equally covered. The Ministerstwo Finansów (Ministry of Finance) confirmed this interpretation in its published guidance in late 2025.

Three categories of Swiss entity are most commonly affected. First, Swiss manufacturers selling goods through a Polish distribution subsidiary and issuing intercompany invoices. Second, Swiss technology companies licensing IP to Polish entities – a scenario that intersects directly with IP Box claims. Third, Swiss holding groups with Polish subsidiaries that invoice management fees or intragroup services. In all three cases, the invoicing obligation sits with the Polish-VAT-registered entity, not with the Swiss parent acting purely in a foreign capacity.

One practical clarification: a Swiss company that sells to Polish buyers but has no Polish VAT number is not directly subject to mandatory KSeF. It may, however, receive KSeF-issued invoices from Polish suppliers and must be able to process the structured format. That is a separate, but real, operational requirement.

What are the key KSeF deadlines for 2026 and 2027?

The timeline has three firm dates. Each carries a different scope of obligation. Missing any of them closes the door to voluntary correction without penalty exposure.

The first date is 1 February 2026. From this date, KSeF is mandatory for taxpayers whose annual VAT turnover exceeded PLN 200 million in 2024. Swiss groups with large Polish subsidiaries or branches will typically cross this threshold. The obligation covers B2B invoices issued within Poland. B2C invoices remain outside mandatory KSeF scope for now, though voluntary use is permitted.

The second date is 1 April 2026. From this date, KSeF is mandatory for all remaining VAT-registered taxpayers in Poland – including smaller Polish entities and foreign entities with a Polish NIP. This is the date most relevant to Swiss companies that registered for VAT in Poland without crossing the PLN 200 million threshold. After 1 April 2026, issuing a paper or PDF invoice to a Polish VAT-registered buyer is not a minor irregularity. It is a structural non-compliance.

The third date is 1 April 2027. From this date, the obligation extends to invoices issued under the VAT margin scheme and certain other currently excluded categories. Swiss entities operating in sectors such as tourism or second-hand goods should note this extension.

• 1 February 2026 – mandatory KSeF for taxpayers above PLN 200m annual VAT turnover
• 1 April 2026 – mandatory KSeF for all remaining VAT-registered entities
• 1 April 2027 – extension to margin-scheme and currently excluded invoice types
• Ongoing – KAS may conduct real-time audits using KSeF data from day one

We helped a Swiss-owned logistics group operating in the Mazowieckie region secure a compliant KSeF onboarding for three Polish entities before the February 2026 deadline (winter 2025–2026). The group had initially underestimated the lead time required to integrate its ERP system with the KSeF API. Early engagement – roughly 90 days before the deadline – proved essential.

How does the step-by-step compliance process work?

KSeF compliance is not a single registration event. It is a process with five distinct stages, each requiring internal coordination between finance, IT, and legal teams. Swiss companies managing this from Zurich or Geneva often underestimate the coordination burden.

Stage one is scope confirmation. Identify every Polish NIP held by entities in the Swiss group. Check whether any entity crossed the PLN 200 million threshold for the February 2026 date. Confirm whether any entity issues margin-scheme invoices. This stage should be completed at least 90 days before the applicable deadline.

Stage two is technical integration. KSeF operates via a REST API. Invoice data must be submitted in the FA(2) structured XML schema. Most major ERP vendors – SAP, Oracle, Microsoft Dynamics – have released KSeF-compatible modules. However, customisations take time. Budget at minimum 60 days for testing in the KSeF sandbox environment, which KAS makes available free of charge.

Stage three is authorisation setup. Each entity must designate a KSeF token holder. This is typically the entity's legal representative or a specifically authorised accountant. The authorisation is registered directly in the KSeF system using the entity's NIP and a qualified electronic signature or a Trusted Profile (Profil Zaufany).

Stage four is staff and process training. Polish invoicing rules contain specific requirements around mandatory fields in the FA(2) schema. Missing a required field causes the invoice to be rejected by KSeF in real time. A rejected invoice has no legal status until resubmitted correctly. That gap can disrupt payment terms and cash flow.

Stage five is ongoing monitoring. KAS has stated publicly that it will use KSeF data for automated cross-matching against VAT returns (JPK_V7) from the first day of mandatory use. Discrepancies trigger enquiries within weeks, not months. Assign internal ownership for monthly reconciliation between KSeF-issued invoice logs and JPK_V7 submissions.

What are the three business scenarios for Swiss companies?

Swiss entities interact with KSeF in meaningfully different ways depending on their Polish structure. Three scenarios cover the most common configurations.

Scenario A – Swiss manufacturer with a Polish distribution subsidiary. The Swiss parent sells goods to its Polish subsidiary, which then sells to Polish end customers. The Polish subsidiary is the KSeF-obligated entity for all B2B sales invoices it issues. The intercompany invoice from the Swiss parent to the Polish subsidiary – if the Swiss parent has no Polish NIP – falls outside mandatory KSeF scope. However, the Polish subsidiary must issue KSeF invoices to its customers from the applicable deadline. Transfer pricing documentation covering the intercompany price must be consistent with the prices appearing in KSeF records, since KAS can cross-reference both data sets. For more on structuring the Polish entity correctly, see our guide on sp. z o.o. vs SA decision matrix for Switzerland investors.

Scenario B – Swiss technology licensor with IP Box exposure. A Swiss company licenses software IP to a Polish subsidiary. The Polish entity claims an IP Box preferential rate on qualifying income. KSeF invoices issued by the Polish entity to its customers will be cross-matched by KAS against the IP Box calculation. Any mismatch between declared qualifying revenue and KSeF-issued invoices is a red flag. This scenario requires close coordination between the KSeF compliance team and the tax advisor managing the IP Box claim.

Scenario C – Swiss holding with a Polish family foundation or operating subsidiary. Swiss groups increasingly use Polish family foundations (fundacje rodzinne) alongside operating subsidiaries. The foundation itself is generally not a VAT taxpayer and does not issue KSeF invoices. The operating subsidiary below it does. For a comparison of structural options, see our analysis of family foundation vs holding company. The key compliance point: ensure the operating subsidiary's KSeF onboarding is not delayed by governance questions at the foundation level.

We assisted a Zurich-based technology group with two Polish subsidiaries in Lower Silesia in reconciling their IP Box claims against projected KSeF invoice volumes (spring 2026). The exercise identified a PLN 1.4 million discrepancy between declared qualifying revenue and invoiced amounts – caught before the annual CIT filing deadline.

What mistakes do Swiss companies most commonly make?

Four errors appear repeatedly in the Swiss-company context. Each is avoidable with early preparation.

The first mistake is assuming the deadline does not apply. Some Swiss finance teams believe KSeF is a domestic Polish matter that affects only locally managed entities. If the Polish subsidiary or branch holds a Polish NIP, the obligation applies – regardless of where the parent is based or who manages the accounts. The Urząd Skarbowy (Tax Office) does not distinguish between locally and remotely managed Polish VAT registrations.

The second mistake is late ERP integration. Swiss groups with centralised finance functions in Zurich or Geneva often process Polish invoices through a shared service centre. Integrating that centre's ERP with the KSeF API takes longer than expected. Companies that started the process fewer than 45 days before the deadline consistently ran into testing delays. Ninety days is the minimum realistic lead time.

The third mistake is ignoring the double-tax treaty dimension. The double tax treaty between Poland and Switzerland affects how certain income streams are characterised for CIT purposes. KSeF data will be used by KAS to verify that invoiced amounts are consistent with treaty-based income allocations. A Swiss company that invoices management fees to its Polish entity should ensure those fees are documented consistently across KSeF records, transfer pricing files, and treaty-based CIT positions.

The fourth mistake is failing to test rejection scenarios. KSeF rejects invoices with missing or incorrect mandatory fields in real time. Many companies discover their FA(2) schema implementation has gaps only after going live. A rejected invoice is not automatically corrected – it must be resubmitted. In the meantime, the buyer has no valid input VAT document. That is a cash-flow and compliance risk simultaneously.

What should Swiss companies prepare before the KSeF deadline?

The checklist below applies to any Swiss entity with a Polish VAT registration. It is sequenced by priority, not alphabetically.

• Confirm all Polish NIP numbers held by group entities and map each to the applicable KSeF deadline (February or April 2026)
• Engage ERP vendor or IT team to begin FA(2) schema integration at least 90 days before the deadline
• Register KSeF token holder for each Polish entity using a qualified electronic signature
• Run full invoice-cycle testing in the KSeF sandbox, including rejection and resubmission scenarios
• Align transfer pricing documentation with expected KSeF invoice volumes and values

One further point on cost: KSeF itself is free to use. The compliance cost lies in ERP integration, legal advice, and internal project management. For a mid-sized Swiss group with two or three Polish entities, budget between CHF 15,000 and CHF 40,000 for full technical and legal onboarding, depending on ERP complexity and the number of invoice types in scope.

The specific situation of your Polish entities may carry irreversible VAT deduction risk if KSeF onboarding is delayed past the applicable deadline. Early assessment prevents forfeiture of input tax that cannot be recovered retroactively.

To receive an expert assessment of your group's KSeF exposure and compliance timeline, contact info@kordeckipartners.com.

Frequently asked questions

Q: Does a Swiss company without a physical presence in Poland need to use KSeF?

A: Yes, if the Swiss company holds a Polish VAT registration number. Physical presence is not the deciding factor. Any entity with a Polish NIP that issues B2B invoices to Polish VAT-registered buyers must use KSeF from the applicable deadline. A Swiss company with no Polish NIP is not directly obligated but may receive KSeF-issued invoices from Polish suppliers and should be able to process the structured XML format.

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

A: For a group using a major ERP platform with an available KSeF module, integration and testing typically takes 60 to 90 days. For bespoke or legacy systems, allow up to 120 days. Direct platform costs are zero – KSeF is a free government service. Total project costs, including ERP customisation, legal advice, and staff training, typically range from CHF 15,000 to CHF 40,000 for a Swiss group with two to three Polish entities.

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

A: Yes. The PLN 200 million threshold determines only which entities must comply from 1 February 2026 rather than 1 April 2026. All VAT-registered entities in Poland – regardless of size or foreign ownership – are subject to mandatory KSeF from 1 April 2026. Swiss companies that registered for VAT in Poland to handle warehouse or distribution activity are fully within scope, even if their Polish turnover is modest.

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 for Swiss and other foreign investors. We work with Polish entrepreneurs, foreign investors, and in-house legal teams. To discuss your situation, contact info@kordeckipartners.com.

Disclaimer: This publication is provided for informational purposes only and does not constitute legal advice. The information herein should not be relied upon as a substitute for professional legal counsel tailored to your specific circumstances. KORDECKI & Partners assumes no liability for actions taken or not taken based on the contents of this material. For advice regarding your particular situation, please contact info@kordeckipartners.com.