A mid-sized Warsaw distributor completes its accounting software upgrade in March 2026, confident that KSeF invoices will flow automatically from 1 April. On the first working day of the new regime, the system returns a validation error on every outbound invoice. The company cannot issue invoices. Cash flow stops. The problem was not the software – it was the untested integration between the ERP and the National e-Invoice System (Krajowy System e-Faktur, KSeF).

Mandatory KSeF applies to VAT-registered taxpayers in Poland from 1 February 2026 for large taxpayers and 1 April 2026 for remaining active VAT payers. Failure to issue invoices through KSeF triggers a financial penalty of up to 100% of the VAT shown on the invoice, and each non-compliant document is treated as a separate infringement. The Ministry of Finance operates a dedicated test environment – the KSeF Test System – where companies can validate their integration at no cost before the live deadline.

This alert covers three things: what the KSeF testing environment offers, which businesses face the most urgent exposure, and the concrete steps your team should complete before the applicable deadline. The article also flags how KSeF intersects with transfer pricing documentation and IP Box structures – two areas where invoice data integrity carries additional compliance weight.

What has changed and who is affected?

Polish tax law now mandates electronic invoicing through KSeF for all VAT-registered entities operating in Poland. The National Revenue Administration (Krajowa Administracja Skarbowa, KAS) enforces the obligation. The National Court Register (Krajowy Rejestr Sądowy, KRS) data is used to verify entity identity during the KSeF onboarding process. The threshold that determines your go-live date is annual turnover: entities exceeding PLN 200 million in the prior tax year were required to connect from 1 February 2026. All other active VAT payers must comply from 1 April 2026.

The change affects more than just the finance department. IT teams must configure API credentials. Legal and tax advisors must review invoice content rules – KSeF rejects documents that omit mandatory fields, including the buyer's VAT identification number in most B2B transactions. Companies running IP Box regimes or transfer pricing arrangements should note that KSeF invoice data will form part of the evidentiary record in any KAS audit. An invoice rejected by KSeF is not a valid invoice under Polish VAT law. That gap in the chain can unravel an otherwise clean transfer pricing position.

Foreign investors with Polish subsidiaries face an additional layer. A German parent company receiving invoices from a Polish entity needs to confirm that its own accounts-payable system can read and archive KSeF-structured XML. Failure to archive correctly triggers a separate documentation penalty. The deadline is fixed. There is no grace period for technical difficulties discovered after go-live.

How should you test your KSeF integration before the deadline?

The Ministry of Finance provides a live test environment at test.ksef.mf.gov.pl. It mirrors the production system. You can send, receive, and query invoices without generating real tax obligations. Testing should begin at least 30 days before your applicable deadline – earlier if your ERP requires custom development. Companies that begin testing fewer than 14 days before go-live consistently encounter problems they cannot resolve in time.

We secured a correction of a VAT surcharge exceeding PLN 1.8m for a manufacturing client in the Mazowieckie region (autumn 2025). The root cause was an invoice schema mismatch that had gone undetected for six months. Early KSeF testing would have caught it at zero cost.

The core testing sequence covers four steps:

  • Register your entity in the KSeF test environment using your NIP (tax identification number) and qualified electronic signature or trusted profile.
  • Send at least 20 test invoices covering your most common transaction types – domestic sales, intra-EU supplies, advance invoices, and corrective notes.
  • Verify that the system returns a valid UPO (Urzędowe Poświadczenie Odbioru – official receipt confirmation) for each document within the 60-second processing window.
  • Test your archiving pipeline: confirm that KSeF XML files are stored in a format accessible for at least 10 years, as required by Polish tax legislation.

A tax advisor in Warsaw with KSeF onboarding experience can run a gap analysis against your current setup in one to two working days. That analysis should cover API authentication, schema version alignment (FA(2) is the current mandatory schema), and user permission mapping. Do not rely on your software vendor's generic test report. That report tests the vendor's system – not your specific configuration.

Our team obtained interim protection of invoice data for a logistics client in Lower Silesia facing a KAS audit (spring 2026). The client had tested in the KSeF environment but had not validated the archiving step. That single gap cost three weeks of management time and significant advisory fees. The lesson is straightforward: test the full chain, not just the send function.

What should you do now?

Time compression is the primary risk at this stage. If your applicable deadline is 1 April 2026, you have a narrow window. Prioritise the following actions. Each has a direct consequence if skipped.

  • Confirm your go-live date based on your prior-year turnover figure – the PLN 200 million threshold determines whether you were already in scope from February.
  • Access the KSeF test environment today and send one invoice. A first-attempt failure tells you immediately whether your credentials and schema are aligned.
  • Review your transfer pricing documentation to ensure that KSeF invoice references are consistent with intercompany pricing records.
  • Check whether your family foundation (if applicable) issues invoices in its own name – family foundations registered as VAT payers are within scope.

Polish tax law does not provide a technical-difficulty exemption. A system outage on your side is not a defence. KAS has confirmed that penalty proceedings will follow the first audit cycle after go-live. The penalty is calculated per invoice, not per period. A company issuing 500 invoices per month and missing the deadline for 30 days faces exposure across roughly 500 documents. That exposure is irreversible once the audit opens.

For cross-border structures, review the double tax treaty between Poland and the Czech Republic if your group has Czech entities receiving Polish invoices – KSeF status affects the documentary evidence chain for treaty relief claims. For entities under financial stress, the insolvency proceedings timeline is relevant if cash-flow disruption from invoice failures triggers liquidity problems. And for intra-Polish holding structures, the domestic tax treaty provisions article provides context on how invoice data interacts with withholding tax positions.

Your specific integration setup determines your actual risk level. A generic checklist is not a substitute for a configuration review against your ERP, your transaction volume, and your invoice types. Discovering a schema error after 1 April 2026 forfeits the option of a penalty-free correction.

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

Frequently asked questions

Q: Can we use our software vendor's test certificate as proof of KSeF compliance?

A: No. A vendor certificate confirms that the vendor's software passed validation in a controlled environment. It does not confirm that your specific ERP configuration, your API credentials, your invoice schema version, and your archiving pipeline are all correctly connected. KAS will assess your system, not your vendor's. You must run your own end-to-end test using your production entity data in the KSeF test environment.

Q: How long does the KSeF test environment take to process a test invoice?

A: The test environment processes invoices within 60 seconds under normal load. If you receive a UPO within that window, the schema and credentials are correctly configured. If the system returns an error code, you have a specific rejection reason – typically a missing mandatory field or an incorrect schema version. The current mandatory schema is FA(2). Allow at least two full business days for iterative testing if your first submission fails.

Q: Does KSeF apply to invoices issued by a Polish family foundation?

A: A family foundation registered as an active VAT payer in Poland is within the scope of the KSeF obligation. The foundation's VAT registration status – not its legal form – determines applicability. If the foundation issues invoices for economic activity subject to VAT, those invoices must be issued through KSeF from the applicable deadline. A tax advisor Warsaw-based with experience in family foundation structures can confirm the foundation's specific VAT status and integration requirements within one working day.

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 onboarding, VAT compliance, and tax advisory. 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.