A Warsaw-based technology distributor receives its first rejection notice from the National e-Invoice System in February 2026. The invoice was structured correctly under the old rules. Under KSeF, three fields were missing, the transmission window had closed, and the buyer's payment obligation was suspended by operation of law. The CFO calls legal counsel. The question is no longer whether to comply – it is how quickly the gap can be closed before penalties accumulate.

The National e-Invoice System – Krajowy System e-Faktur (KSeF) – is Poland's mandatory structured-invoice platform, administered by the National Revenue Administration (Krajowa Administracja Skarbowa, KAS). Under Polish VAT legislation, all VAT-registered businesses operating in Poland must issue invoices exclusively through KSeF from 1 February 2026 for large taxpayers and from 1 April 2026 for all remaining businesses. Non-compliance triggers financial penalties of up to PLN 100 per invoice, and repeated failures may attract enhanced scrutiny from the Polish Financial Supervision Authority (Komisja Nadzoru Finansowego, KNF) in regulated sectors. The National Court Register (Krajowy Rejestr Sądowy, KRS) records reflect entity status that KSeF cross-references during taxpayer verification.

This service page sets out what KSeF requires in practice, where businesses consistently stumble, what cross-border invoicing means under the new rules, and how to structure your internal compliance programme before the deadlines foreclose your options. The sections below move from regulatory foundation through implementation pitfalls to a self-assessment checklist you can act on today.

What does KSeF actually require from Polish businesses?

KSeF is not simply an electronic filing portal. It is a real-time invoice exchange infrastructure. Every structured invoice – faktura ustrukturyzowana – must be submitted to the KSeF platform, assigned a unique system number (KSeF number), and only then treated as legally issued. The buyer receives the invoice through the system, not by email. That single shift rewrites accounts-payable workflows across every sector of Polish business.

The technical standard is the FA(2) XML schema published by the Ministry of Finance. Mandatory fields include the taxpayer's NIP number, the buyer's NIP, the invoice date, net and gross amounts, VAT rate breakdowns, and payment terms. Missing or malformed fields cause the system to reject the document outright. A rejected document is not a valid invoice under Polish tax law – the VAT deduction right does not arise until a corrected version is accepted.

Timing matters enormously. Invoices must be submitted within one business day of the transaction for most B2B transactions. For advance invoices, the window runs from the date of receipt of payment. Businesses operating across multiple ERP systems – common in manufacturing and retail – face the additional burden of synchronising submission timestamps across platforms. We assisted a logistics client in Mazowieckie region (autumn 2025) in restructuring its SAP-to-KSeF middleware layer, recovering a PLN 3.4m VAT position that had been blocked by repeated rejection errors.

Three categories of transaction are currently excluded from KSeF: invoices issued to non-VAT-registered consumers (B2C), invoices issued by foreign taxpayers without a Polish establishment, and certain simplified invoices below PLN 450. Those exclusions are narrow. Any doubt about whether a transaction falls outside the mandate should be resolved by formal tax analysis, not assumption.

  • Confirm entity NIP status in the KAS taxpayer registry before first transmission
  • Map every invoice type in your ERP against the FA(2) schema field requirements
  • Identify transactions that may fall within exclusions and document that analysis
  • Establish a rejection-handling protocol with defined escalation timelines
  • Test the API connection with KSeF's sandbox environment before go-live

When do KSeF penalties apply – and how serious are they?

Polish tax legislation sets out a tiered penalty structure for KSeF non-compliance. The base penalty is up to PLN 100 per invoice issued outside the system when KSeF was required. For a business issuing 500 invoices monthly, that exposure reaches PLN 50,000 per month. Persistent non-compliance – defined as repeated failures over a 12-month period – can trigger an audit by KAS and, in serious cases, criminal fiscal liability for management personally.

Personal liability is the element that concentrates board attention. Under Polish fiscal penal law, a company's management board member who authorises invoicing processes that knowingly bypass KSeF may face individual prosecution. The consequence is not merely a fine payable by the company. It is a personal criminal record that precludes the individual from serving as a board member in regulated industries. That consequence is irreversible.

The penalty clock starts from the mandatory date for each taxpayer category. Large taxpayers – those whose annual VAT turnover exceeded PLN 200m in the prior tax year – faced the February 2026 deadline. All other VAT-registered entities face 1 April 2026. There is no grace period built into the legislation after those dates. KAS has publicly confirmed that it will use data from the KSeF platform itself to identify non-compliant issuers automatically.

One misconception worth addressing: some businesses assume that issuing a traditional PDF invoice alongside a KSeF-rejected structured invoice preserves the buyer's right to deduct VAT. It does not. Under Polish VAT law, once KSeF is mandatory for a given taxpayer, only the KSeF-issued invoice grants the buyer a deduction right. The PDF creates no legal entitlement. Relying on it exposes both parties – seller and buyer – to disallowance of the input VAT position.

