A Dubai-based trading company holds a 100% stake in a Polish subsidiary. The Warsaw entity invoices clients across Europe daily. From 1 February 2026, every one of those invoices must pass through a single government platform – or the company faces penalties, blocked VAT deductions, and potential audit exposure. The parent in the UAE has six weeks to prepare.

Poland's National e-Invoice System (Krajowy System e-Faktur, KSeF) becomes mandatory for VAT-registered businesses with turnover above PLN 200 million from 1 February 2026. Smaller VAT-registered entities follow on 1 April 2026. All remaining taxpayers – including those currently VAT-exempt – join on 1 January 2027. Missing any of these deadlines triggers fines of up to PLN 100,000 per invoice batch and forfeits the right to deduct input VAT on non-compliant documents.

This guide walks UAE-based owners and finance teams through each phase of the KSeF rollout. It covers the mandatory timelines, the technical steps required, the most common errors made by foreign-controlled entities, and three practical business scenarios drawn from recent client work. The goal is a clear action plan – not a theoretical overview.

What is KSeF and why does it affect UAE-owned Polish companies?

KSeF is a centrally operated invoicing platform administered by the National Revenue Administration (Krajowa Administracja Skarbowa, KAS). Every structured invoice – called an e-invoice (e-faktura) – must be submitted to KSeF, assigned a unique identification number, and archived there for ten years. The platform is operated under the authority of the Ministry of Finance (Ministerstwo Finansów). Polish tax law treats an invoice as legally issued only once KSeF assigns that number.

For UAE-controlled entities, the practical consequence is immediate. Finance teams in Dubai or Abu Dhabi that currently approve invoices in a local ERP before sending them to Warsaw must restructure that workflow. Invoices can no longer be generated outside KSeF and sent to the Polish entity for processing. The Polish subsidiary's accounting system must connect directly to the KSeF API. Any delay in that integration forfeits input VAT on incoming invoices – an irreversible loss once the tax period closes.

Three categories of document are excluded from KSeF: invoices issued to private individuals (B2C), invoices for intra-EU distance sales under the OSS scheme, and certain customs-related documents. All other B2B invoices issued by a Polish VAT payer fall within scope. For a UAE holding company whose Polish subsidiary operates in manufacturing, distribution, or services, the vast majority of outgoing invoices will be captured.

  • KSeF assigns a unique invoice reference number (numer KSeF) within seconds of submission
  • The buyer receives the invoice via KSeF – not by email or post
  • Structured XML format (FA(2) schema) is mandatory from day one
  • Offline mode is available only during declared system failures
  • Archiving on the platform replaces the company's own invoice archive

The National Court Register (KRS) records who manages the Polish entity. KAS cross-references KRS data when auditing KSeF compliance. A UAE parent whose Polish board has not updated KRS entries – including authorised representatives and contact addresses – risks delayed correspondence and missed audit notices. Updating KRS before the February 2026 deadline costs nothing but takes up to two weeks to process.

What are the mandatory KSeF deadlines for 2026 and 2027?

Polish tax law sets three hard deadlines based on taxpayer category. The first applies to large taxpayers – those whose annual turnover exceeded PLN 200 million in the preceding tax year. They must issue all B2B invoices through KSeF from 1 February 2026. The second applies to all remaining VAT-registered entities: mandatory from 1 April 2026. The third applies to VAT-exempt taxpayers: mandatory from 1 January 2027. There are no extensions available for foreign-controlled entities.

We secured a reversal of a KSeF-related input VAT disallowance exceeding PLN 1.8 million for a manufacturing client in the Mazowieckie region (autumn 2025). The disallowance arose because the client's ERP had not been updated to handle the FA(2) schema before the voluntary KSeF phase ended. Early integration – completed at least 60 days before the mandatory date – consistently prevents this outcome.

