Poland: KSeF 2.0 API Release 2.7.0 Introduces Collective Identifiers, and the Tightened XML Validation Announced with Release 2.4.0 Took Effect on July 16, 2026

Country Update — Poland  |  11 August 2026  |  Topic: E-Invoicing / Technical Specifications

On July 21, 2026 the IT Centre of the Polish Ministry of Finance published release 2.7.0 of the KSeF 2.0 application programming interface to the test environment. The release introduces collective identifiers and a new permission to manage them, together with a test-data endpoint allowing the validity of a KSeF certificate to be shortened so that expiry can be simulated.

A matching version 2.7.0 of the official .NET client library followed on or about July 22, 2026. Separately, the tightened XML validation announced with release 2.4.0 took effect on July 16, 2026. All of this falls inside the transitional year in which Poland’s mandatory e-invoicing regime operates without sanctions, which makes it the last comfortable window in which to absorb interface change.

Background

Poland’s National e-Invoice System, KSeF, became mandatory in two waves in 2026. Taxpayers whose 2024 sales including value added tax exceeded 200 million zloty came into scope on February 1, 2026. All other taxpayers and invoice issuers came into scope on April 1, 2026. The obligation to receive invoices through KSeF applied to everyone from February 1, 2026. A third tier applies from January 1, 2027 to taxpayers whose monthly invoice-documented sales do not exceed 10,000 zloty gross, who may until then issue invoices outside KSeF.

The legal architecture sits in the Act of June 16, 2023, published at Journal of Laws 2023 item 1598, as deferred to February 1, 2026 by the Act of May 9, 2024 at Journal of Laws 2024 item 852, and as phased by the Act of August 5, 2025, published on September 1, 2025 at Journal of Laws 2025 item 1203.

The European authorization is Council Implementing Decision (EU) 2022/1003 of June 17, 2022. Three executing regulations complete the framework: Journal of Laws 2025 item 1815 on use of KSeF, item 1742 on cases in which there is no obligation to issue structured invoices, and item 1740 amending the invoicing regulation.

The 10,000 zloty relief deserves a precise statement because it is widely misdescribed. It is a statutory transitional provision, not a separate regulation.

The Ministry of Finance states that it runs to December 31, 2026, that the threshold is gross, and that it excludes business-to-consumer sales to natural persons, cash register sales, simplified invoices in the form of receipts bearing a tax identification number up to 450 zloty, and invoices excluded from KSeF under special provisions.

Critically, the Ministry also states that exceeding the limit brings the taxpayer into KSeF from the invoice that breached it, and that the loss of the relief is permanent — there is no return to the previous rules.

Against that legal backdrop sits a technical release cycle that has been unusually active. The binding invoice schema remains FA(3) version 1-0E, in force since February 1, 2026, with no FA(4). What has been moving is the interface, and it has been moving in ways that change taxpayer behavior.

The Legislative Change

There is no legislative change in this window. Both developments operate entirely within the existing legal framework, and it is worth saying plainly why they are nonetheless binding in practice. KSeF is a clearance system: an invoice acquires its legal identity when KSeF accepts it and assigns a KSeF number. A submission that fails validation is not a late invoice or a defective invoice; it is not an invoice at all. An interface release and a validation change therefore enforce themselves at the moment of transmission, without an assessment, a notice or a penalty.

Release 2.7.0 of the KSeF 2.0 application programming interface was published on July 21, 2026 at 15:19 by the IT Centre of the Ministry of Finance, in its official repository, tagged 2.7.0. Its substantive addition is collective identifiers, together with a new permission governing their management.

Collective identifiers allow a group of documents to be handled under a single identifier, which is directly relevant to high-volume issuers and to organizations that submit in batches rather than singly. The release also adds a test-data endpoint that allows the validity period of a KSeF certificate to be shortened, which exists specifically so that certificate expiry can be simulated in testing rather than discovered in production.

The deployment pattern of release 2.7.0 is itself the most important operational fact about it. It was deployed to the test environment on July 21, 2026 and deliberately held there for an extended period. Deployment to the demonstration and production environments had not been dated at the time of writing.

That is a departure from the pattern of earlier releases — release 2.6.1, for example, reached test on June 10, demonstration on June 11 and production on June 16, 2026 — and it signals that the Ministry expects collective identifiers to require a longer market testing cycle. Organizations should read the extended test period as an invitation rather than as a reason to defer.

A matching version 2.7.0 of the official .NET client library was published on or about July 22, 2026 as a package. The precise calendar date could not be confirmed, because the repository displays only a relative timestamp and no corresponding release tag was published; the releases page served a stale view showing version 2.6.0 of May 20, 2026.

Organizations pinning the client library by version should note the absence of a tagged release and verify the package version they have actually resolved.

The second development is a hard date rather than an artifact. The tightened XML validation announced with release 2.4.0 took effect on July 16, 2026.

