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. At that point, the pay-and-refund mechanism forces you to withhold at the full statutory domestic rate regardless of any double tax treaty benefits the recipient would normally qualify for. The recipient must then apply for a refund of the excess. For AP teams processing high volumes of cross-border service invoices, this threshold turns routine payment runs into a tracking exercise with real financial consequences.

Most guidance on Poland withholding tax on service invoices 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. The sections below walk through each step, from invoice classification through to filing deadlines.

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

Polish WHT law draws a hard line at PLN 2 million per recipient per calendar year. Once cumulative payments of intangible service fees, royalties, interest, or dividends to a single related-party non-resident cross that threshold, the rules change mid-stream, and AP must be ready.

What Triggers the Mechanism

The PLN 2 million threshold applies to the aggregate of all WHT-liable payments (the categories covered in the preceding section) made to one related-party recipient within a calendar year. 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 crossing 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. After crossing the threshold, you must withhold at the full statutory domestic rate: 20% on intangible service fees and royalties, 19% on dividends. The treaty rate no longer shields the payment.

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 operational shift is abrupt. One invoice processes at 5% under a treaty. The next, because it pushes the cumulative total past PLN 2 million, must process at 20%. If your ERP or payment system does not flag this transition, you will either under-withhold (creating a tax liability for your company) or need to correct retroactively.

The WH-OSC Alternative

There is one way to avoid the rate jump: 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, AP can continue applying the treaty rate past the PLN 2 million mark. However, this is not a routine filing. Board members who sign the statement assume personal liability for the accuracy of the certification. If KAS later determines the treaty rate was applied incorrectly, the consequences fall on the individuals who signed, not just the company. Most boards will require thorough documentation packages before agreeing to sign.

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, the company must decide: switch to statutory-rate withholding on the next payment, or coordinate with the management board to file a WH-OSC.
If no WH-OSC is filed, apply the statutory rate (20% for services, 19% for dividends) to every payment from the threshold-crossing invoice onward through 31 December.
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 current-year. A COR dated 2025 cannot support payments made in 2026. Collect updated certificates annually.
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. This distinction is a frequent source of confusion. AP teams that demand a beneficial owner declaration for consulting or advisory fees are imposing an extra administrative burden with no legal basis. Save the requirement for where it actually matters.

3. Underlying Agreements and Contracts

Maintain copies of the service agreement or contract that supports each invoiced amount. These documents serve two purposes: they establish the nature of the service (critical for correct classification under the relevant treaty article) and they evidence the commercial relationship between your company and the foreign provider.

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 economic substance in its country of residence and is not merely a conduit or shell. This can include descriptions of the entity's business operations, number of 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. You must also verify that the arrangement is genuine, that the recipient has real substance, and that the transaction reflects economic reality.

The standard is reasonable verification, not forensic investigation. But your documentation file for each foreign service provider should be complete, current, and internally consistent. Where Poland's White List VAT verification for domestic supplier payments addresses counterparty checks for domestic transactions, cross-border WHT documentation demands a broader set of evidence focused 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

Every foreign service provider invoice that crosses your AP queue requires a consistent set of data points before you can classify it, apply the correct WHT rate, and file accurately. The following checklist covers each field, why it matters for WHT processing, and where to watch for problems.

1. Service description / line item detail

This is the single most important field for WHT purposes. The description determines whether the payment falls into a WHT-liable category (consulting, advisory, management, advertising, accounting, royalties, know-how) or sits outside the scope entirely. Vague descriptions like "professional services" or "project support" are not sufficient. When you encounter them, request a detailed breakdown from the vendor or cross-reference the underlying contract to confirm the nature of the work. Misclassifying a payment here cascades into every downstream step.

2. Gross payment amount and currency

WHT is calculated on the full pre-tax invoice amount. If the invoice is denominated in a foreign currency, convert it to PLN using the NBP mid-rate from the business day preceding the payment date, not the invoice date. This PLN equivalent becomes the WHT base and feeds into your cumulative threshold tracking.

3. Supplier entity name and legal form

Capture the full legal name of the foreign entity exactly as it appears on the invoice. This name must match the entity shown on the Certificate of Residence. Any discrepancy between the invoice entity and the COR entity, even minor variations in legal form suffixes, must be resolved before you release payment. A mismatch can invalidate your basis for applying a reduced treaty rate.

4. Country of tax residence

This field determines which Double Tax Treaty applies and what reduced rate, if any, is available. Record the country of tax residence, not merely the country of incorporation. These can differ, particularly for holding structures. The country must align with the COR on file.

5. Tax identification number

The foreign entity's tax ID (or local equivalent) is required for CIT-10Z and IFT-2R reporting. Capture it from the invoice and verify it against the vendor master record. Missing or incorrect tax IDs will cause filing rejections.

6. Invoice date and payment due date

The payment date drives your reporting period: WHT must be remitted by the 7th of the month following the month of payment. The invoice date establishes the chronological audit trail. Track both, but prioritize accuracy on the actual payment date for filing deadlines.

7. Contract or PO reference

Link every invoice to the underlying agreement. The contract supports your service classification by documenting the actual scope of work, which matters when invoice descriptions are ambiguous. It also strengthens your position during a tax authority audit.

8. Related-party indicator

Flag whether the supplier qualifies as a related party under the CIT Act. This determines whether payments to that entity count toward the PLN 2 million annual threshold that triggers the pay-and-refund mechanism. Related-party status should be established at the vendor master level so it applies automatically to every invoice from that supplier, rather than requiring a manual check each time.

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

Polish WHT compliance involves three distinct filing obligations, each with its own deadline and data requirements. When AP teams treat these as calendar-driven checkpoints rather than year-end surprises, the reporting process becomes routine.

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

Every month, the withheld tax on all payments to non-residents must be remitted to the relevant tax office (Urząd Skarbowy) by the 7th of the next month. A payment made to a foreign consultant on March 15 means the corresponding WHT must reach the tax office by April 7.

Your month-end close should include:

Reconciliation of all WHT-liable payments made during the period, matched against the amounts actually withheld
Verification of applied rates, confirming whether each payment used the standard 20% rate, a reduced treaty rate, or was subject to the pay-and-refund mechanism
Currency conversion accuracy, ensuring PLN equivalents were calculated using the correct NBP exchange rate for each transaction

Catching errors here, at the monthly level, prevents them from compounding into year-end filing corrections.

CIT-10Z Annual Return: By End of January

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

To prepare CIT-10Z without a last-minute scramble, AP must 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, ensuring the sum of twelve monthly payments matches the CIT-10Z figure

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 filed 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 of the IFT-2R must also be sent to the foreign recipient. This is the document they use to claim foreign tax credits in their home jurisdiction, so accuracy matters beyond your own compliance.

AP's contribution is straightforward if the underlying data is clean: payment records, invoice details, certificates of residence, and withholding calculations per entity should already exist in your documentation files from the processes described in earlier sections. Preparing the IFT-2R then becomes assembly, not investigation.

Coordination with SAF-T Reporting

WHT transactions must also be correctly classified in Poland's JPK SAF-T filings. The amounts withheld, the gross payment figures, and the net amounts remitted to recipients all need to appear in the general ledger with coding that supports both WHT-specific returns and SAF-T requirements. AP teams should coordinate with tax and accounting staff to confirm that WHT entries use the correct account mapping, particularly given JPK SAF-T reporting and GTU code classification requirements that apply to certain transaction types.

Build WHT into your existing close calendar, not alongside it. When invoice-level data has been captured correctly throughout the year, each of these filings reduces to a defined, repeatable process.