Fiscal Registrar for Torgsoft: Compatibility, Models, and Setup

A fiscal registrar for Torgsoft must be selected based on the exact model, connection profile, checkout operating scheme, and method of access to the database. The current Torgsoft list includes several integration options for the same equipment families: ArtSoft Universal, Atlas, Resonance, and separate Exellio and Help Micro profiles. The manufacturer name alone is not sufficient to verify compatibility.

To operate a hardware RRO in Torgsoft, the additional option «Integration with a fiscal registrar» is used with a 1-year license. The cashier processes the sale in Torgsoft. The program sends the current transaction data to the registrar; the device prints a fiscal receipt. From the Torgsoft interface, the cashier or responsible employee can print X and Z reports, cancel the current receipt in case of a printing error, and perform cash deposits and withdrawals.

If a hardware RRO has not yet been purchased, the entrepreneur should first determine the fiscalization format. Torgsoft also supports the separate «Software RRO» option. The selected format determines the checkout equipment configuration, workstation setup, and subsequent maintenance.

What to check before purchasing a fiscal registrar

Compatibility must be checked before installing the checkout system. Five parameters are important for this.

1. Exact model and modification. Different connection profiles may be used within the same series. Use the full device name.
2. Integration profile. Torgsoft works with registrars through ArtSoft Universal, Atlas, Resonance, and separate manufacturer profiles. The required option depends on the model.
3. Workstation architecture. Determine in advance where Torgsoft operates: on a local computer, in a local network, through a remote server, or in Torgsoft-Hybrid.
4. Connection method. Different profiles use their own interfaces, including COM and TCP/IP. The availability of a specific interface must be checked for the selected model.
5. Complete checkout scenario. Before launch, test sales, returns, X reports, Z reports, cash deposits, and cash withdrawals. If the checkout system works with a bank terminal or customer display, test these operations as well.

Which fiscal registrars are supported by Torgsoft

The current Help documentation includes Datecs, Exellio, Maria, Help Micro, Mini, IKS models, and other equipment. For an entrepreneur, it is important to consider the specific profile through which Torgsoft works with the device.

Datecs

For Datecs, Torgsoft provides the ArtSoft Universal and Atlas profiles. Through ArtSoft, the current list includes FP3530T, FP-3141T, FP-3530T, FP-T260, FP-T88, FP-320, FP-101, FP-7197, CMP-10, and Datecs CMP 10M.

The separate Atlas profile includes FP-101 Smart, FP-T88, FP-320, FP-510, FP-7197, FP-T260, FP-3530T, and CMP-10M. One model may be present in several profiles, so the administrator must select the configuration according to the actual equipment and the checkout connection method.

Exellio

Torgsoft has a separate Exellio profile for FPU-260, Exellio FPP 350, FPU-550, Exellio FP 700, FP-2000, and LP-1000. Some Exellio models are also present in the ArtSoft Universal profile.

For the separate Exellio profile, Help contains an important condition for remote operation: for stable registrar operation, the user's RDP session must be terminated. If Torgsoft runs on a remote server, this feature must be taken into account when organizing the cashier's work.

The FPU-550ES and FP-280 models from older lists are not confirmed under these names in the current main-program list. If such equipment is already installed in the store, the exact device modification must be checked before reconfiguring the checkout system.

Maria

Maria-301MTM, 304T, 304T1, and 304T2 are listed in the current Help documentation under the ArtSoft Universal profile. For Maria-301MTM T7–T11 and Maria-M304, the Resonance profile is used.

Therefore, for Maria-304T, 304T1, and 304T2, the current ArtSoft configuration should be used. Older information about a separate direct connection for these models is not suitable for selecting a modern configuration.

Help Micro and the MG series

The current list includes a separate Help Micro profile for MG N707TS, MG-T808TL, MG-P777TL, and other models. For some equipment, an ArtSoft Universal profile with TCP/IP connection is provided: MG N707TS, P777TL, T787TL, and FR90.XM.

MG-T808TL also has an ArtSoft Universal profile together with IKS models. Therefore, the connection method must be determined based on the exact model and its entry in the current Torgsoft list. Old general rules about the inability of the MG series to work through a particular port should not be applied to the entire family.

Mini and IKS

Mini-FP4 and FP6, as well as MINI-FP54.01, FP81.01, and FP82.01, are supported through ArtSoft Universal. The same profile also includes certain IKS models, including IKC-483 LT, E260T, E-810T, C651T, and A8800.

The current documentation describes these devices as available connection options. A specific model should be selected after checking the connection method, operating architecture, and typical checkout operations.

Other models

The current main-program list also includes NOVITUS HD E 1.0 and certain registrars for localized Torgsoft versions in other countries. For a store in Ukraine, the model should be checked against the current equipment list for the Ukrainian configuration.

Why the registrar model must be checked together with the driver

Classifying fiscal registrars only by manufacturer does not reflect the actual operating scheme. For example, Datecs is represented through ArtSoft and Atlas, Maria uses ArtSoft or Resonance depending on the model, and Exellio has its own profile and is also supported through ArtSoft for some models.

