Poland Withholding Tax on Service Invoices: AP Compliance Guide

Poland imposes withholding tax at 20% on payments to non-residents for intangible services, including consulting, management, advisory, advertising, and accounting services. The legal basis sits in the Polish CIT Act (Ustawa o CIT), which treats the Polish payer as the remitter, meaning your company bears full responsibility for correctly withholding and remitting WHT to the tax authorities. Get it wrong, and the liability falls on you, not the foreign supplier.

A critical compliance layer kicks in once annual payments to a single related-party recipient cross PLN 2 million, but AP teams should not treat every foreign service invoice as automatically subject to the pay-and-refund regime. PwC's Poland withholding tax summary describes the mandatory pay-and-refund mechanism around passive payments such as dividends, interest, and royalties; intangible service payments need separate review, especially where a charge could be reclassified as a royalty or another passive payment.

Most Polish WHT guidance is written for tax advisors and legal departments. AP professionals and financial controllers need something different: a clear framework for identifying which invoices trigger WHT, what data points to extract from each foreign service invoice, what documentation to collect before releasing payment, and how to monitor cumulative payment totals against the PLN 2 million threshold at the transaction level.

Which Payments to Non-Residents Trigger Polish Withholding Tax

Poland's withholding tax applies to outbound payments made by Polish entities to non-resident recipients. The obligation arises at the point of payment, not when the invoice is received or booked. This distinction matters for AP teams: WHT classification and withholding must happen before funds leave your account, not during invoice intake.

Standard WHT Rates Under the Polish CIT Act

The Polish CIT Act (Ustawa o CIT) establishes two primary withholding rates for payments to non-residents:

20% rate applies to:

Interest payments
Royalties and license fees
Intangible service payments, including consulting, management, advisory, marketing and advertising, accounting, market research, legal services, and payments for know-how or technical expertise

19% rate applies to:

Dividends
Income from shares in profits of legal persons

For AP teams processing foreign service invoices, the 20% rate is the one you will encounter most frequently.

Classifying Invoice Line Items

The CIT Act defines intangible services subject to WHT broadly, which means AP teams need a reliable way to flag liable invoices during processing. The following invoice descriptions typically trigger the 20% rate:

"Consulting services" or "advisory fees"
"Management fee" or "management services"
"Technical assistance" or "technical support services"
"Advertising services" or "marketing services"
"Accounting services"
"Royalty payment" or "license fee"
"Know-how" or "transfer of expertise"

When a service description does not clearly fall into one of these categories, flag the invoice for review rather than assuming exemption. The cost of incorrect classification (penalties, back-interest, and potential liability under the pay-and-refund mechanism) far exceeds the cost of a brief tax review.

Conversely, payments for tangible goods, physical on-site services (such as equipment installation or repairs), and transportation generally fall outside WHT scope. The primary classification decision is whether the service is intangible (WHT-liable) or tangible/physical (not WHT-liable). Note that this cross-border WHT regime is separate from domestic payment compliance; if your team also handles Polish supplier invoices, the mandatory split payment rules for domestic Polish transactions involve different requirements and different triggers.

Currency Does Not Affect the Obligation

WHT applies regardless of whether the invoice is denominated in PLN, EUR, USD, or any other currency. For foreign-currency invoices, the withholding base is the gross PLN equivalent calculated at the NBP mid-rate on the business day preceding the payment date. AP teams must capture this rate and apply it to the gross invoice amount to determine the correct withholding in PLN.

The PLN 2 Million Threshold and Pay-and-Refund Mechanism

For AP teams handling service invoices, the PLN 2 million per recipient per calendar year threshold is mainly an escalation and classification-control point. It directly drives the pay-and-refund regime for related-party passive payments such as dividends, interest, and royalties; ordinary intangible service fees should be reviewed separately, especially where a payment could be reclassified as a royalty or another passive payment.

What Triggers the Mechanism

Track WHT-liable payments by recipient, but separate passive payments from service fees. The mandatory pay-and-refund threshold applies to related-party passive payments; service-fee totals are still useful for AP controls and tax review, but should not be treated as triggering statutory-rate withholding by default. Each recipient entity is tracked separately, and the counter resets on 1 January.

