A Warsaw-based software house reaches its third year of profitable operations. The founders know their product generates qualified intellectual property income. Yet the company still pays corporate income tax at the standard rate – because no one has formally structured the IP Box regime. That oversight costs real money every quarter.

IP Box is a preferential tax regime under Polish corporate and personal income tax law that applies a 5% rate to qualifying income derived from commercialising eligible intellectual property rights. For software companies, the primary qualifying asset is a copyright in a computer program. The regime requires meticulous record-keeping and a dedicated nexus calculation, but it can reduce effective tax on qualifying income by up to 14 percentage points against the standard 19% rate.

This page explains which software companies qualify, how the nexus formula works in practice, where the common pitfalls arise, and what cross-border structures need to consider. It also provides a self-assessment checklist. If you are deciding whether IP Box is worth pursuing, the sections below give you the analytical framework to make that call.

What is IP Box and who qualifies under Polish tax law?

IP Box is a preferential income tax mechanism that taxes qualifying intellectual property income at 5% rather than the standard 19% corporate income tax (CIT) rate. The regime sits within Polish income tax legislation and is administered by the National Tax Administration (Krajowa Administracja Skarbowa, KAS). It applies to both corporate taxpayers under CIT and individuals under personal income tax (PIT), making it accessible to sole traders and partners in partnerships as well as limited liability and joint-stock companies registered with the National Court Register (Krajowa Rejestracja Sądowa, KRS).

For software companies, the qualifying intellectual property right is a copyright in a computer program. This is distinct from patents or utility models. Polish tax legislation treats a copyright in a computer program as an eligible IP right without requiring formal registration – a significant advantage. The copyright arises automatically at the moment of creation, provided the work meets the originality threshold under copyright law. That threshold is not high, but it is not automatic either. Tax inspectors at the KAS can and do question whether a given piece of software is sufficiently original.

Eligibility turns on three cumulative conditions. First, the taxpayer must conduct qualifying research and development (R&D) activity – either itself, or by commissioning it from a related or unrelated party. Second, the IP right must be created, developed, or improved as a result of that R&D activity. Third, the income must be derived from the commercialisation of that IP right. Commercialisation includes licensing, selling the right, using it in one's own products or services, and receiving damages for infringement.

  • Copyright in a computer program – no registration required
  • Patents and utility models – registration required
  • Integrated circuit topographies – registration required
  • Medicinal product data exclusivity rights – registration required

The Polish Financial Supervision Authority (Komisja Nadzoru Finansowego, KNF) is not directly involved in IP Box applications, but companies operating in regulated sectors – fintech, payment services – must ensure their IP Box structure does not conflict with licensing conditions. That is a point many advisers overlook at the eligibility stage.

How does the nexus formula determine the qualifying rate?

The nexus calculation is the mathematical heart of IP Box. It determines what proportion of income from a given IP right qualifies for the 5% rate. The formula compares qualifying R&D expenditure with total expenditure connected to the IP right. A higher ratio of own and commissioned R&D to total costs yields a higher qualifying income fraction. Taxpayers who acquire IP rights from related parties face a structural disadvantage: those acquisition costs appear in the denominator but not the numerator, reducing the nexus ratio and therefore the qualifying income.

The formula is: (a + b + c) × 1.3 ÷ (a + b + c + d), where the components are own R&D costs (a), commissioned R&D from unrelated parties (b), commissioned R&D from related parties (c), and acquisition costs of the IP right (d). The 1.3 multiplier rewards own and unrelated-party R&D. The result is capped at 1.0 – meaning the qualifying fraction cannot exceed 100% of income. In practice, software companies that develop entirely in-house typically achieve a nexus ratio close to 1.0. Companies that acquired core technology from a parent entity may find their ratio falls below 0.5.

We secured a reversal of a KAS audit finding that had incorrectly classified internal tool development costs as non-qualifying for a software client in the Mazowieckie region (autumn 2025). The reclassification increased the client's nexus ratio from 0.61 to 0.94 – and reduced the prior-year tax liability accordingly.

