A UK-registered company with a Polish subsidiary receives a notice from its Warsaw accountant: mandatory e-invoicing through the National e-Invoice System goes live in weeks. The finance director in London has never heard of KSeF. The subsidiary's bookkeeper is unsure whether the UK parent's invoices are even in scope. Time is short, and the penalties for non-compliance are not.

The Krajowy System e-Faktur (National e-Invoice System, KSeF) is Poland's centralised electronic invoicing platform, operated by the National Revenue Administration (Krajowa Administracja Skarbowa, KAS). Under Polish tax legislation, mandatory KSeF participation applies to all VAT-registered taxpayers conducting business in Poland – including subsidiaries, branches, and fixed establishments of foreign companies. For UK-headquartered groups with Polish operations, the go-live deadline is 1 February 2026 for large taxpayers and 1 April 2026 for remaining VAT-registered entities. Missing either date triggers financial penalties of up to PLN 100 per non-compliant invoice.

This guide walks through the KSeF timeline step by step, explains which UK-connected entities fall within scope, sets out the practical onboarding procedure, and identifies the mistakes that most commonly derail foreign-parent groups. Three business scenarios – a manufacturing subsidiary, an IT services branch, and a direct UK investor – illustrate how the rules apply in practice.

What is KSeF and why does it affect UK companies operating in Poland?

KSeF is a structured XML invoicing platform administered by the National Revenue Administration. Every compliant invoice receives a unique KSeF number within seconds of submission. That number becomes the legal proof of issue. Without it, a VAT deduction right may be challenged. For UK groups, this is not an abstract risk – it is a direct threat to working capital.

Scope turns on Polish VAT registration, not corporate nationality. A UK parent that holds a Polish VAT number – even without a physical office – falls within KSeF's mandatory perimeter. A Polish subsidiary with a UK shareholder is equally bound. The National Court Register (Krajowy Rejestr Sądowy, KRS) filing does not change the analysis. What matters is the Polish tax identification number (NIP) under which invoices are issued.

Three categories of UK-connected entities typically require attention. First, wholly owned Polish spółki z ograniczoną odpowiedzialnością (private limited liability companies, Sp. z o.o.). Second, registered branches (oddziały) of UK companies. Third, UK companies that have registered directly for Polish VAT without a local entity. Each category is subject to mandatory KSeF from the applicable 2026 deadline.

  • Polish Sp. z o.o. with UK parent – mandatory from 1 February 2026 (if large taxpayer) or 1 April 2026
  • Registered branch of a UK company – same deadlines, branch NIP governs
  • UK company with direct Polish VAT registration – mandatory from 1 April 2026
  • Non-VAT-registered entities – currently outside mandatory scope

The Polish Financial Supervision Authority (Komisja Nadzoru Finansowego, KNF) plays no direct role in KSeF, but regulated entities in the financial sector must align KSeF timelines with their own data-security governance. That coordination takes time. Groups that delay the internal compliance review until January 2026 routinely discover that IT procurement and legal sign-off alone require six to eight weeks.

What is the step-by-step KSeF onboarding timeline for 2026–2027?

Onboarding has five distinct phases. Each phase has a hard output, and skipping one creates problems in the next. UK-based finance teams often underestimate phase one – the Polish legal groundwork – because it sits outside their normal IT-project workflow.

Phase 1 – Entity and NIP audit (weeks 1–2). Confirm which Polish NIP numbers are in scope. A UK group may have multiple NIPs: the subsidiary, a historical branch registration, and a direct VAT registration from an older project. Each NIP requires a separate KSeF account. The audit should produce a definitive list before any technical work begins.

Phase 2 – Authorisation and token setup (weeks 3–4). KSeF access is controlled through the Ministry of Finance's (Ministerstwo Finansów, MF) e-invoicing portal. The legal representative of each entity must grant API tokens or interactive-session credentials. Foreign directors who lack a Polish trusted profile (Profil Zaufany) must use a qualified electronic signature instead. Obtaining a qualified signature from a UK-based director typically takes 10 to 14 business days.

Phase 3 – ERP/accounting system integration (weeks 5–10). The KSeF XML schema (FA(2) structure) must be mapped to the entity's existing invoice fields. Most UK-standard ERP systems – SAP, Oracle, Microsoft Dynamics – require a certified Polish add-on or middleware layer. Budget at least PLN 15,000–40,000 for a mid-size subsidiary integration, depending on invoice volume and system complexity.

Phase 4 – Test environment validation (weeks 11–12). KAS operates a free test environment. Every entity should run at least 50 test invoices covering standard supplies, corrections, and advance invoices before switching to production. This phase catches field-mapping errors that would otherwise produce rejected invoices in live operation.

Phase 5 – Go-live and monitoring (from deadline date). From the mandatory date, every B2B invoice issued under a Polish NIP must be submitted through KSeF in real time. A 60-day grace period for technical failures was discussed in the legislative process but has not been enacted in final form as of the date of this guide. Do not plan around it.

How do the three UK business scenarios differ in practice?

Polish tax law applies uniform KSeF rules, but the operational consequences vary significantly depending on how a UK group has structured its Polish presence. Three scenarios illustrate the range.

Scenario A – UK manufacturing group, Polish Sp. z o.o. subsidiary. A Midlands-based manufacturer supplies components through its Warsaw subsidiary to Polish automotive clients. The subsidiary issues roughly 300 B2B invoices per month. It qualifies as a large taxpayer (annual turnover above PLN 200m at group level). Mandatory KSeF applies from 1 February 2026. The subsidiary's SAP instance needs a Polish KSeF add-on. Lead time from contract signature to go-live is typically eight weeks. Starting in October 2025 is the safe timeline. Starting in December 2025 is a gamble.