Payments to unrelated (arm's-length) foreign service providers fall outside the pay-and-refund mechanism entirely. Standard WHT rules still apply to those invoices, but there is no cumulative threshold triggering a rate change. The distinction matters: if your company pays an unrelated UK consultancy EUR 800,000 annually, the treaty rate governs from the first payment to the last. If the same amount flows to a related-party group entity, you need to watch the running total.

How Pay-and-Refund Works in Practice

Before an in-scope payment crosses PLN 2 million, AP can apply the reduced rate under the relevant Double Tax Treaty (DTT), provided you hold a valid Certificate of Residence (COR) and have completed due diligence. For passive payments that fall inside pay-and-refund, amounts above the threshold normally require domestic-rate withholding unless a relief route is in place. For service invoices, pause before applying this rule mechanically: confirm whether the payment is truly a service fee, a royalty, or another passive payment.

When pay-and-refund applies, the foreign recipient bears the cash flow hit. They must apply to KAS (Krajowa Administracja Skarbowa) for a refund of the difference between the statutory rate and the treaty rate. EY reports that Poland's pay-and-refund WHT regime tripled the refund waiting period to six months when the full reform entered into force on 1 January 2022, up from the previous two-month window. A six-month gap between overpayment and refund is significant enough to strain relationships with group entities that expected net-of-treaty-rate payments.

For AP, the control point is the classification decision before the threshold is reached. If a payment falls inside pay-and-refund and your ERP or payment system does not flag the transition, you may under-withhold or need to correct retroactively. If it is an ordinary service fee, unnecessary statutory-rate withholding can create avoidable supplier disputes.

The WH-OSC Alternative

For in-scope payments, one route can preserve treaty relief above the threshold: the WH-OSC (Oswiadczenie). This is a formal statement submitted to KAS by the management board of the Polish payer, certifying that:

All conditions for applying the reduced treaty rate have been verified
The company holds a valid COR for the recipient
Required due diligence has been completed
The company has no knowledge of circumstances that would disqualify treaty benefits

If the WH-OSC is filed on time for an in-scope payment, AP can continue applying the treaty rate past the PLN 2 million mark. This is not a routine filing: board members who sign assume personal liability for the certification, so most boards require a complete documentation package before approving it.

AP-Level Tracking

Your AP team should maintain a running cumulative total of gross payments per related-party recipient entity throughout the calendar year. A spreadsheet works for low-volume payers; high-volume shared services centers should build automated alerts in their ERP.

The practical workflow:

At 70-80% of the PLN 2 million threshold, flag the recipient relationship internally and notify the tax team or CFO.
Before crossing PLN 2 million, tax must decide whether any upcoming payment is in scope for pay-and-refund, whether treaty relief remains available, or whether a WH-OSC is appropriate.
If no WH-OSC or other relief route is available for an in-scope payment, withhold at the domestic statutory rate on the amount subject to the pay-and-refund mechanism and keep the threshold calculation in the payment file.
On 1 January, the counter resets and reduced treaty rates apply again (assuming valid documentation is in place).

Waiting until the threshold is actually breached leaves no room to prepare a WH-OSC filing or to communicate the rate change to the recipient. Early flagging is the only reliable way to avoid either a compliance gap or an emergency board certification.

Required Documentation for Reduced Treaty Rates

To apply a reduced withholding tax rate under a Double Tax Treaty instead of the statutory 20%, your company must hold specific documentation before releasing the payment. Applying a treaty rate without the required documents in hand exposes your company to reassessment, default interest, and penalties.

Here is what your AP team must collect for every foreign service provider claiming a treaty-reduced rate.

1. Certificate of Residence (COR)

This is the single most critical document. A COR is a tax residence certificate issued by the competent tax authority in the foreign entity's country, confirming that the recipient is a tax resident of that treaty jurisdiction.

Key requirements:

Must be valid on the payment date. If the certificate states a covered period, use that period. If it has no explicit validity period, track the accepted validity window from the issue date and refresh it before it expires.
Must come from the tax authority, not from the entity itself or its advisors.
Must confirm treaty-country residence. A certificate that merely confirms registration or taxpayer status is not sufficient.

Without a valid COR, no treaty rate can be applied. If you have every other document but lack the COR, you withhold at 20%.

2. Beneficial Owner Statement

This requirement applies specifically to passive income payments: dividends, interest, and royalties. The foreign recipient must declare that it is the beneficial owner of the income received.

For intangible service payments (consulting, advisory, management, technical services), this requirement does not apply. Save the declaration for payments where beneficial ownership is legally relevant.

3. Underlying Agreements and Contracts

Maintain the agreement behind each invoice. It supports service classification and proves the commercial basis for the payment.

4. Wire Transfer Confirmations

Retain proof-of-payment records that establish when the payment was made, the amount in PLN, and the transfer method. These records link your WHT filings to actual cash movements.

5. Business Activity Statements

Collect evidence that the foreign entity has genuine substance in its country of residence, such as business operations, employees, office presence, or other indicators that the arrangement is commercially real.

The Due Diligence Standard

Under the Polish CIT Act, your company as the payer bears the burden of exercising due diligence when applying treaty rates. A COR alone is not enough; the file should also show that the recipient has substance and that the transaction reflects economic reality.

The standard is reasonable verification, not forensic investigation. Where Poland's White List VAT verification for domestic supplier payments addresses domestic counterparty checks, cross-border WHT documentation focuses on treaty eligibility and substance.

If KAS challenges your applied treaty rate during an audit and you cannot produce this documentation, the consequence is straightforward: your company is liable for the full statutory-rate WHT that should have been withheld, plus default interest calculated from the original payment date.

What AP Teams Must Extract from Foreign Service Invoices

Before releasing a foreign service payment, capture the fields that drive WHT classification, treaty-rate support, and filing.

1. Service description / line item detail

Classify the payment as consulting, advisory, management, advertising, accounting, royalty, know-how, or outside WHT scope. Vague descriptions like "professional services" or "project support" need vendor detail or contract support before payment.

2. Gross payment amount and currency

Calculate WHT on the full pre-tax invoice amount. For foreign currency, use the NBP mid-rate from the business day preceding the payment date, not the invoice date.

3. Supplier entity name and legal form

Capture the full legal name exactly as it appears on the invoice and match it to the Certificate of Residence. Resolve legal-form or naming differences before applying a treaty rate.

4. Country of tax residence

Record the country of tax residence, not merely incorporation. It determines the treaty, rate, and COR match.

5. Tax identification number

Capture the foreign entity's tax ID or local equivalent for CIT-10Z and IFT-2R reporting, and verify it against the vendor master record.

6. Invoice date and payment due date

Track both, but prioritize the payment date: WHT must be remitted by the 7th of the month following payment.

7. Contract or PO reference

Link every invoice to the underlying agreement so the service scope is available when descriptions are ambiguous.

8. Related-party indicator

Flag related-party status in the vendor master so PLN 2 million threshold monitoring applies automatically. Related-party passive payments are the core pay-and-refund risk; service payments still need classification review before AP changes withholding treatment.

CIT-10Z, IFT-2R, and the AP Filing Calendar

Polish WHT compliance creates monthly remittance work plus annual CIT-10Z and IFT-2R reporting. The payment date drives the calendar.

Monthly WHT Remittance: By the 7th of the Following Month

Withheld tax on payments to non-residents must be remitted to the relevant tax office (Urzad Skarbowy) by the 7th of the following month. A March 15 payment, for example, creates an April 7 remittance deadline.

Your month-end close should include:

WHT-liable payments made during the period, matched against amounts actually withheld
Applied rates, confirming whether each payment used the standard 20% rate, a treaty rate, or pay-and-refund treatment
Currency conversions, confirming PLN equivalents used the correct NBP exchange rate

Catching errors monthly prevents year-end filing corrections.

CIT-10Z Annual Return: By End of January

The CIT-10Z is an annual summary of WHT withheld during the preceding calendar year, filed with KAS (Krajowa Administracja Skarbowa). It aggregates withholding by non-resident recipient and payment type.

Maintain throughout the year:

Cumulative payment totals per recipient, tracked in PLN
Withholding amounts per payment category (services, royalties, interest, dividends)
Reconciliation between monthly remittances and the annual total

If your ledger already segregates WHT-liable transactions by recipient and category, the January filing is a compilation exercise, not a research project.

IFT-2R Information Return: By End of March

The IFT-2R is a per-recipient information return for each non-resident entity that received WHT-liable payments during the preceding year. It reports:

Gross amounts paid to the recipient
WHT rates applied (statutory or treaty-reduced)
Amounts withheld and remitted

A copy also goes to the foreign recipient for foreign tax credit support, so accuracy matters beyond your own compliance.

If payment records, invoice details, certificates of residence, and withholding calculations are stored by recipient during the year, IFT-2R preparation becomes assembly rather than investigation.

Code WHT transactions so the gross amount, withheld tax, and net payment reconcile across monthly remittance, annual WHT returns, and JPK SAF-T reporting and GTU code classification requirements. When invoice-level data has been captured correctly throughout the year, each filing becomes a defined close task rather than a year-end reconstruction.