[Kayleigh Peterson]

@greg-skidmorebelpointe-com Currently, the ability to run a second database would not work for historical conversions. We need to be able to line up the historical account to the starting values of the live downloading accounts, as well as map products and use the local pricing table that is in place. The merging of the two accounts is required to occur in the live database to combine the historical and the active accounts. Having a second database would limit our ability to do this.

If you are seeing historical accounts show up in a view, my recommendation would be to add a filter. The historical client could also be marked as inactive after we get the initial load of data if needed, or for Trends purposes, could be marked as Demo. The account numbers should have _hist appended to them as an indicator they are for the historical conversion.

[Kayleigh Peterson]

@greg-skidmorebelpointe-com
When Orion reconciles accounts historically, we are reconciling to the live downloading account’s starting value and essentially reconciling the historical account backward down to a zero value. Due to the nature of how the reconciliation works, we cannot zero out accounts until they are fully reconciled, and it must be done in your database due to account mapping, product mapping, and local pricing. We do have the ability to mark them as inactive during the reconciliation process, but this can make the work more difficult for us when running scrubs. When the live accounts are reconciled, there may be additional accounts that need your attention as most historical conversions also contain old closed accounts. We refer to these a non-downloading accounts if they still have a value, however, they may also be accounts already at zero in your history. This will also need your attention, and Orion will need your guidance once the conversion is complete to ensure these are closed out properly and moved to the correct household as needed.

[Kayleigh Peterson]

When debating pros and cons for how you want to handle new accounts, it’s important to consider what works best for your business. Do you have a lot of accounts and clients that you are adding to your business; are you in the process of growing ? Are there parts of your business that you do not want on the Orion platform?

Below are some pros and cons to consider when choosing your new account process.

Auto-Add
Pro:
-Orion will create all new accounts and applicable households based on the Name File from the Custodian
-Useful for adding all accounts in the custodial feed
– Requires you to only monitor the new accounts and rehousehold or assign account information as appropriate

Con:
-ALL accounts in the applicable custodial feeds are added. This means you will need to cancel any account you do not want on Orion
– Separate SSNs will not be householded together initially (ie: Spouses and children)

Auto-Exclude
Pro:
-More control over the accounts on the platform (ie: Naming conventions, householding, etc)
– YOU determine what accounts are on Orion, rather than having to cancel accounts after the fact

Con:
– You will need to monitor the exclusion table to see when new accounts are added. Pro tip- You can setup notifications under your settings when accounts are added to the exclusion table.

It’s best to consider what is best for you and your firm.

[Author]

Posts