Fiscalization can be defined as a set of legal and technical rules used to track fiscal records, control transaction data, and support the correct calculation and collection of taxes. While national systems differ, they normally define which taxpayers are covered, what fiscal documents may be issued, how transaction data must be recorded and stored, and whether information must be communicated to the tax authority.
Fiscalization can be grouped into four major models: hardware-based, software-based, combined hardware and software, and online fiscalization. The main difference is where fiscal control takes place and how transaction information is protected, stored, and reported. In every model, tax information is part of the fiscal transaction record and must remain consistent with the receipt and related POS data.
Common requirements across fiscalization models
Fiscalization strengthens control over retail turnover and reduces opportunities to manipulate transaction data. Rules commonly address receipt issuance, mandatory elements, transaction recording, storage, communication with authorities, and audits.
VAT or GST information is part of the transaction record. Depending on the model, it may be processed by a fiscal device or POS application, stored locally or in the cloud, transmitted to the tax authority, and forwarded to accounting systems. Fiscal records may also cover other tax treatments, including excise duties, exemptions, and specific foreign-customer transactions.
Hardware-based fiscalization
Hardware fiscalization relies on an officially approved fiscal device, such as an electronic cash register or fiscal printer. The POS provides fiscal data to the device, which processes the information according to legally defined rules. If the fiscal device prints the receipt, its firmware can determine the layout, mandatory elements, order of information, and other technical limitations.
Fiscal data are typically stored in tamper-resistant fiscal memory or a fiscal journal. Some hardware systems also send information to the tax authority, although not necessarily in real time. VAT calculation and reporting must match between the fiscal device, the POS system, and, where applicable, the data available to the authority.
Important requirements usually include device homologation, registration before sales begin, maintenance, authorized servicing, and defined reporting rules. Because many functions are device-controlled, this model is generally less flexible.
Software-based fiscalization
Software fiscalization moves the main compliance function into the POS application. Dedicated fiscal hardware is generally not required, but the software may need official certification covering areas such as data processing, security, digital signing, transaction chaining, access, and journaling.
Fiscal data are primarily stored by the retailer, while local rules may define the journal format, export format, and storage period. Where online reporting is included, data may also be stored by the tax authority. VAT calculation and reporting must remain consistent with the fiscal records.
This model can support standard POS, mobile POS, online shops, self-checkout, and vending machines. Receipt layouts are more flexible, although retailers must use the certified software version and follow local storage and reporting requirements.
Combined hardware and software fiscalization
Combined fiscalization uses both defined hardware and mandatory software functions. The POS supplies transaction data to a fiscal device or predefined service, while digital signing, transaction chaining, fiscal memory, a fiscal journal, or cloud storage may protect data integrity.
Fiscal information is normally stored in the device or cloud and also in the POS system. The registered transaction and printed receipt must match, including the VAT calculation. Depending on the country, direct communication with the tax authority may not be required, but fiscal-data exports can still be mandatory for reporting or audits.
This model offers more flexibility than traditional hardware-only fiscalization while retaining requirements for approved devices or services, registration, and specific security mechanisms.
Online fiscalization
Online fiscalization generally places the tax authority directly in the transaction flow. It commonly uses two-way communication based on a request-response model: fiscal information is digitally signed and transmitted online, and the authority returns an authorization or validation response linked to the transaction.
Fiscal data are stored at the tax authority, allowing remote access to reported information. Communication can be direct and real-time, and receipts may include security or authorization codes. Online models usually do not require dedicated fiscal equipment.
Connectivity is a key operational issue. Rules commonly define how receipts are issued during offline periods, how transactions are stored, and when they must later be transmitted or reauthorized. VAT calculation and reporting must still match the fiscal transaction data.
Conclusion
The four fiscalization models use different technologies but pursue the same objective: reliable recording of retail transactions and stronger control over tax information. Hardware systems place control in approved devices, software systems in certified applications, combined models distribute it across hardware and software, and online systems connect the transaction directly with the tax authority.
For retailers, the essential questions are where fiscal data are processed and stored, whether transactions must be transmitted to the authority, what certification or registration is required, and how VAT information must be reflected in the fiscal record.
