Transfer pricing

Transfer pricing
Agnieszka Pabiańska

Agnieszka Pabiańska

President of the board at CGO Tax / Tax advisor
Konrad Kusiak

Konrad Kusiak

Attoreney-at-law / Tax advisor

CGO TAX | TRANSFER PRICING

Transfer pricing for groups with a Polish entity

Local documentation, benchmarking and the TPR return — prepared so they hold up when an inspector reads them without your group context, not just when you file them.

A group policy and Polish documentation are two different documents

Groups regularly send us their global master file expecting it to close the Polish obligation. It does not. Poland asks for a local file, in Polish, for each homogeneous transaction above the threshold — and the master file is an additional requirement, not a substitute for it.

The obligation sits with the Polish entity, and the arm’s length statement is made by the people who manage it. So we treat documentation as a defence file rather than a filing formality: it has to answer questions years later, from someone who does not know your business.

  • Can our master file serve as Polish documentation?
  • Does the local file have to be in Polish?
  • Will our group benchmark survive here?
  • Which transactions actually cross the thresholds?

When it matters

Who this is for

Your group tax function sits abroad

The obligation is Polish, the decision-makers are not. We act as the local piece of your tax function and report in English.

The Polish entity signs the statement

Whoever manages the Polish company declares that prices are at arm’s length. That declaration needs a file behind it, not a group policy PDF.

Prices were set centrally, years ago

Group pricing often predates the current Polish rules. We test whether it still holds and say so plainly if it does not.

A review or audit has started

Once questions arrive, the documentation you already have decides how the conversation goes. We work with what exists and close the gaps.

What the engagement covers

Scope is fixed before we start. Take all of it, or only the parts your group does not cover centrally.

Obligation mapping

  • Which transactions cross the documentation thresholds
  • The ones groups forget: guarantees, cash pooling, cost allocations
  • Whether an exemption genuinely applies, condition by condition
  • Transactions with tax haven entities, where thresholds are far lower

Local documentation

  • The local file for each documented transaction, drafted in Polish
  • Functional analysis and the pricing rationale behind the method
  • Consistency with your group policy, or a written note where they differ
  • A file structured for inspection, not for internal circulation

Benchmarking

  • Comparable data analysis using sources a Polish inspector recognises
  • Compliance analysis where reliable comparables do not exist
  • Documented search strategy, screening steps and rejection reasons
  • A review of whether your existing group benchmark can be reused

TPR return and defence

  • Preparation and filing of the TPR information return
  • Reconciliation of the return against the documentation
  • Review of your master file against Polish requirements
  • Responses and representation once prices are questioned

What Poland requires

Thresholds and the three deadlines that do not move

Documentation thresholds apply per homogeneous controlled transaction, in net values. The deadlines run from the end of your tax year, so for a calendar year they land in the following autumn.

ObligationThreshold or deadlineWhat it means for you
Goods and financing transactions10 million PLN netAbove this, a local file is required for that transaction type.
Services and other transactions2 million PLN netThe threshold most groups cross first, often through management fees.
Tax haven transactions2.5 million PLN financing, 500 000 PLN otherFar lower thresholds. Routing payments through a low-tax entity pulls you in early.
Local documentationEnd of the 10th month after year endThe file has to exist, complete, by this date — not be startable.
TPR information returnEnd of the 11th month after year endFiled electronically, including the statement that prices are at arm’s length.
Group master fileEnd of the 12th month after year endRequired where the group meets the statutory criteria.

Exemptions exist and they matter — domestic transactions between profitable Polish taxpayers, and safe harbours for low value-adding services and for certain loans. Each has conditions that have to be met rather than assumed, which is what we check first.

How the engagement runs

Working language

  • All correspondence with you in English
  • The local file drafted in Polish from the start, not translated late
  • Positions your group tax team can review before filing
  • One named adviser across documentation and defence

What we need from you

  • A list of intercompany transactions and their values
  • Your group transfer pricing policy and master file, if they exist
  • Intercompany agreements, including financing and guarantees
  • A contact who can explain the business, not only the ledger

What stays with you

  • A local file that reads as a defence document
  • Benchmarking with a reconstructable search strategy
  • A filed TPR reconciled with the documentation
  • A written record of every judgement call and its date

Not sure which transactions are in scope?

