Risk Management & Analytics: Don’t let your CECL road map turn into a CECL roadblock

Don’t let your CECL road map turn into a CECL roadblock

Jeff Prelle, Head of Risk Modeling at MountainView, a Situs company, served as conference chair at the CECL 2018 Congress Conference.

When it comes to Current Expected Credit Loss (CECL) planning, modeling and implementation, the consensus among financial institutions is that there is no consensus, because no two financial institutions are alike. At Situs, we often reinforce the importance of taking a strategic approach to CECL modeling and implementation. After all, CECL’s tentacles touch a wide range of functions within a financial institution, from model and credit risk to accounting and information technology (IT). But when it comes to achieving CECL milestones and tactics, what will work for one bank, credit union or lender may not work for another.

This was the resounding theme of the 2018 Center for Financial Professionals (CFP) CECL 2018 Congress Conference that Situs sponsored in October. As a sponsor, conference chair and panel moderator, I had the unique opportunity to listen to a range of perspectives on key obstacles facing institutions regarding CECL. Reflecting on the event, it occurred to me just how difficult it was for institutions to discuss CECL in a way that resulted in fervent agreement and nodding. It was not that the information and content lacked value or substance; it was simply that the insights provided by its participants offered a constant stream of new information and unique perspectives. Participant enthusiasm was found in notetaking rather than nodding.

While broad, common themes and goals, such as regulatory compliance and accounting accuracy, were discussed during the conference, these broad themes took a back seat to the more nuanced and institution-specific obstacles. Those obstacles, when overlooked, may leave an institution vulnerable to time-consuming setbacks or costly errors. In response to those obstacles, I have outlined a few key recommendations to help institutions avoid turning their CECL road map into a CECL roadblock:

(1) Get your data and systems assessed

One thing was clear during CECL 2018 Congress Conference: data is still a concern for many institutions, most notably smaller institutions. For some institutions, it is not just about whether they have “enough” data; it is whether they have enough quality data and a strong enough infrastructure to access, update and manage the data. During the conference, several institutions noted that the lack of confidence in data and data management is leading to model indecision. If you are an institution that can’t seem to make modeling decisions, a data assessment will help dissect your data challenges and give you practical next steps to address those challenges and comply, including best-fit models based on your current data.

(2) Learn from IFRS 9 implementation pitfalls: Parallel-test your models

Institutions overseas have already implemented IFRS 9, which means there are case studies to reference. While IFRS 9 is not a perfect replica of CECL, it offers US institutions valuable lessons from its implementation. For example, some institutions scrambled to get their models in place and did not take appropriate precautions to ensure the models were both reasonable and supportable across various scenarios (up/down scenarios, for instance). For both models and scenarios, implement a full parallel test that will run for at least 6-12 months prior to your “go live” date. Stress your models and scenarios during that time to better understand the results; use this period to establish benchmarks for your losses; determine your model attribution plan for Allowance for Loan and Lease Losses (ALLL); establish your audit plan so that it addresses any questions that arise; and vet your approaches with management. Simply put, make sure everything works. It is worth the extra time and effort.

(3) Make sure your model developers don’t get lost in thought

One can imagine it could be easy for a model developer to get deep into his or her data, models, and scenarios. This is great! However, it would be prudent to ensure your model developer has come up for air a few times to mingle with the various business lines. Here’s an easy way to find out: Does your model developer know the name of the manager for each of the relevant business lines? By consulting with the various business lines, your model developer will have a better understanding of loan and portfolio idiosyncrasies and will have likely ensured that any economic factors applied are relevant to the specific loan type or portfolio. The best line of defense, however, is to get your models validated, which will enable your institution to capture model risk earlier in the process.

(4) Create multiple scenarios

Some financial institutions are getting hung up on the likelihood that a certain scenario will occur, but that is not the best question to ask. When evaluating a scenario, it is not necessarily about the probability that a scenario will occur (there are infinite scenarios), it is the probability of a scenario being better or worse than another scenario. Financial institutions need to stretch their models to get a more reasonable and supportable estimate of loss by creating multiple scenarios. It may seem like a hassle at first, but when it comes time to justify your model decision, you will have hard data to show.

If you find yourself experiencing CECL roadblocks, it is likely due to an institution-specific challenge. To solve for institutions-specific CECL challenges, assess/audit your current approach, identify the trouble spots, deconstruct the problem and break it down into practical steps that can be addressed and logged in your documentation. Always keep in mind: If you do not document the process, these discussions get lost in institutional knowledge. To learn more about assessing, validating and implementing CECL, email Jeff Prelle, Managing Director and Head of Risk Modeling at Situs at jeff.prelle@situs.com.


FASB tees up CECL issues, but not deferral

