2.1.1 User Access Control
A flexible application access control provides a means to fit well into a functional responsibility structure of the business area.
2.1.2 Project Approach
Each transaction is managed as a project during its live span. A full history of activities, correspondence, accounting entries, payments etc. is kept and can be recalled long after the transaction has expired. A global project (company-wide) is a special project used to interact with external systems.
2.1.3 Financial Set of Books
For each project a complete financial set of books can be kept. The entries on the local (project) set of books can also be echoed to the global (company-wide) set of books, allowing for a micro-view on local and a macro-view on global.
2.1.4 Documentation
Transactions will over time have several documents (client letters, calculations, e-mails etc.) attached to it. In Topaz these documents can be indexed against the product, client or transaction to allow for a well-kept inventory of documentation.
2.1.5 Contracts and Securities
A separate module manages the legal documentary requirements of a transaction. A flexible security register further enables the documenting of specific regulatory requirements.
2.1.6 Diary System
An extensive diary system is used to generate reminders across the spread of a project or the company. Once a reminder is triggered, the users involved are notified with a message of the event and a task is assigned to each. This enables the proper follow-through and transparency needed to make sure nothing falls through the cracks.
2.1.7 System Integration
No system lives in isolation. Topaz employs a unique middle ware product called Integrat, that is fully customizable for any additional background task. By using Integrat, Topaz can be set up to import or export information into or from Topaz to almost any external system (given that the external system allows for integration). This ensures that Topaz does not live in isolation and contributes to the bigger business environment.
|