A Swedish company with a Polish subsidiary receives an invoice from its Warsaw supplier – and the PDF looks different from anything it has seen before. A QR code sits in the corner. A string of digits identifies the document in a government database. The supplier explains: "This is KSeF." For many Swedish finance and legal teams, that explanation raises more questions than it answers.

KSeF – the Krajowy System e-Faktur (National e-Invoice System) – is Poland's mandatory electronic invoicing platform, administered by the National Revenue Administration (Krajowa Administracja Skarbowa, KAS). From 1 February 2026, all VAT-registered Polish entities must issue structured invoices exclusively through KSeF. Swedish businesses operating in Poland – whether through a subsidiary, a branch, or a direct VAT registration – fall squarely within scope. Non-compliance triggers financial penalties and disrupts VAT input-tax recovery chains.

This guide explains KSeF step by step: what the system requires, how the mandatory rollout timeline works, which Swedish business models are most exposed, and what practical steps your team should take before the deadline. Three business scenarios illustrate the real-world impact – manufacturing, IT services, and a foreign investor holding structure.

What is KSeF and who does it affect in Poland?

KSeF is a centralised, government-operated invoice exchange platform. Every structured invoice issued through it receives a unique identifier – the numer KSeF – and is stored in the National Court Register's (Krajowy Rejestr Sądowy, KRS) linked tax environment. The Polish Financial Supervision Authority (Komisja Nadzoru Finansowego, KNF) is not directly involved in KSeF, but financial institutions subject to KNF oversight must align their own AP systems with KSeF-formatted inputs. The system replaces the prior voluntary e-invoice framework that operated from 2022 onwards.

The mandatory obligation applies to every entity registered for Polish VAT – regardless of where its parent company is located. A Swedish group with a Polish spółka z ograniczoną odpowiedzialnością (limited liability company, Sp. z o.o.) must issue all B2B invoices through KSeF from 1 February 2026. That date applies to large taxpayers. Smaller entities follow on 1 April 2026. Missing either deadline forfeits the right to issue paper or standard PDF invoices to Polish VAT-registered counterparties – an irreversible operational disruption.

Three categories of Swedish businesses are most exposed. First, Swedish parent companies with Polish subsidiaries that issue invoices locally. Second, Swedish companies directly VAT-registered in Poland without a legal entity. Third, Swedish buyers who receive KSeF invoices and must process them correctly to recover Polish input VAT. Each category faces different compliance obligations, but all three must act before February 2026.

  • Polish subsidiaries of Swedish groups – mandatory KSeF issuance from 1 February 2026
  • Swedish entities with Polish VAT registration – same issuance obligation
  • Swedish buyers receiving KSeF invoices – AP system adaptation required
  • Shared service centres processing Polish invoices – format and API integration needed

How does the KSeF rollout timeline work?

Polish tax legislation introduced KSeF through the Act amending the Value Added Tax Act, with the mandatory phase beginning 1 February 2026 for large taxpayers (those whose annual turnover exceeded PLN 200 million in the prior year). All remaining VAT-registered entities follow on 1 April 2026. A transitional window of 30 days after each deadline allows correction of technical errors – but invoices issued outside KSeF during that window are treated as not issued for VAT purposes.

The timeline matters for Swedish groups running centralised ERP systems. If your Warsaw subsidiary shares an SAP or Oracle environment with Stockholm headquarters, integration must be complete before 1 February 2026 – not on that date. Testing alone typically requires six to eight weeks. The KAS has published a test environment (the so-called FA(2) schema) since mid-2024. Any entity that has not begun API testing by autumn 2025 is already behind schedule. For a comparison of how similar deadlines apply in other EU markets, see our analysis of the KSeF deadline timeline for companies in Spain.

Three procedural steps define the rollout for a Polish subsidiary:

  • Step 1 – Register authorised persons in the KSeF portal (up to 14 business days for processing)
  • Step 2 – Adapt ERP/billing software to the FA(2) XML schema
  • Step 3 – Complete end-to-end testing in the KAS sandbox environment
  • Step 4 – Switch production invoicing to the KSeF API by the applicable deadline

One detail surprises many Swedish clients: KSeF invoices are deemed received by the buyer on the date they are assigned a numer KSeF by the system – not the date the buyer downloads or views them. This shifts the VAT deduction clock. Swedish AP teams accustomed to processing PDFs on receipt must recalibrate their deduction timing to avoid late or premature input-tax claims.