Scenario B – UK IT services company, direct VAT registration in Poland. A London-based software firm sells licences to Polish corporate clients and holds a Polish VAT number with no local entity. It issues 20 invoices per month. It is not a large taxpayer. Mandatory KSeF applies from 1 April 2026. The firm's invoicing software does not support KSeF natively. Options include a third-party KSeF-certified invoicing tool (cost: PLN 200–800 per month) or a manual upload through the MF portal for low volumes. Transfer pricing documentation between the UK parent and any Polish-registered activity should be reviewed at the same time – a point often missed by IT firms that treat the Polish VAT registration as administrative rather than substantive.

Scenario C – UK private equity investor, Polish portfolio company. A London-based fund holds a controlling stake in a Polish retail chain. The chain is the KSeF obligor – the UK fund itself has no Polish NIP. However, the fund's management company may issue advisory invoices to the Polish entity. If those invoices are issued under a Polish NIP, they fall within KSeF scope. If issued under a UK VAT number only, they do not. Clarifying this distinction before 1 April 2026 prevents a compliance gap. For context on structuring Polish investments efficiently – including the use of a family foundation in Poland – the structural choices made at entry often determine the tax exposure years later.

What are the most common KSeF mistakes made by UK-connected groups?

Four errors appear repeatedly in our experience advising foreign-parent groups through KSeF onboarding. Each is avoidable. Each, left unaddressed, carries a direct financial cost.

Mistake 1 – Treating KSeF as a Polish IT project, not a legal compliance obligation. When the task is delegated entirely to the Warsaw IT team without legal oversight, the authorisation structure is often set up incorrectly. A token granted to the wrong entity or the wrong person creates a gap: invoices are submitted, but not by an authorised party. KAS may treat those invoices as not issued. The VAT deduction risk flows to the buyer, not just the seller.

Mistake 2 – Ignoring correction invoices. KSeF applies to corrective invoices (faktury korygujące) as well as standard invoices. ERP integrations that handle standard invoices correctly often fail on corrections because the XML schema differs. Test phase must include corrections. A UK manufacturing client in the Mazowieckie region avoided a six-figure VAT exposure in autumn 2025 after our team identified a correction-invoice mapping error during pre-go-live testing.

Mistake 3 – Missing the IP Box and transfer pricing interaction. UK groups that benefit from Poland's IP Box regime (a preferential 5% CIT rate on qualifying IP income) must ensure their KSeF invoice data aligns with their transfer pricing documentation. An inconsistency between invoiced amounts and the arm's length price in the TP file creates audit risk. This is not a theoretical concern – KAS cross-references KSeF data with JPK_CIT files from 2025 onwards.

Mistake 4 – Assuming the deadline will be extended again. KSeF was postponed twice: from 2023 to 2024, and then to 2026. A third postponement is not expected. The legislative record and MF communications as of late 2025 indicate firm commitment to the 2026 dates. Planning around a hoped-for extension forfeits the ability to complete onboarding in an orderly way.

  • Confirm all Polish NIP numbers in scope before starting technical work
  • Obtain qualified electronic signatures for foreign directors at least six weeks before deadline
  • Run test-environment validation with at least 50 invoices, including corrections
  • Review transfer pricing files for consistency with KSeF invoice data
  • Do not rely on a grace period that has not been enacted

For UK nationals who also hold Polish real property – and therefore receive rental invoices or issue them through a Polish entity – the KSeF rules interact with broader property-holding considerations. Our guide on buying property in Poland as a UK national addresses the structural choices that affect both VAT and income tax treatment.

One further point on cross-border treaty interaction: the Poland–US double tax treaty framework provides a useful comparator for understanding how Poland treats foreign-parent entities under its domestic rules. UK groups should note that post-Brexit, the UK–Poland double tax treaty remains in force independently of EU frameworks. Our analysis of the double tax treaty between Poland and the United States illustrates how treaty provisions interact with domestic compliance obligations – the analytical approach applies equally to the UK–Poland context.

Specific KSeF compliance situations require tailored legal input. Our team secured a full correction of a rejected-invoice sequence for a logistics client in Lower Silesia, preventing a VAT surcharge exposure of over PLN 800,000 (winter 2025). For a tailored strategy on KSeF onboarding for your UK-connected Polish entity, reach out to info@kordeckipartners.com.

Frequently asked questions

Q: Does KSeF apply to invoices issued by a UK company to a Polish customer if the UK company has no Polish VAT number?

A: No. KSeF applies only to invoices issued under a Polish NIP. A UK company without Polish VAT registration is outside the mandatory scope. However, the Polish customer cannot claim Polish VAT input on a non-KSeF invoice if the supplier was required to use KSeF. Confirming your registration status before the deadline is therefore important for both sides of the transaction.

Q: How long does KSeF onboarding realistically take for a mid-size subsidiary?

A: Allow 10 to 12 weeks from the start of the entity audit to go-live. The longest single step is ERP integration, which typically takes four to six weeks once the specification is agreed. Groups that begin in October 2025 for the 1 February 2026 deadline have adequate time. Groups starting in December 2025 face a compressed schedule that increases the risk of errors in the test phase.

Q: Can a tax advisor in Warsaw handle KSeF onboarding without involving the UK parent's IT team?

A: The legal and authorisation steps can be handled by a Polish tax advisor. The ERP integration cannot – it requires the UK parent's IT team or their ERP vendor. A common misconception is that KSeF is a purely accounting task. In practice, it is a joint legal-IT project. A Polish tax advisor coordinates the authorisation structure and ensures XML schema compliance; the UK IT team implements the system changes. Neither can complete the task without the other.

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, 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.