Entity Structure Mapping

By building simple rules, paths and mappings you have quick and complete control over uniquely determining how transactions should automatically be allocated through a structure from the instrument it uses. You can also just directly pick paths for a transaction to use if instruments are unmapped or not relevant for certain transactions. This enables you to automate accurately a lot of the manual work involved in maintaining these partnership allocation mechanisms through entity structures. The system, of course, instinctively visualises this for you so it is easy to see where everything sits along mapped paths within your structures.

An entity set is an organisation that contains the set of entities transactions will be allocated amongst. For instance, this could be a Fund or a top-level Company. The API allows you to create as many different types of entity sets as your solution requires.

These are the entities that can belong in an entity set for transactions to be allocated through. For instance, within a fund, this could be SPVs, AIVs and Blockers. Within a top-level Company, this could be subsidiaries.

Using rules you can map out all the different ways in which transactions are to be allocated from this entity up the hierarchy to ultimate owning entities. You can have multiple allocation rules against any given entity in an entity set.

These select a specific combination of entity/rule for each step in the hierarchy resulting in a unique path through the structure. You can have as many Allocation Paths governing routes through your entity set structure as you like. Each path consists of at least one entity and a rule indicating how any transaction owned by this entity would be allocated using this path.

All transaction, from a portfolio perspective, operate against an instrument. You can use the base Instrument or using our API create as many different Instrument types as you like.
An Instrument Set holds a group of related Instrument together.

These illustrate to the system how a transaction should automatically be allocated through the relevant entity structure by mapping the instrument of transactions to determine the path to use You can create as many allocation mappings as you like Each mapping contains an Allocation Path and an associated Instrument Set (or explicitly an individual Instrument)