The system didn't collapse. That's the first and most important finding after the first quarter of mandatory KSeF (Poland's national e-invoicing system) — against the gloomiest forecasts, invoices get issued, delivered, and reconciled. The second finding is less comfortable: the real problems showed up where few people were looking.
First, the dates, because "mandatory KSeF" means different things for different companies. The largest taxpayers have been issuing through KSeF since 1 February 2026; everyone else — including JDG (sole proprietorships) — since 1 April 2026 (MF rollout schedule). So we now have a full quarter of the system running in mandatory mode, and the first weeks in which it applies to the smallest firms too.
This is a good moment to look back, because right now fixing your habits is cheapest. The penalty-free transition period runs until the end of 2026, and sanctions begin on 1 January 2027. Below: what happened, what genuinely changed, and what to do before the grace window closes.
A short timeline: 1 February and 1 April
The 1 February launch was a stress test — and the infrastructure failed it in the first hours. From early morning, taxpayers reported instability in the production API, even though traffic wasn't yet universal. In the first three days (1–3 February), industry estimates put at least 100,000 invoices through KSeF.
The second bottleneck was login. Overload of Profil Zaufany (the Polish "Trusted Profile" used for public-service authentication) made access difficult — and importantly, this was not a security problem in KSeF itself, but in the shared authentication layer that many public services rely on simultaneously.
On 1 April, the obligation reached a much larger wave of companies. There was no paralysis, but that's exactly when — with far more issuers — the problems that surfaced were organizational, not technical. And those problems define this retrospective.
What companies feared — versus what actually broke
Most pre-launch anxiety was about technology and security: that the system wouldn't handle the load, that data would leak, that an invoice would "vanish." The first quarter showed the weight lies elsewhere.
What we feared What's actually happening The system buckles under load It runs; login and the API wobbled mainly in the first days Data leaks from KSeF GDPR risk arises "in transit" — in logs, XML files, test environments (iSecure) The system is hard to operate Operating it is manageable; the change in work logic is the hard part The invoice gets lost The invoice exists — but with a different status, date, and number than in your system
The consensus from the front line is fairly consistent: the biggest challenge isn't "does KSeF work," it's the abrupt change in how you work with a document. A structured invoice (an XML file) passes technical validation, receives a KSeF status and number — and only then functions in commerce. That's a completely different rhythm from "I create a PDF and email it."
Five things that genuinely changed daily work
1. An invoice exists once it reaches KSeF — the "two dates" problem
This is the biggest mental shift. A document takes legal effect in commerce when KSeF accepts it, not when you "wish it into existence." In practice a gap appears between the issue date and the acceptance date in the system — especially when an invoice is sent late without grounds for offline mode. The detailed rules for determining dates are set by MF (the Ministry of Finance) and are worth consulting directly when in doubt (KSeF guidance).
2. KSeF ↔ ERP mismatches
April's most insidious error: an invoice has correct values in KSeF, but after import into the accounting system different amounts appear — net/gross out of sync, wrong rounding, reordered line items. The document is formally correct, yet the data "doesn't add up." That costs hours of manual untangling.
3. A PDF "with no KSeF number"
The visualization isn't the document. A client sometimes receives a PDF without a KSeF number even though the invoice already exists in the system. Confusion follows: "is this invoice even issued?" The KSeF number is now the core identifier — without it, matching a payment to a document is hard, and from 2027 it becomes mandatory on transfers.
4. Duplicate risk
An invoice can arrive through three channels at once: KSeF, email, and the client portal. Without a clear procedure, that ends in double-posting and manual cleanup. It's a classic organizational problem, not a technical one — which is exactly why it's so easy to miss.
5. Corrections that are correct but unreadable
Correction invoices can be formally flawless yet hard to understand from the visualization alone. If the team doesn't know "what this correction actually changes," the risk of a wrong response on the recipient's side grows.
Illustrative scenario (plausible, not from a specific event): a small service company issues an invoice on Friday evening but sends it to KSeF only on Monday. In its system the date is Friday; in KSeF, Monday. The bookkeeper asks which date to use; the client sees a different number than on the PDF sent earlier. Nothing "broke," yet half a day of work is created. That's the typical cost of the first quarter.
A real rejection we see most often looks technically like this:
Status: REJECTED
Code: XML_PARSE_ERROR
Message: Invalid FA(3) namespace:
expected http://crd.gov.pl/wzor/2023/06/29/12648/
The most common causes in the first weeks were exactly these: errors in XML structure, mismatch with the current invoice schema, and discrepancies between the test and production environments.
The transition period: what's still allowed, and when penalties start
The first quarter ran on "soft" rules — worth using rather than being lulled by.
Penalties suspended until the end of 2026. Sanctions for errors and non-compliance begin only on 1 January 2027 (MF legal basis).
Value-based exemption for the smallest firms. Until the end of 2026, invoices may be issued outside KSeF if the combined monthly B2B sales value from those documents does not exceed PLN 10,000, with a single invoice up to PLN 450. This is a temporary relief, not a permanent exemption.
KSeF number on transfers from 2027. From 1 January 2027, the KSeF number becomes part of payments between taxpayers, including the split-payment mechanism.
The legal basis is the Act of 5 August 2025 (Journal of Laws 2025, item 1203). Interpretive questions — dates, scope, exemptions — are worth verifying directly at the source, because here MF is the authority, not a software vendor.
What this means for the smallest firms and accounting offices
For a sole proprietorship, KSeF isn't just a new delivery channel — it's a change in daily habits and a need to tidy up cooperation with bookkeeping. The worst strategy is acting in panic, or "putting it off until December."
On the accounting-office side there's an interesting shift: with data arriving in structured form, less time goes to re-keying and more to advisory and business decisions. The first quarter was chaotic mainly where simple procedures were missing — who sends and receives invoices, when, and through which channel.
Checklist: what to do in the coming weeks
Fix a single moment for sending to KSeF and stick to it, to avoid the "two dates" problem.
Spot-check a few invoices in KSeF against your accounting system — verify net/gross, rates, and rounding.
Start identifying documents by KSeF number, not by the PDF alone.
Define an anti-duplicate rule — which channel (KSeF, email, portal) is the "source of truth."
Test a correction end to end and confirm the recipient understands what's changing.
Verify login and permissions in advance, not on the day you send an important invoice.
Don't wait for December — the grace window closes on 31 December 2026.
Conclusion
The first quarter of mandatory KSeF proved the risk isn't "does the system work," but the organization of work: two dates, ERP mismatches, the KSeF number, and duplicates. These are solvable with procedure and a good tool — while the penalty-free period lasts.
Biurko takes that layer off your plate: it tracks KSeF statuses and numbers, catches rejections before they become problems, keeps corrections and UPO (the official confirmation of receipt) in order, and closes the loop so the date and the document agree. Create an account and try Biurko free for 14 days at biurko.io — before 1 January 2027 ends the window for calm fixes.
FAQ
Is KSeF already mandatory for small businesses? Yes. Small businesses, including sole proprietorships (JDG), must issue invoices through KSeF from 1 April 2026. The largest taxpayers have done so since 1 February 2026. The obligation to receive invoices via KSeF applies to every entity with a NIP (Polish tax ID) from February.
What happens if you don't issue an invoice in KSeF in 2026? In 2026 a penalty-free transition period applies. Sanctions for errors and non-compliance start only on 1 January 2027. That doesn't mean the obligation is absent — the invoice must still be issued in line with the rules.
Can I still issue paper invoices after 1 April 2026? Only in a narrow scope. Until the end of 2026 a value exemption applies: invoices outside KSeF are allowed if the monthly B2B sales value from those documents doesn't exceed PLN 10,000, with a single invoice up to PLN 450. After that period the exemption expires.
Why does my invoice have a different date in KSeF than in my system? That's the "two dates" problem. A document takes legal effect when KSeF accepts it, so the issue date in your system can differ from the acceptance date in KSeF — especially with delayed sending. The detailed rules are set by the Ministry of Finance.
What should I do when KSeF rejects an invoice? The most common causes are errors in XML structure, mismatch with the current FA(3) schema, or an incorrect buyer NIP. Check the error message, fix the file, and resend. When the system itself is unavailable, the rules provide offline modes with defined deadlines for late submission.