Popis verzie 2022.0.32
12.12.2023 22:54New features
182884
The amount of tax turnover has been removed from the X and Z reports for the software PTR. The amount of tax turnover is also missing from the Z-report, which can be viewed on the state website https://webrro.tax.gov.ua.
The inscription "ECR Torgsoft" has been added to the bottom of the X and Z-reports for the software ECR. At the bottom of the Z-report receipt, the following inscription was added "DAILY SUMMARY REGISTERS ARE ZEROED FISCAL REPORTING CHECK IS VALID", and for test checks it will look like "DAILY SUMMARY REGISTERS ARE ZEROED TEST NON-FISCAL REPORTING CHECK".
Fixed a bug when the Z-report of the ECR did not display the total amount of taxes when the list of software ECR did not contain excise. These changes do not apply to templates that were saved earlier.
Changes to the software ECR receipts for X and Z reports of the corresponding state ECR: the amount of tax turnover removed for these reports could only cause confusion before, as goods could be subject to several taxes and the total turnover was more than the amount of goods.
186260
When sending individual notifications, for example, on an invoice (Trade with invoice statement - Send message to client), the SMS service is now remembered for sending both regular messages and sending via Viber.
When you send a message, the service that was selected the last time you sent a message of the corresponding type will be automatically installed. When you change the template, a similar process occurs. Automatic substitution of the SMS service will significantly speed up the process of sending messages of the same type.
186140
For goods that are added as a repair material, a check has been added to determine whether they have a sign of an excise stamp. If an excise stamp is required, a corresponding message will be displayed and the item will not be added as a material.
Eliminated the erroneous addition of goods for repair that require an excise stamp.
186163
-
On the form "Print settings" button "Regional settings..." renamed to "Customize templates...", and button "Template without region" — on"The default template".
-
Robotic form "Regional print settings" renamed to "Print and send settings" (the list of settings and the editing form have been renamed in the same way).
-
Column added to the work form "Enterprise", and on the edit form - a drop-down list for selecting a company.
The ability to customize the template for printing and sending invoices not only for the region, but also for the enterprise.
186165
The "VAT amount" field has been added to the template for printing an invoice, an invoice expense note, and a sales invoice.
The VAT rate and excise tax are taken from the settings of the product type if "Include VAT in product type" is enabled in Settings - Options. Otherwise, the settings specified in Settings - Options - Accounting are used.
Ability to display information about the VAT amount in printed invoice and expense invoice documents.
Improving the operation of modes
185916
Fixed a bug when, when creating an invoice (Document → Trade with invoice statement → Invoice tab → Create invoice action), the payment amount on the invoice differed from the invoice payment amount if the invoice was paid in a different currency at a different rate from the last rate registered in the system (Payment - Currency rate) at the time of creating the invoice.
186392
Fixed a bug that caused the inscription "Canceled" to appear on the customer's display when paying through a bank terminal using the MG N707TS fiscal registrar (HappyMicro) and the "Transfer payment parameters by bank terminal" setting was enabled, and the fiscal receipt was not printed.
186099
Settings → Role settings
Fixed a bug due to which the form "Responsible employees for the canceled sales item" was not displayed in the list of work forms when setting up roles, which made it impossible to call it under a limited user from the Settings → Options → Access mode.
185980
Payroll accounting → Registration of working hours
Fixed a bug that caused a situation when the time worked for an employee who registered an arrival was not recorded in the employee's work log. This situation occurred if an employee worked in more than one position and did not specify a position when registering an arrival.
If an employee works in more than one position, he or she will be prohibited from registering an arrival without specifying a position. If this happens, an error message will be displayed. To fix the problem that arose in the past, you need to manually mark the time worked in the work schedule and save the schedule.
185755
Payroll → Settings → Help → Penalty
Fixed a bug that allowed creating a record with a negative amount in the "Penalty" directory.
183850
Payroll → Work → Advance payments
Fixed an error that prevented the advance from being displayed in the list of advances when creating a deferred payment.
When you create an advance for a future period (or change the date of an existing advance to the date corresponding to the period of the future advance), the period will be created automatically. The list of periods will be updated. The algorithm will work in a similar way when you call the "Calculate advance" action.
186438
Fixed a bug when on the Payment called from sales form, when selecting a current account, the name of the current account was not displayed under the current account selection component.
186349
Document → Trading with an account statement
Fixed a bug that could cause the error "Parameter [TOACCOUNTID] data type is unknown..." when selecting a variable associated with the counterparty's (recipient's) current account when viewing an invoice. The error was detected if the counterparty did not have a current account specified in the counterparty's settings.
186559
Fixed bug [FireDAC][Phys][ODBC][Microsoft][SQL Server Native Client 11.0][SQL Server]Violation of UNIQUE KEY constraint 'uqsPartner'. Cannot insert duplicate key in object 'dbo.Partner'. The duplicate key value is (<NULL>, Shevchenko Taras Grigorievich, <NULL>) when loading a remote client's order if the settings of the synchronization object on the "Clients" tab are set to "Search for customers by phone number" and "Automatically create new customers by order" (or create an invoice immediately or in the order file SaleType is not equal to one), and the hidden setting "If not found by phone number, then always create a new one" is enabled (hidden from version 2020.8.0). At the same time, the order contains the name of an existing customer and does not contain a phone number (the customer also does not have a phone number in the database).
186564
Synchronization with Ukrposhta: fixed a bug in the display of Ukrposhta delivery addresses on the Client editing form, on the Delivery options tab, when a random Nova Poshta delivery address was displayed instead of the Ukrposhta delivery address.
186567
New mail: when performing the action "Update recipient addresses" (Settings → Options → New mail → table "New mail sender addresses"), the following error has been fixed [SQL Server Native Client 11.0][SQL Server]The DELETE statement conflicted with the REFERENCE constraint "fk_M43L17". The conflict occurred in the database "TorgSoftDB", table "dbo.TrackingNewPost", column 'RecipientNewPostAddressesID', which could occur if there were duplicate New Mail delivery addresses in the database.
186058
Localization
Fixed a bug with the lack of translation of the phrase "Close the receipt" on the confirmation window for the action Document → Transfer goods between receipt invoices → select invoice → Close receipt.
186310
Fixed the lack of translation of the message "You need to register to use the subscription features" when trying to activate the Web Interface option using the demo version without registration.
186293
Torgsoft → Application server → Implementation
Fixed an error when adding an item in quantity 2 when the item barcode was scanned only once.
186626
Print template settings: fixed error 'qArticles: Type mismatch for field 'Barcode', expecting: WideString actual: String' that occurred when previewing the print template 'Retail sales invoice (sales)' if there was no sales document in the database.
186657
Fixed the error "[FireDAC][Comp][Clnt]-503. Connection name [AutoUpdateDatabaseName2] must be unique" when checking for updates again (after the program start) (Help → Check for updates), if the confirmation message"Updating the program You will need to restart the program during the update..." or "Attention! Several conditions must be met for the system to update correctly in the retail network..." (appears if the configured data channels are enabled), click No.
186656
Software ECR: on the ECR registration form, when updating the payer's data, the error 'Signature verification error: wrong signer', which occurred if the payer's RNOKPP is a passport number, has been fixed.
186727
Fixed a bug when the fiscal receipt included barcodes of limited circulation starting with 20-29, which are intended for use only within one enterprise or group of enterprises (by agreement), as well as for identifying goods of variable quantity.
186700
Software ECR: starting from 18.12.2023, the fiscal servers of the State Tax Service of Ukraine will check the validity of the codes of goods transmitted by the UKTZED, and therefore the following changes have been made to the program:
-
When selling goods with the UKTZED code, the error 'XML validation errors: Error: 'UKTZED' element is invalid - The value '407210000' is invalid according to its datatype UKTZEDColumn' Pattern constraint failed. which occurred when a valid UKTZED code was specified for a product that started with zero, for example, 0407210000.
-
When saving a product card, the validity of the UKTZED code is now checked (a valid UKTZED code consists of only digits, the required length is 10 characters, it is recommended to check the online reference).
-
When selling existing goods for which an invalid UKTZED code has already been specified, the UKTZED code is ignored (information about the goods is transmitted without an erroneous UKTZED code). This rule also applies to hardware fiscal registrars that use the Artsoft driver, as well as manufacturers of Excelio and Datecs (Atlas).
185823
Synchronization with the online store: fixed the 'Stream read error' error that could occur when uploading product photos to FTP when the storage location of product photos 'in the database' and information about the product photo was damaged.
Now this error will not prevent further uploading of product photos, and the damaged information about the product photo will be deleted.
186137
Synchronization with the ROZETKA marketplace: fixed the 'Out of memory' error that could occur when generating a product import file (price list) if the synchronization object contains a large number of products.
The process of generating a product file has also been optimized, making the operation take much less time.
-
19.03.2026
Popis verzie 2026.0.2
Aktualizácia Torgsoft: opravené nefunkčné akcie produktov a chyba synchronizácie s Prom.ua kvôli ochrane botov
-
11.03.2026
Popis verzie 2026.0.1
Torgsoft 2026.0.1: opravená 0% zľava na produkt – teraz správne funguje priorita zliav a vyberá sa vyššie percento
-
24.02.2026
Verzia 2026.0.0: Strategický prehľad aktualizácií systému
Prehľad aktualizácie Torgsoft 2026.0.0. Optimalizácia zdrojov, správa zásob, nové fiškálne funkcie, bankové integrácie a stabilita databázy.









Vráťte sa na predchádzajúci krok