A Warsaw-based IT services company receives its first rejection notice from the Krajowy System e-Faktur (National e-Invoice System, KSeF) three days before a major client payment is due. The invoice was issued outside the system. The client refuses to pay until a compliant document arrives. Cash flow stalls. This scenario is already playing out across Poland – and the mandatory rollout has not yet reached every business segment.

KSeF is Poland's government-operated platform for issuing, receiving, and archiving structured electronic invoices in a standardised XML format called FA(2). Mandatory KSeF compliance applies to VAT-registered taxpayers in Poland from 1 February 2026 for the largest businesses and from 1 April 2026 for the remaining VAT-registered entities. Failure to issue invoices through KSeF once the obligation applies triggers financial penalties of up to 100% of the VAT shown on the non-compliant invoice.

This guide explains what KSeF requires, how to prepare your business step by step, what the most common implementation mistakes look like, and how three different business types – a manufacturer, a software company, and a foreign investor – should approach the transition. Each section ends with a concrete action point.

What does KSeF actually require your business to do?

KSeF changes the mechanics of B2B invoicing in Poland at the system level. Every VAT-registered business must issue invoices exclusively through the KSeF platform once its mandatory date arrives. The invoice is assigned a unique KSeF number by the Ministry of Finance's platform, and only a document bearing that number qualifies as a valid VAT invoice under Polish tax law.

The technical requirement is straightforward: your accounting or ERP system must generate invoices in the FA(2) XML schema and transmit them to KSeF via an API connection. The National Revenue Administration (Krajowa Administracja Skarbowa, KAS) then processes the file, assigns the KSeF identifier, and makes the document available to the recipient within the platform. The recipient does not need to "accept" the invoice – receipt is deemed to occur on the date the document is made available.

Three elements define the scope of the obligation:

  • You are a VAT taxpayer registered in Poland (active or exempt).
  • You are issuing a B2B invoice to a Polish counterparty.
  • The transaction is subject to Polish VAT rules.

Consumer invoices (B2C) remain outside KSeF for now. Foreign businesses without a Polish VAT registration are also excluded from the mandatory scope – though they may use KSeF voluntarily. The Polish Financial Supervision Authority (Komisja Nadzoru Finansowego, KNF) is not involved in KSeF directly, but regulated financial entities are subject to the same invoicing rules as any other VAT taxpayer.

One figure to keep in mind: the FA(2) schema contains over 300 fields. Most are optional, but mapping your current invoice data to the required fields takes time. Businesses that underestimate this mapping exercise are the ones that miss their compliance date.

What is the KSeF timeline and who is affected when?

The rollout is phased. From 1 February 2026, mandatory KSeF applies to businesses whose prior-year VAT sales exceeded PLN 200 million. From 1 April 2026, the obligation extends to all remaining VAT-registered taxpayers. VAT-exempt businesses face a further deadline – currently set at 1 April 2026 as well, though legislative adjustments remain possible. For a complete breakdown of the phased schedule and its implications for companies operating across borders, see our KSeF deadline timeline 2026/2027 for companies in France.

The 1 April 2026 date is not a soft deadline. A business that issues even a single invoice outside KSeF after its mandatory date – without an authorised offline exception – faces a penalty of up to 100% of the VAT on that invoice. For a PLN 500,000 net invoice at a 23% VAT rate, that means exposure of up to PLN 115,000 on one document. The consequence is irreversible once the tax authority issues the assessment.

Two narrow offline exceptions exist. First, system failure: if KSeF itself is unavailable, businesses may issue invoices in offline mode and upload them within 24 hours of the system being restored. Second, certain force-majeure scenarios. Neither exception covers your own ERP failure or a delayed software rollout.

What this means in practice: businesses that begin their KSeF project in January 2026 are already behind schedule. A realistic implementation requires at minimum eight to twelve weeks for system integration, testing, staff training, and counterparty notification. Starting in Q4 2025 is the minimum prudent approach.

How should you implement KSeF step by step?

