Serbia: Amended E-Invoicing Rulebook Published in Official Gazette 71/2026, a New Internal Technical Guideline, and the Preliminary Tax Return Appears on DEMO SEF

Country Update — Serbia  |  11 August 2026  |  Topic: E-Invoicing / VAT Reporting

On August 1, 2026 the Ministry of Finance of the Republic of Serbia announced that the Rulebook amending the Rulebook on Electronic Invoicing had been adopted and published in the Official Gazette of the Republic of Serbia No. 71/2026.

In the same ten-day window the Ministry, which operates the Sistem e-Faktura (SEF), published a new version of the Internal Technical Guideline dated July 31, 2026, deployed SEF version 4.0.0 to production on July 31 together with version 3.0.0 of the electronic recording of input tax module, moved SEF version 4.1.0 to DEMO on July 31 and to production on August 2, and made the system-generated Preliminary Tax Return available for testing on DEMO SEF.

Taken together these are the artifacts that determine whether a Serbian VAT registrant will still be transmitting successfully in September.

Background

Serbia has operated a mandatory clearance-style e-invoicing regime through SEF since 2022, and has since layered VAT record-keeping obligations on top of the invoicing layer.

The Rulebook on Electronic Invoicing (Pravilnik o elektronskom fakturisanju) is the instrument that carries the operational detail of that regime: the format and content of the electronic invoice, the individual and collective VAT records, the numbering conventions, and the procedures that apply when the system is unavailable. It is amended frequently.

The consolidated text on the Ministry’s own website still recites amendments through Official Gazette No. 30/2026 of March 27, 2026, which is itself an indication of how quickly the underlying instrument moves relative to the published consolidation.

Alongside the Rulebook sits the Internal Technical Guideline (Interno tehničko uputstvo), a separate, versioned document that specifies how the invoice and record schemas are to be populated and how the application programming interface behaves.

The Guideline is not a statutory instrument, but in practice it is the document against which a submission either validates or fails, and a new version of it can change integration behavior without any change in the law.

The third layer is the release cycle of the SEF platform itself, and of the companion module for electronic recording of input tax (elektronsko evidentiranje prethodnog poreza, EEPP). KGT reported on July 31, 2026 that the production deployment of SEF version 4.0.0 had been repeatedly postponed during the second half of July.

That deployment has now taken place, and has been followed within days by a further release.

The fourth and newest layer is the Preliminary Tax Return. Serbia has for some time signaled an intention to move from taxpayer-prepared VAT returns to returns pre-populated by the tax administration from data the administration already holds — invoices cleared through SEF and input tax recorded through EEPP.

The appearance of that return on the DEMO environment is the point at which the intention becomes something a taxpayer can inspect and reconcile against its own books.

The Legislative Change

One of the developments in this window is a legislative change in the strict sense and the remainder are technical. The Ministry of Finance announced on August 1, 2026, on the official SEF portal, that the Rulebook amending the Rulebook on Electronic Invoicing had been adopted and published in the Official Gazette of the Republic of Serbia No. 71/2026, and it attached the instrument to that announcement.

An important qualification applies to how far this can be reported: the Ministry’s announcement does not state the date of the gazette issue, and the attached instrument itself could not be retrieved, so the article-level content of the amendments cannot be verified on a primary source at the time of writing.

Commentary circulating in the market attributes to it revised treatment of advance-invoice corrections, clarified procedures for periods when SEF is unavailable, and the introduction of the Preliminary Tax Return, together with application dates of August 1, 2026 for most provisions and tax periods after December 31, 2026 for the return. None of that detail is confirmed in an official text this update was able to read, and readers should treat it as unconfirmed until the gazette text is obtained.

The remaining items operate entirely within the existing legal framework and change no rule of law. They are nonetheless binding in practice, because in a clearance architecture a document that fails validation is rejected rather than penalized, and a rejected document is not an invoice for VAT purposes. A schema or Guideline version therefore enforces itself at the moment of transmission, without any need for an assessment or a penalty notice.

The Internal Technical Guideline was reissued in a version dated July 31, 2026 and announced the same day. Any integration built against the previous version should be regression-tested against it, because the Guideline is where field-level population rules and interface behavior are specified.

On the platform side, SEF version 4.0.0 was deployed to production on July 31, 2026, after announcements on July 22, 24, 28 and 29 tracking successive slippage, with an accompanying notice of production unavailability during the deployment on July 29. Version 3.0.0 of the EEPP module went to production on the same day, July 31. SEF version 4.1.0 was then published to DEMO on July 31, 2026 and moved to production on August 2, 2026.