Send the intercompany list. We will tell you what has to be documented this year, what is exempt, and where the current file would not hold.

Ask about your case

Process

From intercompany flows to a filed return

1

Transaction inventory

We map intercompany flows with your finance team and the group tax function, and agree which transactions are homogeneous.

2

Obligation map

A short written view of what must be documented, what is exempt, and what has to be reported in the TPR.

3

Documentation and analysis

Local file and benchmarking prepared in Polish, drafted so the pricing logic is legible to someone outside your group.

4

Filing and defence

TPR filed and reconciled with the documentation, and the file kept in a state where it can answer later questions.

Method and outputs

Four questions we answer before drafting anything

Is it a controlled transaction at all?

Related-party status is broader than shareholding. Common management, decisive influence and, for haven transactions, the counterparty’s residence all pull transactions into scope.

Which threshold applies, and to what?

Thresholds apply to homogeneous transactions in net terms, not to a whole intercompany account. How you group transactions changes the answer, and the grouping has to be defensible.

Would your group benchmark survive here?

Regional comparables are widely accepted, but not always as filed. We test whether the search strategy, screening and rejection reasons can be reconstructed.

What belongs to this service, and what needs separate scoping

CGO Tax is a tax advisory firm, not an accounting office — we do not keep books or run payroll. Litigation is scoped separately, because it takes a different kind of work and a different fee arrangement.

Obligation mapping, local file, benchmarking and the TPR returnCore scope
Master file review, group policy alignment, safe harbour analysisDepends on scope
Representation in a transfer pricing audit or disputeSeparate project
Documentation obligations in other jurisdictionsOutside this engagement

Who leads the work

The adviser responsible for transfer pricing

Agnieszka Pabiańska, licensed tax adviser and President of the Board of CGO Tax

Agnieszka Pabiańska, licensed tax adviser (registration no. 12559), President of the Board of CGO Tax. Leads the tax practice and works with international groups on Polish documentation obligations, on reconciling group pricing policy with local requirements, and on defending prices once they are questioned.

Talk to Agnieszka about your group

When the question goes beyond documentation

Polish VAT compliance

Registration and filings where the Polish entity has its own VAT obligations.

E-commerce and marketplace tax

When the group sells into Poland through platforms or Polish stock.

All services

Withholding tax, audits and disputes, and ongoing advisory.

Questions groups ask before the first engagement

Can we use our group master file as Polish documentation?

No. The master file and the local file answer different questions, and Poland requires the local one for transactions above the thresholds. The master file is an additional obligation where the group meets the statutory criteria, not a substitute. Your group file is still useful to us — it usually contains the functional description and the pricing policy we need, which then has to be turned into what Polish rules ask for.

Does the documentation have to be in Polish?

The local documentation is prepared in Polish. The master file may be provided in English, but the authorities can ask for a Polish translation and the time allowed is short. In practice we draft the local file in Polish from the start rather than translating late — translated documentation reads like translated documentation, and inspectors notice.

Do we need a separate Polish benchmark?

Not necessarily a Polish-only one. Regional comparables are widely used and accepted, provided the search strategy and the reasons for rejecting comparables are documented and defensible. What does not work is a benchmark presented as a conclusion: if the screening steps cannot be reconstructed, the analysis is weak regardless of the numbers it produces.

Our transactions are below the thresholds. Are we done?

For local documentation, possibly — but reporting is a separate question, and the arm’s length principle applies to all related-party transactions regardless of value. Two things catch groups out: transactions with entities from tax haven jurisdictions, where thresholds are far lower, and transactions that look small individually but are homogeneous when grouped correctly.

What happens if the TPR is late or inconsistent with the documentation?

Late or incorrect filing exposes the people who signed it to fiscal penal liability, and the entity to an additional tax liability where income has been understated. The more common problem is inconsistency: a TPR reporting one method while the local file describes another is an invitation to look closer, which is why we reconcile the two before filing.

Send us your intercompany flows

A list of transactions and your group policy is enough for us to tell you what Poland will require this year, and where the current documentation would not hold.

Review our Polish obligations

Featured Expert

Agnieszka Pabiańska

Agnieszka Pabiańska

President of the board at CGO Tax / Tax advisor
Konrad Kusiak

Konrad Kusiak

Attoreney-at-law / Tax advisor

Contact form

    CGO Tax