KSeF deadline timeline 2026–2027 for companies in Cyprus

A Cyprus-registered holding company receives a formal notice from its Polish subsidiary: as of 1 February 2026, all domestic VAT invoices in Poland must be issued exclusively through the National e-Invoice System (Krajowy System e-Faktur, KSeF). The subsidiary's finance team has been issuing invoices through a local accounting package. The holding structure – with its intercompany service fees, IP licensing streams, and intra-group loans – has never been through a Polish e-invoicing audit. The clock is already running.

KSeF becomes mandatory for large Polish taxpayers on 1 February 2026 and for all remaining active VAT payers on 1 April 2026. Cyprus-owned Polish entities are fully subject to these deadlines regardless of where their parent is registered. Non-compliance exposes the Polish subsidiary to financial penalties of up to 100% of the VAT shown on a non-conforming invoice, and the parent group loses the ability to deduct input VAT on affected transactions. Remediation after the enforcement window closes is significantly harder and more expensive than timely onboarding.

This guide walks through the mandatory timeline, the step-by-step compliance procedure, the three structural scenarios most common for Cyprus groups with Polish operations, and the mistakes that most frequently trigger penalties. It also addresses how KSeF intersects with transfer pricing documentation and IP Box arrangements – two areas where Cyprus structures are disproportionately exposed.

What is KSeF and why does it matter for Cyprus holding structures?

KSeF is the Polish government's centralised invoicing platform, administered by the National Revenue Administration (Krajowa Administracja Skarbowa, KAS). Every structured invoice (faktura ustrukturyzowana) issued by a Polish VAT payer must pass through KSeF and receive a unique system identifier before it is legally valid. The National Court Register (KRS) is used by KAS to verify the identity of the entity issuing the invoice. This matters for Cyprus groups because the Polish subsidiary – not the Cypriot parent – bears the compliance obligation directly.

The financial exposure is real and time-bound. A non-conforming invoice issued after the applicable deadline triggers a penalty of up to 100% of the VAT amount shown. For a Polish operating company billing PLN 10m per month in taxable turnover, a single month of non-compliance could generate penalty exposure approaching PLN 230,000 at the standard 23% VAT rate. That figure compounds quickly. More damagingly, the counterparty receiving a non-conforming invoice cannot deduct input VAT – meaning commercial relationships deteriorate fast.

Cyprus holding structures interact with KSeF in three distinct ways. First, the Polish subsidiary issues invoices to third-party customers. Second, the subsidiary issues intercompany invoices to the Cypriot parent for services, royalties, or loan interest. Third, the Cypriot parent may issue invoices to the Polish subsidiary. Only the first two categories fall within KSeF's mandatory scope for the Polish entity. The third – invoices issued by a non-Polish entity – does not pass through KSeF, but the Polish subsidiary must still receive and archive them correctly.

• Mandatory KSeF scope: invoices issued by Polish VAT-registered entities
• Intercompany invoices to the Cypriot parent: within scope
• Invoices received from the Cypriot parent: outside KSeF but subject to archiving rules
• Self-billing arrangements: require written agreement and KSeF registration of the authorised issuer

What is the mandatory KSeF timeline for 2026 and 2027?

The KSeF rollout follows a two-phase mandatory schedule. Phase one applies from 1 February 2026 to taxpayers whose VAT turnover in 2024 exceeded PLN 200m. Phase two applies from 1 April 2026 to all remaining active VAT payers, including smaller Polish subsidiaries of Cyprus groups. Entities that were VAT-exempt in 2024 have until 1 January 2027 to comply. These dates are fixed in Polish VAT legislation and are not subject to individual extension requests.

The Polish Financial Supervision Authority (KNF) and KAS have both confirmed that foreign ownership does not affect the classification of a Polish entity under these thresholds. A Warsaw-based IT services company owned 100% by a Nicosia holding vehicle is assessed on its own Polish VAT turnover. If that turnover exceeded PLN 200m in 2024, the February 2026 deadline applies. If not, April 2026 governs. There is no mechanism to delay mandatory status based on group-level revenues or the parent's jurisdiction.

