Architectures of Electronic Recording Systems (ERS)

The definition of "electronic recording system" is not always easy. This article attempts to approach the subject.

Architectural requirements that exist in countries with fiscalisation laws and regulations are disregarded in this article. For a legal clarification of whether your system architecture complies with the relevant fiscalization regulations of the corresponding country, please contact your tax advisor in the respective country.

Also disregarded are any requirements regarding local (fiscal) hardware (fiscal printer, hardware TSE, etc.).

In the following, the term "POS software" is used synonymously for all types of software systems that are used to process transactions in the exchange of services between businesses and consumers (or businesses among themselves).

Stand-alone systems

Definition:

We define a stand-alone system as :

• a logical unit running the POS software, and
• which can process (sales) transactions independently of other systems.
• Stand-alone systems usually have their own number ranges for documents.
• Such systems usually consist of
  
  • Cash register PC, tablet, or other mobile devices, which can work independently,
  • Receipt printer (or other device to issue transaction receipts),
  • monitor (for the cashier),
  • nd other components (bar code scanner, customer display, etc.).

Examples of Stand-alone systems:

• Supermarket cash register,
• cash register at the artisan's shop,
• Cash register in hairdresser's shop,
• E-charging station for electric cars,
• self-service payment terminals at petrol stations,
• self-service payment terminals in a parking garage, etc.

Several stand-alone or individual cash register systems can be operated independently of each other in the same network.

Fig. 1. Stand-alone system / Single cash register system

To ensure the autonomy and independence of the single till / stand-alone system, the RetailForce Fiscal Middleware is also installed directly on it (see Fig. 1.).

Central systems with input devices

Definition:

In central systems:

• the POS software is executed on a central system (host system).
• The central system makes the functions of the POS software available to other units (input devices) which connect to the host system via the local network or via the Internet.
• The central system manages the document number ranges (either one number range - also separated per document type - for all input stations, or separated according to input devices).

Real input devices are not offline-capable. This means, they need a standing connection to the host to be able to carry out transactions.

Examples of central systems with input devices:

• Restaurant cash register with mobile ordering terminals / devices,
• store server / main cash register with connected cash register workstations / terminals,
• Cash register system in data centre with thin clients in the branches / stores,
• Cloud POS systems with web app or web browser access, etc.

Fig. 2. Central system with input devices

Fig. 3. Cloud cash register system with input devices

For central systems, the RetailForce Fiscal Middleware is ideally installed in the host system. However, it can also be installed on another system on the same network, in the same data centre or in the cloud (see Fig. 2. and Fig. 3.).

Central systems - offline capable

Definition:

If, in a central system, the connected terminals / devices are offline-capable and can work and process transactions, albeit in a limited way, without being connected to the central system, it is no longer an input device. In these systems, an application / a component of the EAS runs on the connected devices.

Examples of central systems - offline-capable:

• Branch server / main cash register with connected cash register workstations / terminals
• Cash register system in data centre with fat clients in the branches,
• Cloud POS systems with app installed locally on the device

Fig. 4. Central system (server) - offline capable

Fig. 5 Cloud cash register system - offline capable

For offline-capable central systems, the RetailForce Fiscal Middleware is ideally installed in each connected device (see Fig. 4. and Fig. 5.).

Further information

Installation and Integration variants

System architectures incl. TSE