How Long to Send an Invoice to KSeF? Deadlines 2026
How long do you have to send an invoice to KSeF? Deadlines in online, offline24, unavailability and failure modes. Specific days and legal basis 2026.

Article Summary
Key takeaway: In online mode, invoice submission to KSeF is immediate - the moment of issuance equals the moment of transmission (Article 106na(1) of the Polish VAT Act). In offline24 mode, you have until the next business day at latest (Article 106nda). In KSeF unavailability mode, submit by the next business day after it ends (Article 106nh). In KSeF failure mode announced by the Ministry of Finance, you have 7 business days from the end of the failure (Article 106nf).
Practical advice: Work in online mode by default with automatic submission enabled immediately after issuance. Keep a KSeF Type 2 certificate ready for offline24 scenarios. Monitor the Ministry of Finance BIP for unavailability and failure announcements, and log all invoices issued outside KSeF in an internal register with a day counter to deadline.
Warning: 'offline24' does not mean 24 clock hours - it means by the next business day at latest. Saturdays, Sundays, and public holidays do not count as business days. An invoice issued on Friday evening has a submission deadline of Monday end of day (if Monday is not a public holiday).
How long to send an invoice to KSeF - quick answer
Online: the invoice reaches KSeF immediately, moment of issuance = moment of transmission (Article 106na(1) of the Polish VAT Act). Offline24: by the next business day at latest (Article 106nda). KSeF unavailability: by the next business day after it ends (Article 106nh). Failure: 7 business days from the end of the failure (Article 106nf).
The table below consolidates deadlines from four Ministry of Finance knowledge base pages into a single view.
| Mode | Submission deadline | Legal basis |
|---|---|---|
| Online | Immediate (moment of issuance = moment of transmission) | Art. 106na(1) of the Polish VAT Act |
| Offline24 | Immediately, by the next business day at latest | Art. 106nda of the Polish VAT Act |
| KSeF unavailability | By the next business day after unavailability ends | Art. 106nh of the Polish VAT Act |
| KSeF failure | Within 7 business days of failure end | Art. 106nf of the Polish VAT Act |
Issuance, sending, acceptance - what does 'sending to KSeF' mean
In practice, three separate concepts are confused in KSeF work: issuance, sending, and acceptance. They have different legal and technical meanings, and distinguishing them is key to understanding submission deadlines.
Issuance means setting the invoice date in field P_1 of the XML FA(3) structure. In online mode, the law treats the invoice as issued on the day it is transmitted to KSeF (Article 106na(1)) - the P_1 date should match the transmission date. In offline modes (offline24, unavailability, failure), the issuance date is the date specified in field P_1, regardless of when it is later submitted.
Sending (transmission) is the physical transmission of the XML file to the KSeF gateway via an interactive or batch session. This is a technical act whose deadlines are regulated by the chosen operating mode. Acceptance is the successful XSD and business validation by the Ministry of Finance, resulting in the assignment of a KSeF number (format NIP-YYYYMMDD-10hex-2hex) and the generation of a UPO (Official Confirmation of Receipt).
This distinction is most visible in offline24 mode: you issue the invoice on Friday (P_1 date = Friday), submit to KSeF on Monday, and receive the KSeF number and UPO on Monday afternoon. For VAT purposes, the issuance date remains Friday - the date from field P_1.
| Concept | Meaning | What it proves |
|---|---|---|
| Issuance | Setting the date in field P_1 (offline) or moment of transmission (online) | Date of tax liability, per Article 106na(1) |
| Sending | Transmission of XML FA(3) to KSeF gateway in an interactive or batch session | Fulfillment of the obligation to transmit the invoice to the MF system |
| Acceptance | Successful KSeF-side validation, KSeF number assignment and UPO generation | UPO - legal proof of invoice delivery in the KSeF system |
Online mode: real-time submission
Online mode is the default and mandatory mode from 1 April 2026 for all active VAT taxpayers (from 1 February 2026 for companies with gross sales exceeding PLN 200 million in 2024). In this mode there is no separate deadline - the submission deadline is zero, because issuance and transmission are a single operation.
The online mode sequence: your accounting system or application generates XML FA(3), opens a session (interactive for individual documents or batch for packages), authenticates it (qualified seal, KSeF token or KSeF Type 1 certificate), transmits the file, receives the KSeF number and UPO. In practice this takes a few to a dozen seconds.
Technical limits to keep in mind: a single invoice file cannot exceed 3 MB including attachments; the KSeF number is assigned in the format NIP-YYYYMMDD-10hex-2hex and appears only after successful XSD and business rule validation; the UPO is available in XML and PDF formats with an SHA-256 checksum.
A full description of submission modes, authentication, UPO and the pre-submission checklist can be found in: Sending invoices to KSeF - complete guide 2026.
Offline24 mode: immediately, by the next business day
Offline24 mode is the taxpayer's voluntary choice when there is a problem on their side with sending (no internet, ERP failure) despite KSeF being operational. The submission deadline is defined by Article 106nda of the Polish VAT Act: immediately, at latest by the next business day after the day of issuance.
In offline24 mode, the invoice issuance date is the date specified in field P_1 of the XML FA(3) logical structure - not the KSeF number assignment date nor the transmission date. An invoice provided to the buyer outside KSeF must have two QR codes: CODE I labeled OFFLINE (enables invoice verification in KSeF) and CODE II with the taxpayer's KSeF Type 2 certificate. The KSeF Type 2 certificate is valid for 2 years and requires a separate application in the Taxpayer Application.
The most common practical questions concern the definition of a business day and behavior at weekends or public holidays.
| Issuance scenario | KSeF submission deadline | Note |
|---|---|---|
| Tuesday, 2:00 PM | Wednesday, end of day | Standard next business day |
| Friday, 10:00 PM | Monday, end of day | Saturday and Sunday are not business days |
| Thursday before a holiday (e.g. 31 October 2026) | Monday (3 November 2026) | All Saints' Day (1 November) - statutory public holiday in Poland |
| Saturday (e.g. a trading Saturday) | Monday, end of day | Saturday is not a business day for statutory purposes |
KSeF unavailability mode: next business day after it ends
KSeF unavailability is a planned or sudden outage on the Ministry of Finance side. The announcement appears in the MF Public Information Bulletin (BIP) and via integrator communications received from the KSeF API. Unavailability mode activates automatically on the taxpayer's system side when the KSeF gateway returns a response indicating this state.
The submission deadline is governed by Article 106nh of the Polish VAT Act: no later than the next business day after the end of the unavailability period. The day the MF announces the end counts - not the invoice issuance date. If the unavailability lasted 3 days and you issued 200 invoices during that time, they all share a single deadline: the next business day after the MF's communication announcing restoration of availability.
Invoices issued during unavailability must include the OFFLINE tag in the XML header and CODE I QR on the visualization provided to the buyer. Technically, unavailability mode differs from offline24 (taxpayer-side) and failure (prolonged MF outage), but operationally looks similar to the user.
| MF system action | Taxpayer action | Deadline |
|---|---|---|
| Publishes unavailability notice in BIP MF and via KSeF API | Taxpayer system automatically switches to unavailability mode; invoices are issued with OFFLINE tag and CODE I QR | During unavailability - no submission to KSeF |
| Restores availability and publishes end notice in BIP MF | Submits all invoices issued during unavailability (batch session recommended) | By the next business day after MF notice (Art. 106nh) |
| Upon acceptance, assigns KSeF number and generates UPO for each invoice | Verifies UPO and archives KSeF numbers in internal register | Immediately upon receiving UPO |
KSeF failure mode: 7 business days from the end of the failure
A KSeF failure is an unplanned, prolonged system outage on the Ministry of Finance side, announced in BIP MF and mass communications. The deadline for submitting invoices issued during the failure is governed by Article 106nf of the Polish VAT Act: 7 business days from the end of the failure.
A failure differs from unavailability in two dimensions. First - time scale: unavailability means hours or single days, while a failure means longer periods preventing system operation. Second - submission deadline: in unavailability it is the next business day, in a failure it is 7 business days. This distinction serves as a buffer for taxpayers who had to issue invoices outside KSeF for several days.
A complete failure is a special scenario announced by the MF in mass media (radio, television, official government communications). During a complete failure, invoices are NOT submitted to KSeF at all. This mode has not been activated as of May 2026.
Invoices issued in failure mode (excluding complete failure) require the OFFLINE tag in XML and CODE I QR on the visualization.
Key differences between partial and complete failure:
- Partial failure (regular): announced in BIP MF and API communications; invoices issued outside KSeF with OFFLINE tag and CODE I QR; obligation to submit within 7 business days from the end of the failure (Article 106nf).
- Complete failure: announced in mass media; invoices are NOT submitted to KSeF at all; the invoice remains outside the system as an exception to the universal submission obligation.
- Mode switching: in partial failure - automatic on the ERP side based on status signals from KSeF API; in complete failure - taxpayer's operational decision after MF's public announcement.
- Time scale: partial failure is usually hours or single days; complete failure is a scenario not yet activated (as of May 2026).
All deadlines in one table
The table below consolidates all four submission modes, their use cases, who activates them, the deadline, and the legal basis. This consolidated table cannot be found on any single page of ksef.podatki.gov.pl - the official MF knowledge base spreads the information across separate subpages.
| Mode | When used | Who activates | Submission deadline | Legal basis |
|---|---|---|---|---|
| Online | Default, when KSeF and network are operational on the taxpayer's side | Automatic (accounting system) | Immediate - moment of issuance = moment of transmission | Art. 106na(1) |
| Offline24 | Taxpayer-side problems despite KSeF being operational | Taxpayer (own decision) | Immediately, by the next business day at latest | Art. 106nda |
| KSeF unavailability | Planned or sudden outage on the MF side | Automatic (API/BIP notification) | By the next business day after it ends | Art. 106nh |
| KSeF failure | Prolonged unplanned system outage by MF | MF (BIP announcement) | 7 business days from end of failure | Art. 106nf |
| Complete failure | Failure announced in mass media | MF (public announcement) | Invoices NOT submitted to KSeF | Art. 106nf (exception) |
What if you miss the deadline?
The consequences of missing an offline submission deadline are twofold and are not explicitly specified as a uniform penalty in Ministry of Finance communications. The first risk is formal: late submission may be treated as improper issuance in the KSeF system, potentially affecting the buyer's ability to deduct VAT based on this invoice in the expected settlement period.
The second risk is sanctions under the general provisions of the Polish Fiscal Penal Code (Articles 56-62 KKS) for invoicing irregularities. Specific amounts depend on the scale of the breach, type of violation, and the tax authority's assessment. In practice, a single, sporadic delay by a taxpayer exercising due diligence usually does not result in enhanced penalties, though each case is assessed individually.
A fuller discussion of KKS sanctions, threshold dates, and practical consequences of not using KSeF can be found in: Can you avoid using KSeF in 2026?.
How not to miss the deadline - 6 operational practices
The following six practices come from KSeF implementations at accounting offices and service companies between February and April 2026. This type of list is not available in the MF knowledge base - these are extracts from real operational processes.
1. Set automatic submission immediately after issuance in online mode. This eliminates the risk of forgetting. In KSeFGPT and most ERPs, you enable this option in the invoice issuance module settings.
2. Use reminders when issuing on Friday evening or on the day before a public holiday. In these scenarios, the offline24 deadline shifts over the weekend or holiday, which is a common source of errors.
3. Have a KSeF Type 2 certificate issued and installed before your first offline scenario. The application is submitted in the Taxpayer Application, valid for 2 years. Without this certificate you cannot generate the correct CODE II QR on the visualization.
4. Monitor the MF BIP (Communications section) and ERP integrator communication channels. Unavailability and failure announcements typically appear in BIP within a few dozen minutes of the event.
5. Maintain an internal register of invoices issued in offline modes with a day counter to the deadline. A spreadsheet or a dedicated view in your ERP will show which documents are approaching their deadline.
6. When there are many overdue invoices, use a batch session instead of individual ones. Sending 100 documents in one batch session takes less time than 100 interactive sessions and yields a consolidated UPO.
Have a batch of offline invoices to submit? Send in bulk
A batch session lets you send hundreds of invoices in one operation with a consolidated UPO. See how to prepare a CSV file, map data to FA(3) and handle validation errors.
Read the bulk sending guideHow KSeFGPT helps you meet deadlines
KSeFGPT is an application for issuing, importing and exporting invoices in KSeF, designed for scenarios where deadlines have operational significance. Three mechanisms directly impact time: bulk CSV and PDF import (a few clicks for hundreds of invoices), AI data recognition from PDFs (reduces XML preparation from hours to minutes), and pre-submission validation (fewer rejections = more time buffer).
For offline24 work or after a KSeF failure, KSeFGPT handles batch sessions with a consolidated UPO - instead of sending 200 overdue documents individually, you prepare a package from CSV and send it in a single operation. The XML validator and PDF-to-XML converter are also available as free tools without registration.
Full features (bulk CSV/XLS import, AI mapping, exports, UPO history dashboard) are available in paid plans with a 1-day free PRO trial. A full feature overview can be found in: KSeFGPT - application for invoice import, export and AI analytics.
Try KSeFGPT - 1 day free PRO trial
Bulk CSV/PDF import, AI FA(3) field mapping, pre-submission validation, batch sessions with consolidated UPO. No card required to start.
Launch KSeFGPTExpert perspective: deadlines in accounting office practice
From the experience of our tax advisor, from the perspective of an office serving several dozen clients, KSeF submission deadlines fall into three risk categories. The first, least dangerous, is online mode - when automation works, there is no deadline to track. Real risk starts only in offline scenarios.
The second category is offline24 - a mode consciously chosen by the client or their ERP. The risk: the client issues an invoice on Friday evening, the weekend passes, the client forgets, and by Monday they already have an overdue submission. Accounting office practice: a weekly check (Tuesday morning) of each client's offline register and automated reminders sent on Friday afternoon.
The third category, most surprising, is failure mode. 7 business days sounds comfortable, but when a failure lasted 2 days, the office receives batches of 50-200 invoices from several clients to submit - totaling several hundred documents to handle during the current week, alongside normal operations. The solution is a batch session per client and pre-prepared CSV templates.
Recommendation: don't treat offline deadlines as buffers to be used - treat them as control checkpoints. The earlier you submit, the less risk that an XSD validation error appears only on the last day.
Frequently asked questions
How long do I have to send an invoice to KSeF in online mode? - In online mode, the invoice is sent in real time, deadline = 0. The moment of issuance is identical to the moment of transmission, in accordance with Article 106na(1) of the Polish VAT Act.
How long do I have to send an invoice in offline24 mode? - Immediately, at latest by the next business day after the invoice issuance date. Legal basis: Article 106nda of the Polish VAT Act.
What does '24 hours' mean in the context of KSeF? - It is an industry shorthand. The law does not say 24 clock hours, but 'the next business day'. An invoice issued on Friday must be transmitted by Monday at latest (if Monday is not a public holiday).
How many days do I have to send invoices during a KSeF failure? - 7 business days from the end of the failure announced by the Ministry of Finance in BIP MF. Legal basis: Article 106nf of the Polish VAT Act.
What if KSeF is unavailable? - In unavailability mode, you submit the invoice no later than the next business day after the end of the unavailability period. Legal basis: Article 106nh of the Polish VAT Act.
Does the weekend count as a business day? - No. Saturdays, Sundays and statutory public holidays do not count as business days. An invoice issued on Friday in offline24 mode has a submission deadline of Monday.
Recommended related articles
To deepen your knowledge of KSeF submission and deadlines, start with these four articles:
Sending invoices to KSeF - complete guide 2026 - submission modes, authentication, UPO, pre-submission checklist.
Bulk sending of invoices to KSeF - CSV import and batch session - how to prepare an invoice package from CSV, pre-submission validation and handling partial rejections.
Can you avoid using KSeF in 2026? - exceptions, threshold dates and consequences of not sending an invoice in mandatory mode.
KSeFGPT - application for invoice import, export and AI analytics - full description of bulk CSV/PDF import and AI FA(3) field mapping.
Send overdue invoices to KSeF without deadline stress
KSeFGPT handles batch sessions with consolidated UPO, bulk CSV/PDF import, AI FA(3) field mapping and pre-submission validation. 1-day free PRO trial; free tools (PDF to XML converter, XML validator) without registration.
Launch KSeFGPTZweryfikowano merytorycznie: Bogdan Mazurek
Tax Advisor · 6 May 2026
Verified dates and deadlines in online, offline24, unavailability and failure modes along with references to Articles 106na, 106nda, 106nf and 106nh of the Polish VAT Act.
Related articles
KSeF AI - What is Artificial Intelligence in KSeF 2026?
What is KSeF AI, when does it make sense and when does it not? Definitions, market landscape 2026, ViDA, GDPR and a map of AI applications in invoicing in Poland.
Bulk invoice submission to KSeF from CSV
How to mass-send invoices to KSeF: batch sessions, CSV structure, FA(3) mapping, validation, and bulk import with KSeFGPT.
AI invoicing tools - 2026 review
Ranking of AI tools for issuing and submitting invoices to KSeF. Feature comparison, table, FAQ. KSeFGPT leads - AI-powered, bulk CSV/PDF import, 1-day free PRO trial + free online tools.
How to send invoices to KSeF - complete guide 2026
How to submit invoices to KSeF in 2026: modes (online, offline24, unavailability, failure), authentication, UPO, limits, common errors and free tools.