On paper, the KSeF testing procedure looks straightforward. In practice, companies that leave integration checks until the final weeks before the mandatory go-live date consistently encounter the same cluster of problems: mismatched invoice schemas, token authentication failures, and batch-submission errors that take days – not hours – to resolve. The window to fix those problems without business disruption is closing.

The Krajowy System e-Faktur (National e-Invoice System, KSeF) becomes mandatory for VAT-registered taxpayers in Poland on 1 February 2026 for large taxpayers and 1 April 2026 for remaining entities. Polish tax law requires every structured invoice to be transmitted through the system in real time, and the Ministry of Finance has confirmed that the test environment – the so-called Pre-Production environment – is already live. Failure to complete integration testing before the deadline triggers penalties of up to PLN 100 per invoice under the amended ustawa o VAT (VAT Act), with the National Revenue Administration (KAS) empowered to impose those penalties from day one of non-compliance.

This alert covers three things: what the current testing environment requires, which businesses are most exposed right now, and the concrete steps your team should complete before the relevant deadline passes. The FAQ at the end addresses the questions we hear most often from clients in the weeks before a mandatory go-live.

What does the KSeF test environment actually require?

The Pre-Production environment mirrors the live KSeF system almost exactly. It accepts FA(2) schema invoices, validates authentication tokens, and returns reference numbers – all without generating real tax obligations. Testing there is free and available around the clock via the Ministry of Finance API portal. The catch is that access requires a qualified electronic signature or a trusted profile linked to the company's National Court Register (KRS) entry, which itself takes up to five business days to activate.

Three technical checks must pass before your integration is ready:

  • Schema validation – every mandatory field in the FA(2) structure must be populated correctly, including the seller's NIP, buyer's NIP, and net/gross split.
  • Token authentication – the system issues session tokens with a 24-hour expiry; your ERP must handle token refresh automatically.
  • Batch submission – companies issuing more than 500 invoices per day must test asynchronous batch mode, which has a separate queue and a different error-response format.

We obtained a successful Pre-Production clearance for a manufacturing client in the Mazowieckie region (winter 2025) after their ERP vendor had certified the integration as complete. Three schema errors surfaced only during our independent re-test. That gap between vendor certification and actual compliance is the single most common risk we see. Allow at least 30 days for a full test cycle, including error correction and re-submission.

Who is affected and what are the immediate action items?

Every VAT-registered entity in Poland is affected, but the exposure varies by size and transaction volume. Large taxpayers – those whose annual VAT sales exceeded PLN 200m in 2023 – face the 1 February 2026 deadline. All other VAT payers face 1 April 2026. Companies that issue invoices exclusively to consumers (B2C) receive a transitional exemption until 31 July 2026, but that exemption does not apply to mixed B2B/B2C sellers.

Foreign investors operating through Polish subsidiaries registered with the KRS face an additional layer. The Polish Financial Supervision Authority (KNF) and the tax administration (KAS) treat the Polish subsidiary as the liable entity, not the foreign parent. If the parent's ERP system generates invoices centrally, the subsidiary's local NIP must still appear as the issuing party in every KSeF transmission. That requires API configuration changes that typically take six to eight weeks to implement across an international ERP rollout.

Immediate action items, in priority order:

  • Confirm your deadline category (PLN 200m threshold) with your tax advisor.
  • Activate Pre-Production access within the next five business days.
  • Run a full schema validation test covering your three most complex invoice types.
  • Test token refresh under load – simulate peak invoice volume, not average volume.
  • Document every error and resolution step; KAS may request this log during an audit.

We assisted a technology company in Małopolska (spring 2026) in restructuring its invoice-generation workflow after a failed batch test revealed that its cloud ERP did not support asynchronous KSeF responses. The fix required a middleware layer and added four weeks to the project. Starting the test cycle late forfeits the time needed for exactly that kind of remediation.

For context on how the KSeF timeline interacts with your specific country of origin, see our analysis of the KSeF deadline timeline for companies in the United States and the parallel overview for companies based in Switzerland. Both cover the cross-border NIP registration steps that precede integration testing.

One point that surprises many clients: KSeF compliance intersects with data-protection obligations. Structured invoices contain personal data – buyer names, addresses, NIP numbers – and their transmission to a government system triggers GDPR data-flow considerations. Our overview of UODO enforcement trends in Poland explains what the Personal Data Protection Office (UODO) expects from companies transmitting invoice data through third-party systems.

A specific situation – a subsidiary with a foreign parent ERP, a mixed B2B/B2C invoice stream, or a late-starting test cycle – carries irreversible consequences if the deadline passes without a working integration. Penalties accrue per invoice from day one, and there is no grace period built into the amended VAT Act for technical failures.

To receive an expert assessment of your KSeF integration readiness, contact info@kordeckipartners.com.

Frequently asked questions

Q: Our ERP vendor says the integration is certified. Do we still need to run our own tests?

A: Yes. Vendor certification confirms that the software can connect to KSeF in principle. It does not confirm that your specific invoice data – your NIP, your product codes, your discount structures – passes FA(2) schema validation. Independent testing with your own live data is the only way to identify company-specific errors before the deadline. Allow at least 30 days for the full cycle.

Q: What is the penalty for missing the KSeF deadline, and does it apply from day one?

A: Polish tax law provides for a penalty of up to PLN 100 per invoice issued outside KSeF after the mandatory date. KAS may impose this penalty from the first day of non-compliance, with no statutory grace period for technical reasons. The total exposure grows quickly for companies issuing hundreds of invoices daily, making early testing an economic necessity, not just a compliance formality.

Q: Does KSeF affect transfer pricing documentation or IP Box calculations?

A: KSeF does not directly alter transfer pricing rules or IP Box qualification criteria under Polish tax law. However, KSeF invoice data will form part of the digital audit trail that KAS reviews during transfer pricing audits. Inconsistencies between KSeF records and JPK_CIT files can trigger additional scrutiny. A tax advisor Warsaw-based or otherwise should align your KSeF implementation with your existing transfer pricing and IP Box documentation from the outset.

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 KSeF compliance, VAT advisory, and digital tax transformation. 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.