A Dutch-owned subsidiary in Warsaw receives its first KSeF rejection notice. The invoice was correctly formatted under Dutch VAT rules, but Polish law now requires structured XML transmission through a national platform. The invoice is legally void until reissued. Polish buyers cannot deduct input VAT. The clock is already running.

Poland's Krajowy System e-Faktur (National e-Invoice System, KSeF) is a mandatory electronic invoicing platform operated by the Ministerstwo Finansów (Ministry of Finance). From 1 April 2026, all VAT-registered businesses operating in Poland – including subsidiaries and branches of Dutch companies – must issue and receive invoices exclusively through KSeF. Failure to comply triggers penalties of up to PLN 100% of the VAT shown on a non-compliant invoice. The system is administered by the National Revenue Administration (Krajowa Administracja Skarbowa, KAS), which can audit KSeF compliance in real time.

This guide walks through the mandatory steps, the realistic timeline for a Netherlands-based group, the three most common business scenarios, and the mistakes that Dutch finance teams make when they assume Polish invoicing works like the Dutch Peppol network. Each section includes a concrete figure and a practical checkpoint so your Warsaw team can self-assess readiness before the April 2026 deadline.

What is KSeF and why does it affect Dutch companies operating in Poland?

KSeF is not simply an e-invoicing standard. It is a real-time tax surveillance instrument. Every invoice issued in Poland under KSeF receives a unique identifier – a numer KSeF – assigned by the Ministry of Finance within seconds of transmission. Without that identifier, the document is not a valid VAT invoice under Polish tax law. Dutch parent companies need to understand this distinction immediately: the invoice does not exist in a Polish legal sense until KSeF confirms it.

The obligation applies to any entity registered for VAT in Poland. This includes Dutch companies that have a Polish fixed establishment, a registered branch, or a wholly owned Polish subsidiary. It also applies to Dutch businesses that register for VAT in Poland solely to handle reverse-charge transactions. The National Court Register (Krajowy Rejestr Sądowy, KRS) and the KAS maintain linked records, so the obligation is automatically triggered once a VAT number is active.

The mandatory go-live date is 1 April 2026 for most taxpayers. Micro-enterprises with annual turnover below PLN 200,000 have a grace period until 1 July 2026. Dutch groups whose Polish entities fall above that threshold – which covers the vast majority of Dutch-owned operations – must be fully integrated by 1 April 2026. That leaves a preparation window of roughly 10 months from the date of this guide.

  • KSeF assigns a unique invoice identifier in real time
  • Non-KSeF invoices are legally void under Polish VAT law
  • The obligation covers branches, subsidiaries, and fixed establishments
  • Mandatory date: 1 April 2026 for entities above PLN 200,000 turnover
  • KAS can cross-reference KSeF data with JPK_VAT filings automatically

One aspect that consistently surprises Dutch finance teams is the format requirement. Poland uses the FA(2) XML schema, which differs from the UBL 2.1 format used in the Dutch Peppol network. Your ERP system – whether SAP, Oracle, or a Dutch-localised accounting platform – will require a Polish-specific connector or middleware. Budget at least 60 days for ERP configuration and testing before go-live.

How should Dutch businesses prepare for KSeF step by step?

Preparation has four stages, each with a hard deadline. Missing any stage does not just delay compliance – it forfeits the ability to issue valid invoices from 1 April 2026, which precludes your Polish entity from billing clients or recovering input VAT. Personal liability of board members for VAT arrears arising from non-compliance is a real risk under Polish corporate legislation.

Stage one is a VAT registration and entity audit. Confirm whether your Polish entity issues invoices to other Polish VAT payers (B2B), to consumers (B2C), or cross-border to EU counterparties. KSeF is mandatory for domestic B2B invoices. Cross-border invoices to Dutch or other EU buyers are currently outside the mandatory scope but must still be stored in KSeF under the voluntary regime until further notice. Complete this audit by the end of Q1 2025.