For 2027, the key compliance milestone is the full operationalisation of KSeF's B2G (business-to-government) module, which becomes mandatory for public procurement invoices. Cyprus groups with Polish subsidiaries holding public contracts must plan for this separately. The self-invoicing (samofakturowanie) regime also becomes fully integrated into KSeF by mid-2027, which affects intercompany arrangements where the Cypriot parent historically issued invoices on behalf of the Polish entity.

One date frequently misread: the 1 April 2026 deadline applies to the issuance of invoices, not to the archiving of historical invoices. Companies do not need to re-issue past invoices through KSeF. The obligation is forward-looking from the applicable deadline date. However, KAS audit practice treats the quality of pre-KSeF invoice archives as an indicator of general compliance culture – relevant when the authority exercises discretion on penalty amounts.

How should Cyprus groups prepare step by step?

Preparation has four sequential phases, each with a hard internal deadline. Starting late on phase one compresses the remaining phases and increases the risk of a deficient go-live. We assisted a manufacturing client in the Małopolska region (winter 2025) in compressing a standard 16-week preparation into 10 weeks after a delayed board decision – the exercise required parallel workstreams and external IT resource, at roughly 40% higher cost than a standard timeline.

Phase 1 – System assessment (weeks 1–4). Map every invoice flow touching the Polish subsidiary. Identify the ERP or accounting system in use. Confirm whether the vendor has released a KSeF-certified API connector. Many Cyprus groups use accounting software licensed through the Cypriot parent; Polish KSeF integration requires a Polish-language certified module. Budget PLN 15,000–80,000 for integration depending on system complexity.

Phase 2 – Entity registration and authorisation (weeks 3–6). The Polish subsidiary must register its KSeF credentials through the KAS e-services portal (e-Urząd Skarbowy). Authorised persons – typically the management board members listed in KRS – must be granted system roles. For Cyprus groups where the board is domiciled in Nicosia, this step requires a Polish-language power of attorney and certified translation. Allow 3–4 weeks for this process. Errors at this stage are the single most common cause of delayed go-live.

Phase 3 – Invoice schema mapping (weeks 5–10). KSeF uses a structured XML schema (FA(2) format as of 2026). Every data field in the existing invoice template must be mapped to the schema. Intercompany invoices to the Cypriot parent require careful mapping of the counterparty's EU VAT number and the transaction currency. Transfer pricing documentation should be cross-referenced at this stage – the KSeF invoice description fields are increasingly scrutinised by KAS during transfer pricing audits. Our article on transfer pricing safe harbours under Polish law explains the documentation thresholds relevant to intercompany service invoices.

Phase 4 – Testing and go-live (weeks 9–14). KAS operates a dedicated test environment. All invoice types must be tested before live issuance. A minimum of 4 weeks of parallel testing is recommended. Entities that skip testing and go live directly risk invoice rejection at the point of issuance – which means the transaction is legally uninvoiced until a corrected invoice is issued through KSeF.

• Week 1–4: system assessment and vendor confirmation
• Week 3–6: KAS registration and authorisation setup
• Week 5–10: XML schema mapping including intercompany flows
• Week 9–14: testing environment validation and parallel run
• Go-live: no later than 7 days before mandatory deadline

What are the three business scenarios for Cyprus groups?

Cyprus-based groups operating in Poland fall into three structural patterns. Each generates a different KSeF compliance profile and a different risk exposure. Identifying the correct scenario early determines the scope of preparation work and the budget required.

