UTBS handles counter-, ATM- (automated teller machine), POS- (point of sale), EP (rechargeable electronic purse), ASP-
(account statement printer), and similar transaction and clearing data
UTBS handles internal, national, and international events
UTBS handles IBAN (international bank account number) and RFID (radio frequency identification) information
UTBS can be used both for acquirer- and issuer accounting
UTBS handles both authorization and clearing data
UTBS handles both normal events and reversing entries
UTBS handles both events being relevant and events not being relevant to accounting
UTBS handles debit-cards, credit-cards and chip-cards
UTBS handles separately records for single events and aggregated records
UTBS initiates both client accounts and cash accounts
UTBS handles all balancing accountings between branches and UTBS systems playing part of client and cash systems
UTBS can pass accounting data in every manner of combinations described before both directly to an internal accounting system and in an intra-banking format
(for example SWIFT, DTAUS in Germany)
UTBS comprises automatic control mechanisms in whole network monitoring accounting procedures
in accordance with generally accepted accounting principles and technical opinions
UTBS in addition comprises programs for statistics and fee simulation (RSS), for complex matching problems and for difference handling, to clear availability data
, to control cash desks and other devices etc. each task solved in the whole UTBS-network
UTBS can generate a charge for every event or set of events and is able to generate multiple transaction fees, event fees, and periodical fees
including special conditions (for example an amount of free transactions per month/week/…) controlled by tables
UTBS is capable of accumulating information making an entry for the accounting system controlled by tables
UTBS is capable of transferring selected events to one or simultaneously to various datasets using one or several intra- and/or inter-banking formats
In addition UTBS comprises interfaces to account data, to card data, to availability data, and to management information systems
UTBS can take up both a record-centered view and an event-centered view
UTBS operates on both single record level and level of sets of data
UTBS is designed for every kind of sales, in general for every kind of events
UTBS can realize specific data views with one event belonging to several views by combining selected kinds of sales and base-processes to so-called
synthetic processes, which will be handled as a separate process-item
Assigning processes to client-processes UTBS has the ability to handle clients thru the whole UTBS-System
UTBS is capable of dealing with several separated processes simultaneously
UTBS is extensively controlled by process-, event-, system-, and account-tables
UTBS-programs automatically control themselves via special information about sets of data (no "useless" lists in case of temporarily missing data)
UTBS is process-specifically parameterised, thus controlling data management among other things
UTBS automatically constructs correction lists in the whole UTBS-network
UTBS-program-tasks are reproducible in every manner during normal operation without loading back any data files as far as the necessary data still exists
UTBS provides a security method, which eliminates identical records in the whole network
UTBS can execute functions by executing subtasks on several or all UTBS-systems in a UTBS-network
UTBS can exchange single event records, aggregated records, etc. with every single UTBS-system controlled by tables, thereby corrected data can be
exchanged automatically
UTBS can control every interdependency on programs in an automatic manner
UTBS is constructed to handle large datasets
by a special technique named "job-number"-logic (hereby the main access is reading data and only less writing data)
UTBS runs on various platforms (for example IBM MVS, SNI BS2000, UNIX, MS Windows)
UTBS can operate with various database management systems (for example ORACLE, IBM-DB2, MS SQL-Server, ADABAS, etc.)
UTBS can be configured in every network topology of UTBS-systems simultaneous on different platforms and different database management systems
UTBS-programs using the job-number-logic logic have the ability to read and write the same datasets simultaneously
UTBS by generalization of the job-number-logic can operate on a transaction-computer or in real-time-mode; therefore UTBS can operate simultaneously
transaction-oriented as well as batch-oriented
UTBS completely fulfils software quality criteria as correctness, robustness, continuity, reusability, and compatibility
