Soft-logic
fiscal farm
Software solution for the provision to third-party companies, online stores, vending business cash registers in the cloud for the payments data transfer in compliance with 54-Federal law
Prerequisites
for creation
for creation
On July 15, 2016, amendments to Federal Law No. 54 of May 22, 2003, regulating the use of cash registers, came into force. In accordance with this law, in addition to the existing requirements to equip regular retail outlets with new cash registers, new fiscal requirements were added:
Purchases made at online stores
Purchases of goods and services at vending machines
Transactions by providers, trade and service enterprises that accept non-cash payments from private individuals
Software
purpose
purpose
Soft-logic fiscal farm is a high-tech solution that enables online fiscalization of payment transactions by a pool of cash registers. The work of these registers is fully organized by our specialized software.
Target
audience
audience
Soft-logic fiscal farm is a perfect solution for customers, who:
1
Plan to fiscalize from 5000 operations per day
2
Want to hide structure of their sales from third-party services
3
Strive to get the cheapest fiscalization of their transactions
Ownership
cost comparison
cost comparison
A farm with 30 cash registers
Soft-logic fiscal farm
Third-party service 1
Third-party service 2
ПCash register purchase
300 000
—
—
Software purchase
400 000
—
—
Fiscal storage cost
Identical
Ownership cost per 1 year
52 000
720 000
756 000
Ownership cost per 2 years
100 000
1 440 000
1 512 000
Ownership cost per 3 years
150 000
2 160 000
2 268 000
Total
1 000 000
4 320 000
4 536 000
Need take into account that the organization of the fiscal farm, including the assembly, placement, maintenance carries out by the customer.
In addition to the organization of the staff work also need a specialized room, equipped with server racks and surge protection devices.
Solution architecture
and technologies
and technologies
Database
PostgreSQL 11
A web service to deal with transactions
Java, Spring
Back office
JavaServer Faces, PrimeFaces
Queuing process
Java, веб-сервисы
Fiscal module
Java, JNI
Architecturally the system is a solution which uses a central server and any number of fiscal modules.
The functions of the central server:
1
Directory maintenance (legal entities, online registers, users, etc.)
2
The transactions routing to a required fiscal module
3
Технический мониторинг:
- Доступности узлов с фискальным модулем
- Состояния контрольно-кассовой техники, включая отображение версии прошивки
- Срока действия фискального накопителя
- Количества фискализированных операций через каждый фискальный накопитель
- Среднего времени фискализации одного чека
- Наличия связи с ОФД самой кассы и размера очереди документов
4
The display of the transaction list and the details for specific operation
5
The display of general statistics
3
Technical monitoring:
- Accessibility of nodes with fiscal module
- Status of cash register, including the display of the firmware version
- Expiration date of the fiscal storage
- The amount of fiscal transactions through each fiscal storage
- The average time of one receipt fiscalization
- Cash registers connection availability with the Fiscal data operator and the size of the documents queue
Architectural scheme
Fault tolerance
and scalability
of the solution
and scalability
of the solution
The role of the fiscal module:
All control computers or racks have got limited resources, the same is of those that will house online cash registers. However, the software package should have the ability to increase resources as needed. Therefore, the complex requires a software module, which is deployed at a specific server and works with cash registers connected to it. When the resources of one server are exhausted, the second one will be launched and all the subsequent cash registers will be connected to it. Such software module is called a fiscal module.
A fiscal module composition:
1
An integrated web service to receive incoming requests from the fiscal farm core
2
A set of drivers to work with the specific models of the cash registers
3
A set of threads that provide ongoing technical monitoring for specific node
Due to a full-featured diagnostic module as a part of the solution, the system has the information about the state of all connected devices at any time. To fiscalize a transaction the system selects a cash register according to a special algorithm that takes into account the different parameters, such as a specific legal entity that the cash register belongs to, the functionality of the device and others.
The fiscal errors are handled as follows
- If there is no functioning cash registers at the time of fiscalization, the transaction is transferred to a special status. Another processing attempt will be in 20 minutes
- If at the time of fiscalization of an operation system receives an error signal, the fiscal module performs up to three fiscalization attempts, including trying to choose new cash register at the same host. If all attempts of fiscalization are failed, operation is transferred at the server in a special status. Another attempt will be in 20 minutes
Any other models of online cash registers can be added at the request of the customer!
100 000 +
Fiscal documents per day
3 000 +
Payment points
10 000 +
Operations per day at one device
0,8 секунд *
The minimum time of fiscalization for 1 operation
1,5 секунды *
The average time of fiscalization for 1 operation
*
It depends on a cash register model and the number of product items in the receipt.
A calculation example
of the number of cash registers
of the number of cash registers
Input data:
50 000
An average number of operations per hour
50%
A required performance reserve
4
An average number of purchased items in the receipt
We take 1 second as the average fiscalization time. At such performance one cash desk can fiscalize 3600/1,0 = 3600 operations per hour.
In total, to ensure continuous fiscalization of 50 000 operations per hour 50 000/3600 = ~ 14 cash registers will be necessary. Then we add figure required performance reserve of 50% to latter and the result is 14 + 50% = 21 cash register.
It should be noted that the average resource of the fiscal storage is 250 000 operations. Therefore, a specified set of cash registers will be able to process about 21 x 250 000 = 5 250 000 operations, after that it will be necessary to replace these fiscal storages.
Licensed
parts
parts
Licensed parts include:
The core of the complex
A connected cash register
Still have
any questions?
any questions?
Leave request and our specialists will contact you shortly