The Federation of Bosnia and Herzegovina has moved a long-discussed fiscalization overhaul from \u201ceventually\u201d to \u201cnow.\u201d In late January 2026, the Parliament\u2019s House of Peoples adopted the Law on Fiscalization of Transactions, and the Government simultaneously fine-tuned the proposal with amendments that clarify key concepts and raise the financial guarantee required for certified fiscal system manufacturers to 1 million KM.<\/p>\n\n\n\n
I\u2019m writing this article based on the webinar \u201cFiscalization Reform in the Federation of BiH\u201d<\/strong> delivered today (January 29, 2026)<\/strong> by Vuka\u0161in Santo<\/a><\/strong>, Fiscal Solutions<\/a>. The full webinar recording will be published on From \u201cfiscal device\u201d to \u201cfiscal software”, the direction will feel familiar: the Federation is stepping away from a hardware-centric model and toward a software-and-platform model where the tax authority can supervise transactions continuously. The legal backbone is explicit: the law centers on an Electronic System for Recording Transactions, in the legislation abbreviated as ESET, defined as a specialized software system that reliably records business transactions and reports them to the Tax Administration.<\/p>\n\n\n\n In practice, ESET is not your POS. That distinction matters technically and commercially. The webinar framed ESET as the \u201csystem layer\u201d that receives transaction data from POS\/ERP\/webshops, applies required security steps, communicates online with the tax authority\u2019s central platform, and supports archiving and evidence.<\/p>\n\n\n\n The cleanest way to understand the new model is as a chain of responsibility. There is a typical POS (or webshop\/e-commrece engine) and the ESET becomes the compliance engine. Inside ESET sits a Security Module (SM), which the law defines as a software component responsible for secure processing and protection of transaction data.<\/p>\n\n\n\n The Federation\u2019s concept is built around a central fiscalization platform operated by the tax authority, which verifies transactions and enables real-time oversight. The webinar emphasized a critical operational implication: transactions are expected to be authorized online, and stable internet connectivity becomes a compliance dependency, not an IT nice-to-have.<\/p>\n\n\n\n Modern fiscalization systems always have two audiences: the tax authority and the consumer. Bosnia\u2019s Federation is aligning with that logic. In the webinar, Santo explained that receipts will carry retailer authorization data, tax-authority verification data, and a mandatory QR code that allows verification of fiscalization. He also addressed the uncomfortable question every retailer asks: \u201cWhat if the connection is down?\u201d The session described an offline\/timeout scenario where a receipt can be issued with the retailer-side signature first and then reauthorized within 48 hours to obtain the authority\u2019s verification, with the QR code adapting when the authority code is missing at the moment of sale.<\/p>\n\n\n\n This is where architecture meets store reality: your queues, your network design, your retry logic, and your exception handling become part of your tax risk.<\/p>\n\n\n\n The reform also tightens transactional semantics, something POS teams often underestimate until late testing. The webinar highlighted that a sale receipt is meant to represent a positive-value sale only, while returns\/corrections are handled as separate negative-value documents linked to a prior sale. If a customer returns and buys something else, the operational expectation is two steps: a return document first, then a new sale receipt.<\/p>\n\n\n\n For retailers, this impacts the entire returns and \u201cexchange\u201d flow: customer service desks, omnichannel returns, and mixed baskets must be reviewed early, not after integration.<\/p>\n\n\n\n ESET is broader than receipts. The law describes ESET as software or a cloud solution that supports composing invoices\/receipts, signing them, communicating with the Tax Administration via the Security Module, and archiving transaction data. It can be installed on practically any device, computer, mobile phone, tablet, cash register, and similar endpoints.<\/p>\n\n\n\n It also formalizes three \u201cvariants\u201d: an ESET for fiscal receipts, an ESET for e-invoices, and a combined version for businesses that need both. This matters for retail groups that run B2C sales in stores and B2B\/B2G flows through ERP, because the compliance layer must span both, cleanly.<\/p>\n\n\n\n Self-service devices and automats (think vending and similar unattended endpoints) are explicitly carved out from what the law considers ESET, with the expectation that the Ministry will further define treatment through by-laws. The webinar echoed this, signaling that details are still pending during the transition period.<\/p>\n\n\n\n Retailers shouldn\u2019t treat \u201cexcluded\u201d as \u201cignored.\u201d Unattended endpoints have a habit of becoming the biggest compliance blind spot, precisely because they sit outside the store\u2019s core POS landscape.<\/p>\n\n\n\n One of the most commercially consequential aspects is how the Federation intends to control who can place compliant fiscal software on the market. In the webinar, Santo outlined conditions for registered manufacturers\/representatives, including a local presence hitered business activity, ISO-related requirements, and a significant bank guarantee, described as roughly 1 million KM (about half a million euros)<\/strong>, with status granted for five years and subject to renewal.<\/p>\n\n\n\n That direction is consistent with the Government\u2019s January 2026 statement that increased the guarantee for registered\/certified fiscal system manufacturers to one million KM, aimed at legal certainty and consistent application. (Vlada Federacije Bosne i Hercegovine<\/a>)<\/p>\n\n\n\n The webinar described the go-live expectation as an 18-month horizon after publication, with the current rules continuing until the new system begins.<\/p>\n\n\n\n For large retailers, the practical takeaway is simple: the critical path will not be coding alone. It will be registration flows, certificate\/security lifecycle, store connectivity standards, returns logic, and the readiness of the central platform and its technical documentation.<\/p>\n\n\n\n This reform is a classic example of where compliance becomes architecture. The Federation is effectively telling the market: fiscalization is no longer feature of the POS; it is an online system that must work across stores, e-commerce, and back office, with auditability built in.<\/p>\n\n\n\n If you treat this as a last-minute \u201cPOS change,\u201d you\u2019ll pay for it twice: once in rushed implementation, and again in operational exceptions. If you treat it as a compliance platform integration, where POS is a producer of transactions and ESET is the controlled compliance layer, you\u2019ll end up with something that is not only legal, but resilient.<\/p>\n\n\n\n Note:<\/strong> This article is based on the webinar \u201cFiscalization Reform in the Federation of BiH\u201d<\/strong> delivered on January 29, 2026<\/strong> by Vuka\u0161in Santo<\/a><\/strong>. The complete webinar is published at https:\/\/www.fiscal-requirements.com<\/a><\/code>.<\/p>\n\n\n\nHow the new architecture works<\/h3>\n\n\n\n
What changes at the receipt: signatures, verification, QR, and \u201coffline reality\u201d<\/h3>\n\n\n\n
Sales, returns, and the end of the \u201cexchange on one receipt\u201d<\/h3>\n\n\n\n
What\u2019s excluded now, and why it still matters<\/h3>\n\n\n\n
Vendor economics: the market will be regulated, not just the taxpayer<\/h3>\n\n\n\n
Timeline: \u201c18 months\u201d is the headline, but transitions are layered<\/h3>\n\n\n\n
The strategic point retailers should not miss<\/h3>\n\n\n\n
https:\/\/www.fiscal-requirements.com<\/code><\/a><\/p>\n\n\n\nSource<\/h2>\n\n\n\n