Scenario 1 – Cyprus holding with a single Polish operating subsidiary. This is the most common structure. The Polish entity issues invoices to Polish customers and intercompany invoices to the Cyprus parent for management fees or royalties. KSeF applies to both invoice streams. The primary risk is the intercompany invoice: if the XML description of a management fee does not match the transfer pricing documentation, KAS may challenge the deductibility of the cost. A Polish IT services company in this scenario – with annual intercompany fees of approximately EUR 2m – should allow 12 weeks for preparation and PLN 40,000–60,000 for integration and legal review.

Scenario 2 – Cyprus IP holding with Polish entity as IP licensee. Here the Cypriot parent owns intellectual property and licenses it to the Polish subsidiary, which claims IP Box relief on qualifying income. The Polish subsidiary issues invoices for its services; the Cypriot parent issues royalty invoices to the Polish entity. The outbound service invoices are within KSeF scope. The inbound royalty invoices from Cyprus are not – but they must be archived in a KSeF-compatible format from 1 April 2026 onwards. This scenario also raises the question of whether the Polish entity's IP Box claim survives KAS scrutiny of KSeF invoice data. Our analysis of branch vs subsidiary structures for Cyprus groups addresses the entity-form implications of this arrangement.

Scenario 3 – Cyprus group with Polish branch. A branch (oddział) of a Cyprus company registered in Poland is treated as a separate VAT taxpayer for Polish purposes. The branch is subject to the same KSeF deadlines as a subsidiary. However, the branch does not have a separate legal personality – which creates complications for the KSeF authorisation process, since the KRS entry for the branch differs from that of a standalone Polish company. Groups operating through a branch should seek legal advice at least 16 weeks before the applicable deadline. We have handled KSeF onboarding for a branch structure in the Mazowieckie region (spring 2026), securing compliant go-live within a compressed 8-week window after the parent board approved the project.

What common mistakes forfeit compliance and trigger penalties?

The mistakes that most frequently result in penalty exposure are not technical failures – they are planning failures. Four patterns appear repeatedly in KAS enforcement actions in early 2026. Each forfeits the company's window to self-correct before the authority acts.

The first and most damaging mistake is treating KSeF as an IT project rather than a legal and tax project. The XML schema mapping phase requires input from tax advisors, not only system integrators. Incorrect mapping of transaction type codes – for example, classifying an intercompany management fee as a standard service rather than a related-party transaction – creates a mismatch between the KSeF record and the transfer pricing file. KAS has direct access to KSeF data and cross-references it against JPK_VAT filings. A mismatch triggers a query; an unresolved query triggers an audit.

The second mistake is failing to register authorised persons in time. The KAS registration process for entities whose board members reside outside Poland – as is typical for Cyprus-owned companies – requires certified translations and can take 4–6 weeks. Companies that start this process in January 2026 for a February deadline are already late. Personal liability of board members for failure to ensure timely KSeF compliance is a live issue under Polish corporate legislation.

The third mistake is ignoring the interaction between KSeF and family foundation structures. Some Cyprus groups have restructured through Polish family foundations (fundacje rodzinne) since May 2023. Where the foundation holds shares in the Polish operating company, the invoicing relationships between the foundation and the subsidiary must also be mapped. Foundations that conduct limited business activity are VAT-registered and subject to KSeF. Overlooking this layer creates a gap in the compliance map.

The fourth mistake is failing to update the tax advisor Warsaw-side engagement to cover KSeF. Many Cyprus groups retain Polish tax advisors for CIT and transfer pricing work but have not extended that engagement to VAT and KSeF. The two advisory streams must be coordinated. An uncoordinated approach – where the IT team implements KSeF without tax advisor input – produces technically functional but legally deficient invoices. For a more detailed comparison of KSeF compliance approaches across jurisdictions, see our guide on KSeF deadline timeline 2026–2027 for companies in Switzerland.

What to prepare before your KSeF go-live date

A structured pre-go-live checklist reduces the risk of last-minute failures. The following items are the minimum required for a Cyprus-owned Polish entity to achieve compliant KSeF status. Each item should be assigned an owner and a completion date at least 14 weeks before the applicable deadline.

