Manage Client Composites

You can group third party clients together to form a client composite by creating a parent-child relationship among client records. You can perform ISTAR reporting and refreshes at the client composite level once the relationship is established. After adding a client record to serve as the parent client, you relate the parent to multiple third party clients. The parent client is not directly associated with entities. The parent client exists to identify the members of the client composite, and each third party client is associated to an entity.
To form a Client Composite:

Do one of the following:

In Portfolio Data Center, in the left navigation pane, click Portfolio Desk > Accounting Portfolio Setup > Third Party Details > Create Third Party Relationship.
In Accounting Center, in the left navigation pane, click Setup > Portfolio Setup > Third Party Details > Create Third Party Relationship.

You see the Create Third Party Relationship panel.

Complete the options on the panel.

The following table describes the options required to associate a child third party client to the parent third party record.

Option	Description
Lookup Third Party
Lookup Client Name	Specifies the name of the parent third party client.
Lookup Client ID	Specifies the client identifier of the parent third party client.
Lookup Client Type	Specifies the client type associated with the parent third party client.
Lookup Entity
Entity Name	Do not use.
Entity ID	Do not use.
Lookup Third Party Contact
Lookup Company Name	Specifies the company name of the child third party client.
Lookup Company	Specifies the company of the child third party client.
Lookup Company Type	Specifies the company type associated with the specified child third party client.
Add Third Party Relationship
Relationship Type	Specifies the relationship of the third party to the third party contact. Set to PARENT. Note: Values are maintained in the CODE_VALUES table under code category iRelation Type for source EAGLE PACE. If the value PARENT is not available as an option, you must add the code value for this category, to complete panel entry.
Investment Team Code	Determines how to treat interportfolio transfers that occur between entities belonging to the same client composite, but different underlying clients Options include: REPORTING. Treat the transactions in interportfolio transfers as if they applied to entities that belong to different clients. Existing continuation logic does not apply. *Blank.* Treat the transactions in interportfolio transfers as if they applied to entities that belong to the same client. The existing continuation logic continues to apply. Any value other than REPORTING causes the system to treat interportfolio transfers with the existing continuation logic.
Start Date	Specifies the start date for the relationship.
End Date	Specifies the end date for the relationship.
Status Flag	Specifies the status of the relationship. Set to ACTIVE. Options include: Active and Inactive. Note: Values are maintained in the CODE_VALUES table under code category iCliStat Type for source EAGLE PACE.

Click Submit.

The system adds the parent-child relationship to the RULESDBO.CLIENT_RELATIONSHIPS table.
You can associate any number of child clients with a parent client record. And a given child client can be associated with multiple parent clients.
After you establish the parent-child relationship, you can:

Submit reports at the parent client level, to create a client composite level report aggregating the values for all of the underlying clients.
Refresh ISTAR at the parent client level, to refresh all of the underlying clients.

Manage Client Composites

0 Comments