ATM Fee Vigilantes Filing Reg E Lawsuits Against Credit Unions

Joe Spenski

Individuals across the country are filing lawsuits against credit unions and banks for failing to place surcharge notices on their ATMs.  Financial institutions in Michigan, California, and Illinois have been hit hard by the recent suits which claim that the terms of the Electronic Funds Transfer Act (EFTA, or Reg E)  are violated when the institution fails to post notice on or at the ATM that non-members will be assessed a surcharge.  More than 30 suits are pending in Michigan alone.

The language of EFTA requires an ATM customer be told up-front when a fee will be charged, how much the fee is, and the opportunity to cancel the transaction. Some of the lawsuits are class actions, which in theory could mean all of a credit union’s ATM customers may qualify for reimbursement.

http://www.ncua.gov/Resources/RegulatoryAlerts/Files/Prior2003/01-RA-06.pdf

http://www.fdic.gov/news/news/financial/2009/fil09066.html

http://www.cutimes.com/2011/01/13/big-spike-seen-in-atm-fee-disclosure-lawsuits

Regulation E and e-Statements

Jim Vilker, NCCO

The CU*Answers mantra has always been “we make the tools, not the rules.”  Regulation is always subject to interpretation and in some cases business risk.  When we developed the e-Statement platform, credit unions requested we give them the ability to physically enroll members at the time of account opening.  This request came from those credit unions that want and need to reduce statement cost and do it at the time the member is being sold credit union products.  

The e-Statement Compliance Tax

E-Statements are a major cost-reduction service but are not a once-and-done type of offering.   According to a recent article by attorney Brian Witt, this service comes with a compliance tax.  This tax comes in the form of understanding and keeping abreast of a few regulations including Regulation E, Regulation Z, e-sign act, and TIS.  

I have attached a copy of a recent web post related to auto enrolling members into e-statements without them giving the credit union an electronic affirmative consent.  This document is written as if this attorney’s interpretation is correct and is intended to give guidance on the proper management of the e-statement services.  Many CEOs that read this may become upset as this potential compliance risk has been weighed in the past and is now being challenged and publicized.

My only recommendation to those CEOs is to read on, speak with your own compliance attorney, and make sure you have a legal opinion on your process to justify your interpretation, if different from this one.

