Client Divorce

Included in:
Core
Primary Planning
Expanded Planning

When a client gets divorced, a few key settings must be updated in the eMoney platform to ensure an accurate financial plan.  Follow these steps to make those changes.

Step 1:  Update Client's Marital Fields in Client Record

Utilize the /clients API to modify the "maritalStatus" to "Divorced" and "previousMarriages" to "true".

Step 3:  Delete Spouse From the Client Record

Utilize the /spouse API to delete the spouse from the client record.

Step 4:  Delete Spouse Client Portal Logon (If Applicable)

Utilize the /logons API to delete the spouse's access to their client portal.

Generic Use Case

More Use Cases

Initial Office Setup

eMoney's APIs make the initial onboarding of your firm onto the platform straightforward and efficient.  See the steps below for the process to create offices, users and households.

Pre-requisites:  You will be provided with your eMoney root office path, developer ID and firm admin GUID by a member of the Client Implementations team.

Step 1:  Create Offices

Utilize the /offices API to create new sub-offices from the main parent offices.

Step 2:  Create Advisor

Utilize the /users API to create new users (advisors, assistants, planners, etc) in the desired office.

Step 3:  Create Client

Utilize the /clients API to create new clients assigned to the desired advisor.

Step 4:  Assign Sharing Rule / Delegation

Utilize the /sharingrules API to modify the delegation of clients to specific users.

Step 5:  Connect Accounts

Utilize the /connections API to add advisor managed account data to the platform.

Step 6:  Create Client Website Logon

Utilize the /logons API to initialize client portal access and login information

Generic Use Case
Add an Advisor Managed Connection

eMoney's aggregation capabilities allow for easy addition of advisor connections into the platform.  With this capability, the advisor can connect their managed accounts and see up-to-date values for consideration into the financial plan.

The following APIs are used in this use case:

/public/v1/users/{userId}/connections

Generic Use Case