KSeF 2026 — How to Prepare Your Company for Mandatory E-Invoicing

Poland’s National e-Invoice System (KSeF) is coming into force as the mandatory invoicing standard. For thousands of companies this means having to change the way they issue, transmit, and archive invoices — within strictly defined deadlines and in accordance with a new XML format. Companies that put off preparation are risking financial penalties and operational paralysis.

This article explains step by step what KSeF is, who it affects and when, what the penalties are for being unprepared — and, above all, how to successfully guide your company through this implementation.

What Is KSeF?

KSeF — the National e-Invoice System — is a central IT system operated by the Polish Ministry of Finance that serves as a platform for issuing, receiving, and archiving structured invoices. In short: instead of sending a PDF invoice by email or post, you issue it in the government system — and the recipient retrieves it from their account in the same system.

KSeF is not a new invoicing programme — it is mandatory infrastructure through which VAT invoices issued between business entities must flow. Your existing invoicing system (ERP, accounting software, online application) can continue to function — but it must be integrated with the KSeF API and generate invoices in a standardised XML format called FA(2).

Key KSeF functions:

Centralised real-time invoice issuing and receipt
10-year invoice archiving on the government system side
A unique KSeF number assigned to each invoice by the Ministry of Finance system
Authentication via qualified electronic signature, electronic seal, or session token
Built-in tax audit mechanisms (data immediately accessible to tax authorities)

Who and When Does Mandatory KSeF Apply To?

The KSeF implementation schedule has been revised several times. The currently applicable deadlines are:

1 February 2026 — mandatory KSeF for active VAT payers whose sales value (VAT-inclusive) in the previous tax year exceeded PLN 200 million.

1 April 2026 — mandatory KSeF for all remaining active VAT payers, without a sales value threshold.

1 January 2027 — planned inclusion of VAT-exempt entities (subject or object exemption) and local government units.

Exceptions and exclusions:

Consumer invoices (B2C) — not subject to KSeF (though voluntary use is possible)
Invoices issued by foreign taxpayers with no fixed establishment in Poland
Some simplified invoices (receipts with the buyer’s tax number up to PLN 450)

Important: the “1 April 2026” deadline does not mean companies have until March. KSeF implementation requires testing, system integration, and training — which realistically takes 3–6 months. Companies starting preparations in February 2026 are already leaving it to the last minute.

How Does KSeF Work? The Structured XML Invoice FA(2)

The heart of KSeF is the structured electronic invoice format — an XML schema called FA(2) (currently FA_VAT(2) or FA(2) depending on invoice type). This is a strict technical specification defining what fields an invoice must contain, in what order, and in what format.

How an invoice flows through KSeF:

The seller issues the invoice in their system (ERP, accounting software) in XML FA(2) format
The seller’s system sends the invoice to the KSeF API
KSeF validates the invoice (XML structure verification, tax numbers, mandatory data)
KSeF assigns a unique KSeF number and timestamp to the invoice
The invoice becomes available in the buyer’s KSeF account
The buyer retrieves the invoice from their system (via API or manually through the browser)

How FA(2) differs from a standard PDF invoice:

Must contain all mandatory fields according to the XSD schema
“Currency code”, “KSeF number”, “Issue date” — strictly defined formats
No option to add custom fields outside the schema
Electronic signature or qualified seal of the issuer
Cannot be modified once submitted to KSeF — corrections require a corrective invoice

The Ministry of Finance provides a test environment (KSeF Test) for validating invoices and testing integrations before the production go-live.

What Are the Penalties for Being Unprepared?

Penalties for KSeF obligation breaches are serious and financial in nature:

Penalty for issuing an invoice outside KSeF (once the obligation applies): Up to 100% of the VAT amount on an invoice issued in breach of the KSeF obligation. Minimum penalty: PLN 1,000 per invoice.

Penalty for issuing an invoice in KSeF that does not comply with the schema: Up to 50% of the VAT amount on an invoice with structural errors. Applies to invoices submitted to KSeF that did not pass validation or contain material discrepancies.

