Poland's KSeF Is Live. What Happens Next
Mandatory structured invoicing arrived in Poland during 2026, and the grace period that softened it ends with the year. For companies already inside KSeF: what changes on 1 January 2027, where live implementations are quietly failing, and how KSeF and the JPK files fit together.
Country briefing · September 2026 · CFOs, Tax and Finance leads
Download Full Briefing (PDF, EN)FA(3)
The structured format in force, with attachment support and additional party fields
24h
To deliver an offline-issued invoice into the system: the next business day
10 years
Invoices retained centrally, which changes what your own archive is for
1 Jan 2027
Payment references change and the smallest taxpayers join; penalties now proposed for 2028
Key takeaway for finance and tax leaders: a suspended penalty regime is not the same as a working process. Through 2026 an invoice that failed to reach the platform, a rejection nobody noticed, or a customer quietly receiving a PDF instead of a structured document has carried no immediate cost. Once penalties apply, those same gaps carry exposure, and they will be visible, because everything that did reach the platform is already recorded there.
Live for Everyone, but Not Yet Enforced
Poland's National e-Invoice System (KSeF) moved from optional to compulsory during 2026. Structured invoices in the national format, issued through a central government platform, are now the norm for business-to-business transactions. What has not yet arrived is enforcement.
Where the Mandate Stands Today
Mandatory for the largest taxpayers
Broadly those whose 2024 sales exceeded PLN 200 million.
Mandatory for all other businesses
Those established in Poland, and foreign entities with a Polish fixed establishment.
Grace period
Penalties for invoicing failures suspended, and the obligation to quote the KSeF number in payments deferred.
Payment references change and the smallest taxpayers join
This was also the planned start date for penalties; see below.
Penalties, under the Ministry of Finance proposal
In September 2026 the Ministry proposed extending penalty protection to the end of 2027 (bill UD477, not yet enacted).
Three Things That Surprised Companies at Go-Live
| Expectation | What actually happened |
|---|---|
| “It is an IT project” | It changed how sales are billed, how corrections are made and when revenue is recognised as invoiced. The people most affected sat in finance, not in IT |
| “We will connect the ERP and we are done” | Invoices also came from billing engines, service tools and local spreadsheets. Every one of those had to reach the platform too |
| “Receiving will look after itself” | Supplier invoices stopped arriving by email and started waiting in the platform. Accounts payable had to change before month-end, not after |
Who Is Still Outside
Below the defined monthly sales and per-invoice values, with an exemption that runs until the start of 2027.
Outside the mandate, so most businesses run two paths and have to keep them reliably separate.
Without a Polish fixed establishment, generally outside the obligation; precisely the sort of determination worth confirming rather than assuming.
A Central Platform, an Identifier and a Moment of Legal Truth
Poland uses a centralised model. The invoice goes to the government platform, which validates it and returns an identifier; only then does it exist as a legal invoice. Your customer collects it from the same platform.
Qualified signature, trusted profile or a token with a certificate
Certificates and tokens expire, and an expiry discovered during a billing run is an outage.
The invoice is transmitted in the national structured format
Anything the schema does not allow is rejected outright, not warned about.
The platform returns a unique number: the invoice legally exists
The number has to be stored against the document, not just logged.
Your customer retrieves the invoice from the platform
You do not send it to them; a PDF you email is a courtesy copy, not an invoice.
The same is true in reverse
Your supplier invoices wait in the platform to be pulled into your system and posted.
Who Has to Do What, After Go-Live
| Role | Daily or periodic responsibility |
|---|---|
| Accounts receivable | Check that yesterday's invoices are confirmed; fix and resend anything rejected; issue corrections through the structured process |
| Accounts payable | Collect supplier invoices from the platform, match and post them, and query anything that arrives outside it |
| Tax | Reconcile what was invoiced to what was reported, and own the treatment of the awkward cases |
| IT | Keep authentication valid, monitor the interface, and hold a tested procedure for the day the platform is unavailable |
| Finance leadership | Ask for the completeness numbers monthly, and treat a gap as an exception requiring an explanation |
Why This Model Is Stricter than a Network Model
In Peppol-style countries, invoices travel between accredited providers and the authority receives a copy of the tax data. In Poland the platform is the route: there is no fallback path, no second provider, and no version of the invoice that exists outside the system. That makes availability, authentication and status handling operational matters, not IT details. A rejected invoice is not a technical ticket; it is an unbilled sale.
Offline Modes and the Awkward Cases
Poland accepts that an invoice sometimes has to be issued when the platform cannot be reached, by you or at all. The rules allow it, with conditions, and those conditions are where most operational problems appear.
Issuing Outside the System
| Situation | What is permitted | The obligation that follows |
|---|---|---|
| Permanent offline option | An invoice may be issued outside the platform and given to the customer, carrying a QR code that lets them verify it | It must be delivered into the platform by the next business day |
| Platform unavailable | Issuing continues under the published failure rules while the outage lasts | Submission once service is restored, within the period the rules allow |
| Your own systems down | The same practical route, but the reason is yours rather than the platform's | The clock still runs; nothing about the deadline is softened |
The QR Code Is Not Decoration
An invoice handed over before it reaches the platform must carry the prescribed code so the recipient can verify it, and where it is issued using a certificate outside the system a second code applies. This is a layout and printing requirement that reaches every invoice form you produce, and a common gap in implementations that focused only on the data being transmitted.
Write the Procedure Down, Then Rehearse It
It should name who decides the platform is unreachable, who authorises issuing outside it, how the invoices are tracked until they are submitted, and who confirms that every one of them landed. Rehearse it once a year: the first execution should not be during a real outage at month-end.
The Cases That Catch People Out
The format now allows an attachment as part of the invoice, with notification requirements, but only in defined circumstances. Businesses that used to append schedules to a PDF need a different answer.
Billing engines, field-service applications and local tools all have to reach the platform and return the identifier to wherever the accounting entry lives.
Agreed arrangements between parties still have to fit the structured process rather than the informal one they replaced.
Outside the mandate, so two paths exist. The failure mode is a business customer treated as a consumer, and an invoice that never reaches the platform.
What belongs in the system is not always obvious, and getting it wrong in either direction has consequences.
What Changes on 1 January 2027
Three changes, and one of them reaches treasury.
Penalties Begin, Probably a Year Later
The suspension of sanctions was due to end with 2026. In September 2026 the Ministry of Finance proposed extending it to 1 January 2028 (bill UD477, not yet enacted). Exposure is framed as a proportion of the VAT on the documents concerned, so the cost scales with the size of the gap. Be ready for January anyway.
Payments Carry the KSeF Number
Buyers settling invoices issued through the system are to quote the invoice's identifier in the payment reference: a change that reaches banking files, payment runs and cash application.
The Smallest Taxpayers Join
The exemption for very small issuers ends, bringing the final group into the regime and completing the coverage of domestic business-to-business invoicing.
Dates have been amended repeatedly during implementation, and the extension of penalty protection is still going through the legislative process; confirm the current position with your tax adviser.
The Payment-Reference Change Deserves Attention Now
It looks like a formatting detail and it is not. Outgoing payment files must carry the identifier in the right field, which means the payment proposal has to find it on the invoice it is paying: it has to have been stored there, reliably, from the moment it was received.
On the receivable side, the identifier will start arriving on incoming payments: an opportunity for automatic matching if the data is in place, and noise if it is not. Bank formats may need review, and supplier invoices captured before the change may not carry the identifier at all.
How to Test the Payment Change Before It Is Mandatory
Pick ten supplier invoices
Proves the identifier is on the accounting document, not only in an interface log.
Run a payment proposal
Proves the proposal can read the identifier from the invoice it is settling, without anyone looking it up.
Generate the bank file
Proves the reference field carries the identifier intact, without truncation or reformatting.
Check with the bank
Proves the format is accepted and the reference is passed through to the beneficiary as sent.
Look at incoming payments
Proves your cash application can use an identifier arriving on a customer payment, rather than discarding it.
A Practical Sequence for the Fourth Quarter
Identifier stored and retrievable
Confirm the identifier is stored against every inbound and outbound invoice, and that it is retrievable from the accounting document.
End-to-end payment run
Test a payment run carrying the reference end to end, including the bank file, and agree with your bank that the format is accepted.
Start January clean
Close the gap between invoices issued and invoices confirmed, and decide how the transitional population of older supplier invoices will be paid.
What It Means for Your SAP System
SAP addresses Polish requirements through SAP Document and Reporting Compliance. Its electronic-document side turns billing and supplier documents into structured invoices, submits them, and returns the identifier and status to the document; its statutory reporting side produces the periodic JPK files. Both draw on the same ledger, and that is the point.
What a Healthy Implementation Looks Like
| Element | What “good” means |
|---|---|
| Determination | Every document that must go to the platform does, and nothing else does. Consumer and out-of-scope flows are separated by rule, not by memory |
| Identifier handling | Stored against the accounting document and retrievable for payments, reporting and audit, not only visible in a monitor |
| Validation before sending | Content is checked in your system first, so rejections are rare and are fixed by the person who caused them |
| Status monitoring | A daily view of documents without a final status, with alerting, owned by a named person in finance rather than by an inbox |
| Inbound processing | Supplier invoices pulled in, matched and posted from structured data, with the identifier carried through to payment |
| Output and QR | Printed and emailed forms carry the required codes in the required cases |
Where Live Systems Are Usually Weakest
Nobody owns the daily check, so failures accumulate silently.
Stored in an interface table, not on the document.
Non-ERP billing sources were left for “phase two” and never returned to.
Offline and failure procedures were written but never rehearsed.
Certificate and token expiry has no owner and no calendar entry.
Inbound is still keyed by hand because the project ran out of time.
Reaching the Platform Is Not the Same as Being Compliant
Most implementations delivered in the 2026 rush achieved the first milestone: invoices reach the system. Fewer achieved the second: a process that proves every invoice reached it, catches the ones that did not, and can be operated by the finance team without the implementation partner. The grace period hid the difference. The end of suspended penalties will not.
Five Questions for Whoever Supports Your System
- Show me last month's completeness figures — invoices issued against invoices confirmed — produced from the system rather than assembled by hand.
- Where exactly is the identifier stored, and can a payment programme read it without a custom lookup?
- What alerts exist, who receives them, and when did one last lead to an action?
- Which billing sources are not connected, and what is the plan and date for each?
- Who applies the next specification change, under what arrangement, and is regression testing included?
KSeF and JPK: Poland Asks for the Invoices and the Books
Structured invoicing is only half of Poland's digital reporting. The JPK files, Poland's implementation of the standard audit file (SAF-T), have been in place for years and have recently extended from VAT into the accounting and corporate-income-tax domain. A company operating in Poland now files at several levels of detail, and the administration can compare them.
Individual structured invoices, at the moment of issue. Continuous.
The VAT records and the return combined in one file, with transaction-level detail and classification codes. Monthly, by the 25th.
Accounting books with tax reconciliation data, plus a fixed and intangible asset file. Annual, phasing in by taxpayer group.
The accounting and CIT files have phased in from 2025 for the largest taxpayers, extending to further groups in 2026 and 2027, with the annual deadline subject to change. Confirm which files and dates apply to your entity.
The Same Transaction, Three Times
The same transaction is reported three times, at three levels of detail, to the same administration. Differences between them are findable automatically, and they are the natural starting point for an enquiry.
Shared Data
Tax codes, partner identification, document types and the chart of accounts drive all three. Fixing them once improves all three; leaving them broken means explaining the same issue repeatedly.
Reconciliation Is a Control
Companies that reconcile invoices issued to invoices in KSeF, and the VAT file to the ledger, find their own problems first. That is a materially better position than being told about them.
What a Monthly Reconciliation Should Cover
| Comparison | What a difference tells you |
|---|---|
| Invoices issued ↔ invoices in KSeF | Completeness. A difference is an unreported sale, and it is the easiest thing for the administration to find |
| VAT file ↔ the ledger | That what you declared is what you posted. Differences here are the classic source of enquiry |
| VAT file ↔ invoices in KSeF | That the transaction-level detail agrees with the documents themselves, including corrections |
| Annual accounting file ↔ statutory accounts | That the books you file and the accounts you publish tell the same story |
The Regional Picture
Poland is not unusual any more. Romania has filed a standard audit file since 2022 and has piloted automated comparison against the VAT return; Bulgaria began its own regime in 2026. For a group operating across the region, the efficient answer is one compliance design and one team rather than a local solution and vendor per country: the second country costs a fraction of the first when the foundation is shared.
A Health Check Before January: Fourteen Questions
If your implementation went live during 2026, use this as a short diagnostic. Each answer should rest on a number or a document, not on an opinion.
The Fourteen Questions
| # | Question | If the answer is unclear |
|---|---|---|
| 1 | How many invoices did we issue last month, and how many are confirmed in the system? | You cannot demonstrate completeness — the first thing an enquiry tests |
| 2 | Who looks at failures, and how often? | Failures are accumulating and will surface all at once |
| 3 | Is the identifier stored on the accounting document? | The 2027 payment-reference change becomes a project you have not planned |
| 4 | Do all our billing sources reach the platform? | An unreported population exists, and it is invisible until it is penalised |
| 5 | When do our certificates and tokens expire? | An avoidable outage during a billing run |
| 6 | Has the offline procedure ever been rehearsed? | It will be executed for the first time under pressure |
| 7 | Do our printed forms carry the required codes? | A compliance gap on every document handed over early |
| 8 | Are supplier invoices posted from structured data? | Manual effort you are still paying for, and the 2027 change is harder |
| 9 | Can finance correct an invoice without IT? | Every correction becomes a ticket, and cycle time suffers |
| 10 | Does the VAT file reconcile to the ledger each month? | Differences will be found by someone else, later |
| 11 | Do we know which JPK accounting files apply, and when? | An annual obligation discovered after its deadline |
| 12 | Who applies specification changes after go-live? | The solution drifts out of compliance without anyone deciding to let it |
| 13 | Can we reproduce, for any invoice, exactly what was sent and what came back? | You cannot evidence your own position in an enquiry or a customer dispute |
| 14 | Do consumer and out-of-scope flows separate by rule, or by judgement? | A business customer will eventually be treated as a consumer, and that invoice never reaches the platform |
Questions 1, 3 and 4 are the ones to fix first in almost every case: completeness protects you in an enquiry, identifier storage decides how hard January is, and unconnected billing sources are the gap that grows quietly for as long as nobody measures it. Three or more unclear answers is not unusual for a system delivered against a hard 2026 deadline, but it is worth correcting now, while the grace period still absorbs the cost of what you find.
How 30 Advisory Can Help
A founder-led boutique specialised in SAP DRC & e-invoicing compliance, S/4HANA Finance optimisation and CFO/CIO strategic advisory. Most of the Polish work we are asked for now is not implementation. It is making a live implementation trustworthy before it starts to cost money.
KSeF health check, two to three weeks
Against the questions above, evidenced from your own system: completeness by month and source system, identifier storage, monitoring, offline readiness and output. Output: a prioritised gap list with effort and dates, and a 2027 readiness view.
Remediation and 2027 readiness
Identifier handling through to payments, inbound automation, monitoring with real ownership, rehearsed failure procedures and corrected output forms. Output: a clean January.
Run and legal change
Specification changes watched and applied in controlled windows, JPK obligations kept aligned, and the same design extended to your other countries.
A Sensible First Step
Ask for last month's numbers: invoices issued, invoices confirmed in the system, failures outstanding, and identifier coverage. If they arrive quickly and they agree, you are in good shape. If they do not, you have found your fourth-quarter priority, with time still on your side.
What Makes This Different
We work from evidence, not from a questionnaire: the health check is run against your data, because that is what an enquiry will do. We treat KSeF and JPK together, because they share a data foundation. And we are not your tax adviser: we work alongside the people who are.
Founder-led
Finance + SAP DRC depth
Multi-country: Italy, Türkiye, Spain
Boutique agility
Sources consulted 25 September 2026: Sovos, Marosa, PIKON, Banqup, EDICOM and VATupdate guidance on the KSeF mandate, its phasing, offline modes, QR codes, attachments, payment references and penalties; vatcalc on the JPK accounting and corporate-income-tax files. Proposed extension of penalty protection to 1 January 2028: Ministry of Finance announcement of September 2026 and bill UD477, as reported by VATupdate. SAP behaviour from the SAP Help Portal and partner commentary on SAP Document and Reporting Compliance.
Prepared by 30 Advisory, October 2026 (status at 5 October 2026). Information only — not legal or tax advice. Polish requirements have been amended repeatedly during implementation and secondary sources disagree on detail, including thresholds and deadline dates. Confirm the position for your entity with the tax administration or a qualified adviser before acting.
Not Sure What This Means for Your SAP Landscape?
We'll review your KSeF completeness, identifier handling through to payments and your SAP landscape's 2027 readiness in a 1-hour diagnostic session.
Schedule Assessment (1 hour)