This is the kind of change that is easy to under-weight: no new document was published on the day, and nothing in the law changed, but from that date submissions that previously passed may fail. Any organization that has not submitted a test document since mid-July has not established that its output still validates.

One data quality caveat should be recorded for anyone reading the Ministry’s own changelog. The application programming interface changelog states a test deployment date of July 21, 2027 for release 2.7.0. That is a typographical error in the official document; it contradicts both the release note and the repository timestamp, which agree on July 21, 2026.

Scope

The interface release and the validation tightening apply to every taxpayer that transmits to KSeF programmatically, which in practice means every taxpayer above trivial volume. Taxpayers using the Ministry’s taxpayer application rather than a direct integration are insulated from the interface change but not from validation behavior, since the application submits against the same rules.

Collective identifiers are of practical interest principally to high-volume issuers, to organizations submitting in batches, and to shared service centres transmitting on behalf of multiple entities.

The associated permission means that the ability to manage collective identifiers must be granted deliberately, which brings it within the scope of authorization design and segregation of duties rather than being a purely technical setting.

The certificate-validity test endpoint is relevant to every integrated taxpayer, because KSeF certificates expire and an expired certificate stops transmission. Until now, expiry behavior could not readily be rehearsed. It now can, and that rehearsal belongs in any organization’s business continuity testing.

The 10,000 zloty tier is relevant to the smallest taxpayers only, but it is relevant to larger businesses indirectly, because a supplier operating under the relief may legitimately be issuing invoices outside KSeF until December 31, 2026, and a buyer’s process needs to accommodate that without treating the invoice as defective.

No new version of the invoice schema was published in this window. The binding schema remains FA(3) version 1-0E, and organizations should not expect the interface releases to imply a schema change.

Timeline

• June 17, 2022 — Council Implementing Decision (EU) 2022/1003 authorizes the Polish measure.
• June 16, 2023 — the founding Act published at Journal of Laws 2023 item 1598.
• August 5, 2025 — the phasing Act adopted; published September 1, 2025 at Journal of Laws 2025 item 1203, introducing the transitional relief for monthly sales up to 10,000 zloty gross.
• February 1, 2026 — KSeF becomes mandatory for taxpayers whose 2024 sales including value added tax exceeded 200 million zloty; the reception obligation applies to all taxpayers; the FA(3) version 1-0E schema takes effect.
• April 1, 2026 — KSeF becomes mandatory for all other taxpayers and invoice issuers.
• June 10 to 16, 2026 — application programming interface release 2.6.1 deployed to test, demonstration and production.
• July 16, 2026 — the tightened XML validation announced with release 2.4.0 takes effect.
• July 21, 2026 — release 2.7.0 of the KSeF 2.0 application programming interface deployed to the test environment, introducing collective identifiers, the associated management permission, and the certificate-validity test endpoint. Deployment to demonstration and production not yet dated.
• On or about July 22, 2026 — version 2.7.0 of the official .NET client library published as a package; exact date not confirmed and no corresponding release tag published.
• December 31, 2026 — end of the transitional year without sanctions, and end of the relief for monthly sales up to 10,000 zloty gross.
• January 1, 2027 — the remaining tier of taxpayers comes into scope.

Businesses Affected

Every taxpayer with a direct KSeF integration is affected by the July 16, 2026 validation tightening, whether or not it has noticed. This is the single item in this update with the widest reach and the least visibility, because it produced no artifact on the day it took effect.

High-volume issuers and organizations submitting in batches are affected by collective identifiers, and should be participating in the extended test cycle rather than waiting for the production deployment date to be announced. The deliberate decision to hold the release on test for an extended period is a strong signal that the Ministry expects issues to surface.

Organizations using the official .NET client library are affected by the untagged 2.7.0 release and by the stale releases view, and should verify the resolved package version directly rather than relying on the repository’s release listing.

Buyers with Polish supplier populations that include very small businesses are affected indirectly by the 10,000 zloty relief through to December 31, 2026, and should ensure that accounts payable does not reject a legitimately non-KSeF invoice from a supplier operating under the relief.

Shared service centres and organizations with delegated authorization models are affected by the new collective identifier management permission, which needs to be assigned deliberately and reflected in access reviews.

Required Actions

• Submit a test document to KSeF now, if you have not done so since mid-July 2026, and confirm that your output still validates following the tightening that took effect on July 16, 2026. This is the highest-value and lowest-cost action in this update.
• Review release 2.7.0 in the official repository and assess whether collective identifiers change your submission design. If you submit in batches or at high volume, they probably do.
• Participate in the extended test cycle for release 2.7.0 rather than waiting for the production deployment date. The extended test period exists because the Ministry expects the market to find problems in it.
• Use the new certificate-validity test endpoint to rehearse KSeF certificate expiry in a controlled environment, and confirm that your monitoring detects an approaching expiry before transmission stops.
• Add the collective identifier management permission to your KSeF authorization design and to your periodic access review. A permission that can group documents under one identifier warrants the same control attention as any other privileged capability.
• If you use the official .NET client library, verify the package version actually resolved in your build, and do not rely on the repository releases listing, which was serving a stale view.
• Confirm that your invoice schema remains FA(3) version 1-0E and resist the temptation to read the interface releases as implying a schema change.
• Use the remainder of 2026 deliberately. The transitional year runs to December 31, 2026 without sanctions. Rejections observed and corrected now cost nothing; the same rejections in 2027 will.
• On the buy side, confirm that accounts payable can accept an invoice issued outside KSeF by a supplier operating under the 10,000 zloty relief through December 31, 2026, and that it does not treat such an invoice as non-compliant.