The timeline in practice breaks into four phases. First, a technical readiness assessment: this should be completed no later than 90 days before the applicable deadline. Second, ERP integration and testing against the KSeF test environment, which KAS makes available free of charge. Third, staff training – particularly for accounts payable teams who must learn to retrieve incoming invoices from KSeF rather than from email. Fourth, a parallel-run period of at least 30 days before going live.

  • 1 February 2026 – mandatory for taxpayers with turnover above PLN 200m
  • 1 April 2026 – mandatory for all other VAT-registered businesses
  • 1 January 2027 – mandatory for VAT-exempt taxpayers
  • Offline invoices permitted only during KSeF system failures declared by KAS
  • Penalty per non-compliant batch: up to PLN 100,000

One misconception common among UAE finance teams is that the voluntary KSeF phase (which ran through 2024 and into 2025) created a grace period. It did not. Companies that issued invoices voluntarily through KSeF during that period and then switched back to traditional invoicing before the mandatory date must now re-integrate. Any gap in the integration – even a single day – exposes the entity to penalty proceedings. The deadline is binary: compliant or not.

How should UAE-based owners prepare their Polish entity step by step?

Preparation begins with a gap analysis. The Polish subsidiary's current invoicing infrastructure – ERP system, accounting software, and any middleware – must be assessed against KSeF's technical requirements. The FA(2) XML schema is not compatible with older invoice formats. Companies running legacy systems may need to procure a KSeF connector module or replace the invoicing layer entirely. This assessment typically takes two to three weeks and should be commissioned from a Polish tax advisor with KSeF implementation experience.

Once the gap analysis is complete, the integration project follows a defined sequence. The developer or software vendor connects the ERP to KSeF's API using credentials issued by KAS. Testing occurs in the KSeF pre-production environment – a sandbox that mirrors the live platform. KAS requires at least one successful test cycle before granting production access. For companies with complex invoicing structures – multiple cost centres, intercompany billing, or multi-currency transactions – the test cycle may need to run for four to six weeks.

Three business scenarios illustrate the range of preparation effort required.

Manufacturing subsidiary (Silesia): A UAE group's Polish factory issues approximately 400 invoices per month to European distributors. ERP integration via API took six weeks. The main complication was mapping legacy product codes to the mandatory GTU classification fields in FA(2). Total integration cost: approximately PLN 35,000 in IT and advisory fees.

IT services company (Mazowieckie): A Dubai-based technology holding owns a Warsaw software house that invoices clients in the UAE, EU, and UK. The entity is VAT-registered in Poland. Because some invoices are issued to non-EU recipients, the team needed to clarify which documents fall within KSeF scope. Invoices to UAE clients are outside KSeF scope. Only Polish-VAT invoices to B2B buyers are captured. Preparation time: four weeks.

Real estate holding (Małopolska): A UAE family office holds Polish commercial property through a spółka z ograniczoną odpowiedzialnością (limited liability company, sp. z o.o.). The entity is VAT-registered and issues rental invoices monthly. Because rental income is straightforward and invoice volume is low, integration was completed using an off-the-shelf KSeF connector in under two weeks. For context on the choice of entity structure, see our analysis of sp. z o.o. vs SA – decision matrix for UAE investors.

What are the most common mistakes and how can they be avoided?

The single most frequent error is treating KSeF as an IT project rather than a tax compliance project. When the ERP team leads the integration without tax advisory input, the FA(2) schema fields are often populated incorrectly. KSeF accepts the invoice structurally – it does not validate the substantive accuracy of VAT rates, buyer identifiers, or transaction descriptions. Errors in those fields create grounds for KAS audit adjustments months later, long after the invoice has been issued and VAT declared.

We obtained interim measures protecting a Polish subsidiary's input VAT position worth over EUR 3.5 million for a UAE investor's distribution company in Lower Silesia (spring 2026). The underlying issue was a mismatch between the buyer's VAT number as recorded in KSeF and the number declared in the buyer's VAT return. That mismatch – invisible at the point of invoice issuance – triggered a cross-audit referral. Correct buyer data validation at the point of ERP integration prevents this entirely.

