Skip to main content

Poland: KSeF 2.0 API Release 2.9.0 Is Scheduled for Production on 15 October 2026 and Adds Owner Permissions to the Personal-Permissions Query

KGT Country Update | 20 October 2026 | VAT, e-invoicing and SAF-T monitor

On 14 October 2026, the Centrum Informatyki Resortu Finansów (CIRF), the Polish Ministry of Finance’s IT center responsible for the National e-Invoice System (Krajowy System e-Faktur, KSeF) 2.0, published API release 2.9.0 in its official ksef-api repository.

According to the release schedule and the api-changelog.md file in the ksef-docs repository, the release was deployed to the TEST and DEMO environments on 13 October 2026 and scheduled for production (PROD) on 15 October 2026. It is a small, additive release: the personal-permissions query endpoint can now return owner permissions, and the error documentation gains one code that the API already returned.

Background

KSeF became mandatory for taxpayers with turnover above PLN 200 million from 1 February 2026 and for all other VAT-registered taxpayers from 1 April 2026. Since go-live the Ministry of Finance has shipped incremental API versions through CIRF, each documented in the ksef-api repository and its companion ksef-docs repository.

KGT’s earlier country updates tracked releases 2.7.0, 2.7.1, 2.8.0, and 2.8.1; release 2.8.1 (production 23 September 2026) added collective-identifier error codes and allowed the CollectiveIdentifierManage permission to be granted. Release 2.9.0 is the next increment after that production cutover.

The Legislative Change

This is not a legislative or regulatory change. KSeF’s legal basis, scope, thresholds and go-live dates are unaffected. Release 2.9.0 operates entirely within the existing legal framework as a technical update to the published API contract.

It is nonetheless binding in practice. KSeF is a mandatory clearance system and an integration must conform to the API contract actually deployed in production. A client that parses responses with a fixed schema can be affected by a new optional response field or enumeration value even when the change is described as additive.

According to the api-changelog.md entry for version 2.9.0, the release contains two changes:

  • Permissions (Uprawnienia): the POST /permissions/query/personal/grants endpoint now supports OwnerPermissionScope, which returns owner permissions.

  • OpenAPI: the error-response documentation now includes code 21001 (unreadable content). The changelog describes this as a documentation-only change, because the API already returned the code before.

Scope

The release affects every taxpayer, software house and service provider integrating with the KSeF 2.0 API, directly or through an ERP add-on, middleware or accredited intermediary.

Functionally, only integrations that call the personal-permissions query endpoint (for example, to display or audit which permissions the authenticated person holds) are likely to see different response content; all other integrations are unaffected functionally but should still re-generate or re-validate client code against the new specification version.

Timeline

  • 21 July 2026, 26 August 2026 and 14 September 2026 — releases 2.7.0, 2.7.1 and 2.8.0 published (covered in earlier KGT updates).

  • 22 September 2026 — release 2.8.1 published; DEMO and PROD on 23 September 2026.

  • 13 October 2026 — release 2.9.0 scheduled for TEST and DEMO.

  • 14 October 2026 — release 2.9.0 published on the ksef-api GitHub repository (tag 2.9.0).

  • 15 October 2026 — scheduled PROD deployment of release 2.9.0.

Businesses Affected

All taxpayers required to use KSeF and every SAP add-on, middleware or accredited-intermediary integration built on the KSeF 2.0 API are affected in principle. In practice, the most exposed are organizations that generate client code from the OpenAPI specification and run strict response validation, and those whose permission-governance tooling reads the personal-permissions query.

Required Actions

  • Confirm against the CIRFMF/ksef-api releases page and the api-changelog.md file, not a vendor summary, which version and rollout date applies to each environment.

  • Re-generate or re-validate OpenAPI-derived client stubs against version 2.9.0, in particular any model for the personal-permissions query response, so the new owner-permissions content does not break strict deserialization.

  • If your system uses the personal-permissions query, decide how owner permissions should be displayed or logged, and test against the DEMO environment.

  • Ensure error handling treats code 21001 (unreadable content) as a documented, non-retryable request-content error.

Practical Implications

Taken alone, release 2.9.0 is minor. Its significance is cadence: five numbered releases (2.7.0 to 2.9.0) have reached the environments in about three months, and the TEST and DEMO deployment preceded production by only two days. A change window this short leaves little time to validate after publication, which is why a standing monitoring routine for the release channel is more valuable than any single release note.

For groups running SAP-integrated e-invoicing, the practical step is to keep the generated API client under version control, pin it to a named specification version, and run an automated contract check against DEMO whenever CIRF publishes a new tag.

Verification note: the rollout dates and the two changes above were read from the api-changelog.md entry and the ksef-api release page. KGT has not independently confirmed from an official source that the 15 October 2026 production deployment completed as scheduled; that remains an open item.

Expected Next Steps

KGT will continue to monitor the ksef-api and ksef-docs repositories for the next numbered release and for any corrective build, and for official Ministry of Finance communication on further KSeF 2.0 functionality ahead of the January 2027 taxpayer wave and the end of the penalty deferral.

How Can KGT Support You?

KGT delivers SAP-integrated electronic invoicing and statutory reporting for Poland. Our SAP add-on for KSeF produces the FA(3) structured invoice from SAP billing data, manages authentication and session handling against the live KSeF 2.0 API, and reconciles the KSeF acknowledgement back to the SAP document, built and tested against the API version actually deployed in production.

For clients running SAP Document and Reporting Compliance (SAP DRC), we support scoping, configuration, country activation, credential governance, and a standing process for tracking KSeF API releases against the CIRF repositories, so that a release such as 2.9.0 is caught and validated before it affects a production integration.

This country update is provided for general information only and does not constitute tax, legal or professional advice. Actual completion of the 15 October 2026 production deployment was not independently confirmed at the time of writing.

Country update for Poland
20 October 2026
Poland
Stay informed about the latest indirect tax developments in Poland, including regulatory changes, compliance requirements, and indirect tax guidance affecting businesses operating locally and cross-border. This page provides a structured overview of country-specific updates, such as new legislation, reporting obligations, digital tax initiatives, and implementation timelines.
These insights help tax, finance, and compliance professionals anticipate regulatory changes, adjust processes and systems, and maintain compliant operations in Poland.