Say your practice is to enroll members by utilizing the opening workflow functions in CU*BASE in order to keep your e-statement penetration up.  To manage this in accordance with the opinion listed above you would need to pull the e-Statement enrollment report (menu MNRPTE option #19) and on the drop-down select “1 Not accepted the Use Agreement” prior to the end of the month.  The members listed on this report are those who you have physically enrolled but have not accepted the use agreement via It’s Me 247 online banking. 

When you pull this report you do have the capability to export the file.  Why?  Perfect opportunity to use the Member Connect email option and send this group of members an email with a link to online banking reminding them to log on accept the agreement.  You can also use Member Connect to populate a telemarketing group for outbound calls and call them directly. 

Those who do not accept the agreement would need to be un-enrolled. 

Projects on Tap at CU*Answers

To make the un-enrollment process even easier, our development team is working on specifications to add a new feature to CU*BASE that would help you un-enroll a batch of members from e-Statements according to your desired measurement (i.e., members who have not accepted the Use Agreement, or who have not logged on recently, or even those who have a bad email address).  Watch for a special announcement and a new page on the Kitchen coming soon.

A final note on the author of the attached publication:  Brian Witt is one of the best credit union compliance attorneys in the country and has worked closely with both CU*Answers and CU*NorthWest clients on issues related to compliance, loan forms, and working with regulatory bodies.Farleigh Wada Witt 3-4-11-Newsletter

Dormancy Webinar for Michigan Clients

Joe Spenski

Here is a copy of the Dormancy webinar from March 18th that was directed to our Michigan clients.

Dormancy-Michigan WebConference

Vilker’s Dirty Dozen

Jim Vilker, NCCO

This is a list of suggested projects that have made it to my radar and are currently being discussed here at CU*Answers. As you read through the list, you’ll notice a few that have been implemented already. Some are in process with our QC team, and still others are at the stage of specifications being written.

However, many of these suggestions remain on the drawing board and we do not anticipate ever turning them into projects unless they are championed by a client. Our continuing mantra is to design system features that create a least cost process in the credit union and meet the minimum requirements imposed by regulators and third party auditors. Some of these suggested projects just need credit unions to share best practices and existing methodologies to accomplish the task and do not even require software enhancements.

This list of suggestions, also known as Vilker’s Dirty Dozen, has grown to the traditional baker’s dozen and now stands at 13. Credit unions can comment on the suggestion, make recommendations, and participate in an online dialogue. This method is a valuable tool for gathering opinion, both pro and con, and we hope to use this forum to collect commentary that can be used not only to communicate CU*Answers’ stance but also to share best practices throughout the entire community.

It will take the persistence of clients who have reviewed this list, commented on the items, and participated in communications through focus groups or online dialogue to cause these projects to either morph into something real…or die for lack of a champion.

Download the Dirty Dozen in a PDF

1. Abnormal Activity Monitoring

Jim Vilker, NCCO

Activity – Excessive ACH activity on an account could indicate an account defined as personal is being used as a business account. Most transactions come from ATM providers, while others are excessive NSF returns. The credit union is often unaware that excessive and abnormal activity is occurring. These could be commercial accounts flying under the radar while purposely being used to avoid the scrutiny and due diligence required for accounts of this type. Flag these accounts as high risk when large withdrawals and corresponding deposits occur. They are invitations for money laundering and potential for money store accounts. Nearly every origin with excessive suspicious activity should be analyzed for potential fraud, money laundering, check kiting, and high risk activity.

Solution – Through system configuration, broaden the scope of reporting. Encompass an array of origin codes where the credit union can categorize the number and dollar amount of transactions as normal, abnormal, or high risk within a specified time period.

Status – Currently in specification writing.

2. BSA Enhancement: ATM Activity

Jim Vilker, NCCO

Activity – Member uses an ATM to deposit and withdraw funds to avoid scrutiny of the BSA tracking system.

Solution – Update the system to monitor for ATM cash activity in the BSA file. Model it after the feature used in shared branching activity.

Status – We went ahead and analyzed the data that is coming back from the ATM networks and discovered there is not consistency between switches and in some cases we have no idea if the transaction was a cash or check transaction. From a practical perspective this would throw off false positives and create a situation where the credit union could be filing CTRs erroneously. If this becomes a requirement by credit union auditors the credit union would need to write a Query and evaluate these transactions against the daily BSA logs.

3. BSA Enhancement: Joint Owner Activity

Jim Vilker, NCCO

Activity – Member avoids currency transaction monitoring by depositing cash into multiple accounts, some on which the member is the primary account holder and others as only a joint owner.

Solution – Enhance the BSA monitoring feature to enable account tracking on every account connected to the Social Security number of every member, regardless of classification: Primary Owner or Joint Owner.

Status – Investigations with the programming team finds this request to be an extremely complicated programming effort as at this time we do not record the Social Security number of the person performing the transaction. We are developing specifications for a change in the teller software where we would only display accounts on which the joint owner is allowed to transact business. When that feature goes go in we will reevaluate this suggestion. (Hence the thumbs up and down from Randy!)

4. BSA Enhancement: Layering

Jim Vilker, NCCO

Activity – Member gets a line of credit and wires the money out of the credit union, or they purchase giftcards through the miscellaneous receipts process. Member then makes large payments on the loan and each time the available limit grows, another wire transfer is made. Many times it is a wire. If the member receives the disbursement via cash, our BSA monitoring system picks it up and there’s a record of the transaction. Consequently the activity is the transfer to the wire G/L.

Solution – Review transactions on member LOCs against the wire transfer log and miscellaneous receipts log.

Status – In the envisioning stage and will require credit union interaction to formulate the specification and a champion to push this along.

5. Check Cashing Function

Jim Vilker, NCCO

Activity – Member comes in to cash a check and the teller uses the check cashing function which does not write out a transaction on the member’s account. Four issues: First, in most states this is prohibited on business accounts. Second, when reviewing BSA activity the auditor must also review the teller audit log. Third, when required to provide transaction information to legal authorities, most credit unions provide copies of the member statements and certify that this constitutes total activity on the account. If they do not consider audit logs as part of the information they provide they are signing the certification incorrectly. Fourth, if the check comes back NSF it is difficult to find what account to apply it against as it is not part of the transaction history.

Solution – Needs to be discussed further. Top of mind suggests that when the transaction occurs we would write out a zero $ transaction record to the member’s base share. Will require focus group interaction to determine the scope of this potential project.

Status – In the envisioning stage. However, this one remains one of Vilker’s pet peeves as it currently requires the BSA officer to review the audit logs when doing the daily BSA work.

6. Check Kiting Monitoring

Jim Vilker, NCCO

Activity – Members who make deposits at one institution using funds drawn from another financial institution, when that account has no balance, are guilty of Check Kiting. These members are “playing the float.” Viewed as suspicious in most cases, tellers are encouraged and even obligated to place extended holds on these accounts.

Solution – Review deposit and withdrawal activity on a checking account. When a pattern emerges where a deposit is made followed by a corresponding withdrawal within a short period of time, report these accounts as suspect. One metric to follow is when the withdrawal and deposit are within X percent (5%) of each other over an X (5) day period of time.

Check kiting can also be traced to excessive use of online banking. Another indicator is the frequent return of deposited items. Tying indicators together requires strong analysis, but is worth the investment. Whether manual or using software solutions you will apply the same investigative logic: look backward to find how often this account would have gone negative if the deposit had not been made within 24 hours.

Status – Very few clients are requesting this one; would require a credit union champion to push this along.With the suspicious activity monitoring option in the system, most CU*BASE clients review members who have had excessive online banking logins to detect kiting activity. This has been found to be a very reliable source of information to uncover the fraudster.

7. Critical Field Monitoring

Jim Vilker, NCCO

Activity – Currently credit unions must review the file maintenance logs to determine if the changes made to member accounts were completed correctly and with the proper authority.

Solution – Create a screen where the credit union could chose up to 15 different critical system fields which currently show on the file maintenance log. At the end of the day, populate a screen similar to the one used for BSA daily monitoring where the credit union would work these changes in real time.

Status – Still in the envisioning stage.

8. Debit/Credit Card Fraud Detection

Jim Vilker, NCCO

Activity – Member cards are compromised.

Solution – Create a flexible system configuration for the credit union to specify conditions to monitor as noted in the following situations:

  • Excessive PIN failure (add a counter to the login procedure)
  • Excessive cash withdrawals or cash advances
  • Members over the age of X have more than Y transactions (elder or minor abuse)

Status – There are very few clients requesting this and without a champion this one will die on the vine. Will probably also require focus group interaction to determine project scope.

9. FinCEN

Jim Vilker, NCCO

Activity – Credit unions are required to extract the FinCEN report and visually compare the reported list of names to see if any members are on the list. To date this has been done manually using Member Inquiry.

Solution – Pull the file into CU*BASE and automate a scan similar to the manner in which the credit union performs the OFAC check.

Status – Project # 25834 is awaiting implementation in the 11.0 release. Companion project for improvements to the file upload project is also in process with implementation expected second half 2011.

10. Identity Theft

Jim Vilker, NCCO

Activity – Member has not had any debit card or credit card activity (primarily Visa) for an extended period of time. A sudden onslaught of transactions in extraordinarily large amounts are one clue that this is identity theft. This activity has the potential for both loss of the card and card information. With the stolen identity, the perpetrators often purchase gift cards from retailers which they re-sell at a discount; or they take copious cash advances which are then used to purchase high-demand, easily liquidated goods such as electronics and jewelry.

Solution – Track the transaction history on debit and credit card accessible accounts and create a system configuration that allows tracking of a specified number of months since the last transaction. If transactions process after that time period, report any accounts having in excess of X number of transactions per day, which total at least X percentage of the specified limit or dollar amount.

Status – Still in the envisioning stage. The member transaction analysis software does retain the monthly activity by origin code and it is believed that we could use this data to monitor these activities.