Using A Password Manager For Account Aggregation
- Created: Sunday, 19 December 2010 20:40
Aggregating a client’s accounts in one of these apps opens the possibility of managing assets now held away from your firm. For instance, if a client has a company 401(k), you could track its growth—even though you don’t manage those assets. It gives you data crucial in assessing the client’s retirement plan.
Since many wealthy clients tend to have assets scattered or insist on working with more than one advisor, using an account aggregation app to see assets managed by others is good for the client and may be good for you, too.
Your client gets you to keep an eye on other advisors, and a little competition keeps you on your toes.
Moreover, if you help the client aggregate his investment data, it puts you in the position of the trusted advisor. If the other advisor does a poor job, you can suggest a change.
Though account aggregation is useful to clients and advisors, adoption remains a big hurdle.
Clients must first establish online access to each of their accounts. Then, they must share their user IDs and passwords for each account with you.
The logistical problems pose a serious obstacle to implementing account aggregation for clients.
But it occurred to me today that a good way to manage these logistics is by utilizing a password manager.
These programs not only store passwords but also store an associated URL. So if your click on your Bank of America entry in your password manager, it navigates to the BA website, fills in your password, and logs you in to see your account.
Importantly, the passwords are encrypted. You just need to remember one master password in order to gain access to all of the passwords that you save, and you can save hundreds of passwords in a password manager.
For advisors, what I am suggesting that you save clients’ passwords in your password manager.
You could create a naming convention to store each client’s passwords in your password manager. For instance, you might save an entry in your password manager for “Smith-John & Vicki - IRA,” which would store the user ID and password for John and Vicki Smith’s IRA at a brokerage. When you click on that entry of your password manager, it will log you into the account holding the Smith’s IRA.
While some account aggregation apps include workflow and dashboards for getting clients signed up, advisors have reported mixed results using these tools.
Using the password manager to store the data might be a lot easier. You can log into the account while you’re with the client. That avoids painstakingly walking through with a client the many steps in an account aggregation app’s workflow. Instead, you just save the password and user ID in your password management app. After you get the information needed to log into the client’s accounts, you can go through the workflow in the account aggregation app.
What’s especially nice is that, if you ever want to fire the account aggregation service, you’ll have retained all of the passwords. You won’t have to start all over from scratch if you need to change aggregation systems.
A word of caution: when you know a client’s sign-on credentials to his investment accounts, you could be held as a fiduciary on those assets—even if they are held away. Generally, if you can trade the assets using the client’s credentials, you should be willing to accept the role as a fiduciary for those assets—even if you don’t manage them. You should speak with a compliance consultant to nail down how you want to handle this issue. Or maybe one of your A4A compliance experts can comment on how they’d like to see advisors handle this issue.
What do yo think about using a password manager to create a record of your clients' passwords?