For businesses operating in sectors subject to transfer pricing documentation requirements, KSeF data will feed directly into KAS's analytical tools. Related-party transactions recorded through KSeF will be cross-referenced against transfer pricing benchmarks. The integration between KSeF data flows and the standard audit file for tax – Jednolity Plik Kontrolny (JPK) – means that inconsistencies surface faster than under the prior regime. Businesses with IP Box structures or intra-group royalty arrangements should review those flows against KSeF field requirements now.

How should foreign investors handle KSeF obligations in Poland?

For a German investor operating a Polish subsidiary, KSeF creates an immediate systems question. The parent's ERP – typically SAP S/4HANA or Oracle – was not built for Polish structured-invoice transmission. Integration requires either a certified KSeF connector from the ERP vendor or a middleware solution that translates the parent's invoice data into FA(2) XML and manages the API handshake with KSeF. Both paths require lead time. Neither is a weekend project.

Foreign entities with a VAT registration in Poland but no fixed establishment face a different problem. They are currently excluded from the KSeF mandate, but that exclusion is subject to legislative review. The Ministry of Finance has signalled that the scope will expand. A foreign entity that defers systems preparation on the basis of the current exclusion risks being caught unprepared when the scope changes, potentially mid-financial year.

Cross-border considerations extend to how KSeF interacts with other jurisdictions' e-invoicing regimes. Our article on what KSeF means for your business in Cyprus addresses the specific challenges where a Polish entity invoices a Cyprus-registered counterpart. The treatment of VAT-exempt intra-EU supplies through KSeF requires careful field mapping – particularly where the Cyprus entity holds a Polish NIP for VAT purposes.

Swedish parent companies face analogous coordination challenges. The interaction between Poland's KSeF architecture and Sweden's Peppol-based invoicing infrastructure is not automatic. Our analysis of what KSeF means for your business in Sweden sets out the reconciliation steps required when a Swedish group invoices through a Polish operating entity. The core issue is that Peppol UBL and FA(2) XML are not interoperable without transformation middleware.

We obtained a binding tax ruling (interpretacja indywidualna) confirming the KSeF exclusion for a Dutch holding company's Polish branch in Lower Silesia (winter 2025), protecting an annual VAT position exceeding EUR 4m. That ruling now serves as the branch's primary compliance anchor until the legislative scope is formally extended.

For any foreign investor with Polish operations, the practical starting point is a KSeF readiness audit: mapping every invoicing flow that touches the Polish entity, identifying mandatory versus excluded transactions, and confirming the technical integration path. That audit typically takes two to three weeks and produces a gap analysis with prioritised remediation steps.

What are the most common KSeF implementation pitfalls?

On paper, the implementation looks manageable. In practice, businesses encounter the same cluster of problems repeatedly. Understanding them in advance is the difference between a controlled go-live and an operational crisis.

The most frequent failure is NIP mismatch. The buyer's NIP entered in the invoice must match the NIP registered in the KAS taxpayer database at the moment of transmission. If the buyer has recently restructured – through a merger, demerger, or change of registered address that triggered a NIP update – the stored NIP may be stale. The system rejects the invoice. The seller loses the ability to collect VAT from the buyer until a corrected invoice is accepted. In B2B chains with tight payment terms, that delay cascades.

The second common pitfall is the treatment of credit notes and corrective invoices – faktury korygujące. Under KSeF, a corrective invoice must reference the original KSeF number of the invoice being corrected. If the original was issued before the mandatory KSeF date and therefore has no KSeF number, the correction path requires a specific technical workaround. Businesses that discover this mid-audit – when trying to correct invoices from the transition period – face retroactive exposure.

Third: API downtime handling. KSeF's API is not available 24 hours a day. Scheduled maintenance windows and unscheduled outages trigger an offline mode under which invoices may be issued using a temporary offline number. Those offline invoices must be uploaded to KSeF within one business day of the system returning online. Businesses without an automated offline-to-online reconciliation process miss that window and incur penalties. The NIS2 implementation obligations discussed in our article on NIS2 implementation in Poland overlap here – businesses in essential sectors must treat KSeF API availability as a component of their ICT continuity planning.

Fourth: employee expense invoices. Polish employees who receive VAT invoices for business expenses – fuel, hotels, equipment – generate a separate stream of incoming KSeF documents. The company's accounts-payable team must be trained to retrieve those invoices from KSeF rather than from paper or email. The old workflow of collecting paper receipts at month-end is incompatible with KSeF's real-time architecture.

What should your KSeF compliance programme include?

A KSeF compliance programme is not a one-time IT project. It is an ongoing operational and legal framework. Businesses that treat it as a software installation miss the governance dimension – and the governance dimension is where personal liability originates.

