How to Determine the KSeF Obligation Deadline for Your Company Based on Turnover and Prepare n8n Automation for It

TL;DR: According to information from biznes.gov.pl until 31 January 2026 KSeF (Poland mandatory national e-invoicing system) remains a voluntary solution for most companies. From 1 February 2026 the obligation to receive invoices starts for all taxpayers. In this post I describe how to determine the exact deadline based on company status and how to prepare a workflow in n8n to handle structured invoices.

The deadlines around KSeF have changed several times in recent years. This means that many companies still do not know exactly from when they must adapt their processes.

I rely exclusively on official sources from the Ministry of Finance and industry analyses. There is no room for assumptions here.

Current KSeF deadlines according to applicable regulations

Until 31 January 2026 KSeF is a voluntary solution. You can issue structured invoices or in the previous form.

From 1 February 2026 all taxpayers have the obligation to receive invoices in KSeF. This applies to invoices from contractors.

According to information on ksef.podatki.gov.pl some elements, such as providing the KSeF number in payments, are postponed until the end of 2026.

This postponement provides an additional buffer, but does not exempt from preparing systems for sending and receiving.

The table of invoice issuance modes from February 2026 shows that offline invoices will be treated differently if the transmission date is later than the issuance date.

How to determine the obligation deadline based on company turnover

The company status and its turnover determine whether you fall under earlier or standard deadlines. First check if you are an active VAT taxpayer.

Sources indicate that for companies exceeding certain turnover thresholds in previous years additional reporting requirements may apply. However, do not assume that your case is standard.

Go to the podatki.gov.pl portal and verify your NIP and settlement history. Compare with the table available in the Ministry of Finance materials.

If your annual turnover exceeded the thresholds for large enterprises within the meaning of the act, the deadline may be treated as priority. I assume here data from 2024 and 2025 as the base.

In practice most SMEs have the same starting deadline from February 2026. I look critically at the fact that many companies ignore this fact until the last moment.

Check also the KSeF step-by-step guide for SMEs.

Most common mistakes in determining the deadline and status

Companies often assume that since KSeF is voluntary until the end of January 2026, there is no need to do anything earlier. This approach leads to integration problems at the peak.

A source from nicoma.pl emphasizes exceptions and risks for companies with high turnover. Check the change map there before deciding on the schedule.

Another mistake is omitting the obligation to receive invoices from February 2026. Even if you do not send, you must be ready to receive.

KSeF in practice: the most common integration errors and how to avoid them shows what most often goes wrong when connecting systems.

Preparing n8n for KSeF process automation

n8n allows building an integration with the KSeF API without writing full code. However, it requires understanding authentication based on certificates or tokens.

Start with a self-hosted n8n instance. You will find the cost comparison in n8n Cloud or self-hosted? Cost calculator for the company.

Configure the HTTP Request node to the KSeF endpoints. First test in the Ministry's test environment before moving to production.

Critically: ready templates rarely fit the specifics of Polish invoicing. Always adjust the workflow to your data structure.

Building a workflow in n8n for sending and receiving invoices

The workflow starts with a trigger - for example a webhook from the invoicing system or a daily scheduler.

Then you format the data to the FA(2) structure required by KSeF. Use the Function Item node for field mapping.

After authorization send the document via POST to /api/online/Invoice/Send. Handle the response with the KSeF reference number.

For receiving configure a separate flow that periodically checks the inbox in KSeF and parses incoming invoices. Redirect them to accounting or database.

Add error handling - a separate branch for error statuses. Without this the automation will fail at the first certificate problem.

Test on small batches. Do not send hundreds of invoices at once.

Testing, monitoring and what after implementation

Before launching in production prepare at least a 30-day testing period with fictitious data. Monitor n8n logs for authentication errors.

After implementation do not forget about KSeF API updates. The Ministry may change schemas without prior notice.

It is worth combining this with broader automation. See how to calculate automation ROI before you invest time.

I critically assess that tools alone are not enough. A change in processes inside the company is needed.

Summary

Determining the KSeF deadline based on turnover requires checking the status in official registers. Do not postpone it until 2026.

Automation in n8n gives control, but requires precise configuration. Test everything twice before trusting the data.

Preparing now minimizes the risk of penalties and downtime in February 2026.