Poland’s KSeF 2.0: Lessons from the first wave

In the world of e-invoicing, 2025 was a year of "waiting for Poland". After a technical audit and several delays, the redesigned KSeF 2.0 officially went live on February 1, 2026.

We are now several weeks into the mandate for Wave 1 (large taxpayers with over PLN 200 million turnover). While the total nationwide adoption is still a few months away, the early data from February gives us a clear look at how the system is holding up under pressure.

A stable start for KSeF 2.0

Despite the pre-launch anxiety, the Ministry of Finance reported a surprisingly smooth first week. By February 4:

• 50,000+ invoices were successfully processed in the first few days.

• 320,000 users logged into the new Taxpayer Application 2.0.

Contrary to the outages seen in earlier voluntary phases, the Ministry has described the system as "operating stably and in line with its intended purpose," with early load tests and the new API architecture passing without major disruption.

The "teething issues": What’s actually happening?

While the central hub is stable, the "last mile" of integration is where the friction lies. Our resident experts have noted three specific hurdles that emerged in the first 21 days:

1. The token trap: On February 1, the legacy Certificate and Authorizations Module (MCU) was permanently shut down. Many firms found that tokens generated under KSeF 1.0 were no longer valid, leading to a scramble to re-issue credentials through the new KSeF 2.0 portal, which replaced the old MCU functionality.

2. API latency: While the system hasn't crashed, peak-hour "slowdowns" are real. API response times have fluctuated between 2 and 5 seconds, which is a significant jump from the sub-1-second target businesses need for high-volume automated processing.

3. Schema strictness: The move to the FA(3) XML schema brought stricter validation rules. We’ve seen a spike in rejection errors due to missing mandatory fields that were previously optional, proving that "technical readiness" is nothing without "data quality."

The "safety net" of 2026

Perhaps the most important takeaway for those in the upcoming April wave is the Ministry’s current mindset: Compliance over Punishment.

The Ministry confirmed in a February 3rd Q&A that no financial penalties will be imposed in 2026. Errors are currently being treated as learning opportunities. This "grace period mindset" has successfully lowered the temperature, allowing tax offices to work with businesses to fix validation errors rather than issuing fines.

What’s next: The April 1 "stress test"

While 320,000 users logged in this month, that is just a fraction of what’s coming. On April 1, 2026, the mandate expands to the remaining 2 million other VAT taxpayers in Poland, excluding micro-businesses, which will not be impacted until 2027.

The lesson for Wave 2? Don't rely on "Offline24" as a permanent solution. While the fallback works for technical hiccups, the volume expected in April means that only a fully automated, API-integrated workflow will keep your business moving at speed.

Strategy takeaways from our resident experts:

• Audit your Master Data now: The FA(3) schema is unforgiving. If your ERP data is messy, KSeF will reject it.

• Test your 2.0 Tokens: If you haven't migrated from the old MCU yet, do it today.

• Watch the "Receipt Obligation": Remember, since Feb 1, all Polish businesses must be able to receive KSeF invoices, even if they aren't yet mandated to issue them.

Is your business ready for the April 1 expansion?

If you weren't in the first group, your "go-live" countdown is now under 40 days. While Wave 1 handled the initial stress test, Wave 2 is nearly seven times larger in terms of business volume.

We’ve pulled together this short and practical checklist to help you ensure you don't hit the same "teething issues" that early adopters faced.

1. Technical identity & authentication

[ ] Abandon KSeF 1.0 Tokens: If you have tokens generated before February 2026, delete them. They are incompatible with KSeF 2.0.

[ ] Generate Production Tokens Now: Access the new Taxpayer Application 2.0 (replacing the old MCU) to generate new API keys. Don’t wait until April 1st - Wave 1 saw a 48-hour bottleneck for certificate issuance.

[ ] Set Up "Qualified Seals": If you are a larger SME with multiple departments, ensure you have a qualified electronic seal. This allows for automated "hands-off" signing without needing an individual’s Trusted Profile (Profil Zaufany) for every batch.

2. Data quality & schema mapping

[ ] FA(3) Schema Audit: Map your ERP fields to the new FA(3) structure. Wave 1 data shows that most rejections occur in the "Buyer" block - therefore, we recommend that you ensure NIP numbers are cleaned, and address fields are split exactly as the XML requires.

[ ] Manage Your Attachments: KSeF does not support generic attachments, such as PDFs or images. While structured invoice-related data can be included via the “Attachment” (zalacznik) node within the XML, this functionality requires prior approval from the tax authority and is subject to a 3MB total file size limit. Alternatively, if your invoices require work logs, time sheets, or meter readings, you must establish a separate channel (email/portal) for these.

[ ] Check for Mandatory "New" Fields: The FA(3) schema is stricter than its predecessors. Ensure your system captures "DataWytworzeniaFa" (the timestamp of XML creation), which is now critical for tracking.

3. Operational continuity

[ ] Test "Offline24" Fallback: Download your KSeF Certificate now. This certificate is the only way to generate the mandatory QR codes required if you need to issue an invoice during a system outage or peak-hour slowdown.

[ ] Review Accounts Payable (AP) Flow: Even if you aren't issuing via KSeF yet, you are legally required to be able to receive them since February 1. If your suppliers are in Wave 1, they are already sending invoices to the portal - make sure your team knows how to fetch them.

[ ] Update Payment Vouchers: While KSeF numbers aren't mandatory on payments until 2027, your systems should start recording the long KSeF ID assigned to every accepted invoice now to avoid a massive data-entry debt later.

4. The "safety net" strategy

[ ] Embrace the 2026 Grace Period: Remember that the Ministry has confirmed no financial penalties for errors throughout 2026. Use this to your advantage: if an invoice is rejected, fix it and resend it. The focus is on learning, not punishment.

[ ] Prepare for Peak Latency: We’ve seen API response times jump to 5 seconds during peak hours. If your business issues high-volume invoices, schedule your batch transmissions for early morning or late evening to avoid the 10:00 AM "peak hour" rush.

Insights from our resident experts:

"The biggest mistake we saw in Wave 1 was businesses assuming their 2025 'test' tokens would work in the 2026 'live' environment. They don't. Your priority this week should be establishing a fresh handshake with the KSeF 2.0 production API."

To stay ahead of the compliance curve and receive updated information first, sign up for our tax compliance newsletter, and follow us on LinkedIn for even more timely announcements.