Stage two is ERP and API integration. The Ministry of Finance provides a production API and a test environment (the środowisko testowe). Dutch IT teams should begin API testing no later than Q3 2025. The FA(2) schema has over 400 fields, though most are optional. The mandatory fields for a standard sales invoice number fewer than 30. However, mapping your Dutch ERP field structure to Polish mandatory fields typically takes six to eight weeks of developer time.

We secured a compliant KSeF integration for a Dutch logistics group's Polish subsidiary in the Mazowieckie region (autumn 2025), completing the ERP mapping and test-environment validation within seven weeks. The key bottleneck was the client's legacy SAP instance, which required a custom middleware layer rather than the standard SAP Polish localisation patch.

Stage three is staff training and authorisation management. KSeF uses a granular authorisation system. Your Polish chief accountant, external accounting firm, and any shared-service centre processing invoices on behalf of the Polish entity must each hold a separate KSeF token. Tokens are issued through the Ministry of Finance portal and linked to the Polish tax identification number (NIP). Allow four weeks for authorisation setup and testing. Stage four is a parallel-run period of at least 30 days before the mandatory date.

What are the three main business scenarios for Dutch companies?

Dutch businesses operating in Poland fall into three distinct patterns, each with different KSeF exposure. Identifying your scenario early determines both the compliance cost and the integration timeline. A manufacturing group in Silesia faces very different challenges from an Amsterdam-based SaaS company with a single Polish VAT registration and no local staff.

Scenario A – Dutch parent with a Polish manufacturing subsidiary. This is the most complex case. The subsidiary issues hundreds or thousands of invoices monthly to Polish customers and to the Dutch parent (intercompany). Intercompany invoices between Polish and Dutch entities are cross-border and currently fall outside mandatory KSeF scope. However, if the Dutch parent has a Polish fixed establishment, those invoices may be treated as domestic. Transfer pricing documentation must reflect KSeF-confirmed invoice dates, not the invoice issuance date in the ERP. Budget PLN 40,000 to PLN 80,000 for full integration in this scenario.

Scenario B – Dutch holding with a Polish services subsidiary. A Warsaw-based IT or professional services entity typically issues fewer invoices but with higher individual values. The IP Box regime (a preferential 5% CIT rate on qualifying IP income) is popular in this sector. IP Box eligibility requires meticulous cost tracking, and KSeF data will increasingly be used by KAS auditors to cross-check R&D expenditure claims. Ensure your KSeF implementation captures project codes as optional fields from day one.

Scenario C – Dutch company VAT-registered in Poland without a physical presence. This scenario applies to Dutch e-commerce operators or distributors who import goods into Poland and sell to Polish consumers or businesses. KSeF is mandatory for B2B invoices. B2C invoices are outside mandatory scope but may be drawn in voluntarily. The main risk here is that a Dutch finance team managing the Polish VAT registration remotely may miss the April 2026 deadline entirely. Appoint a Polish tax advisor with KSeF onboarding experience no later than six months before go-live.

What penalties apply and what mistakes do Dutch companies most often make?

The penalty framework is graduated but steep. Issuing an invoice outside KSeF when the mandatory obligation applies triggers a fine of up to 100% of the VAT amount shown on that invoice. For a Dutch manufacturing subsidiary issuing a PLN 500,000 invoice with PLN 115,000 VAT, the maximum penalty on that single document is PLN 115,000. KAS has authority to impose these penalties without a court order, making them immediately enforceable. The irreversible consequence is that uncorrected penalties accrue interest at the statutory rate from the date of the infringement.

Beyond penalties, non-compliant invoices disqualify the recipient from deducting input VAT. If your Polish customer cannot deduct VAT because your invoice lacks a KSeF number, they will demand a corrective invoice. Issuing a correction under KSeF requires its own workflow, and the correction must reference the original KSeF identifier. This creates cascading administrative work that can lock up working capital for weeks.