A minor version arriving two days after a major one, in production, is a pattern that warrants attention: it means the baseline against which a taxpayer tested in July was superseded twice inside a week.

Separately, and more consequentially for groups, the Ministry issued a guideline on July 24, 2026 on the numbering of VAT records for entities that share a tax identification number (PIB).

Where several SEF-registered entities operate under the same PIB, a unique number must be assigned to both the individual VAT record and the collective VAT record. Public-sector entities holding their own budget beneficiary identification number (JBKJS) must add that number as a prefix or suffix to differentiate record numbers within the shared PIB.

This is a numbering rule, but it has direct consequences for how a shared-PIB group configures document numbering in its source system.

Finally, the Preliminary Tax Return (Preliminarna poreska prijava) was made available on DEMO SEF and announced on July 31, 2026. The correct official name matters here, because the acronym “PPP PDV” has circulated in secondary commentary and appears on no official page; the Ministry’s own term is Preliminarna poreska prijava.

Scope

The Rulebook, the Internal Technical Guideline and the SEF release cycle apply to every entity registered on SEF. That includes VAT-registered businesses in the private sector, public-sector entities, and voluntary users. There is no size threshold and no exemption based on invoice volume.

The EEPP module and its version 3.0.0 release are relevant specifically to taxpayers discharging the obligation to record input tax electronically, which is the data set the Preliminary Tax Return will draw on for the deduction side.

The shared-PIB numbering guideline has a narrower but sharply defined scope: it applies only where more than one SEF-registered entity operates under a single PIB. In Serbia this arises most often in the public sector, where separate budget beneficiaries share a PIB, but it also arises in private-sector structures with multiple registered establishments.

The Preliminary Tax Return is currently available on DEMO only. It is a test-environment artifact at this stage, not a filing obligation, and nothing in the material this update was able to verify obliges a taxpayer to act on it yet. Its practical scope is that any taxpayer wishing to understand what the administration will pre-populate, and to identify in advance where its own figures will diverge, can now do so.

Timeline

• July 24, 2026 — Ministry of Finance guideline on the numbering of VAT records for entities sharing a tax identification number (PIB), including the JBKJS prefix or suffix rule for public-sector entities.
• July 22, 24, 28 and 29, 2026 — successive announcements on the postponed production deployment of SEF version 4.0.0, with a production unavailability notice on July 29.
• July 30, 2026 — publication of the recording of the webinar on integrating the e-Faktura system with the SEF Admin module, announced on July 28, 2026.
• July 31, 2026 — SEF version 4.0.0 deployed to production; EEPP version 3.0.0 deployed to production; SEF version 4.1.0 published to DEMO; new version of the Internal Technical Guideline dated July 31, 2026; Preliminary Tax Return made available on DEMO SEF. SEF performance degradation reported the same day.
• August 1, 2026 — Ministry of Finance announces adoption and publication of the Rulebook amending the Rulebook on Electronic Invoicing in Official Gazette of the Republic of Serbia No. 71/2026.
• August 2, 2026 — SEF version 4.1.0 deployed to production.
• August 3, 2026 — further SEF performance degradation reported.
• August 5, 2026 — degraded access via the electronic identification portal reported and subsequently restored.
• Tax periods after December 31, 2026 — reported, but not officially confirmed, as the point from which the Preliminary Tax Return would apply. Treat as unconfirmed.

Businesses Affected

Every business registered on SEF is affected by the platform releases and by the new Internal Technical Guideline, whether or not it has read them. Businesses that integrate with SEF through an application programming interface — which is the normal arrangement for anything above low volume — are affected most directly, because a change in the Guideline or in the platform version can alter validation behavior without any change in the taxpayer’s own configuration.

Multinationals with Serbian entities should note the compressed release cadence specifically. A test cycle completed against SEF 4.0.0 on DEMO in mid-July was validated against a baseline that was superseded in production on July 31 and again on August 2. Where testing is outsourced to a local provider, it is worth asking explicitly which version was tested and on which date.

Groups and public-sector bodies operating multiple SEF-registered entities under one PIB are affected by the July 24 numbering guideline and should confirm that their document numbering produces a unique number for each individual and collective VAT record within the shared PIB.

Taxpayers using the EEPP module for input tax recording are affected by the version 3.0.0 production release and, prospectively, by the Preliminary Tax Return, since the quality of the EEPP data will determine the quality of the pre-populated deduction figures.