Practical Implications

The through-line in this window is that Poland’s KSeF risk has moved from legal to operational. The statute is settled, the schema is settled, the dates are settled. What is not settled is the interface, and the interface is what determines whether an invoice exists.

An organization can be entirely compliant in its legal analysis and entirely unable to invoice, and in a clearance regime the second problem is the one that stops the business.

The July 16 validation tightening illustrates the specific failure mode. It arrived as an effective date attached to a release announced earlier, produced no publication of its own, and changes outcomes for submissions that previously succeeded.

Organizations that monitor legislative gazettes and authority news pages will not have seen it. Organizations that monitor the repository and re-run a validation test on a schedule will.

Collective identifiers are the more interesting change strategically. They are the Ministry’s acknowledgment that document-by-document clearance is awkward at scale, and their introduction inside the transitional year is well timed.

For an organization submitting large volumes from SAP or another enterprise system, they may materially simplify the submission and reconciliation model — but only if the design decision is taken now, while the release sits on test and while errors carry no sanction.

The certificate-validity test endpoint deserves more attention than its modest description suggests. Certificate expiry is among the most common causes of sudden, total transmission failure in clearance regimes, and it is among the least frequently rehearsed. A facility that lets an organization observe its own failure behavior on demand is a business continuity tool, and it should be used as one.

Finally, the small errors in the official material — the 2027 date in the changelog, the stale releases view, the untagged client release — are a reminder that even a well-run authority repository needs to be read critically. Organizations should verify version facts against more than one location in the official material before making a build decision.

Expected Next Steps

Deployment dates for release 2.7.0 to the demonstration and production environments should be expected to be announced, and organizations should watch the official repository rather than the Ministry’s news pages, which have lagged the repository throughout 2026.

Further releases of the application programming interface and of the client libraries should be expected. On the 2026 record the cadence has been roughly monthly, and each release has arrived on test first.

Guidance and further frequently asked questions on collective identifiers should be expected as market testing progresses, since the concept is new and its interaction with correction and cancellation flows is not yet documented.

The end of the transitional year on December 31, 2026 should be expected to be preceded by Ministry communication on the transition to a sanctioned regime, and organizations should expect scrutiny of rejection rates to increase from January 2027.

No FA(4) schema has been announced, and organizations should not plan for one on present information. KGT will report separately if that changes, and on the production deployment of release 2.7.0.

How Can KGT Support You?

KGT is a specialist indirect tax technology firm. Our SAP-integrated e-invoicing and e-reporting add-ons generate, validate and transmit country-compliant structured documents directly from SAP ECC and SAP S/4HANA, keeping tax determination, document mapping, status handling and the audit trail inside the system of record rather than in a downstream converter. Because the add-ons validate against the current national schemas, schematrons and code lists before transmission, a change of specification version becomes a configuration and regression-test exercise rather than a redesign.

We also deliver SAP Document and Reporting Compliance (DRC) services end to end: fit-gap assessment against the national mandate, activation and configuration of the relevant country versions, eDocument and eStatement setup, interface and connectivity design, master and transactional data remediation, test strategy including negative testing against the authority’s own validation artifacts, and post-go-live monitoring of rejections and status reconciliation. If you would like a readiness review against the developments described above, or an impact assessment for your SAP landscape, we would be glad to help.

Official sources

• Ministry of Finance IT Centre, official KSeF application programming interface repository and releases (release 2.7.0, July 21, 2026): View source
• Ministry of Finance IT Centre, KSeF application programming interface changelog: View source
• Ministry of Finance IT Centre, official KSeF .NET client library package versions: View source
• Ministry of Finance, KSeF 2.0 legal basis and key dates: View source
• Ministry of Finance, KSeF information for sole traders and small and medium-sized enterprises: View source
• Ministry of Finance, what to know before the start of the second stage of KSeF implementation, March 31, 2026: View source
• Ministry of Finance, second stage of KSeF implementation, March 26, 2026: View source
• Journal of Laws 2025 item 1203, Act of August 5, 2025 amending the value added tax legislation: View source
• Council Implementing Decision (EU) 2022/1003 of 17 June 2022, EUR-Lex: View source

This publication is provided for general informational purposes only and does not constitute tax, legal, or professional advice. Please consult your advisor before acting on any information contained in this update.