Tracking the nexus formula requires a dedicated cost allocation system. Costs must be allocated to individual IP rights, not pooled at project or company level. That requirement drives the single most common compliance failure: companies that maintain a single R&D cost centre cannot demonstrate the per-IP allocation that KAS expects. Establishing the right accounting structure before the first tax year is far cheaper than reconstructing records under audit.

Transfer pricing rules interact with IP Box where related-party R&D is commissioned. The arm's-length price paid to a related party for R&D services enters the nexus formula at component (c) – but only if it reflects market pricing. Inflated related-party R&D fees that push costs into (c) to game the multiplier are a known audit trigger. KAS has issued guidance making clear that transfer pricing documentation must support every related-party R&D charge used in the nexus calculation.

What are the record-keeping and compliance obligations?

IP Box compliance is not a year-end exercise. It requires continuous, contemporaneous record-keeping throughout the tax year. Polish income tax legislation specifies that taxpayers claiming IP Box must maintain separate records that allow the calculation of qualifying income for each eligible IP right. Those records must be kept for five years from the end of the tax year to which they relate – the standard limitation period for tax obligations in Poland.

The minimum record-keeping framework includes three elements. First, a register of IP rights listing each qualifying right, its creation date, the R&D activity that produced it, and the commercialisation model. Second, cost allocation records attributing R&D expenditure to individual IP rights with supporting documentation. Third, income allocation records linking revenue streams to specific IP rights.

  • IP rights register – updated monthly
  • R&D cost allocation ledger – per IP right, not per project
  • Revenue attribution schedule – per IP right, per contract
  • Nexus calculation workbook – updated quarterly
  • Supporting contracts and timesheets – retained for five years

The IP Box claim is made in the annual tax return. There is no advance application or separate filing. The 5% rate applies to the qualifying income figure derived from the nexus calculation and entered in the return. However, taxpayers may apply for an individual tax ruling (indywidualna interpretacja podatkowa) from the Director of the National Revenue Information (Dyrektor Krajowej Informacji Skarbowej, DKIS) to confirm their eligibility before committing to the regime. Rulings take up to three months to issue. They provide protection against later KAS challenge if the facts match the ruling description.

One practical point deserves emphasis. The IP Box regime does not suspend standard CIT advance payment obligations during the year. Companies must continue paying advances at the standard 19% rate. The benefit is realised at year-end settlement – meaning cash flow timing differs from the effective rate. Some companies use simplified advance calculations to manage this, but that requires separate analysis of whether the simplified method is advantageous in a given year.

Specific situation requiring analysis? IP Box eligibility depends on your exact R&D structure and cost allocation methodology. Applying the wrong nexus approach forfeits the 5% rate permanently for that tax year – an irreversible consequence.

To receive an expert assessment of your IP Box eligibility and nexus structure, contact info@kordeckipartners.com. Our tax team will review your R&D documentation, calculate a provisional nexus ratio, and identify any record-keeping gaps before your next filing deadline.

What pitfalls affect software companies specifically?

Software companies face IP Box pitfalls that differ from those affecting pharmaceutical or manufacturing IP holders. The most damaging is the failure to distinguish between qualifying software development and non-qualifying maintenance. Polish tax law draws a clear line: creating new functionality constitutes R&D; fixing bugs in existing functionality does not. In practice, developer time is often mixed between both activities. Without granular timesheet records, KAS will apportion costs against the company – reducing the qualifying R&D base and the nexus ratio.

A second pitfall concerns work-for-hire contracts. Where a software company develops a product under a contract that transfers all IP rights to the client on delivery, the company has no IP right to commercialise. It cannot claim IP Box on that project income. Companies that operate on a time-and-materials basis with full IP transfer clauses structurally exclude themselves from IP Box on those projects. Restructuring contracts to retain a licence model – rather than transferring all rights – can restore eligibility, but requires careful contract drafting and client negotiation.

