Automatic acceptance of a transaction request

In addition to entering transactions manually, OfficeLine 3.1 Corporate Banking allows the importing of a transaction (or a batch of transactions) from, for instance, the client's payroll system.

Automatic update of data in another system

The application allows delivering the records of performed transactions (in a batch) to, for example, the client's accounting system.

Generic interface

The generic data exchange interface to a related system supports standard formats (such as ABO and CC). Support for any other format may be implemented by configuring the interface. This allows the application to communicate with any other system (a payroll, accounting, or different system), always in the format required by the system.

Communication channels

The application allows selecting from among several methods of connection between the client and the server (service provider). These methods include:
  Communication over the Internet using the TCP/IP protocol;

  Direct connection over a phone line using an analog modem;

  Direct connection over a phone line using an ISDN modem;

  Data connection through a cell phone;

  GPRS connection through a cell phone;

  Communication over a public data network.
The operator can support several communication channels at the same time. The client can then use multiple communication channels, or choose the communication channel that best suits his/her preferences.

Application security model

The security of services provided by the application is addressed at multiple levels:
  User's access to the application (authorized user's log-on, authorization to use the application, limits);

  Protection of data stored on the disk (database encryption);

  Check of the authorization to access the services (verification of the user's identity during a connection attempt, digital signatures for transactions);

  Protection of data transmitted between the client and the provider's server (recipient identity verification, data encryption);

  Irreversibility of transactions (the provider can prove in the future that the transaction was requested by an authorized user and that the provider was authorized to perform the transaction).

  Possibility to audit the application operation down to the level of users or workstations.
All these levels offer a choice of multiple configuration options which can be combined to implement a security model based on the required security policy.
A part of the security model is defined by the provider (the maximum allowed limits for transactions, the obligation to use a digital signature, encryption method, etc.); the other part is defined by the clients themselves (e.g., user rights or the limits of operations allowed for users).