The programme starts with a legal assessment of all invoicing flows: which are mandatory, which are excluded, and which fall into grey areas requiring a binding ruling. That assessment feeds the technical specification for ERP configuration. The legal and technical workstreams must run in parallel, not sequentially. Businesses that hand the project to IT without legal input tend to configure the system correctly for the standard case and incorrectly for the edge cases – which are precisely the cases that generate audits.

Training is underestimated. Accounts-payable staff, sales administrators, and finance controllers all interact with KSeF differently. Each group needs role-specific training, not a single all-staff presentation. The training must cover rejection handling, offline mode protocols, and the corrective invoice procedure. It should be documented and dated – that documentation becomes evidence of good-faith compliance in any subsequent KAS audit.

The programme must also address the interaction between KSeF and the broader Polish tax reporting architecture. KSeF data feeds into JPK_VAT, which feeds into KAS's risk-scoring model. Businesses with transfer pricing exposure, IP Box elections, or family foundation structures (where applicable under Polish income tax law) should map how their KSeF transaction data will appear in KAS's analytical environment. Inconsistencies between KSeF records and transfer pricing documentation are a red flag that accelerates audit selection.

A tax advisor in Warsaw with KSeF implementation experience will typically structure the programme across four phases: readiness audit (two to three weeks), configuration and testing (four to six weeks), go-live support (first 30 days), and ongoing monitoring (quarterly review). The quarterly review is where most businesses find value – because the Ministry of Finance continues to issue technical updates to the FA(2) schema, and each update requires a configuration response.

To receive an expert assessment of your KSeF readiness position, contact info@kordeckipartners.com.

KSeF compliance checklist: what to prepare

The following checklist covers the minimum preparation steps for a business approaching the KSeF mandatory deadline. Each item should be assigned an owner and a completion date.

  • Confirm mandatory deadline applicable to your entity (1 February or 1 April 2026) based on prior-year VAT turnover
  • Complete an invoicing flow audit covering all B2B, intra-group, and advance invoice transactions touching your Polish VAT registration
  • Obtain or configure a KSeF-certified API connection and complete sandbox testing with at least 50 representative invoice types
  • Document the offline mode procedure and assign responsibility for upload within the one-business-day window
  • Deliver role-specific KSeF training to accounts-payable, sales administration, and finance control teams with written attendance records

This checklist is a starting point. Complex businesses – those with multiple Polish VAT registrations, intra-group invoicing, or cross-border supply chains – will require a more granular programme. The checklist does not substitute for a legal readiness assessment.

Specific circumstances in your business may create exposure that a generic checklist will not identify. Personal liability for management arises from systemic non-compliance – and systemic non-compliance typically originates in gaps that looked minor during implementation. For a tailored strategy on KSeF implementation for your Polish operations, reach out to info@kordeckipartners.com.

Frequently asked questions

Q: Does KSeF apply to my Polish branch if the parent company is registered in Germany?

A: A foreign entity with a Polish VAT registration but no fixed establishment in Poland is currently excluded from the KSeF mandate under the transitional provisions. However, if your branch constitutes a fixed establishment under Polish VAT law – assessed by reference to human and technical resources present in Poland – the mandate applies from the relevant deadline. The distinction requires a fact-specific legal analysis. A binding tax ruling from the Director of the National Tax Information (Dyrektor Krajowej Informacji Skarbowej, DKIS) is the most reliable way to confirm the position. The ruling process typically takes three months.

Q: What happens if my ERP system goes down and I cannot submit invoices to KSeF on time?

A: Polish tax legislation provides an offline mode for periods when the KSeF system itself is unavailable. It does not provide an exception for the taxpayer's own systems being unavailable. If your ERP fails and you cannot submit within the required window, the invoice is treated as issued outside KSeF and the penalty exposure arises. For this reason, businesses should maintain a manual fallback process – a simplified offline invoicing tool that can generate FA(2)-compliant XML even when the primary ERP is down. That fallback must be tested, not merely documented. The offline invoice must be uploaded to KSeF within one business day of the system returning online.

Q: How does KSeF interact with transfer pricing documentation for intra-group transactions?

A: KSeF records intra-group invoices in real time, and that data is accessible to KAS. The practical consequence is that any inconsistency between the invoice price recorded in KSeF and the arm's-length price documented in your transfer pricing file will be visible to auditors without the need for a formal information request. Businesses with related-party transactions exceeding the local file threshold – currently PLN 10m for goods transactions and PLN 2m for service transactions – should review their KSeF invoice fields against their transfer pricing benchmarking analysis before go-live. Retroactive corrections are possible but attract scrutiny. Proactive alignment is materially less costly.

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 KSeF implementation, VAT advisory, and tax compliance. 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.