Poland KSeF 2026–2027: How Mandatory
E-Invoicing Changes Your AP Workflow

What Makes Poland's Approach Different from the Rest of Europe

Most of the EU's e-invoicing mandates follow a pattern: governments designate a set of approved platforms, businesses pick one, and invoices flow through a network of interoperable providers. France is building its PDP (Plateforme de Dématérialisation Partenaire) model with multiple certified platforms. Germany's upcoming mandate is similarly decentralized. Italy's Sistema di Interscambio (SdI) was the template many others followed.

Poland chose a different path entirely.

KSeF is a single, state-owned, centralized platform. There is no marketplace of certified providers. Every Polish B2B invoice goes through one system, operated by the Ministry of Finance (Ministerstwo Finansów), using one XML schema — the FA(3) logical structure. An invoice does not legally exist until KSeF validates it and assigns a unique KSeF identification number. This is a clearance model: the government sees every invoice before either party considers it done.

Why does this matter for your AP workflow? In the multi-platform models coming to France or Germany, you have options — you can choose a provider that aligns with your existing tools. With KSeF, there is exactly one system to integrate with. The upside: one standard means one predictable data structure. The tradeoff: if your ERP can't talk to KSeF's API, there's no alternative route.

The Timeline: Three Phases, One Hard Truth

The rollout is size-based. The detail most timeline summaries miss: February 1 wasn't just "large taxpayers must issue." From that date, every VAT-registered Polish business — regardless of size — had to be technically capable of receiving purchase invoices through KSeF. If you're a small Polish company buying from a large supplier, you needed a way to retrieve your incoming invoices from KSeF months before your own issuing obligation kicked in.

The entire calendar year 2026 operates as a transition period: no financial penalties, and authorities emphasize education and adaptation. Invoices issued outside KSeF when they should have been in the system may still be treated as not legally issued — the penalty just doesn't include a fine. That changes on January 1, 2027, when sanctions of up to 100% of the VAT amount per non-compliant invoice become enforceable under Article 106ni of the Polish VAT Act.

How KSeF Changes Your AP Workflow, Day by Day

Before KSeF, a typical Polish AP workflow looked like this: supplier emails a PDF invoice → AP clerk downloads the attachment → manually enters data into the ERP → routes for approval → schedules payment.

Under KSeF, the first link in that chain breaks. The supplier submits a structured XML file to KSeF. The platform validates it — checking XML schema compliance and issuer authorization — and assigns a KSeF number. The buyer does not receive the invoice from the supplier. The buyer retrieves it from KSeF, either through the KSeF Taxpayer Application (Aplikacja Podatnika KSeF), their ERP's KSeF integration, or an intermediary service.

This is a fundamental rewire of how accounts payable operates. Here's what changes in practice:

Cross-Border Complications: When a Polish Supplier Invoices a Foreign Buyer

This is where KSeF creates genuine operational overhead that most introductory guides gloss over.

Polish supplier → foreign buyer (no Polish NIP): The Polish supplier must still issue the invoice through KSeF — including for intra-EU supplies and exports. The invoice receives a KSeF number and is archived in the KSeF system for 10 years. But the foreign buyer has no access to KSeF. Non-Polish entities without a Polish NIP cannot log into the platform. So the supplier must also deliver the invoice to the buyer through an alternative agreed method: typically as a PDF with a QR code that links back to the KSeF entry for verification.

For the foreign buyer's AP team, the result is a PDF that looks superficially like a normal invoice — but carries a KSeF number their ERP has no field for, referencing a platform they can't access. If the buyer needs to verify the invoice's authenticity or check for corrections, they rely entirely on the supplier to provide that information. There's no self-service lookup for foreign recipients.

Foreign supplier → Polish buyer: Foreign suppliers without a Polish fixed establishment are not required to use KSeF. The Polish buyer handles these invoices through standard reverse-charge accounting and reports them in their JPK_VAT (SAF-T) filing with a special code indicating a foreign invoice. No KSeF number is generated for these inbound foreign invoices. The AP team's workflow for non-Polish suppliers remains largely unchanged — at least until ViDA's cross-border digital reporting requirements take effect in 2030.

The Software Landscape: What Polish Businesses Actually Use

Unlike some EU countries where e-invoicing means picking from a list of certified providers, KSeF integrates directly with the accounting and ERP software businesses already run. Most platforms built KSeF modules during the 2022–2025 voluntary phase. Here's what the landscape looks like for AP teams evaluating their options:

For enterprise users, SAP (via SAP Document and Reporting Compliance) and Microsoft Dynamics 365 both offer KSeF modules. Large multinationals typically route KSeF through an intermediary compliance platform (Vertex, Sovos, EDICOM) rather than building direct API integrations.

If your invoice volume crosses multiple markets, look for platforms that handle both KSeF's FA(3) schema and Peppol BIS for EU cross-border. enova365 and enterprise compliance platforms offer this dual support natively. The PEF (Platforma Elektronicznego Fakturowania) handles Polish B2G transactions using Peppol — a separate pipeline from KSeF B2B.

What Happens If You Don't Comply

The Polish Ministry of Finance built a deliberate two-stage enforcement model. Throughout 2026, no financial penalties apply. This grace period gives businesses time to register for KSeF, authorize users, connect their software, and stabilize their workflow. But invoices issued outside KSeF when the mandate applies may still be treated as not legally issued — which means the recipient cannot claim input VAT deduction on them. That's a 23% cost increase on every non-compliant purchase invoice, with or without a fine.