The Financial Accounting Standards Board (FASB) will meet soon to discern implementation issues associated with its credit losses standard, but the agenda doesn’t include consideration of a deferral in the effective date.

In an upcoming routine meeting, the board has teed up a session to review implementation concerns associated with Accounting Standards Codification Topic 326 on financial instruments, which is the standard taking effect January 1, 2020, for public companies requiring a “current expected credit losses (CECL)” approach to recognizing loan losses. The board plans to address concerns raised during the most recent meeting of the board’s Transition Resource Group (TRG) on credit losses, which is fielding and answering technical questions from entities as they prepare to adopt the new accounting.

A FASB spokesman said the board “will discuss the feedback received on the issues discussed” at the most recent TRG meeting, where the group addressed extensions and measurement inputs for contractual terms, vintage disclosures for revolving loans, and recoveries. She could not say what activity, if any, may be under way at the FASB to answer increasing calls to delay the effective date of the standard.

The American Bankers Association and the Banking Policy Institute, which represent virtually all major banks in the United States, have called on the U.S. Treasury to intervene on CECL. As banks are refining and testing their CECL models to determine when and in what amounts to recognize loan losses in financial statements, they are growing concerned that the new accounting will produce “procyclicality” in the economy or cause any kind of economic downturn that might occur to snowball.

Read more: Compliance Week


What’s keeping chief risk officers up at night

The banking industry’s chief worriers have a lot to worry about these days.

Whether it’s increased competition from nonbank lenders, the rise of e-commerce and its impact on traditional bank clients or the uncertainty created by the pending shift to a new benchmark lending rate, risk executives and board members at big banks see no shortage of threats to their industry.

Speaking at forum in New York last Thursday, chief risk officers at Citigroup and PNC Financial Services Group and the head of the risk and compliance on Fifth Third Bancorp’s board said that they worry, too, about the rise of populism around the globe and whether the country is heading toward another economic downturn.

Competition from nonbanks was top of mind during a panel discussion at a conference hosted by the Financial Times.

Joseph Rockey, the chief risk officer at PNC, said that as banks compete with hedge funds and other firms for loans, they need to be worried about the quality of the loans those nonbanks are making.

Read more: American Banker


Dodd-Frank reform requires surgical precision

Goldman Sachs’ letter last week to federal agencies about Volcker Rule reforms demonstrates its position along the fault line between those who believe systemic protections are still needed versus those who feel post-crisis regulation is too restrictive.

Goldman, unsurprisingly, wants the rule, which prohibits banks from making certain proprietary investments, weakened and believes amendments proposed earlier this year by regulators do not go far enough to provide relief.

Based on the Federal Reserve’s recent statement in favor of cutting burdens on banks with less than $700 billion in total assets, they apparently aren’t alone in rethinking the Dodd-Frank Wall Street Reform Act.

Perhaps they are both right. But we all would do well to remember the bailouts that prompted this sometimes-overheated regulatory response.

Those bailouts of large, complex and politically well-connected financial institutions came at great taxpayer expense and often against taxpayers’ wishes. The rules Goldman and the Federal Reserve now think need weakening were created amid this dynamic.

Read more: The Hill


Click here to subscribe to Situs Newswatch.

Thank you for choosing the Situs Newswatch. If you want to see your company here or have an idea for coverage, please respond to this email or email inquiries@situs.com for more information.

Disclaimers:

General. This disclaimer applies to this publication and the verbal or written comments of any person presenting it. In this publication Situs Group LLC taken together with its affiliates are collectively referred to as “Situs”.

Forward Looking Statements. Forward looking statements (including estimates, opinions or expectations about any future event) contained in this publication are based on a variety of estimates and assumptions. There can be no assurance that any such estimates and/or assumptions will prove accurate, and actual results may differ materially.

No advice. Situs advises that no statement in this publication is to be construed as advice of any kind, including, without limitation, as a recommendation to make any investment or to buy or sell any security or as investment advice. The examples contained in this publication are intended for use as background on the real estate industry as a whole, not as support for any particular real estate investment or security.

Information. Certain information contained in this publication includes articles, data, calculations and/or figures that have been prepared by and obtained from others, including publically available sources. Such information has not been audited or verified by Situs. This publication does not purport to be complete on any topic addressed. This publication may contain the subjective views of certain Situs employees and may not necessarily reflect the collective view of Situs or certain Situs business units.

Logos, trade names, trademarks and copyrights. Certain logos, trade names, trademarks and copyrights included in this publication are strictly for identification and informational purposes only. Such logos, trade names, trademarks and copyrights may be owned by companies or persons not affiliated with Situs. Situs makes no claim that any such company or person has sponsored or endorsed the use of any such logo, trade name, trademark and/or copyright.