Consequences for the buyer: A buyer who accepted for accounting purposes an invoice issued outside KSeF during the obligation period may lose the right to deduct input VAT from that invoice. This creates a motivation to verify that suppliers are issuing invoices correctly.

Loss of shortened retention period: Companies using KSeF can shorten their own invoice documentation retention obligation (KSeF archives on their behalf for 10 years). Companies that are unprepared lose this benefit.

Reputational and operational: Delays in issuing invoices, reconciliation errors, cash flow problems — these are real operational consequences for companies that do not implement KSeF on time.

How to Prepare Your Company for KSeF — Step-by-Step Checklist

Audit Your Current Invoicing System

The starting point is a thorough understanding of how the company currently issues invoices:

Inventory all systems generating invoices (ERP, accounting software, online application, Excel spreadsheets — yes, this does happen)
Determine monthly invoice volume: how many sales invoices, how many corrections, how many internal invoices
Check whether your system vendors have a ready KSeF integration (ask directly: “Do you have a certified integration with the KSeF API in production?”)
Identify manual steps in the invoicing process — these are the places with the highest error risk after implementation
Assess data quality in your systems: tax numbers, addresses, bank details — incorrect data means rejected invoices in KSeF

The audit should end with a list: what works, what needs to change, what needs a new integration or new software.

Choosing Software / Integration

Three integration paths with KSeF are available on the market:

Option 1 — Upgrade your existing system: If you use a popular ERP or accounting software (Comarch, Subiekt, SAP, Symfonia, enova), the vendor has probably already released or is planning to release an update with KSeF integration. Simply update the software and configure the KSeF API connection.

Option 2 — Middleware / KSeF broker: If your accounting system has no native KSeF integration, you can use an external intermediary — software that connects your company’s system to KSeF. Examples: KSeF Connector, EDI provider solutions.

Option 3 — Implement a new system: For companies with outdated software that will not be updated for KSeF — replace the system. This involves the most effort, but can be an opportunity for broader modernisation.

Selection criteria: does the vendor have certified tests on the KSeF production environment? What are the licence and implementation costs? What is the technical support model?

Staff Training

KSeF changes not just technology — it changes processes and the daily work of invoicing staff:

Accountants and billing clerks must understand the new invoice flow: where they issue invoices, how they check status, how they handle rejections
The sales team must know that “editing a PDF” is no longer possible — a correction requires a formal corrective invoice in the system
Management should understand the new risks: what happens if the KSeF system is unavailable (the Ministry of Finance provides for an emergency mode), what the penalties are for errors

Training is best conducted before the test environment is activated — so employees can immediately practise on the actual interface.

Testing and Implementation

The test phase is critical and should not be shortened:

Technical testing — sending test invoices to the KSeF Test environment. Verification of XML schema correctness, error handling, KSeF number retrieval.
Process testing (UAT) — employees test the new workflow on data resembling production data. Identification of ergonomic problems, processing times, exception handling.
Performance testing — for companies with high invoice volumes: can the system handle peak loads (e.g. month end)?
Emergency scenario testing — what happens when KSeF is unavailable? The Ministry of Finance has provided for an offline mode — invoices with a QR code issued locally and transmitted to KSeF once availability is restored.

The production go-live should ideally be planned several weeks before the mandatory date — to allow time to correct problems without the pressure of penalties.

Accounting Systems Ready for KSeF

The table below summarises the KSeF readiness of the main ERP and accounting systems according to vendor information (as of 2026):

System	Vendor	KSeF integration	Model	Additional cost
Comarch ERP Optima	Comarch	Yes — native	Update	Included in subscription / one-off
Comarch ERP XL	Comarch	Yes — native	Update	Depends on service agreement
Subiekt GT / nexo	Insert	Yes — native	Update	Included in subscription
SAP S/4HANA	SAP	Yes — SAP Document and Reporting Compliance integration	Configuration + module	SAP module licence
Symfonia ERP	Sage	Yes — native	Update	Included in subscription
enova365	Soneta	Yes — native	Update	Included in subscription
wFirma	wFirma.pl	Yes — native	SaaS, automatic	None
Fakturownia	Fakturownia	Yes — native	SaaS, automatic	None