Required Actions

• Obtain the text of the Rulebook as published in Official Gazette No. 71/2026 and have it reviewed against your current SEF configuration. Do not rely on secondary summaries of its content, several of which conflict.
• Download the Internal Technical Guideline version dated July 31, 2026 and perform a differential review against the version your integration was built to. Regression-test invoice issuance, credit and advance-invoice handling, and both individual and collective VAT records.
• Confirm which SEF version your integration was last tested against and retest against production behavior following the 4.1.0 deployment of August 2, 2026.
• Retest the EEPP interface against version 3.0.0 and reconcile recorded input tax against your general ledger and purchase VAT accounts.
• If any of your entities share a PIB, verify that VAT record numbering yields a unique number per record type per entity, and add the JBKJS prefix or suffix where the entity is a public-sector budget beneficiary.
• Access the Preliminary Tax Return on DEMO SEF and reconcile it, line by line, against your own VAT return for the same period. Identify and document every divergence now, while it carries no consequence.
• Review your outage procedures. The unavailability and performance-degradation notices of July 29, July 31, August 3 and August 5, 2026 are a reminder that invoice issuance in a clearance model depends on a platform you do not control, and that your process needs a defined queue-and-retry behavior and a defined position on the legal date of issue.

Practical Implications

The most useful way to read this cluster is as a single readiness question rather than five separate news items. Serbia is moving from a system in which the administration receives invoice data to a system in which the administration prepares the return.

The Preliminary Tax Return on DEMO is the visible edge of that shift, and it changes the nature of VAT compliance work in Serbia.

Where the taxpayer previously compiled and asserted a figure, the taxpayer will increasingly be reconciling and, where necessary, contesting a figure the administration has already computed from data the taxpayer itself supplied.

That makes upstream data quality the controlling variable. A misclassified transaction, a wrong VAT category, an advance invoice not correctly linked to its final invoice, or an input tax record omitted from EEPP will no longer merely produce a wrong return; it will produce a pre-populated return that disagrees with the taxpayer’s books, and the burden of explaining the difference will sit with the taxpayer. Reconciling the DEMO return now is materially cheaper than reconciling a live one later.

The release cadence carries its own implication. Two production releases in three days, a new technical guideline on the same day as a major deployment, and four availability incidents in a week describe a platform under active change close to a period end. Organizations should assume that the validation baseline will continue to move and should build regression testing into a recurring cycle rather than treating it as a project task that closes.

Finally, the difficulty of verifying the Rulebook text is itself a practical finding. The consolidated version on the Ministry’s website lags the gazette, and the attached instrument was not retrievable. Absence of a document on a ministry website is not evidence that the document does not exist, and organizations relying on a consolidated text should confirm the amendment history separately.

Expected Next Steps

The text of the amending Rulebook in Official Gazette No. 71/2026 should be expected to appear on the national legal information portal and, in due course, in the consolidated text on the Ministry’s own site. Until then the gazette issue itself is the authoritative source.

The Preliminary Tax Return should be expected to progress from DEMO to production, and eventually to a defined filing interaction, with the reported start point of tax periods after December 31, 2026 being the figure to watch for official confirmation. Businesses should expect further guidance on how a taxpayer accepts, amends or rejects a pre-populated return, because that procedure does not yet exist in published form.

Further SEF and EEPP releases should be expected, and on the evidence of July and August they may arrive with short notice. The Internal Technical Guideline should be expected to be reissued alongside them.

KGT will report separately when the gazette text of the amending Rulebook can be read and its article-level content confirmed, and when the Preliminary Tax Return moves beyond the DEMO environment.

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 (SEF portal), announcement of the adopted amending Rulebook published in Official Gazette RS No. 71/2026, August 1, 2026: View source
• Ministry of Finance (SEF portal), Rulebook amending the Rulebook on Electronic Invoicing, August 1, 2026: View source
• Ministry of Finance (SEF portal), updated Internal Technical Guideline, version of July 31, 2026: View source
• Ministry of Finance (SEF portal), Preliminary Tax Return on DEMO SEF, July 31, 2026: View source
• Ministry of Finance (SEF portal), guideline on VAT record numbers for entities sharing a PIB, July 24, 2026: View source
• Ministry of Finance (SEF portal), announcements index: View source
• Ministry of Finance of the Republic of Serbia, register of rulebooks: 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.