Therefore, before installation, the responsible specialist must record four values: the full registrar model, integration profile, connection type, and the location where Torgsoft is launched. This check is especially important for checkout systems operating through RDP or a remote server.

Local computer, RDP, and Torgsoft-Hybrid

The operating architecture affects the connection of fiscal equipment. When Torgsoft operates locally, it communicates with the registrar through the profile available for the specific model. For a remote server, it is also necessary to check exactly how the checkout equipment is made available to the server session.

For Exellio, the current Help documentation separately specifies the requirement to terminate the user's RDP session. This condition must be included in the cashier's or administrator's instructions if the registrar operates in such a configuration.

For Torgsoft-Hybrid, a separate fiscal registrar activation applies, and the list of supported models differs from the main program. In this mode, Help confirms the ability to print a fiscal receipt during offline operation. Before connection, check that the specific model is included specifically in the Torgsoft-Hybrid list.

How Torgsoft works with a fiscal registrar at the checkout

Sale

The cashier adds products to the «Sale» document and processes the payment. Torgsoft sends the transaction data to the fiscal registrar. The registrar generates and prints the fiscal receipt.

For products sold through an RRO, the administrator sets the «Fiscal» attribute under «Inventory management → Product type». This setting must be checked before the test sale.

Return

The cashier processes the transaction in «Return» mode. For a supported configuration, Torgsoft sends the transaction to the fiscal registrar to print the corresponding receipt. Return specifics may depend on the particular registrar profile, so this scenario must be tested during checkout setup.

X and Z reports

In «Document → Sale» mode, using the fiscal registrar actions, the responsible employee can print an X report to view daily indicators and a Z report to close the day.

Cash deposits and withdrawals

Torgsoft provides separate commands for cash deposits and withdrawals through the fiscal registrar. The employee performs the corresponding action in the program, and the registrar records the transaction in its cash register section.

Cancelling the current receipt

If an error occurs while printing a fiscal receipt, the cashier can use the «Cancel receipt» action. The command applies to the current fiscal receipt, so after an error the transaction status must be checked before repeating the sale.

Persistent connection to the registrar

For ArtSoft Universal, Maria through Resonance, and Datecs registrars through Atlas, Torgsoft provides the «Keep connection with the fiscal registrar» setting. The program maintains a continuous connection with the device, which speeds up receipt printing, including in terminal mode.

This setting has a limitation: while a persistent connection is active, the user cannot open a second or additional «Sale» form. If cashiers use several parallel sales on one workstation, the administrator must take this condition into account.

Customer display in the fiscal registrar

For models using ArtSoft Universal, Maria through Resonance, and the Exellio models listed in Help, Torgsoft can send information to the display built into the registrar. The administrator determines what the customer sees during the sale: the product price, quantity and price, or the total receipt amount.

For the extended mode, text can be configured for standby mode, information displayed when adding a product, and the amount of change. The set of available parameters depends on the registrar profile.

What to check when working with a bank terminal

If the POS terminal is integrated with the checkout system, the administrator separately checks the transmission of card payment information. For supported fiscal registrars, Torgsoft can add bank-terminal slip receipt data to the fiscal receipt.

For this, the bank terminal must return the slip receipt information to the checkout system. This behavior depends on the terminal, integration protocol, and bank settings. Testing must be performed on the actual equipment before the checkout system begins operation.

Why old compatibility lists require rechecking

The set of supported models and their connection methods have changed. Some models that were previously described as working directly are now listed under ArtSoft, Atlas, or Resonance profiles. Separate TCP/IP profiles have appeared for other models.

Firmware versions from old recommendations should also not be used as a current compatibility criterion without separate verification. If the entrepreneur already has a registrar, the technical specialist should be given the exact model, modification, and actual device version.

Assessments such as «best model», «problematic model», or a general recommendation to avoid a particular manufacturer do not provide enough information for a modern configuration. The practical criteria remain support for the specific model, integration profile, checkout architecture, connection interface, and the results of test operations.

Checklist before launching the checkout system

• check the full name of the fiscal registrar in the current Torgsoft list;
• activate the «Integration with a fiscal registrar» option for the workstation where the hardware RRO is used;
• install and configure the integration profile corresponding to the specific model;
• check the connection type between the computer and the registrar;
• for remote operation, check the RDP or Torgsoft-Hybrid scenario;
• check the «Fiscal» attribute for products sold through the RRO;
• perform a test sale and return;
• print X and Z reports;
• check cash deposits and withdrawals;
• if a bank terminal is present, check the transmission of the payment result and slip receipt;
• if a customer display is present, check the information visible to the customer;
• record the working checkout configuration for subsequent maintenance.

A fiscal registrar requires separate configuration to work with Torgsoft. Before purchasing the device, provide the specialist with the exact model, connection method, Torgsoft operating scheme, and information about remote access. After configuration, test the main checkout operations at the same workstation that the cashier will use.