We obtained a favourable individual tax ruling for an IT services company in Lower Silesia that had previously operated under full IP transfer contracts (spring 2026). After restructuring to a perpetual licence model, the company qualified for IP Box on approximately 70% of its annual revenue – a material change in effective tax rate.

A third pitfall is the interaction with the R&D tax relief (ulga B+R). Both regimes are available simultaneously under Polish tax law, but they cannot apply to the same costs. Costs deducted under R&D relief cannot also be included in the IP Box nexus calculation. Companies that claim both reliefs must maintain separate cost pools and ensure no double-counting. This is a frequent audit focus point. Getting the allocation right from the outset requires a documented cost segregation policy.

Finally, there is the question of software used internally rather than commercialised externally. Income from using qualifying IP in one's own products or services does qualify for IP Box – but the income must be separately calculated. Where software drives a SaaS platform, the income attributable to the IP right must be isolated from income attributable to hosting, support, or other services bundled in the subscription price. Bundled pricing without allocation is an audit risk.

How do cross-border structures interact with IP Box in Poland?

Cross-border software companies face additional layers of analysis. Where a Polish entity is part of an international group, transfer pricing documentation must address IP Box income directly. If the Polish company holds the qualifying IP right and licenses it to group entities abroad, the licence fees are qualifying commercialisation income for IP Box purposes. However, the arm's-length pricing of those licences is subject to KAS scrutiny – and the Polish Transfer Pricing Guidelines align with OECD BEPS Action 8-10 standards on IP valuation.

For foreign investors structuring a Polish software subsidiary, the choice of entity matters. A Polish limited liability company (spółka z ograniczoną odpowiedzialnością, sp. z o.o.) registered with the KRS is the standard vehicle. It qualifies for IP Box under CIT. A branch of a foreign company does not have a separate legal personality and its eligibility for IP Box requires case-by-case analysis. The preferred structure for clean IP Box access is a Polish subsidiary with clear IP ownership and a documented R&D function performed in Poland.

The interaction with the KSeF e-invoicing system is relevant for compliance rather than eligibility. From 2026, Polish companies will issue structured invoices through the National e-Invoice System (Krajowy System e-Faktur, KSeF). IP Box clients licensing software to Polish counterparties must issue KSeF-compliant invoices for those licence fees. For context on the KSeF rollout timeline for international groups, see our analysis of KSeF deadline and timeline for 2026–2027 for companies in France and our note on what KSeF means for your business in Sweden.

Double tax treaty implications also arise. Where a Polish IP Box company receives royalties from abroad, the treaty withholding tax rate in the source country may reduce the net benefit. Treaty shopping is not a solution – Polish general anti-avoidance rules and BEPS minimum standards apply. The more productive analysis is whether the Polish entity has sufficient substance to be respected as the true IP holder under both Polish and foreign law. Substance requirements include local R&D staff, decision-making in Poland, and genuine risk absorption by the Polish entity.

One further cross-border consideration: companies with turnover above EUR 750m are subject to Pillar Two global minimum tax rules. For those groups, the IP Box benefit may be partially offset by the qualified domestic minimum top-up tax (QDMTT) mechanism. Groups approaching or exceeding that threshold should model the interaction before committing to an IP Box structure. For smaller groups below the threshold, Pillar Two does not currently affect IP Box planning.

Your company's specific structure determines whether IP Box delivers its full benefit or is eroded by related-party adjustments, treaty withholding, or Pillar Two. An incorrect cross-border setup forfeits years of preferential rate access – an irreversible consequence once the tax year closes.

For a tailored strategy on IP Box structuring for international software groups, reach out to info@kordeckipartners.com. We will assess your group structure, substance position, and transfer pricing documentation against current KAS audit practice.

What should software companies prepare before claiming IP Box?

