Hopp til innhold
Tilbake til bloggen
PolandPublisert 2. juli 202611 min lesing

KSeF FA(3): Poland's mandatory e-invoicing in 2026 — the complete guide

KSeF becomes mandatory in Poland in 2026 with the new FA(3) schema. Deadlines, what changed from FA(2), how to generate a structured invoice, KSeF vs Peppol, penalties and an API example.

From 2026, structured e-invoicing through KSeF — the Krajowy System e-Faktur, Poland's National e-Invoice System — becomes mandatory for businesses in Poland, using a new invoice schema called FA(3). If you sell in Poland, or your ERP issues Polish invoices, this is the change you cannot skip. This guide covers the KSeF deadlines for 2026, what FA(3) changes compared to FA(2), how a structured invoice is generated, how KSeF relates to Peppol, and the penalty grace period.

What is KSeF and what is FA(3)?

KSeF (Krajowy System e-Faktur) is Poland's central, government-run e-invoicing platform. Every domestic invoice in scope must be issued into KSeF, which validates it, assigns it a KSeF ID and timestamp, and makes it available to the buyer. It is a clearance (CTC) model: the tax authority sits in the middle of every invoice, unlike a pure Peppol four-corner exchange.

FA(3) is the XML schema (the logical structure) that a KSeF invoice must follow. It is the successor to FA(2): the Ministry of Finance published the FA(3) draft in 2025 and it replaces FA(2) as the mandatory structure when the obligation starts. If your system still emits FA(2), it needs to move to FA(3).

KSeF deadlines in 2026

The mandate is phased by company size, but the obligation to receive invoices through KSeF applies to everyone from day one:

  • 1 February 2026 — large taxpayers (turnover above PLN 200 million in the prior year) must issue structured invoices via KSeF. FA(2) is fully replaced by FA(3) on this date.
  • 1 February 2026 — every taxpayer must be able to receive invoices through KSeF, regardless of size.
  • 1 April 2026 — the obligation to issue extends to all other taxpayers established in Poland.
  • 1 January 2027 — the smallest (micro) businesses come into scope.

Practical takeaway: even a small business that is not yet obliged to issue via KSeF in February still has to be able to receive KSeF invoices from 1 February 2026.

What changed from FA(2) to FA(3)?

FA(3) keeps the overall shape of a Polish structured invoice but refines it. When migrating, focus on these areas:

  • Updated schema version and namespace — your XML generation must target the FA(3) structure, not FA(2).
  • Adjusted and clarified fields around invoice types, correction invoices and payment data.
  • Alignment with the operational KSeF 2.0 changes (attachments handling, offline modes) that accompany the 2026 go-live.

The migration is mostly a serialisation change — the business data on your invoice does not change, but the XML it is written into does. A converter that already targets FA(3) removes that burden.

How to generate a compliant FA(3) invoice

You do not have to hand-build FA(3) XML. With MyInvoice you send the invoice data you already have — CSV, Excel, UBL, EDIFACT or legacy XML — and request the ksef-fa3 profile. The API returns FA(3) XML validated against the official Ministry of Finance schema:

curl -X POST https://api.myinvoice.llc/v1/convert \
  -H "X-API-Key: ek_live_..." \
  -F "[email protected]" \
  -F "format=csv" \
  -F "profile=ksef-fa3"

You get back a structured FA(3) document that is ready to submit into KSeF. You keep your existing data source; you do not have to learn the schema field by field.

Try the converter in your browser

KSeF vs Peppol — how do they relate?

This is the most common point of confusion. KSeF is the mandatory national clearance system for domestic Polish invoices, in the FA(3) format. Peppol is an international network for exchanging EN 16931 invoices (Peppol BIS 3.0) between trading partners across borders. They solve different problems: KSeF is compliance with the Polish tax authority; Peppol is cross-border interoperability.

Many businesses need both: FA(3) into KSeF for their Polish domestic flow, and Peppol BIS 3.0 for EU trading partners. MyInvoice can emit both from the same invoice data.

Penalties and the 2026 grace period

The Ministry of Finance has confirmed that KSeF-related penalties will not be imposed throughout 2026. This grace window is meant for resolving technical issues, training staff and stabilising integrations — but it is not a reason to wait. Receiving is mandatory from February, and the earlier you can issue clean FA(3) invoices, the less risk you carry into 2027.

How to prepare — a short checklist

  • Confirm which phase you fall into (turnover above or below PLN 200 million).
  • Make sure you can receive KSeF invoices from 1 February 2026.
  • Move invoice generation from FA(2) to the FA(3) schema.
  • Decide how you connect: the Ministry portal, accounting software, or a direct API/integration for volume.
  • If you also trade cross-border, plan your Peppol BIS 3.0 output alongside FA(3).

Frequently asked questions

Is FA(2) still valid in 2026? No — FA(2) is replaced by FA(3) when the obligation starts on 1 February 2026. New invoices must use FA(3).

Do I need KSeF if I only issue a few invoices? Yes — the obligation is based on the transaction type and your phase, not on volume. And receiving is mandatory for everyone from February 2026.

Can I integrate KSeF without using the government portal? Yes — you can generate FA(3) and submit programmatically. An API-based converter fits high-volume or ERP-driven flows better than manual portal entry.

Where MyInvoice fits in

MyInvoice turns the data you already have into a validated FA(3) invoice for KSeF — and, from the same data, into Peppol BIS 3.0, XRechnung, Factur-X or any other profile you need for other markets. One API, every format, XSD + Schematron validated before it reaches you.

Read the API docs