Welcome to the BCC Blog. What is a Blog? It is simply a webpage where entries are written by our consultants to provide commentary or news on a particular subject. Blogs are usually brief and informal, may contain links and can even be accompanied by graphics.
Our intent is to publish one new blog every week to keep you up to date on the current hot topics within the compliance community or to simply let you know what we are thinking. Because the internet is full of inappropriate content and language, we are not allowing posts or replies to our blog. This is not a forum but an editorial post allowing you to peer into our minds and our thought processes.
The best part of all, it's FREE! We encourage you to subscribe to our blog.
Feel free to use what you read, provided that you supply proper credit.
Thanks for visiting.
New & Emerging Compliance IssuesAugust 18, 2008 by David Dickinson
This is my last installment of what I learned at the ABA's Regulatory Compliance Conference in June. I hope my notes have provoked some thoughts and helped you manage compliance at your bank. This last session dealt with how Compliance Officers handle keeping up with the barrage of compliance issues, new proposals, final regulations, and more. Also, it touched on developing procedures for new requirements. Here are my notes: New issues: Is it a Proposal, final, Guidance, FAQ? You don't have to respond to all of these (proposals) or take them all the same (final rule vs. FAQ/Guidance). Can you leverage off consultants/vendors (BOL, ABA, Compliance Headquarters, etc.)? Call your vendors and ask them what they know and how they can help your bank. Compliance personnel should not develop procedures. Take the Compliance Officer expertise of requirements and the expertise of the business lines to develop procedures together.
Don't cry wolf every time a new requirement is proposed.
Access the implication of new requirements:
When new requirements are issued, don't send an email out to people and scare your personnel ("this goes into affect in 6 months and we have to do it"). Rather send an email to the key people that need to know and ask them for a face to face meeting. You can give them a short synopsis "I need 1 hour of your time to discuss the new ID Theft requirements". Attach the Word summary (discussed above) so they can be prepared for the meeting.
Compliance Officers - Risk Rating & PrioritizingAugust 13, 2008 by David Dickinson
I'm still providing you with my notes from the ABA's Regulatory Compliance Conference. I attended a session on Risk Rating and Prioritizing tasks as a Compliance Officer. Below are my notes from this session: Gone are the days of checking off tasks. Now you must risk assess everything. Apply a risk approach to everything. What issues are facing your bank? Getting Organized: Design a "Issues Status Report"
Design a "Project Status Report"
Risk Rating/Prioritizing: Lower risk = lower priority
"Don't let the Compliance Tail wag the Banking Dog" If you under manage, issues will arise.
If you over manage, you risk profits. It's not a "compliance culture". It's a "Risk Culture." Risk management starts at the top. Many senior people don't like the term "compliance". Use "risk". Auditing & Risk Rating:
HMDA: What is Your HMDA Data Telling You?August 5, 2008 by David Dickinson
Here are some more notes from the ABA's Regulatory Compliance Conference. I attended a session on analyzing your institution's HMDA data that was very good. Below are my notes from this session.
"We expect banks to be self identifiers" - Calvin Hagins, Director of Compliance Policy, OCC
BSA Risk RatingJuly 29, 2008 by David Dickinson
I continue to bring you my notes from the ABA's Regulatory Compliance Conference. This session dealt with risk ratings. Not just the bank's BSA/OFAC risk rating, it also includes risk rating customers and employees of your institution.
ABA RCC Flood IssuesJuly 21, 2008 by David Dickinson
I'm continuing to report about things I learned while at the ABA's Regulatory Compliance Conference (ABA RCC) in Chicago in June. I had the fantastic opportunity to speak on a Flood Panel with a representive from FEMA, the FDIC and two bankers. Here's some things we discussed that I thought may be of interest to you:
ID Theft Prevention ProgramJuly 14, 2008 by David Dickinson
In my last blog, I wrote the first installment concerning my attendance at the American Bankers Association's Regulatory Compliance Conference (ABA RCC) in Chicago. Here's another short piece on what I learned in a session on the new ID Theft Prevention Program requirements. These are my notes and not necessarily complete sentences. If you need more information on the FACTA ID Theft requirements be sure to read our June & January 2008 e-newsletters.
Flood Insurance at Loan Closing?July 9, 2008 by Jerod Moyer
Recently someone asked me what I thought was a very easy flood insurance question. The scenario played out like this: The bank is going to make a loan secured by buildings located within a Special Flood Hazard Area (SFHA). The borrower does not have enough funds to pay for the flood insurance out of their own pocket. The bank told them not to worry that they would add the flood insurance premiums to the loan amount and disburse funds to the insurance agent at closing. The lender asked if this practice would satisfy the flood insurance requirements. I responded without hesitation that indeed it would and what would be better proof than the bank issuing the check and delivering it to the insurance agent.
Using the same scenario above the bank could have met the regulatory requirement by instructing the borrower to write a check to the flood insurance agent prior to loan closing. Obviously, the bank would have to then cover the check if the borrower was short on funds, depending on when the payment was made. The bank could then reimburse the borrower/cover the check with funds from the loan closing disbursement. When it comes to flood insurance we need to remember that things that seem to make logical sense don't necessarily ensure compliance with the regulatory requirements.
UDAP (Unfair and Deceptive Acts or Practices)July 3, 2008 by David Dickinson
This is the second installment about things I learned while at the ABA's Regulatory Compliance Conference. Here's another short piece on what I learned in a session on UDAP - something we don't talk about much, but is very ugly if the regulators believe your institution is involved in a deceptive act. These are my notes and not necessarily complete sentences.
What I Learned at the ABA's RCCJuly 1, 2008 by David Dickinson
I recently attend the American Banker Association's Regulatory Compliance Conference (ABA RCC) in Chicago along with 1200 other compliance professionals. I had the honor of speaking on the topic of Flood Insurance on a panel with representatives from the NFIP and the FDIC, along with two bankers. Over the next few weeks, I'll be giving you some notes from some of the sessions I attended.
The first session was called the "State of the Union". We, at Banker's Compliance Consulting, are always trying to stay on top of the regulatory issues, hot topics and new releases. This session really scared me when they began listing all the issues we face or are about to face. Here's a short list:
On top of all this, the speakers indicated, there are more regulations & guidance likely to be coming from Congress. With the current mortgage "crisis", Congress feels they need to get more involved in the regulatory process. They are more than concerned with several issues like Predatory Lending and Broker licensing and regulating. While I agree there are a few bad apples out there that need to be reigned in, I don't believe more regulations will improve our industry or protect the victimized. In fact, the more disclosures we give, the less the "protected" will read. Hence, the effect is "more is less". We (that means YOU) need to write comment letters and talk to our Congressional Representatives. Help them understand your perspective so they are more informed instead of just hearing from the few victims.
Flood Insurance & Insurable ValueJune 25, 2008 by David Dickinson
As you all know, one of the "hot buttons" of regulatory compliance is flood insurance. Recently, there has been a lot of commotion about "insurable value". If you're not familiar with this, I encourage you to read our Comment Letter - specifically pages 2-4 - concerning FAQ #7.
When I have the chance to talk to regulators about this issue, they have always "come around" and "softened" their approach. Many have said they are backing off on this issue - at least until the regulatory FAQs are finalized (we're hoping by the end of 2008) or other guidance is issued. I'm not against purchasing RCV when it will pay. If my home flooded, I would hope I was adequately insured. However, you can't get a RCV payout on non-primary dwellings and even in many instances when you are insuring a primary dwelling. So why should a lender require insurance that won't pay? I believe to require insurance when it won't pay is not only a bad PR issue for lenders, but it can also be seen as a deceptive act - something none of us want to be associated with. So why would our regulatory agencies ask us to do just that? Good question, one that I don't have the answer to. Stay tuned and good luck.
|
Well, I was wrong. You see, flood insurance is required prior to making, increasing, renewing or extending any loan secured by improved property located within a SFHA. In the scenario above, flood insurance was not in place prior to closing; rather, it was put in place after closing. The loan was closed, a check was cut and then delivered to the flood insurance agent for payment. Therefore, the flood insurance requirements were not met.
Unfortunately, some regulatory Regional and Field offices are stating lenders must use Replacement Cost Value (RCV) when calculating the proper amount of flood insurance. I'm aware of guidance from the Dallas OCC Regional Office and the Dallas, Philadelphia and San Francisco Districts of the Federal Reserve Board stating this incorrect information. Now that sounds pretty bold of me (I'm disagreeing with all of those regulatory offices) yet there's no question in my mind that using RCV is NOT what the National Flood Insurance Act requires nor is it a requirement of the regulation. It is simply a "best practice" published in the