Poland KSeF e-invoicing 2026

Plan for Poland's 2026 KSeF e-invoicing rollout with structured FA_VAT XML readiness guidance and EN 16931 invoice workflows.

What this covers

• KSeF mandatory windows start in 2026 — large companies first, all businesses after.
• Seller, buyer, VAT, and line-item data organized for FA_VAT XML handoff.
• EN 16931-ready invoices generated while your KSeF integration matures.

Largest firms

Feb 2026 (>PLN 200M)

All others

Apr 2026 · small biz end-2026

Format

FA(3) XML via KSeF

The KSeF 2.0 rollout windows

Poland's mandatory e-invoicing through KSeF (Krajowy System e-Faktur) goes live in two waves during 2026: February 2026 for the largest taxpayers (sales above PLN 200 million in 2024), and April 2026 for all other businesses, with the smallest taxpayers (under PLN 10 million) receiving a deferral on digitized invoices until the end of 2026. KSeF 2.0 is a clearance system — an invoice legally exists only once the platform accepts it and assigns a KSeF number.

This is the strictest model in the current EU wave: you do not send the invoice to your customer at all — you submit structured FA(3) XML to KSeF, the platform timestamps and registers it, and the buyer retrieves it from KSeF or their own integration. Correction invoices, partial payments, and offline issuance each have defined procedures under the new law.

What the FA(3) schema means for your data

The FA(3) logical structure is more demanding than EN 16931 basics: it requires Polish tax identifiers (NIP), structured line-item tax rates, and field-level discipline that exposes sloppy master data immediately. Common failure points in early adoption are incorrect buyer NIP handling, missing or inconsistent payment data, and unit-of-measure codes that do not match the schema's expected vocabulary.

Because the platform validates on submission, data errors surface as submission failures — a rejected invoice is legally not issued, which means the transaction is uninvoiced until corrected. Companies migrating from PDF workflows should treat the schema validation rules as their new definition of "a correct invoice," not the visual layout.

How foreign and smaller businesses should prepare

Foreign entities with a Polish VAT registration fall inside the mandate and need a KSeF integration path — either direct API integration or a service provider. Non-established suppliers invoicing Polish buyers are not obligated, but Polish buyers increasingly prefer KSeF-compatible handling since their books integrate with the platform.

For smaller businesses the pragmatic path is: clean your customer and item master data now, run your typical invoice shapes through a structured generator to see where fields are missing, and choose a KSeF connectivity approach (government app, accounting-software module, or integrator) before your window opens. The businesses that struggled in other countries' mandates were the ones whose data was PDF-shaped; the format conversion is trivial once the data is right.

Last reviewed September 2026 by the Eurorix team.