Multibanking
FTM is able to serve a set of banks and entities within a single FTM database instance in a way that you can separate the transactions to different parties. The system, and the applications that are built on it, are able to categorize operational data by entity and prevent critical information from being compromised. In other words, you can use FTM to build applications that are aware of the complex hierarchies of banking groups and that deal with corporate users and different banking entities. This capability is called multibanking.

When a multibank solution is implemented, the FTM graphical user interface must be configured to restrict the user's view of operational data according to their role within the operational hierarchy. The restriction can be applied to individual parties, sets of parties, or party subtrees. Multibanking applies only to operational data; configuration data is not separated. So, all users who have access rights that allow them to change configuration data are able to change the configuration data for any entity, not just their own. For this reason, it is important to establish a clear hierarchy that allows only the system administrators to implement configuration changes.