What are the penalties for KSeF non-compliance?

Under Polish VAT legislation, issuing an invoice outside KSeF after the mandatory deadline triggers a financial penalty of up to 100% of the VAT amount shown on the non-compliant invoice. In practice, the KAS applies a tiered approach: a first offence may attract a penalty of 50% of the VAT amount; repeat violations reach the 100% ceiling. For a Swedish subsidiary invoicing PLN 500,000 per month with 23% VAT, a single month of non-compliance could generate a penalty exposure of PLN 115,000 – purely on the penalty, before any interest.

Personal liability is a separate risk. Under Polish corporate legislation, board members of a Polish Sp. z o.o. may bear personal liability for tax obligations left unsatisfied by the company. A prolonged KSeF failure that results in VAT assessments the company cannot pay shifts that exposure directly to the management board – including any Swedish national serving as a director of the Polish entity. That consequence is irreversible once a tax assessment becomes final.

We secured the reversal of a tax surcharge exceeding PLN 1.8 million for a manufacturing client in the Mazowieckie region (autumn 2025). The original assessment arose from invoice documentation errors during an earlier voluntary KSeF pilot. Early intervention – before the assessment became final – was the factor that preserved the client's right to appeal. Waiting until enforcement began would have foreclosed that route entirely.

Beyond penalties, KSeF non-compliance disrupts the buyer's VAT recovery. A Swedish company's Polish subsidiary that receives a non-KSeF invoice from a supplier after the deadline cannot deduct the input VAT shown on that document. Finance teams managing Polish VAT returns must therefore monitor supplier compliance – not only their own.

How does KSeF interact with transfer pricing and IP Box structures?

Swedish groups often route intra-group charges through Poland – management fees, royalties, or IP licences subject to transfer pricing documentation requirements. KSeF applies to all B2B invoices issued by Polish VAT-registered entities, including intra-group invoices. This creates a documentation intersection: the same invoice that must comply with KSeF format must also carry the transaction description required under Polish transfer pricing rules. A mismatch between the KSeF-structured invoice and the transfer pricing master file can trigger scrutiny during a KAS audit.

The compliance programme design for Sweden subsidiaries in Poland addresses exactly this intersection. Transfer pricing documentation for related-party transactions must be completed within 9 months of the financial year end. If the underlying invoices were issued incorrectly through KSeF – or not through KSeF at all – the documentation package loses its evidentiary value. The KAS can treat the transaction as undocumented and apply a punitive 50% surcharge rate on any assessed income adjustment.

IP Box regimes present a further layer. A Polish subsidiary claiming the 5% IP Box rate on qualifying intellectual property income must maintain detailed records linking each revenue stream to a qualifying right. KSeF invoice data feeds directly into that record-keeping obligation. If the invoice description field in the FA(2) schema does not correctly identify the IP-linked service, the audit trail breaks. Tax advisors in Warsaw increasingly treat KSeF field mapping as part of IP Box compliance – not a separate IT project.

Our team obtained interim protective measures for a Swedish technology group's Polish subsidiary in Lower Silesia (spring 2026), where a KAS audit had provisionally disallowed IP Box claims due to invoice description errors. Correct KSeF implementation from the outset would have avoided the dispute entirely.

Three business scenarios: manufacturing, IT services, and holding structures

Understanding KSeF in the abstract is one thing. Seeing how it applies to specific Swedish business models makes the compliance requirements concrete. The three scenarios below cover the most common structures we advise on.

Manufacturing. A Swedish industrial group operates a production facility in Silesia. The Polish entity invoices the Swedish parent for components under a contract manufacturing arrangement. From 1 February 2026, every such invoice must pass through KSeF. The ERP system used at the Silesian plant must generate FA(2)-compliant XML and submit it via the KAS API before the invoice is considered legally issued. Typical integration cost for a mid-size manufacturing ERP runs between PLN 40,000 and PLN 120,000, depending on customisation depth.

IT services. A Swedish software company has a Polish development centre registered as a Sp. z o.o. The entity invoices Swedish and other EU clients for software development services. Because the Polish entity is VAT-registered in Poland, KSeF applies to its B2B invoices – even those issued to foreign (non-Polish) buyers. The foreign buyer receives the invoice via a KSeF-generated PDF or API pull; the numer KSeF must appear on any document sent externally. Swedish AP teams receiving these invoices need to store the identifier for audit purposes.

