KSeF Is Down and Your Client Is Waiting. What to Do Now?
A KSeF outage does not block your sales if you follow the correct emergency procedures. You can issue invoices offline using the FA(3) schema, provided you upload them to the system within the legal deadline once it is back online.

Since 1 April 2026, mandatory e-invoicing has covered most VAT taxpayers in Poland (the smallest ones from 1 January 2027). Under the current act, penalties under Article 106ni of the VAT Act apply from 1 January 2027. On 16 September 2026 the Ministry of Finance announced it will move them to 1 January 2028; that is a bill not yet passed, and it moves only the penalties, not the obligation to use KSeF. Regardless of the penalty date, an outage procedure is worth rehearsing rather than merely documenting. Below is the decision tree, the deadlines, and the list of things you must prepare in advance, because you cannot arrange them mid-outage.
Step 1: identify the scenario (30 seconds)
The Polish VAT Act defines four distinct situations, and each carries a different upload deadline. The difference is not a legal nuance. It is the difference between one business day and seven.
| Situation | Mode | Legal basis | Deadline to upload to KSeF |
|---|---|---|---|
| Any reason, also when KSeF is up: for example no internet, timeout, integration error, poor connection | offline24 | Art. 106nda of the VAT Act | without delay, no later than the next business day after the issue date |
| Ministry of Finance announced KSeF unavailability (scheduled maintenance) in its Public Information Bulletin (BIP) | offline (unavailability) | Art. 106nh | no later than the next business day after the unavailability period ends |
| Ministry of Finance announced a KSeF failure in BIP and in the interface software | emergency mode | Art. 106nf | within 7 business days from the day the failure ends |
| A total failure is announced through mass media | total failure | Art. 106ne(3), Art. 106ng | invoices are not uploaded to KSeF at all |
Sources: the Ministry of Finance pages on offline24 mode, emergency mode and offline mode during system unavailability.
The practical takeaway: do not wait for an official announcement. Checking BIP takes a minute, but if there is no announcement, offline24 is available to you anyway. It is voluntary, always available, and carries no eligibility restrictions.
Step 2: issue the invoice in offline24 mode
Offline24 is your default move because it does not depend on anyone else's decision. Under Art. 106nda of the VAT Act you issue the invoice electronically, using the applicable FA(3) logical structure, and then upload it to KSeF without delay, no later than the next business day after the issue date.
Three things people routinely get wrong here:
The issue date does not change. The issue date is the one you state on the invoice in field P_1, not the date KSeF finally assigns a number. Issue on Friday, upload on Monday, and the issue date is still Friday.
The KSeF number arrives later, and that is normal. For a buyer who is a Polish VAT taxpayer, the receipt date is the date the KSeF number is assigned, so formal delivery happens after you upload.
You cannot immediately correct an offline invoice. A correcting invoice can only be issued once the original has been assigned its identifying number in KSeF. If you made a mistake on an offline invoice, you must upload it first.
Step 3: the QR codes on an offline invoice
This is where improvised outage procedures usually fall apart.
If you hand the invoice to the buyer outside KSeF, before uploading it, the document must carry two QR codes:
Code I ("OFFLINE") provides access to the invoice in KSeF and lets the buyer verify its data once uploaded. The link in the code contains the seller's NIP, the issue date and the SHA-256 hash of the invoice file, with no invoice number or amounts. Code I is on every invoice, including those issued online (then the signature is the KSeF number).
Code II ("CERTYFIKAT") confirms the identity of the issuer at the moment of issuance.
Generating the second code requires a KSeF certificate of the Offline type, which is separate from the login (Authentication) certificate and has to be issued in advance. Here is the catch: you cannot obtain that certificate during an outage, because issuing it requires a working system. If you do not have it today, your offline procedure exists on paper only.
One exception simplifies things: if the invoice reaches the buyer outside KSeF only after it has been uploaded, a single QR code carrying the KSeF number is enough.
Step 4: what happens when the system comes back
The outage ends, and the part that is easy to sleep through begins, because nothing hurts anymore.
Upload the backlog. Offline24 gives you the next business day. Emergency mode gives you 7 business days from the day the failure ends, and if the Ministry announces another failure during that window, the clock restarts from the end of that one.
Verify that every invoice received a KSeF number. That number is the only proof the document actually landed in the system. One missing number in a batch is a classic post-outage scenario.
Flag the invoices correctly in JPK_V7. An invoice issued offline that received its KSeF number later carries its own marking in the VAT ledger; the period in which you report it follows the general VAT rules, not the offline mode itself, so check with your accountant if in doubt.
The consequence of missing a deadline is specific. Article 106ni of the VAT Act provides for a penalty of up to 100% of the VAT shown on the invoice, or up to 18.7% of the total amount due where no VAT is shown, calculated for each invoice separately. Under the current act these penalties apply from 1 January 2027. On 16 September 2026 the Ministry of Finance announced it will move them to 1 January 2028; that is a bill not yet passed, and it moves only the penalties, not the obligation to use KSeF.
How this works in Biurko
The design assumption was simple: during an outage, a human should not be making technical decisions.
Biurko detects a KSeF gateway outage automatically, based on three gateway errors within 60 seconds, and switches new submissions into offline24 mode instead of returning an error; every 5 minutes it also reads the Ministry notices about downtime, failure and total failure (the "Latarnia" feed). An invoice issued during that window gets a validated FA(3) XML file stored in the archive, its SHA-256 hash, and on the buyer's PDF a QR code with the verification link (Code I) and, if the company has an Offline certificate, Code II.
When the system recovers, queued transmissions return to the pipeline automatically, every 5 minutes, with nothing to click. If one misses its deadline, Biurko does not resubmit it by itself: after the deadline it marks the document "Needs review" and notifies the person who issued it (it does not warn beforehand).
To be straight about it: the second QR code ("CERTYFIKAT") requires a KSeF certificate of the Offline type. Biurko can order it from the Ministry for you, but it has to be done before an outage. Without it Biurko issues the offline invoice with one code (Code I) and a warning, and you should not hand such an invoice to the buyer outside KSeF before it is sent to KSeF.
Checklist: prepare this before KSeF goes down
Order a KSeF certificate of the Offline type (in Biurko or in the Taxpayer Application) and confirm your software can generate the "CERTYFIKAT" code from it.
Check that your system produces valid FA(3) XML without a KSeF connection. If it only produces a PDF, you do not have an offline mode.
Bookmark the announcement sources: the Ministry of Finance BIP and the technical announcements on ksef.podatki.gov.pl. Decide who checks them.
Agree in advance how invoices reach buyers outside KSeF (email, client portal, printout). This is a conversation to have before the counter, not at it.
Assign ownership of the post-outage upload. The deadline runs whether or not anyone remembers it.
Run one dry rehearsal. To practise without legal effect, use the Biurko demo (demo.biurko.io, 7-day access, the KSeF demo environment). An account on app.biurko.io sends invoices to production KSeF, so every invoice you send there is real. You will learn more than from any guide.
Summary
A KSeF outage does not stop your sales, provided you know which mode you are in and what your deadline is. The difficulty is that the decision has to be made in under a minute, in front of a client, without access to the system you would normally use to check.
Which is why the software should make that call while you just issue the invoice. Biurko detects the outage, switches modes, generates the QR codes, and uploads the backlog once the system returns. Create a free account and see in the Biurko demo (demo.biurko.io, 7-day access) how issuing and sending invoices to KSeF works.
FAQ
What do I do if KSeF is down and I need to issue an invoice? Issue it in offline24 mode using the FA(3) structure and upload it to KSeF no later than the next business day after the issue date. You do not need to wait for any Ministry of Finance announcement, as this mode is always available.
How long do I have to upload an invoice after a KSeF outage? In offline24 mode, the next business day after the issue date. In emergency mode announced by the Ministry, 7 business days from the day the failure ends. If another failure is announced during that period, the clock runs from the end of that one.
What is the difference between offline24 and emergency mode? You choose offline24 yourself, for instance when your internet is down, and you get one business day to upload. Emergency mode applies only when the Ministry announces a failure in BIP and in the interface software, but it gives you 7 business days.
Is an offline invoice valid without a KSeF number? Yes. The issue date is the one stated on the invoice, and the KSeF number is assigned once the document is uploaded. The obligation to upload within the deadline still applies.
Why are there two QR codes on an offline invoice? The first gives access to the invoice in KSeF and verifies its data, the second confirms the issuer's identity. The second (Code II) requires a KSeF certificate of the Offline type, separate from the login certificate. Both are needed only when you hand the invoice to the buyer outside KSeF before uploading it.
Tags
Previous article
How to avoid KSeF penalties without an accountant?
Next article
How to verify a Polish contractor before issuing an invoice?