Note: Before purchasing or upgrading, verify with the vendor that the integration works on the KSeF production environment (not just test) and covers all invoice types (VAT, corrective, advance, intra-community).

Invoice Process Automation During KSeF Implementation

KSeF implementation is a good opportunity for broader automation of invoicing processes. Companies that treat KSeF purely as a technical obligation miss the chance to genuinely improve their processes.

What can be automated alongside KSeF:

Automatic retrieval of purchase invoices from KSeF: Instead of waiting for a PDF from a supplier, the system automatically retrieves invoices from KSeF, verifies them against purchase orders (three-way matching: order → goods receipt → invoice), and passes them for approval.

Automatic invoice status notifications: The system notifies the relevant people when an invoice has been delivered to the counterparty via KSeF, rejected by validation, or when a payment deadline is approaching.

Archiving and categorisation: KSeF invoices can be automatically archived in a DMS system and categorised by cost account based on structured data (supplier tax number, line item description, VAT amount).

Integration with approval workflow: Purchase invoices flow into the workflow system — automatically assigned to the correct cost centre and approving manager, without manual data re-entry.

Reporting and analytics: KSeF invoice data in structured format is ready for analysis — purchasing trends, cash flow, budget comparisons — without manual exporting and mapping.

Companies that combine the mandatory KSeF implementation with invoicing process automation frequently report 30–50% reduction in invoice processing time alongside a simultaneous improvement in financial data quality.

If you want to know which financial processes in your company are worth automating alongside KSeF — the QA10 Process Intelligence Audit identifies precisely those areas where automation will deliver the greatest return.

FAQ

Does KSeF apply to invoices issued to foreign counterparties?

Not directly. Invoices issued to foreign buyers (EU and non-EU) do not have to be issued through KSeF — the obligation covers domestic B2B transactions. However, export invoices and intra-community supplies are worth documenting in a system integrated with KSeF for process consistency.

What happens if KSeF is unavailable?

The Ministry of Finance has provided for an emergency mode. In the event of a KSeF system failure, companies may issue invoices offline in FA(2) format with a special QR code. Once KSeF availability is restored, these invoices must be transmitted to the system within a specified timeframe (typically 24 hours). Important: emergency mode is activated by the Ministry of Finance, not unilaterally by the company.

Can a KSeF invoice be corrected?

Yes, but only by issuing a corrective invoice in KSeF — in the same FA(2) format. An invoice already accepted by KSeF cannot be edited. A correction note (issued by the buyer) is not replaced by KSeF — it still functions as a correction of the buyer’s data, but requires the issuer’s acceptance.

How should invoices be stored after KSeF implementation?

KSeF archives invoices automatically for 10 years — the company does not need to maintain its own archive of structured invoices issued through KSeF. Purchase invoices retrieved from KSeF can also be deemed stored in the government system. However, it is advisable to keep a local copy in the ERP system for operational access.

Do B2C invoices (for consumers) also have to go through KSeF?

Not for now — the KSeF obligation currently covers B2B and B2G (public sector) transactions. Invoices issued to private individuals who are not running a business do not have to go through KSeF. Voluntarily issuing B2C invoices through KSeF is possible, but requires the buyer’s consent.

Treat KSeF as an Opportunity, Not Just an Obligation

KSeF changes invoicing in Poland permanently. Companies that treat this implementation purely as compliance will do the minimum and miss the opportunity to genuinely improve their financial processes. Companies that think more broadly will come out of this project with better data, faster processes, and lower invoicing costs.

The key to a successful implementation is an accurate diagnosis of the current state, the right technology choices, and a realistic testing schedule.

QA10 Process Intelligence Audit helps companies understand not just technical readiness for KSeF, but above all the potential for automating financial processes — so that KSeF implementation becomes a springboard for broader digitalization, not a one-off compliance project.

➡ See how the QA10 Process Intelligence Audit works