When Does a POS Software Update Require New ESIR Approval?

Serbia does not require new ESIR approval merely because a retailer’s POS build number changes. Re-approval is required when the approved Serbian ESIR is affected, particularly where its functionality, fiscalization process or Fiscal Receipt output changes. 

For retailers and POS providers operating one software platform across several countries, version management raises a practical question: does every change to the global POS release require a new Serbian ESIR approval? Based on the Serbian approval rules and the clarification provided by the Tax Administration team responsible for ESIR approvals, the answer is No.

This is not a new fiscalization requirement, but a clarification of how the existing approval framework applies when a wider POS platform changes while the approved Serbian fiscal functionality remains unchanged. Under the Law on Fiscalization, an Electronic Fiscal Device consists of an approved PFR and one or more approved Electronic Systems for Issuing Receipts (ESIR), together with the security element. Retailers must use approved elements, while suppliers may provide only elements whose use has been approved by the Tax Administration.

What changes require a new ESIR approval?

Article 9 of the Regulation governing Electronic Fiscal Device elements establishes the general rule: where a change affects an EFU element whose use has already been approved, the supplier must submit a new approval request for each element affected by the change.

The Tax Administration’s Technical Instruction provides a more practical test. Section 7.9 states that changes to an approved product that change its functionality or the appearance of issued receipts must be reported through the supplier development environment. In such a case, the applicant submits a new technical-review application, updates the relevant hardware and/or software version and goes through the approval procedure again. The same instruction expressly states that each new version affecting the appearance of the Fiscal Receipt requires new approval.

There is no published exhaustive list covering every possible software modification. Based on the rules and the Tax Administration clarification provided for this case, new approval should therefore be expected where an update affects, for example, Serbian Fiscal Receipt generation or appearance, fiscal data sent for fiscalization, fiscal calculation or transaction logic, the handling of sales, refunds or advances, ESIR-to-PFR communication that affects fiscalization, or introduces new Serbian fiscal functionality.

The Tax Administration may also verify whether the ESIR actually used by a taxpayer corresponds to the approved model. Its Technical Instruction states that approval may be revoked if the deployed product does not have the same functions relevant to fiscalization as the approved model, or if the supplier fails to adapt the solution following changes to legislation, bylaws or the applicable Tax Administration instruction.

Why does e.g. a global POS version change not automatically require re-approval?

The relevant question is what changed in the approved Serbian ESIR, rather than whether the enterprise-wide POS release number changed.

A global software version may cover the operating system, technical components, POS application and functionality for several jurisdictions. An update introduced for another country may therefore increase the global software version without changing the Serbian ESIR or any Serbian fiscalization functionality.

The Tax Administration approval-team clarification provided for this scenario confirms that a change limited to non-fiscal elements does not automatically require new Serbian approval. The same applies to functionality developed for another jurisdiction, provided it genuinely does not affect the approved Serbian ESIR.

This distinction does not mean that software versioning is irrelevant. The Technical Instruction requires a software-based ESIR to make information about the manufacturer, serial number and software version easily accessible. The Tax Administration’s public Register of Approved EFU Elements also contains separate fields for the Version and EFU Element ID of the approved product.

The practical distinction is therefore between the wider global POS software version and the identification/version of the approved Serbian ESIR. They do not have to follow the same release numbering merely because the Serbian fiscal functionality forms part of a larger global software stack.

What must remain consistent on the Fiscal Receipt?

The ESIR identification used for fiscalization should remain linked to the approved Serbian ESIR rather than automatically following every global POS release.

The Tax Administration’s Technical Instruction requires the Fiscal Receipt to display an ESIR number representing the EFU Element ID/software version of the approved ESIR, and this applies across receipt and transaction types.

According to the Tax Administration clarification provided for this case, the ESIR number used for a particular approved ESIR should therefore remain consistent on the printed Fiscal Receipt and the corresponding records in the Fiscalization Management System and journal. A new global release number caused by unrelated changes is not, by itself, a reason to change that approved ESIR identification.

Impact on retailers and POS providers

For international retailers, this allows the global software lifecycle and the Serbian ESIR approval lifecycle to be managed separately.

For POS providers, however, this requires controlled release management. Calling an update “non-fiscal” internally is not enough; its actual effect on the approved ESIR, Fiscal Receipt, transaction logic and PFR integration should be assessed. The approved solution used in production must continue to correspond to the product that passed the Tax Administration’s approval process. The Technical Instruction requires suppliers to maintain approved ESIR and L-PFR products in accordance with fiscalization rules and allows the Tax Administration to check the identity of the product in use against the approved element.

What should retailers and POS providers do?

A new approval request must be submitted where a change affects the approved EFU element in a manner covered by the approval rules, including changes to ESIR functionality or Fiscal Receipt appearance.

Also, retailers and software providers should maintain change-control documentation showing whether each software release affects the Serbian ESIR, particularly receipt generation, fiscal data, transaction processing, PFR communication and approved functionality. Global (international) POS versioning and Serbian ESIR versioning may be managed separately, provided the approved ESIR remains clearly identifiable and the version and identification used for Serbian fiscalization remain consistent with the approved solution.

For a retailer and his software provider, the difficult question is therefore not whether a build number changed, but whether the approved fiscal product changed.  

I would say that the main compliance risk is not the change of the global POS version itself, but losing a clear link between the software running in production and the ESIR version approved by the Serbian Tax Administration, and additionally not noting the changes that do in fact affect the fiscalization portion of the software and could lead to non-compliance if not further checked and/or re-certified.

The public regulatory basis includes the Serbian Law on Fiscalization Zakon o fiskalizaciji | Republika Srbija | Paragraf Lex, Article 9 of the Regulation governing approval of Electronic Fiscal Device elements Uredba o obliku i sadržaju registra elemenata i vrstama elektronskih fiskalnih uređaja , and the Tax Administration’s Technical Instruction for the administrative and technical review of ESIR and L-PFR functionality Tehnickouputstvo-ESIRiliL-PFR.pdf. The approved ESIR version and EFU Element ID can also be verified in the Tax Administration’s public register. Additonally, Tax authorities’ technical certification team has confirmed further on the application of these rules.

Tara Nedeljković, Team Lead of Legal Consultants at Fiscal Solutions

Linkedin profile