Implementation breaks into five stages. Each stage has a defined output. Missing one stage does not make the next one faster – it makes it more expensive.

Stage 1 – Gap analysis (weeks 1–2). Map every invoice type your business currently issues: standard VAT invoices, corrective invoices, advance invoices, self-billing documents. Identify which systems generate them. Check whether your ERP vendor has released a certified KSeF module. This stage should produce a list of all invoice flows and the fields currently missing from your data.

Stage 2 – System integration (weeks 3–8). Your IT team or ERP vendor connects your system to the KSeF API using the authentication token issued by the Ministry of Finance. This requires a qualified electronic signature or a trusted profile (profil zaufany) for the authorised person. Larger businesses with high invoice volumes should configure batch transmission rather than single-document uploads.

Stage 3 – Data mapping and testing (weeks 5–10). Map your existing invoice data to the FA(2) schema. Run test invoices in the KSeF test environment, which the Ministry of Finance has made available at no cost. Correct schema errors. This stage often reveals legacy data quality issues – wrong NIP numbers, missing addresses – that must be cleaned before go-live.

Stage 4 – Internal training (weeks 8–10). Finance, accounts receivable, and procurement teams need to understand the new workflow. The most important change: a corrective invoice under KSeF requires the original KSeF number. Staff who do not know this will issue corrections incorrectly.

Stage 5 – Go-live and monitoring (week 11 onwards). Switch to live KSeF transmission. Monitor rejection rates daily for the first 30 days. Set up an alert for any invoice that fails to receive a KSeF number within the processing window.

How do three business types approach KSeF differently?

The same legal obligation falls differently on different businesses. Understanding your scenario prevents over-engineering – or under-preparing.

Manufacturing company (Silesia region). A mid-size manufacturer issues around 2,000 invoices per month across 40 counterparties. Its SAP system requires a vendor-supplied KSeF plugin. The primary risk is batch transmission: large invoice runs must complete within the KSeF processing window. The manufacturer should prioritise API performance testing and agree a contingency protocol with its IT team for offline-mode activation if the platform shows latency. We assisted a manufacturing client in the Silesia region in completing their KSeF integration and test-environment validation within ten weeks (autumn 2025), avoiding a last-minute scramble.

IT services company (Warsaw). A Warsaw-based software firm issues fewer invoices – perhaps 80 per month – but many are complex: multi-line service contracts, partial advances, and invoices in EUR for Polish VAT purposes. The challenge here is data mapping, not volume. Each service line must be coded correctly in the FA(2) schema. The firm should run parallel invoicing (KSeF and legacy format simultaneously) in the test environment for at least four weeks before go-live.

Foreign investor entering Poland. A German investor establishing a Polish subsidiary must register for VAT at the National Court Register (Krajowy Rejestr Sądowy, KRS) stage and immediately configure KSeF access. There is no grace period for new registrants. The investor should also understand that KSeF data will be visible to the KAS in near-real time – meaning transfer pricing positions and intercompany invoicing patterns will be more transparent than under the prior paper or PDF system. For guidance on related employment and structuring risks, see our analysis of B2B reclassification risk and PIP enforcement powers in 2026.

Our team secured a successful KSeF readiness audit and remediation for a foreign-owned distribution subsidiary in the Małopolska region (winter 2025), identifying three schema mapping errors that would have triggered rejections on day one of mandatory compliance.

What are the most common KSeF mistakes to avoid?

Most KSeF implementation failures are predictable. They cluster around four recurring errors.

Assuming the ERP vendor will handle everything. Your vendor will supply a KSeF module. That module will not automatically map your business-specific invoice data to the FA(2) schema. Your finance team must own the mapping exercise. Vendors are responsible for the technical connection; you are responsible for data quality.

Ignoring corrective invoice workflows. Under KSeF, a corrective invoice must reference the original KSeF number. If the original was issued before your mandatory date (and therefore has no KSeF number), a transitional referencing rule applies. Many businesses discover this gap only when they need to issue their first correction after go-live – by which point the deadline pressure makes clean resolution difficult.