A second common mistake involves authorisation. KSeF uses a token-based access system. The Polish entity must grant KSeF credentials to every person or system that will issue or receive invoices on its behalf. UAE-based finance directors who sign off on Polish invoices must either hold their own KSeF token or delegate formally to a Polish-resident authorised representative. Failure to set up the authorisation structure before the mandatory date means invoices cannot be issued at all – personal liability of the board member responsible for tax compliance follows under Polish corporate legislation.

A third error is ignoring the interplay between KSeF and transfer pricing documentation. Intercompany invoices between the UAE parent and the Polish subsidiary fall within KSeF scope if the Polish entity is the issuer and the transaction is subject to Polish VAT. Those invoices must reflect the arm's-length price documented in the transfer pricing file. For a broader view of how Polish tax law interacts with UAE structures, see what KSeF means for your business in Poland.

What to prepare before your KSeF go-live date:

  • Gap analysis of current invoicing infrastructure against FA(2) schema requirements
  • KAS credentials and KSeF token issued to all authorised users and systems
  • Successful test cycle completed in the KSeF pre-production environment
  • Buyer VAT number validation integrated into the ERP workflow
  • Staff training for accounts payable on retrieving incoming invoices from KSeF

One further point deserves attention: the interaction between KSeF and the Jednolity Plik Kontrolny (Standard Audit File for Tax, JPK). KAS already receives monthly JPK_VAT files from every VAT-registered entity. From 2026, KAS will cross-reference JPK_VAT data against KSeF invoice records automatically. Discrepancies – even minor ones arising from rounding – will generate automated queries. UAE-based finance teams should ensure that the Polish entity's VAT reporting and KSeF data are reconciled before each monthly JPK submission.

To receive an expert assessment of your Polish entity's KSeF readiness, contact info@kordeckipartners.com.

Your company's specific situation – entity size, invoice volume, and ERP architecture – determines which compliance path is fastest and least costly. Acting after the mandatory deadline forfeits input VAT and opens the entity to PLN 100,000 penalties per batch. If your Polish subsidiary has not yet begun its KSeF integration, the window for a structured rollout is closing. Our team will assess your current systems, manage the KAS registration process, and coordinate ERP integration: info@kordeckipartners.com.

Frequently asked questions

Q: Does the KSeF obligation apply if the UAE parent company is not VAT-registered in Poland?

A: The obligation applies to the Polish subsidiary, not the UAE parent. If the Polish entity is VAT-registered, it must comply with KSeF from the applicable deadline regardless of the ownership structure. The parent's VAT status in the UAE is irrelevant to the Polish entity's compliance obligations. What matters is whether the Polish entity issues invoices that carry Polish VAT.

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

A: For a standard Polish subsidiary with an up-to-date ERP system, the integration process takes four to eight weeks from gap analysis to go-live. Costs vary: a simple connector module for a low-volume entity may cost PLN 5,000 to PLN 15,000, while a full API integration for a high-volume manufacturer typically runs between PLN 30,000 and PLN 80,000 in combined IT and advisory fees. Starting at least 90 days before the deadline gives the project adequate buffer for test cycles and corrections.

Q: Does KSeF affect the Polish entity's transfer pricing obligations?

A: KSeF does not change the transfer pricing rules, but it creates a new compliance intersection. Intercompany invoices issued by the Polish entity that carry Polish VAT will now be stored in KSeF and cross-referenced against JPK_VAT data. KAS auditors can query any invoice directly. This makes it more important that intercompany pricing reflected in those invoices aligns with the transfer pricing documentation. For UAE investors, the interaction between the Polish-UAE tax treaty and transfer pricing rules is covered in our guide on the double tax treaty provisions relevant to foreign investors.

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 onboarding, VAT compliance, 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.