From January 1, 2027, the penalty structure under the KSeF Act activates:

• Up to 100% of the VAT amount on each invoice issued outside KSeF when the mandate requires it. A single 50,000 PLN invoice at 23% VAT carries 11,500 PLN in tax — and an equal penalty.
• Up to 18.7% of the gross invoice value for VAT-exempt invoices issued outside the system.
• Late offline submission penalties for failing to submit offline-mode invoices within the next-business-day window.

The Ministry has stated that penalties will be applied proportionally and assessed case-by-case — the maximum figures are ceilings, not automatic fines. But the risk of blocked VAT deductions alone makes non-compliance commercially untenable for any business issuing more than a handful of B2B invoices per month.

Frequently Asked Questions

When exactly does KSeF become mandatory for my business?

If your 2024 turnover exceeded PLN 200 million (~€46M), your issuing obligation started February 1, 2026. All other VAT-registered businesses (except micro-entrepreneurs) must issue through KSeF from April 1, 2026. Micro-entrepreneurs with monthly invoiced sales under PLN 10,000 have until January 1, 2027. However — every Polish VAT-registered business, regardless of size, must be capable of receiving invoices from KSeF as of February 1, 2026.

Do I still need to accept PDF invoices from Polish suppliers?

No — once KSeF applies to your supplier, the legally valid invoice is the structured XML in KSeF, not the PDF. However, foreign buyers who cannot access KSeF will continue receiving PDFs with QR codes as a practical delivery method. The PDF is a convenience copy — the KSeF entry is the legal original. For Polish domestic buyers, the invoice is deemed delivered the moment KSeF assigns its number, as long as your NIP is correctly listed on it.

Can KSeF reject an invoice?

Yes. KSeF rejects invoices that fail XML schema validation or are submitted by unauthorized persons. However, it does not verify whether the invoice amounts, service descriptions, or tax calculations are correct — those remain the responsibility of the parties. KSeF validates structure and authorization, not accounting accuracy.

What if an invoice has the wrong buyer NIP?

This is the most common error under KSeF. The correction requires a two-step procedure: first, issue a corrective invoice "to zero" that neutralizes the original, then issue a new invoice with the correct buyer NIP. You cannot simply update the NIP on the original. This two-step correction process is more rigid than pre-KSeF practices and requires careful tracking in your AP system.

How long are invoices stored in KSeF?

KSeF automatically archives all submitted invoices for 10 years. Businesses can retrieve their historical invoices at any time through the platform. However, the Ministry of Finance advises businesses to maintain their own archives as well — KSeF's archiving is a compliance service, not a backup for your own records.

Does KSeF support attachments like delivery notes or contracts?

FA(3) includes an optional attachment element (Załącznik), but with strict restrictions: it can only contain structured tax-related data, not free-form PDFs, JPGs, or contracts. Using the attachment element for marketing materials, contracts, or price lists can result in revocation of attachment rights. Supporting documents like delivery notes and timesheets still flow through separate channels, which means AP teams continue to handle a mix of structured KSeF XML and unstructured supporting documents.

How does KSeF relate to Peppol and EU e-invoicing standards?

KSeF's FA(3) schema is not based on the European Norm EN 16931. It derives from Poland's SAF-T (JPK) structure instead. This means KSeF invoices are not Peppol-compatible by default. Polish businesses that also trade with EU partners via Peppol need to handle two separate formats and submission pipelines. The PEF (Platforma Elektronicznego Fakturowania) handles Polish B2G transactions using Peppol BIS — entirely separate from KSeF B2B. Some tools (enova365, enterprise compliance platforms) bridge both, but there's no single unified pipeline.

What practical steps should my AP team take now?

Three non-negotiable steps: (1) Register your business in KSeF and authorize the right people — without this, you cannot receive invoices. (2) Connect software that can consume KSeF XML — whether that's your ERP's KSeF module or an intermediary like SaldeoSMART. (3) Add KSeF number tracking to your AP workflow — from invoice receipt to payment reference, the KSeF number needs a dedicated field and reconciliation step. Everything else — approval routing, coding, payment scheduling — builds on top of these three foundations.

The Bigger Picture: Structured E-Invoicing as an AP Efficiency Lever

There's a tendency to treat KSeF as a compliance burden — another government system to integrate with. That framing misses something important.

Before KSeF, when your AP team received a Polish invoice, the data was locked inside a PDF. Someone had to manually extract the supplier name, NIP, invoice number, line items, VAT breakdown, and total — keying each field into the ERP. Tools exist to automate this, using AI to extract data from PDF invoices, but there's always a parsing step between the document and your system.

Under KSeF, the invoice data arrives already structured. The extraction step — for the invoice itself — disappears. Where extraction tools remain valuable is in bridging the gap: processing the supporting documents that KSeF doesn't handle (delivery notes, contracts, timesheets), cross-checking KSeF XML data against PDF copies to detect duplicates, and automating discount capture from payment terms embedded in structured data.

The AP teams that treat KSeF solely as a compliance project will get the compliance checkbox. The teams that treat it as a data-quality upgrade — recognizing that structured invoice data enables rule-based approval routing, faster month-end close, and straight-through processing for clean invoices — will get a measurable efficiency gain alongside the compliance box.

The question isn't whether you need to connect to KSeF. That ship sailed in February. The question is whether your AP workflow is designed to consume structured data, or whether you're treating KSeF XML like a PDF you have to download and re-key.