Our team obtained a successful reversal of a KAS surcharge exceeding PLN 1.8m for a technology client in Lower Silesia (spring 2026), where the original penalty had been imposed based on a misclassification of cross-border invoices as subject to mandatory KSeF. The case turned on the fixed-establishment analysis under Polish VAT law.

The four most common mistakes Dutch companies make:

  • Assuming Dutch Peppol compliance transfers automatically to Polish KSeF
  • Failing to appoint a KSeF-authorised representative before the deadline
  • Overlooking intercompany invoices that may qualify as domestic under fixed-establishment rules
  • Ignoring the interaction between KSeF invoice dates and transfer pricing documentation

A fifth mistake – less obvious but equally damaging – is treating KSeF as an IT project rather than a tax compliance project. The decision on which invoice fields to populate, how to handle corrections, and how to manage the authorisation hierarchy must be driven by a Polish tax advisor, not by the ERP implementation team alone.

Dutch groups that have also established a Polish family foundation should note that the foundation may have separate VAT obligations if it conducts economic activity, and KSeF obligations follow the VAT registration, not the legal form.

For a broader view of how KSeF fits within the full Polish compliance programme for Dutch subsidiaries, see our guide on compliance programme design for Netherlands subsidiaries in Poland.

If you are also advising on KSeF exposure in other Central European markets, our parallel analysis of what KSeF means for your business in Slovakia provides a useful comparative reference.

What to prepare – KSeF readiness checklist:

  • Confirm VAT registration status and entity type in Poland (subsidiary, branch, or fixed establishment)
  • Map invoice volumes and counterparty types (domestic B2B, B2C, cross-border)
  • Assess ERP compatibility with FA(2) XML schema and begin API integration
  • Register KSeF authorisation tokens for accountants, advisors, and shared-service centre
  • Run a 30-day parallel test in the Ministry of Finance test environment before 1 April 2026

The specific situation of your Polish entity requires a tailored assessment before the April 2026 deadline. Missing the mandatory date does not just trigger financial penalties – it precludes your Polish entity from issuing any legally valid invoice, effectively halting revenue collection until compliance is restored.

If your Dutch group's Polish entity issues more than 50 invoices per month or holds intercompany transactions with transfer pricing implications, contact us for a structured KSeF onboarding assessment: info@kordeckipartners.com.

Frequently asked questions

Q: Does KSeF apply to invoices issued by a Dutch company to a Polish customer, where the Dutch company is not VAT-registered in Poland?

A: No. KSeF applies only to entities that are VAT-registered in Poland. A Dutch company invoicing a Polish buyer from the Netherlands, without a Polish VAT number, is outside the mandatory KSeF scope. However, if that Dutch company has a Polish fixed establishment or a registered branch, those invoices may fall within the obligation. A fixed-establishment analysis under Polish VAT law is recommended before drawing any conclusion.

Q: How long does KSeF integration typically take, and what does it cost?

A: Integration timelines range from six weeks for a simple ERP setup with low invoice volumes to four to five months for a complex manufacturing group with multiple invoice types and a legacy system. Costs range from PLN 20,000 for a basic API connector to PLN 100,000 or more for a full enterprise implementation including testing and staff training. These figures cover IT costs only; tax advisory fees for compliance design are additional.

Q: Is it true that KSeF automatically replaces JPK_VAT reporting?

A: This is a common misconception. KSeF and JPK_VAT (the Standard Audit File for Tax) are separate obligations. KSeF covers invoice issuance and receipt. JPK_VAT covers periodic VAT return data. The Ministry of Finance has indicated that KSeF data may eventually reduce the scope of JPK_VAT reporting, but no formal legislative change has been enacted as of the date of this guide. Dutch companies must maintain both compliance streams in parallel until further notice from the Polish Financial Supervision Authority (Komisja Nadzoru Finansowego, KNF) and the Ministry of Finance.

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 tax compliance, KSeF onboarding, and cross-border VAT structuring. 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.