What KSeF is and who it applies to
KSeF (Krajowy System e-Faktur) is the Polish Ministry of Finance system that structured invoices pass through: instead of emailing a PDF, the seller submits an XML file in the FA(3) structure. The system validates the file, assigns it a KSeF number and makes the invoice available to the buyer. The obligation arrives in stages:
| From | Who it applies to |
|---|---|
| 1 February 2026 | companies whose 2024 sales including tax exceeded PLN 200 million |
| 1 April 2026 | all other businesses |
| 1 January 2027 | the smallest sellers, with invoiced sales of up to PLN 10,000 gross per month |
Invoices for consumers can be issued in KSeF voluntarily. For a distributor or manufacturer selling to companies, this means in practice that nearly every sales document goes through KSeF. Current rules and deadlines are published on the Ministry of Finance KSeF website.
The path of an invoice: from the order to KSeF and back
- Issuing. The invoice is created in the platform: manually from the order, or automatically once the order is confirmed, with a number built from the pattern set for the sales channel.
- Submission. The KSeF module generates the document in the FA(3) format and places the submission on a durable Redis-backed queue, the same one that handles webhooks and transactional email. When KSeF is temporarily unavailable, the job retries with increasing delay while orders keep processing. During a longer outage, invoices wait on the queue marked as issued in offline mode, and once it is over they are submitted automatically, with no duplicates. Pro forma invoices are never sent to KSeF, as they are not VAT invoices.
- KSeF number. Once the document is accepted, the KSeF number and the processing time are stored on the invoice. They show on the invoice page in the admin panel, and a finance system can read them through the API.
- Official confirmation. The UPO (Urzędowe Poświadczenie Odbioru, the official confirmation of receipt) is downloadable once issued.
- PDF. The printout carries the KSeF number and a verification QR code. KSeF is one of the sections in the invoice template editor, so you decide where it sits on the document.
Corrections take the same path and reference the KSeF number of the original invoice. That matters, because an invoice accepted by KSeF cannot be edited or deleted: an error can only be fixed with a corrective invoice.
Configuration and monitoring in the admin panel
The KSeF module has its own section in the admin panel. There you set:
- The environment: test (the default, with no legal effect), pre-production (demo) or production. The connection test checks the stored credential against the selected environment and describes the outcome in plain language, for example an expired certificate or the wrong environment.
- Credentials: you upload a KSeF authentication certificate with its private key, optionally also an offline-mode certificate, or generate them with a wizard that creates the key pair and a CSR and enrolls it with KSeF. A KSeF token is accepted as a temporary solution.
- Certificate validity: the panel shows the validity period and warns that a certificate is about to expire before submissions start failing. Private keys and tokens are stored encrypted and are never returned by any API.
The submissions tab shows the number of documents in each status and a filterable list. Each submission shows its attempt count and full error history. Accepted documents offer a UPO download, and rejected ones a reason and a retry button. The previous attempt then stays in the history.
Limit: VAT rates
The FA(3) structure in the module supports the 23%, 8%, 5% and 0% VAT rates. A document with a line at any other rate is refused before it is sent, and the message names the invoice and the rate, so it can be corrected at its source. If you sell goods at other rates, raise it before the rollout.
Why the PDF carries a QR code
A Polish buyer with a tax identification number (NIP) receives the invoice in KSeF. Some recipients, however, get it outside the system, in an agreed manner: foreign customers, entities without a NIP and consumers. Such a document must carry a QR code labelled with the KSeF number, which leads to the invoice in the system and lets the recipient check its data. The PDF downloaded from the customer account in the store or sent by email has that code, so a paper copy can also be checked against KSeF.
Native submission or through an accounting system
Who submits invoices to KSeF is decided by one setting in the admin panel: “Invoice ledger”, the “Routing” tab. It applies to the whole instance and can be overridden for a selected sales channel.
- Native KSeF module: the platform submits the document itself. It is a paid module, outside the platform’s open-source core; in rollouts run by Endora its cost is included in the rollout price. This is convenient when invoices originate in the platform and the ERP receives them later, or when sales run through several channels at once.
- Submission by the vendor: a copy of the invoice goes to the accounting system, that is wFirma, inFakt or Subiekt 123, and that system submits it to KSeF. The native module then does not send this invoice, so the document does not reach the system twice.
In both variants the KSeF number is stored on the same invoice in the platform. A third setup is an ERP as the only place where sales documents are issued, for example Comarch ERP Optima with its own KSeF support. In that case the platform does not need to submit anything. Neither approach is better in principle: the choice depends on where in the company the invoice is created.
What to prepare on the KSeF side
These requirements come from KSeF itself, whichever system issues the invoices:
- Permissions. A system submitting invoices on behalf of a company has to authenticate. The KSeF 2.0 API accepts a KSeF token, a KSeF certificate, or a qualified signature or seal. A token carries the set of permissions granted when it is generated, for example for issuing invoices. Changing the scope requires a new token, and an existing one can be revoked.
- Environments. The Ministry provides three: test, pre-production (demo) and production. They are separate, and credentials from one do not work in another. Real invoices and company data must not be sent to the test environments.
Technical details are covered in the official KSeF 2.0 API documentation.
KSeF landed in the platform in one of the platform updates, together with the Comarch ERP Optima and Subiekt GT connectors.