Self-assessment is the right starting point. Before engaging advisers or filing a claim, a software company should work through the following checklist. It identifies the most common gaps before they become audit findings. The checklist covers the five areas that KAS reviews first in an IP Box audit.

  • IP rights register: Does the company maintain a written register of each qualifying copyright in a computer program, with creation dates and R&D activity descriptions?
  • Cost allocation system: Are R&D costs allocated to individual IP rights – not pooled at department or project level – with supporting timesheets or task records?
  • Revenue attribution: Can the company demonstrate which revenue streams derive from each specific IP right, including internal use valuations for SaaS platforms?
  • Contract review: Have all client contracts been reviewed to confirm the company retains a qualifying IP right rather than transferring all rights on delivery?
  • R&D relief segregation: If the company also claims R&D tax relief, are the two cost pools strictly separated with no double-counting?

The decision matrix for IP Box works as follows. A company developing original software entirely in-house, retaining IP rights under licence agreements, and maintaining contemporaneous records should achieve a nexus ratio close to 1.0 and qualify for the full 5% rate on commercialisation income. A company that acquired its core technology from a related party, operates under full IP transfer contracts, and pools R&D costs at company level will face a materially lower nexus ratio – potentially making the compliance cost disproportionate to the benefit.

Three business scenarios illustrate the range. A manufacturing-sector software company developing industrial automation tools in-house and licensing them to clients is a strong candidate. An IT services company operating on time-and-materials contracts with full IP transfer needs contract restructuring before IP Box is viable. A foreign investor establishing a Polish R&D centre to develop group software qualifies – provided the Polish entity has genuine substance and clear IP ownership documented from day one.

The cost of getting IP Box right is front-loaded: structuring, documentation, and an optional individual ruling. The cost of getting it wrong is back-loaded: KAS audit, interest at 8% per annum on underpaid tax, and potential additional tax liability. For a company generating PLN 2m annually in qualifying IP income, the difference between a 5% and 19% rate is PLN 280,000 per year. That figure concentrates the mind on compliance quality.

For employment-related questions that arise when structuring R&D teams for IP Box purposes – including employment contracts versus B2B arrangements – see our overview of severance pay calculation under the Polish Labour Code, which addresses the employment law implications of workforce restructuring.

Frequently asked questions

Q: Can a sole trader running a software business claim IP Box under Polish tax law?

A: Yes. IP Box is available to individuals taxed under personal income tax as well as corporate taxpayers. A sole trader (jednoosobowa działalność gospodarcza) who develops qualifying software and commercialises it through licensing or service agreements can apply the 5% rate to qualifying income. The same nexus calculation and record-keeping obligations apply. The claim is made in the annual PIT return. Sole traders who use the flat-rate income tax (ryczałt) regime cannot access IP Box – the 5% rate requires the general tax scale or the 19% flat rate for business income.

Q: How long does it take to get an individual tax ruling confirming IP Box eligibility?

A: The Director of the National Revenue Information is required to issue an individual tax ruling within three months of receiving a complete application. In practice, rulings on IP Box questions have taken between two and four months in recent years. The ruling covers the facts as described in the application – any material difference between the described and actual situation removes the protection. Applying before the start of the first IP Box tax year is strongly advisable, as the ruling cannot retroactively protect periods before the application was filed.

Q: Is IP Box compatible with the Estonian CIT (ryczałt od dochodów spółek) regime?

A: No. Companies that elect Estonian CIT – the lump-sum tax on distributed income available to qualifying Polish companies – cannot simultaneously claim IP Box. The two regimes are mutually exclusive under Polish income tax legislation. A company must choose one or the other for a given tax year. The decision depends on whether the company distributes profits regularly (favouring Estonian CIT if the rate is advantageous) or retains and reinvests them (potentially favouring IP Box). This is a common misconception: many founders assume the two can be stacked, but they cannot.

About KORDECKI & Partners

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 IP Box structuring, KSeF compliance, and tax advisory for software and technology companies. We work with Polish entrepreneurs, foreign investors, and in-house legal teams. Our tax practice handles CIT and PIT advisory, transfer pricing documentation, IP Box eligibility assessments, individual tax rulings, and family foundation structuring. 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.