Failing to notify counterparties. Your clients and suppliers need to know you will be issuing KSeF invoices. Some of their systems may not yet be configured to retrieve invoices from the KSeF platform. Early notification – ideally 60 days before go-live – prevents payment delays caused by their system limitations, not yours.

Overlooking the archiving obligation. KSeF stores invoices for ten years on the Ministry of Finance platform. You are no longer required to maintain a separate invoice archive for documents issued through KSeF. However, you must retain access credentials and be able to retrieve documents on request from the KAS. Businesses that decommission their own archives prematurely without verifying KSeF access continuity create a compliance gap.

One checkpoint worth building into your project plan: run a full dress rehearsal in the KSeF test environment using real invoice data (anonymised) at least 30 days before your mandatory go-live date. This single step catches the majority of schema and data errors before they carry financial consequences.

What to prepare before your KSeF go-live:

  • Inventory of all invoice types currently issued by your business.
  • Confirmed ERP/accounting system KSeF module or API integration.
  • FA(2) schema mapping completed and tested in the Ministry of Finance test environment.
  • Staff training completed for finance, AR, and procurement teams.
  • Counterparty notification sent at least 30 days before go-live.

Businesses with exposure to cross-border VAT, IP Box regimes, or transfer pricing arrangements should also assess how KSeF data visibility affects their existing tax positions. The KAS will have access to structured invoice data in near-real time. That changes the risk profile of positions that previously relied on documentation opacity. For tailored advice on Polish tax law obligations including IP Box and transfer pricing, visit our tax practice page for Poland.

The specific circumstances of your business determine the right implementation sequence, the acceptable risk tolerance, and the documents you need to prepare. Proceeding without a structured review risks penalties that cannot be reversed once the assessment is issued.

To receive an expert assessment of your KSeF readiness and a tailored implementation plan, contact info@kordeckipartners.com. If your business is approaching the April 2026 deadline without a completed integration – we will conduct a gap analysis, identify critical path items, and coordinate with your ERP provider to reach compliant go-live: info@kordeckipartners.com.

Frequently asked questions

Q: Does KSeF apply to my business if I am VAT-exempt?

A: Yes, VAT-exempt businesses in Poland are also brought within the mandatory KSeF scope, with an obligation date currently set at 1 April 2026. The exemption from VAT does not exempt you from the invoicing platform requirement. You will need to register on the KSeF platform and configure your invoicing system to transmit documents in the FA(2) XML format, even if no VAT is shown on your invoices.

Q: How long does a KSeF implementation typically take, and what does it cost?

A: A realistic implementation timeline for a business with a standard ERP system runs eight to twelve weeks from project kick-off to go-live. Costs vary: an SME using off-the-shelf accounting software may spend under PLN 10,000 on configuration and training. A mid-size business requiring custom API development and data migration can expect costs in the range of PLN 50,000 to PLN 150,000. These figures do not include internal staff time, which is often the largest hidden cost.

Q: Is it true that PDF invoices sent by email will still be valid after the mandatory date?

A: This is the most common misconception. Once your mandatory KSeF date applies, a PDF invoice sent by email does not qualify as a valid VAT invoice under Polish tax law – even if it contains all the required data. Only a document issued through KSeF and bearing a KSeF number is a valid invoice. A buyer who receives a PDF after your mandatory date cannot deduct input VAT on that document, which creates a shared compliance risk for both parties.

KORDECKI & Partners is a law firm based in Warsaw and Krakow, advising business clients across 30 jurisdictions. Our team combines expertise in Polish and international law with a practical approach to tax compliance, KSeF implementation, and VAT advisory. We work with Polish entrepreneurs, foreign investors, and in-house legal teams. To discuss your situation, contact info@kordeckipartners.com.

Disclaimer: This publication is provided for informational purposes only and does not constitute legal advice. The information herein should not be relied upon as a substitute for professional legal counsel tailored to your specific circumstances. KORDECKI & Partners assumes no liability for actions taken or not taken based on the contents of this material. For advice regarding your particular situation, please contact info@kordeckipartners.com.