If you do not see the Parent column in your Relationship Grid, please see this article.


Merging and splitting relationships with the Move functionality is quick and easy. This guide will teach you how the process works, and what happens to the relationships involved.

PrecisionLender uses a unique identifier from your bank’s core system (for example, a taxpayer ID) to create each relationship. However, just because a relationship has a unique ID, that doesn’t always mean lenders think of it separately from its related owners and entities.

In order to reflect how lenders view relationships from an organization and profitability standpoint, PrecisionLender allows you to manually merge and split relationships. When relationships are merged, the parent relationship becomes the entity under which all the merged relationship activity takes place.


In This Article


Who Can Move Relationships?

In order to move relationships in PrecisionLender, you must have one of the following rights on the relationship being moved:

  • You must own it OR
  • You must have the rights to Edit it (have Edit Any Relationships rights) AND see it (have View All Relationship rights AND the Relationship is in a visible region)

Let's take a look at a couple of examples.

Example 1 Example 2

Lender A owns Relationship 123 and wants to merge it into Relationship 456. Lender A owns both relationships. Can Lender A successfully merge these relationships?

Yes, Lender A can merge these relationships because they own both Relationship 123 and Relationship 456.


How to Move Relationships?

Whether you need to merge or split relationships, the Move process is easy:

  • First, navigate to the relationship you want to move and find the Existing Core Relationships section.
  • If the relationship is already a parent, you will see the option to expand and view child relationships. If the relationship is a standalone, you will only see the current core relationship.
  • To move the relationship, select the checkbox to the left of the core relationship name and the Move button will activate.
  • Click Move to open the Move Relationships window.


Moving a Relationship under a Parent (Merge)

  • Once the Move Relationships window is open, select a parent relationship for the relationship currently being moved.
  • Use the search bar above the grid to filter results.
  • When you select a relationship from the grid, the row will highlight with a blue color and the New Parent field displays the current selection.
  • After making your selection for the new parent, click Save. This will prompt a confirmation window where you will confirm the changes.

Moving relationships is not a permanent action and can be easily reverted using the Split process.

To view the new hierarchy created by this move, navigate to the parent relationship page and notice the new child relationship nested under the parent in the Existing Core Relationships section.


Moving a Parent relationship under another Parent (Merge)

In addition to moving standalone relationships under a parent, you can also move parent relationships (along with their child relationships) under another parent, creating multiple layers of hierarchy.

  • Select the checkbox next to parent relationship name under the Existing Core Relationships section and click Move.


You do not need to also select the checkbox of the child relationship. Selecting the parent level relationship will move the entire hierarchy associated with it, keeping the structure in form.


  • When moving a parent relationship, you will see the number of associated child relationships in the Move Relationships window. Using the same workflow as before, use the grid to identify the new parent of the relationship being moved.


Removing a Relationship from a Parent (Split)

If you would like to split a relationship from its parent:

  • Open the Move Relationships window from the relationship being split out.
  • Save without selecting a new parent.

After submitting changes this will remove the current hierarchy and the selected relationship will be treated as a standalone relationship.


Related Articles