Serbia: SEF Update 4.1.1 Reaches the Production Environment One Day After Demo

Country Update — Serbia  |  25 August 2026  |  Topic: E-Invoicing / Platform Release

On August 21, 2026, the Ministry of Finance of the Republic of Serbia announced that update 4.1.1 of the Sistem elektronskih faktura (SEF) had been made available in the production environment. The same update had been published to the demo environment only one day earlier, on August 20, 2026. The Ministry describes 4.1.1 as an ispravka — a corrective release — to version 4.1.0, which itself went to demo on July 31, 2026, and to production on August 2, 2026.

Background

SEF is Serbia's mandatory continuous transaction control platform. Under the Law on Electronic Invoicing (Zakon o elektronskom fakturisanju), every domestic B2G, G2B and B2B invoice must be issued, transmitted and received through SEF, and VAT recording obligations — including electronic recording of VAT calculation and of input VAT — are discharged through the same platform. There is no compliant channel outside it.

The Ministry of Finance maintains SEF on a rolling release cadence. Each update is first published to the demo environment, then to production, with a release-note PDF attached to the announcement and a running list maintained on the portal's “SEF ažuriranja i verzije” page.

The pace over the last eight weeks has been unusually high: the Interno tehničko uputstvo was reissued on July 31, 2026; the preliminary VAT return appeared on demo SEF on the same day; an amending Rulebook on Electronic Invoicing (Pravilnik o izmenama i dopunama PEF) was adopted on August 1, 2026; and version 4.1.0 followed on August 2, 2026. Version 4.1.1 is the fourth material platform event in three weeks.

The Change

This is a technical release, not a legislative one. It operates entirely within the existing framework of the Law on Electronic Invoicing and the Rulebook on Electronic Invoicing, and it does not alter any statutory obligation, deadline, or threshold.

It is nonetheless binding in practice. SEF is the only lawful transmission channel, so the behavior of the production platform defines what a compliant invoice is on any given day. A corrective release changes what the platform accepts, rejects or renders, and that takes effect for every taxpayer at the moment of deployment — without a transition period, and enforced by rejection rather than by penalty.

Scope

The update applies to the production environment of SEF at efaktura.mfin.gov.rs, and therefore to all users of the system: taxpayers issuing and receiving electronic invoices, public-sector users, information intermediaries (informacioni posrednici) holding Ministry approval, and any ERP or middleware connected through the SEF application programming interface.

The functional detail of the release is set out in the release-note document “SEF detalji nove ispravke 4.1.1” (131.95 KB), published as an attachment to the August 21 announcement and, in a slightly larger version, to the August 20 demo announcement.

That attachment could not be retrieved for this article — attachments served from the efaktura.gov.rs /extfile/ path are not machine-retrievable — so the specific functional changes carried by 4.1.1 remain provisional until the release note is read. Readers should download it directly from the announcement page or obtain it from their information intermediary.

One point can be confirmed negatively: as at August 25, 2026 the Interno tehničko uputstvo published on the portal remains the version of July 31, 2026. The internal technical instruction was not reissued alongside 4.1.1, which suggests the release does not change the documented interface contract — but this is an inference from the absence of a reissue, not a statement by the Ministry.

Timeline

• July 31, 2026 — SEF 4.1.0 published to the demo environment; Interno tehničko uputstvo reissued; preliminary VAT return made available on demo SEF.
• August 1, 2026 — amending Rulebook on Electronic Invoicing adopted.
• August 2, 2026 — SEF 4.1.0 published to the production environment.
• August 20, 2026 — SEF 4.1.1 published to the demo environment, with release notes.
• August 21, 2026 — SEF 4.1.1 published to the production environment, with release notes.

Businesses Affected

All entities transacting through SEF are affected, but the operational burden falls unevenly. Businesses that integrate directly with the SEF API — typically larger taxpayers running SAP or another ERP with a certified connector — carry the regression-testing obligation themselves. Businesses that operate through an information intermediary depend on that intermediary having absorbed the change, and should not assume silence means readiness.

Foreign-headquartered groups with Serbian entities are the most exposed. A one-day gap between demo and production leaves no room for a change-advisory cycle in a global IT organization, and Serbian releases rarely feature on a group-level release calendar.

Required Actions

• Download “SEF detalji nove ispravke 4.1.1” from the August 21 announcement and read it against your current interface build before assuming no impact.
• Confirm with your information intermediary or platform provider, in writing, that 4.1.1 has been absorbed and on which date.
• Re-run your regression pack against production for the transaction types you actually issue — in particular any document type touched by the 4.1.0 release three weeks earlier, since a corrective release is by definition aimed at defects introduced or exposed by its predecessor.
• Verify that outbound and inbound processing, status polling and the retrieval of individual and collective VAT records still behave as expected.
• Check that you are building against the Interno tehničko uputstvo of July 31, 2026 and monitor the portal for a reissue.

Practical Implications

The interval between demo and production for 4.1.1 was one day. That is the practical planning assumption groups should now use for Serbian corrective releases: the demo environment exists, but it does not deliver a usable validation window. Organizations that require a formal change-approval step before touching a production interface need a standing pre-authorization for Serbian platform patches, or they will be permanently behind the platform.

There is also a documentation risk. Where a release is issued as a fix rather than as a functional version, the technical instruction is often not reissued, so the authoritative description of what changed lives only in a short release-note PDF attached to a news item. That document is easy to miss and is not versioned in the way a specification is. It should be captured into the group's compliance evidence file at the time of release, not reconstructed later.

Finally, the cadence itself is the signal. Four material platform or regulatory events in three weeks — rulebook amendment, technical instruction reissue, minor version and corrective release — indicates the Serbian system is being actively reworked ahead of the preliminary VAT return going live. Groups should budget for continued release traffic through the remainder of 2026 rather than treating each announcement as an exception.

Expected Next Steps

Further point releases in the 4.1.x line should be expected, followed by work associated with the preliminary VAT return (prethodna poreska prijava), which has been available on demo SEF since July 31, 2026 and has not yet been given a production date by the Ministry. A reissue of the Interno tehničko uputstvo would be the first reliable indication that the interface contract itself is moving.

How Can KGT Support You?

KGT is a specialist indirect tax technology firm working exclusively inside the SAP landscape. We deliver SAP-integrated e-invoicing add-ons for countries where a local mandate outpaces the standard SAP roadmap, and we implement and run SAP Document and Reporting Compliance (SAP DRC) where the standard solution is the right answer. Because we build and operate both, our advice on which route to take for a given country is not a sales position.

For the development described above, KGT typically helps clients in four ways: assessing the impact on the existing SAP configuration and interface build; carrying out the mapping and regression work against the current official specification version; managing the platform, provider or registration dependency; and running the resulting flows as a managed service, so that each release, schema version and validation change is absorbed for you rather than by you. 

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.