Centralization – the OraSYS PO integrated financial information system is built on a centralized principle, which allows for its easy management, access rights to functions and data, and facilitated improvement and modification of the system's operation when necessary. The centralized principle of the system reduces the requirements for equipment on site and allows flexible and easy management of the hierarchical structure of the organization. Additionally, the need for specialised field staff is reduced as the operations performed to service the system (start of day, end of day, backup, etc.) are carried out only at the Central Office of the payment or/and electronic money institutions. The level of operational security of the organization's information system is enhanced because the centralized system server is complete with reliable devices to ensure the operability of the hardware, and the OraSYS PO Client applications used in the field do not store operational data. Therefore, in the event of a power outage or communication link failure, the system is protected from data loss.

Flexibility – The OraSYS PO system consists of specialized modules with integration tools according to the needs of users, which allows easy and fast transformation or expansion of the financial services offered by payment or/and electronic money institutions. The OraSYS PO system is built on a modular principle, which allows easier management of the system functions used and improved investment planning. If necessary, any new module can be easily added to the information system at any time, while maintaining the common processing logic and uniform data management. Each installed module can be used by all users in the system of the payment institution or electronic money company, and the responsible staff in the Central Management can manage individual or group access to the functions and data of the modules. Employees of the payment institution and electronic money company divisions responsible for the relevant sectors within the division are able to analyse, via the module's report functions, the activities of their structure (within the company division), which increases the ability to control and evaluate each specific activity. The modular design principle of the system facilitates the integration (through the development of appropriate data interfaces) of the OraSYS PO system with other systems operating in the payment or/and electronic money institution.

 Integrity – The OraSYS PO system offers unity between systems in all divisions and units of the payment or/and electronic money institution, avoiding multiple data entry. The product reduces the possibility of inaccuracies, miscalculations, and erroneous accounting transactions through an operating and accounting methodology standardized by the organization's management that users are forced to follow.

The OraSYS PO system, regardless of its modular construction principle, is an integrated system. The integrated principle is implemented with common procedures for all modules: service procedures (start and end of day, archiving, revaluation, etc.), common parameters (exchange rates, etc.) and common data registers into which data from the modules are integrated. The integrated data of the system allow a comprehensive assessment and analysis of the activities of payment or/and electronic money institutions through the separate analytical level, even though the data are created and processed through different modules of the system. The possibility of a common analysis of the activity parameters increases the efficiency and competitiveness in the operational management of the payment institution or electronic money company.

Security – The OraSYS PO system has a sophisticated security system that defines the individual and group rights of each user in the organization's system. Restrictions can be easily changed and controlled by information system managers.

Log file – The system's logical architecture, built on the basis of input/output queues, not only significantly reduces hardware requirements, but also provides a natural mechanism by which any action or operation allowed to the user is recorded in a complete log of requests sent to the system, which can be easily monitored preventively or subsequently. A similar log is maintained for responses to queries sent, including information extracted from the database when a request is made to produce a reference form.

Individuality – The OraSYS PO system, despite its universal architecture, contains all the individual features, requirements and advantages of the financial technology implemented in the organization. The fact that the SYS Consulting Ltd. team has been working successfully for many years with various banks and other financial institutions and knows the nature of a significant number of individual financial information technologies, allows us to quickly and successfully incorporate the specifics of a particular methodology into the OraSYS PO system. The presence of the aforementioned specific features in the OraSYS PO system and the possibility of continuous improvement of the system by the developers, defines the proposed system as a custom–made system for payment or/and electronic money institutions.

Accessibility – The OraSYS PO system is based on affordable system technologies, which ensures cross–platform portability, application scalability and ease of compatibility and operation. A key requirement in building complex information solutions is the ability to use the data stored in a particular system with the tools of other information systems or standard data analysis tools. In this aspect, the OraSYS PO system is characterised by a high degree of openness to other systems. The OraSYS PO system is built with the RDBMS Oracle tools and has all standard data access capabilities. The means of access can be standard report generators (e.g. Crystal Reports, Oracle Reports) or any other information system with standard RDBMS Oracle data access capability (ODBC or API). In order to use OraSYS PO data through other systems, appropriate permissions must be defined in advance (by the organization's system administrator) through the financial information system security system.