Among the various issues engendered by the Department of Labor’s fiduciary rule, one is especially concerning to insurers, advisors and intermediaries in the distribution chain: What will the rule mean for the industry’s massive information technology infrastructure?
Will software and systems need to be tweaked, retrofitted or replaced? What are the stumbling blocks to surmount in transitioning to a DOL-compliant IT architecture? Do market stakeholders have the financial wherewithal to meet the DOL’s January 1, 2018 deadline?
Related: Got DOL rule compliance questions? IRI training program has answers
For answers to these and other questions, LifeHealthPro turned to John Sarich, an insurance industry analyst and vice president of corporate strategy at VUE Software, a firm that advises the industry on innovating and automating business processes. Sarich is a senior solutions architect, strategic consultant and business advisor with more 25 years of insurance industry experience.
The following are excerpts.
LHP: How do you expect the DOL rule will impact the technology needs of the industry? Can existing IT platforms handle the new regulatory requirements?
Sarich: The DOL rule will force a tremendous amount of change, not only as to customer-facing interactions between advisors and clients, but also in respect to the technology needed to support them. Most of the systems in place today won’t, in my view, do the job.
LHP: What new IT capabilities are required?
Sarich (pictured): New solutions will be needed to manage changes in advisor compensation, notably the anticipated shift from commissions-only to commissions plus fees or fee-only. The solutions will also have to manage changes to product design, policy administration, client-servicing and other functions.
The first of these — compensation — will be particularly challenging, as advisors and their distribution partners are grappling with how much to charge. There are a lot of questions to resolve.
What constitutes reasonable compensation? If you have a lot of clients who have bought annuities, what fee arrangement is appropriate for them? Should you charge, as a law firm does, a billable, hourly rate? Also, would an upfront fee provide for ongoing advice and service, or would you charge separately for these? All of these questions have to be addressed.
Related: 5 questions clients may ask about the DOL fiduciary ruling
New software will have to be customized to meet clients’ unique needs in terms of business processes, work flow and making apps interoperable with existing legacy systems, says Sarich. (Photo: Thinkstock)
LHP: What other issues must be resolved from a technology vantage point?
Sarich: In respect to insurance, software will need to manage, among other things, policy implementation and contract changes, licensing, documentation of client conversations, the needs analysis and product recommendations, as well as disclosure of compensation and potential conflicts of interest.
Related: The DOL: In your face once more with an overtime pay rule
This is an arcane area of insurance and technology. If, as I expect, compensation moves to the billable/hourly model of law firms, then agents and brokers now working on a commission basis are facing a major transition, as they’ll have to document their time at each step of the client engagement. And that will require replacing many of the software tools that they and other players in the distribution chain use today.
How all of this will look we can’t say yet, again because of the many issues still to be resolved. Nor have we done any DOL-related application development. None of our clients has requested this to date. But we have discussed in broad terms the issues and questions we’re collectively up against.
LHP: How many software developers are active players in your space? What other DOL-compliant app development is taking place in the market now?
Sarich: It’s a narrow universe of players. Apart from our firm, the big players include IBM, Callidus Software, Oracle and Computer Sciences Corp. (CSC). All of the software vendors are in a holding pattern now because, again, we don’t yet have clarity on what functionality is needed.