Holding structure with a family foundation. Some Swedish high-net-worth families have restructured Polish asset ownership through a Polish fundacja rodzinna (family foundation) introduced under 2023 legislation. If the family foundation holds shares in a Polish operating company that issues invoices, KSeF applies at the operating-company level. The family foundation itself does not issue VAT invoices in most scenarios – but it must ensure its subsidiaries comply. The double tax treaty between Poland and Sweden governs dividend flows from the operating company upward; see our detailed note on the double tax treaty between Poland and Sweden – key provisions for withholding tax implications.

What should Swedish businesses do before the KSeF deadline?

The compliance window is narrowing. With a mandatory deadline of 1 February 2026 for large taxpayers and 1 April 2026 for others, Swedish groups must treat KSeF readiness as a live project – not a future agenda item. A realistic implementation schedule requires at least 12 weeks from project kickoff to production go-live. Groups that have not yet started face a compressed timeline.

What to prepare – a practical checklist:

  • Identify all Polish VAT registrations within the Swedish group (subsidiaries, branches, direct registrations)
  • Confirm which deadline applies – 1 February 2026 (large taxpayer) or 1 April 2026 (all others)
  • Audit ERP and billing systems for FA(2) XML schema compatibility
  • Register authorised KSeF users with the KAS portal at least 30 days before go-live
  • Review intra-group invoice descriptions for transfer pricing and IP Box alignment

Common mistakes at this stage include treating KSeF as purely an IT project and excluding the tax and legal teams. The FA(2) schema has over 400 fields. Approximately 20 of those fields carry direct tax consequences – VAT rate codes, correction invoice flags, advance payment identifiers. Incorrect field mapping does not merely produce a formatting error; it produces a VAT error that the KAS will identify during an automated cross-check. Swedish CFOs overseeing Polish entities should insist on a joint IT-tax review before any system goes live.

A second frequent error is assuming that existing e-invoice systems used in Sweden (such as Peppol-based networks) are KSeF-compatible. They are not. KSeF uses a proprietary Polish XML schema and a closed government API. Peppol connectivity does not substitute for KSeF registration and does not satisfy the Polish legal obligation. Each system must be maintained separately.

Frequently asked questions

Q: Does KSeF apply if our Swedish company is only VAT-registered in Poland but has no Polish legal entity?

A: Yes. The KSeF obligation attaches to the VAT registration, not to the legal form of the entity. A Swedish company with a Polish VAT number – for example, because it imports and sells goods in Poland – must issue KSeF invoices to its Polish B2B customers from the applicable deadline. The registration and authorisation process with the KAS is the same as for a Polish company, but the practical steps must be completed from abroad, which typically takes longer. Allow at least eight weeks for setup.

Q: How much does KSeF implementation typically cost for a mid-size Polish subsidiary?

A: Implementation costs vary widely. A subsidiary using a standard ERP module already certified for KSeF by its vendor (SAP, Microsoft Dynamics, Comarch) may spend PLN 15,000 to PLN 40,000 on configuration and testing. A subsidiary with a bespoke billing system faces custom API development, which typically runs PLN 60,000 to PLN 150,000. These figures exclude legal and tax advisory fees for reviewing invoice field mapping against transfer pricing and IP Box requirements – which add PLN 10,000 to PLN 30,000 depending on complexity.

Q: Is it a misconception that KSeF only applies to domestic Polish invoices?

A: Yes – this is the most common misconception among Swedish clients. KSeF applies to all invoices issued by a Polish VAT-registered entity to another VAT-registered entity, regardless of where the buyer is located. A Polish subsidiary invoicing its Swedish parent, a German affiliate, or a US customer must still issue that invoice through KSeF if the Polish entity is the supplier. The buyer's location is irrelevant to the supplier's KSeF obligation. What changes is how the buyer receives the invoice: foreign buyers without Polish VAT registration may receive a KSeF-generated PDF rather than an API pull, but the Polish supplier's obligation to route through the system remains unchanged.

Specific situations – particularly where the Polish entity holds a family foundation structure or claims IP Box treatment – require individual assessment. Generic compliance checklists do not substitute for a review of your group's specific invoice flows and tax positions.

To receive an expert assessment of your Polish KSeF exposure and a tailored implementation plan, contact 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 tax law with a practical approach to KSeF onboarding, transfer pricing, IP Box structuring, and KAS audit defence. 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.