Trusted Digital Transformation Partner

Home / E-Invoicing / Poland

Poland · KSeF · Penalties from January 2027

E-Invoicing in Poland (KSeF)

Poland routes invoices through KSeF, its national platform, tying e-invoicing directly to real-time tax reporting. 2026 is a grace year — penalties of up to 100% of the invoice VAT begin in January 2027.

Talk to us about Poland

In short

E-invoicing in Poland requires domestic B2B invoices to be issued as structured electronic documents through KSeF national platform, using KSeF (Krajowy System e-Faktur). KSeF became mandatory for large taxpayers (annual turnover above PLN 200 million) from February 2026, with most other VAT-registered businesses following in April 2026 and micro-enterprises in January 2027. A full-year grace period applies throughout 2026: no financial penalties are imposed until 1 January 2027, after which non-compliance can carry penalties of up to 100% of the VAT amount on the invoice. Whatever the local mechanism, the invoice still has to come out of your ERP correctly — and in our experience that is where projects actually succeed or fail. ROSTAN builds the integration into Oracle EBS and Fusion Receivables so compliance is generated from the invoice the business already raises.

The deadline

Grace year now, penalties 2027

Dates reported from published guidance. Confirm your own obligation with your tax adviser — ROSTAN implements the ERP integration and does not provide tax or legal advice.

What Poland requires

KSeF became mandatory for large taxpayers (annual turnover above PLN 200 million) from February 2026, with most other VAT-registered businesses following in April 2026 and micro-enterprises in January 2027. A full-year grace period applies throughout 2026: no financial penalties are imposed until 1 January 2027, after which non-compliance can carry penalties of up to 100% of the VAT amount on the invoice.

Forbes — 2026: mandatory e-invoicing across Europe

What makes Poland different

The details that change the integration

Central clearance, not exchange

Unlike Belgium's Peppol model, KSeF is a government platform the invoice passes through. That changes the integration: you are submitting and receiving a reference, not just transmitting a document.

The grace period is the opportunity

2026 without penalties is the window to get this right. Organisations that treat the grace year as permission to wait arrive at January 2027 with an untested integration and real financial exposure.

Real-time reporting

Poland ties e-invoicing directly to tax reporting, so the invoice data and the tax position have to agree at the moment of issue. Reconciliation after the fact is not a strategy here.

Phased by turnover

Large taxpayers first, then most VAT-registered businesses, then micro-enterprises. Groups with several Polish entities may have different obligation dates within the same organisation.

The portal is rarely the problem

Statutory e-invoicing is the single largest workload on our own Oracle service desk. These are the causes we see behind rejections, wherever the mandate is.

Tax or product master data that does not match what the schema expects — the most common single cause.

Party identifiers (VAT numbers, registration IDs, addresses) missing or formatted for a human rather than a validator.

A payload that validates in test and fails in production because a real invoice carries a case the sample never did.

No controlled retry path — a rejected invoice is not a valid invoice, and manual re-keying does not scale.

Nobody owning reconciliation: invoices issued in the ERP but never confirmed as accepted downstream.

The receiving side left out of scope, so supplier invoices arrive in a format Accounts Payable cannot process.

FAQ