• Confirm the applicable mandatory deadline (1 February or 1 April 2026, or 1 January 2027) based on 2024 VAT turnover
• Obtain KRS-certified authorisation for all persons who will hold KSeF system roles
• Complete XML schema mapping for all invoice types, including intercompany flows to the Cyprus parent
• Run minimum 4 weeks of parallel testing in the KAS test environment
• Cross-reference KSeF invoice descriptions against current transfer pricing documentation

One concrete figure to anchor the planning: the KAS test environment has been available since October 2024. Entities that have not yet initiated testing as of January 2026 have fewer than 90 days to complete all four preparation phases. At the standard 16-week preparation timeline, they are already in compressed territory. The cost of engaging external support at this stage is typically PLN 20,000–50,000 higher than engaging at the 20-week mark – a direct financial consequence of delayed action.

For Cyprus groups with Polish tax law obligations spanning VAT, CIT, and transfer pricing, KSeF compliance is not a standalone project. It is the visible surface of a broader data-transparency regime that KAS is building systematically. JPK_CIT, mandatory disclosure rules (MDR), and Pillar Two reporting all feed the same analytical infrastructure. Getting KSeF right in 2026 is the foundation for managing that broader exposure in 2027 and beyond.

Specific circumstances of your Polish subsidiary require individual assessment. Delayed action on KSeF onboarding forfeits the ability to self-correct before KAS enforcement begins – and enforcement in 2026 is expected to be active from the first quarter.

If your Cyprus group's Polish entity is approaching the applicable KSeF deadline without a confirmed go-live plan, we will conduct a compliance gap assessment, map your invoice flows, and coordinate the legal, tax, and IT workstreams: info@kordeckipartners.com.

Frequently asked questions

Q: Does the KSeF obligation apply to a Cyprus company that is VAT-registered in Poland but has no Polish-registered subsidiary?

A: Yes. A foreign entity – including a Cyprus company – that holds a Polish VAT registration number and issues invoices for transactions subject to Polish VAT must comply with KSeF from the applicable mandatory deadline. The obligation attaches to the Polish VAT registration, not to the legal form of the entity. The applicable deadline (1 February or 1 April 2026) depends on the entity's 2024 Polish VAT turnover. Foreign entities without a Polish establishment but with a Polish VAT number should register KSeF credentials through the KAS portal at least 8 weeks before the deadline.

Q: How much does KSeF onboarding typically cost for a Cyprus-owned Polish company?

A: The total cost depends on system complexity and the number of invoice types in scope. For a single-entity Polish subsidiary with a standard ERP system and 2–4 invoice types, the realistic budget is PLN 30,000–70,000 covering IT integration, legal review of the XML mapping, and KAS registration support. Companies with multiple invoice streams, intercompany arrangements, or branch structures should budget PLN 80,000–150,000. These figures assume a 12–16 week preparation timeline. Compressed timelines – under 10 weeks – typically add 30–50% to the cost. Ongoing KSeF advisory (post-go-live monitoring and update management) costs approximately PLN 1,500–4,000 per month depending on invoice volume.

Q: Is it a common misconception that intercompany invoices between a Polish subsidiary and its Cyprus parent are exempt from KSeF?

A: Yes, this is one of the most widespread misunderstandings among Cyprus groups. KSeF applies to all invoices issued by a Polish VAT-registered entity, including invoices addressed to a foreign counterparty. An intercompany service fee invoice from the Polish subsidiary to the Nicosia parent must pass through KSeF from the applicable mandatory deadline. The only invoices excluded from KSeF are those issued by non-Polish entities (including the Cyprus parent's invoices to the Polish subsidiary) and certain narrow categories defined in Polish VAT legislation, such as invoices for intra-Community transport under specific simplification regimes. Standard management fees, royalties, and loan interest invoices are fully within KSeF scope.

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 Cyprus and other international holding groups. 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.