Composer pays considerable attention to the complexity and volume of data that must be managed by the Fund Manager or administrator. This has resulted in the use of simple presentation, navigation and maintenance techniques that bring related information together in a logical and operationally sensible manner. Examples of this includes:

• Investor details such as multiple mailing addresses, related contacts, email addresses, preferred contact methods, date of birth, pin numbers (for call center & web access), web and phone access, adviser details
• Account and holdings details on an individual portfolio basis or consolidated basis
• Insurance details
• Banking details for as many bank accounts as required, including regular Savings Plans, regular Drawdowns, Distribution and Redemption accounts
• Transaction and correspondence histories and diarised and standing notes Audit history with before and after images

Similar information is available for other entities such as Advisers, Dealer Groups, Employers, Fund Managers and Custodians that are involved in transaction processing.

Further to this, Composer pays attention to simplifying and managing transaction-processing routines. Transactions are initiated by some form of instruction from a party and are logged and optionally linked to workflow processes. These workflow routines push the transaction through a series of user defined Quality Control and Compliance steps. This architecture can be applied to all types of user-defined transactions in Composer.