Regions’ 2015 overdraft order described a misread rule, a warning not escalated and fixes that failed

The CFPB’s April 28, 2015 order, accepted by Regions Bank without admitting or denying the findings, traced unlawful overdraft fees to a misread rule, a manager’s unescalated conclusion and programming changes that failed. Its remedy put a consultant’s model under board oversight.

Looking Back revisits past weeks one at a time, up to the most recent, and asks what it meant for the banks, health systems and public agencies we serve. The series was written in 2026, with the benefit of hindsight, and each article says which week it looks back on.

Two-minute summaryThe dek and the first sentence of each section, quoted from the article

The CFPB’s April 28, 2015 order, accepted by Regions Bank without admitting or denying the findings, traced unlawful overdraft fees to a misread rule, a manager’s unescalated conclusion and programming changes that failed. Its remedy put a consultant’s model under board oversight.

  1. The week The order’s findings described what happened inside the bank.
  2. Interpretation: a working group’s reading of linked coverage The order is brief about the interpretive error.
  3. Escalation: a correct reading that stayed with a manager The order’s escalation finding travels furthest, in our reading.
  4. Implementation: system changes that did not work The order describes two implementation failures, in two products. [1] Both involved programming changes that did not do what the bank intended. [1] Both kept fees flowing after a decision to stop them.
  5. Remediation: refunds that missed people, and a model to find them Even that was incomplete.
  6. Where the argument is weakest The strongest objection is that we generalize from findings Regions did not admit. [1] That is true, and it limits what can be said about Regions.
  7. Checks for banks and credit unions These checks follow the four parts.
  8. With hindsight The 2015 order has run its course.

The week

On April 28, 2015, the Consumer Financial Protection Bureau issued a consent order against Regions Bank. [1] The order was filed that day as File No. 2015-CFPB-0009. [1] Regions had signed a stipulation dated April 27, 2015, consenting to the order “without admitting or denying any of the findings of fact or conclusions of law or wrongdoing,” except jurisdiction. [1]

The order described Regions as a regional bank headquartered in Birmingham, Alabama. [1] It said the bank operated approximately 1,700 branches and 2,000 ATMs across sixteen states. [1] It said the bank had $119.2 billion in total assets as of September 30, 2014. [1]

The Bureau identified three violations. [1] First, it found Regions failed to obtain an affirmative opt-in from certain customers before charging overdraft fees on ATM and one-time debit card transactions, in violation of Regulation E. [1] Second, it found Regions deceptively represented that it would not charge those fees without an opt-in. [1] Third, it found Regions deceptively represented that it would not charge overdraft fees on repayments of its deposit advance product. [1]

The rule at issue was the Opt-In Rule in Regulation E. [1] The order said the Federal Reserve Board adopted it in 2009 to change what the order called a “pervasive industry practice.” [1] It required affirmative consent before a fee for paying ATM and one-time debit card overdrafts. [1] Its mandatory compliance dates were July 1, 2010 for new accounts and August 15, 2010 for existing ones. [1]

The order’s findings described what happened inside the bank. Shortly after the Board published the rule in November 2009, Regions formed a working group to implement it. [1] The working group “erroneously determined” that the rule did not apply to customers whose accounts had linked coverage, a service that moved money from savings or a credit line to cover a transaction. [1]

By August 2011, the order said, a mid-level manager concluded the linked overdraft fees likely violated the rule. [1] The issue was not escalated to senior executives, and the Legal department was not informed. [1] Systems changes attempted from November 2011 were found inadequate in February 2012, and the fees continued. [1]

The compliance department and others raised the issue with Legal in April 2012, at a governance working group. [1] Regions reported a regulatory issue to the Bureau in May 2012. [1] In June 2012 it adopted system changes that stopped the fees, which the order described as “ten months after the mid-level manager had first concluded” there was a likely violation. [1]

The order found that linked-coverage consumers paid at least $47 million in fees requiring an opt-in, between July 1, 2010 and June 2012. [1] Regions had reimbursed 198,387 consumers $34,946,530 in December 2012, and another $12,891,088 in December 2013. [1] In January 2015, Regions identified an additional limited group of consumers still being charged unlawful fees. [1]

The order required a $7.5 million civil money penalty. [1] It required the bank to retain a consultant to verify full redress, under a proposal subject to the non-objection of the Bureau’s regional director. [1] It required the bank’s board to review every submission to the Bureau. [1]

Overdraft enforcement can look like a story about fees and the customers who pay them. The Regions order is better read as a story about a compliance program’s plumbing. Every failure it describes happened between people and systems inside one bank, in the Bureau’s account. [1] The order does not describe any of them as intended. [1]

Our argument is that the order describes four distinct failures, each of which a well-run program can test for. A rule was read wrongly at implementation. A correct reading reached a manager and stopped there. System changes meant to stop the fees failed, more than once. Remediation missed a group of customers for years. [1]

Each failure belongs to a different part of a bank’s operating model. Interpretation belongs to a project team and its legal advisers. Escalation runs through reporting lines and governance forums. Implementation is the work of technology and operations. Remediation falls to whoever owns the customer data. [1] In our reading, the order is a map of hand-offs that can break.

These are Bureau findings, which Regions neither admitted nor denied. [1] We use them as the Bureau stated them, and draw lessons for any institution, not conclusions about Regions’ conduct beyond the order.

How this applies differs by institution. A regional bank of Regions’ size has a compliance department, a Legal department and governance forums, all of which appear in the order. [1] A community bank or credit union may have one compliance officer and outside counsel. The four hand-offs still exist; they just pass through fewer people. In our reading, a smaller institution’s risk is that one person holds two roles and the check between them disappears.

We take the order in four parts:

  1. Interpretation: how a working group read the Opt-In Rule as not applying to linked coverage.
  2. Escalation: how a manager’s conclusion stayed below senior management and Legal.
  3. Implementation: how system changes to stop the fees, and to stop fees on the deposit advance product, failed.
  4. Remediation: how refunds missed consumers, and what the order required to find them all.

The parts do not overlap. The first is about reading a rule, the second about moving a concern upward, the third about changing systems and the fourth about making customers whole. Together they cover the order’s account from rule to refund. After them we take the strongest objections, and end with checks for banks and credit unions.

Interpretation: a working group’s reading of linked coverage

The order is brief about the interpretive error. It says the working group “erroneously determined” that the rule did not apply to accounts with linked coverage. [1] It does not say why. [1] The consequences it lists are concrete. Regions did not obtain opt-ins from linked-coverage customers, and did not reprogram systems to stop linked overdraft fees. [1]

Where the confusion could arise

The regulation’s text offers a possible source. Regulation E defines “overdraft service” and lists exclusions. [3] One exclusion is “a service that transfers funds from another account held individually or jointly by a consumer, such as a savings account.” [3] The transfer itself is outside the rule. [3]

The fee the order addressed was different. A linked overdraft fee was the fee for paying a transaction that “exceeded the balances of both the Account and linked account.” [1] At that point the bank was paying an overdraft beyond the linked funds. [1] In our reading, a team reading the exclusion quickly could treat the whole linked product as outside the rule. The order does not say that is what happened.

Why interpretation is an operations question

Implementation teams translate rules into system requirements. A rule’s scope becomes a list of account types, transaction codes and fee codes. [1] An error in that list is copied into every system that consumes it. The Regions error reached opt-in prompts and fee logic at once. [1]

The order’s remedy shows how the Bureau saw that link. It required a plan, subject to the regional director’s non-objection, to assure that “policies, procedures and processing systems” comply with Regulation E. [1] Policies and systems appear in one requirement. In our reading, the Bureau treated the interpretation and its coding as one control.

How one reading produced a deception finding

The interpretive error had a second consequence. The order found that “a number of” Regions’ account materials wrongly stated that it would not charge overdraft fees for ATM and one-time debit card transactions unless consumers opted in. [1] For linked-coverage customers, the bank did charge them. [1] The Bureau found those representations deceptive. [1]

In our reading, that finding shows how an interpretation travels. The disclosures were written to the rule as the bank described it to customers generally. [1] The systems were built to the working group’s narrower reading. [1] The two did not match for one group of customers, and each mismatch became a separate violation in the order. [1]

For a program, the fix is to scope disclosures and systems from the same document. If the scoping memo excludes a product, the disclosure team should see that exclusion and ask whether customers are told. A mismatch found in review is cheaper than one found by a regulator.

What a second reading would have tested

Rule implementations involve judgment calls. A program can make those calls visible. A scoping memo can list each product and each fee, with the rule section that covers or excludes it. A second reader, from Legal or compliance outside the project team, can sign off.

Linked coverage is the kind of edge case such a memo surfaces. It lies at the boundary of an exclusion. [3] A fee that applies only when two balances are exhausted is easy to miss in a product-level review. In our reading, the test is to list fees, not products, because fees are what the rule restricts. [3]

Differences by type of institution

The Opt-In Rule applies to financial institutions holding consumer accounts, including banks and credit unions. [3] The order noted that Regions was an insured depository institution with assets greater than $10 billion, within the meaning of 12 U.S.C. 5515(a). [1] Smaller banks and credit unions are subject to the same rule. [3]

Smaller institutions may rely on core processors for fee logic. A credit union that configures overdraft settings in a vendor’s system faces the same interpretation risk, with less in-house coding. The scoping decision is still the institution’s. In our reading, a vendor’s default settings are an interpretation the institution adopts unless it reviews them.

What the rule asks of each account

The rule’s mechanics show how much an implementation must touch. A financial institution may not charge the fee unless it provides a written notice, segregated from other information, describing its overdraft service. [3] It must give a reasonable opportunity to opt in, obtain the consumer’s affirmative consent, and confirm that consent in writing with a statement of the right to revoke. [3]

The rule adds conditions that reach product design. An institution may not condition payment of overdrafts on checks or ACH transactions on the consumer opting in for debit card and ATM transactions. [3] It must give consumers who do not opt in the same account terms, conditions and features, apart from the overdraft service itself. [3] The notice must be substantially similar to the model form in the regulation’s appendix. [3]

Each requirement becomes a system feature: a notice template, a consent capture screen, a status flag, a confirmation letter, a revocation path. [3] A product left out of scope misses all of them at once. In our reading, that is why the Regions error reached both opt-in prompts and fee logic: the scope decision fed every downstream feature. [1]

Escalation: a correct reading that stayed with a manager

The order’s escalation finding travels furthest, in our reading. By August 2011, a mid-level manager concluded the linked overdraft fees likely violated the rule. [1] The order calls that “13 months after the Opt-In Rule’s mandatory compliance date.” [1] At that time, “the issue was not escalated to senior bank executives,” and Legal was not informed. [1]

The manager’s conclusion was right, by the Bureau’s account. [1] What failed was the path from that conclusion to people who could decide. The order does not say why the issue stayed where it was. [1] It records that mid-level management then tried to arrange systems changes, starting in November 2011. [1]

Fixing alone versus escalating

Mid-level management’s response was to fix the problem. [1] That is a natural instinct for operations staff. A fix can keep work inside the team and avoid alarm. It can also keep the issue away from Legal, which would ask whether customers were owed money and whether a regulator should be told.

The order’s timeline shows the cost. The attempted fix failed in February 2012, and the fees continued. [1] Legal learned of the issue in April 2012, through compliance and a governance working group. [1] In May 2012, the bank reported to the Bureau and said it would reimburse. [1] In our reading, escalation, once it happened, moved things faster than the earlier attempt to fix the problem alone.

Self-reporting and its value

The order records that Regions reported a regulatory issue to the Bureau in May 2012 and said it intended to reimburse unlawful fees. [1] It records the refunds that followed in December 2012 and December 2013. [1] The deposit advance problem was reported in November 2013, after its correction. [1]

The order does not say how self-reporting affected the penalty. [1] It cites the statutory factors the Bureau took into account in setting the $7.5 million amount, without listing how each applied. [1] Institutions should not read a specific discount into the figure.

Self-reporting still changes the record. A bank that reports can describe the problem, its cause and its fix in its own terms, before an examiner frames it. The order’s timeline is built from the bank’s own internal events and discoveries. [1] In our reading, that is the posture an escalation program is designed to produce.

The governance forum that worked

The order names the forum where the issue surfaced. It was raised at an April 2012 governance working group “called the Compliance/Fair & Responsible Lending Touchpoint.” [1] The Legal department then addressed the issue with senior executives. [1]

That detail matters for program design. A standing forum where compliance, business lines and Legal meet gave the issue a place to land. [1] Without it, the issue depended on individuals deciding to raise it. In our reading, the order shows a governance meeting doing the job a reporting line had not.

What an escalation standard looks like

Banks can write escalation triggers. A conclusion that a fee “likely” violates a rule is one. A trigger can require notice to compliance and Legal within a set number of business days, whatever the business line thinks of the fix. The trigger turns a judgment into a duty.

Triggers need a record. An issue log that captures who concluded what, and when, gives examiners and boards the timeline the Bureau reconstructed in this order. [1] It also protects the employee who raised the issue. A manager who logs a concern has done the job, whatever happens next.

Training matters too. The person who first sees a problem may sit in operations or product, far from compliance. They need to know that a possible violation is an escalation item, not a ticket. In our reading, the Regions order is a useful training case because the first person to see the problem saw it correctly.

A hypothetical timeline with a trigger

Consider how the same facts might run with a written trigger. A hypothetical manager concludes that a fee likely violates a rule. The trigger requires notice to compliance and Legal within five business days. Legal reviews the reading and agrees.

From there, the steps the order describes come earlier. The institution can stop the fee by a manual override while a permanent fix is built. It can begin sizing refunds. It can decide whether and when to report to its regulator. Each of those decisions in the Regions order followed Legal’s involvement in April 2012. [1]

The trigger does not guarantee a perfect fix. The Regions order shows a fix can fail even after escalation, as the deposit advance product did in 2013. [1] What the trigger changes is who knows. In our reading, the order’s escalation gap is the one failure a written rule can most directly close.

Workforce and incentives

Escalation has a human cost for the person who raises it. It can mean admitting a team’s error or triggering a costly refund. Programs that treat escalation as a performance positive make it easier. That is an inference about human behavior, not a finding in the order. [1]

The order did reach individuals in one way. It required the bank to deliver a copy to board members, executive officers and managers and employees with related responsibilities. [1] Each had to sign an acknowledgment. [1] For five years, new people taking on those responsibilities had to receive it too. [1]

Implementation: system changes that did not work

The order describes two implementation failures, in two products. [1] Both involved programming changes that did not do what the bank intended. [1] Both kept fees flowing after a decision to stop them.

The two cases differ in origin. The linked-coverage fees came from a misread rule; the deposit advance fees came from the bank’s own decision to stop charging. [1] In the first, the system did what the working group intended. In the second, it did not do what the business intended. [1] Both ended with customers charged fees the bank’s materials said would not apply. [1] In our reading, the common thread is that nobody checked the fees actually charged against what the bank had promised.

Linked overdraft fees

From November 2011, mid-level management tried to arrange systems changes to stop linked overdraft fees. [1] In February 2012, those changes were judged inadequate and not implemented. [1] The fees continued until June 2012, when the bank adopted changes that stopped them. [1]

The order does not say why the first changes were inadequate. [1] It records the attempt beginning in November 2011 and the fees continuing until June 2012. [1] In our reading, every month in between added fees that would later need refunds.

Deposit advance repayments

The second failure involved Regions Ready Advance, which the order describes as a small-dollar line of credit offered from May 2011. [1] Around August 2011, the bank decided to stop charging overdraft and insufficient funds fees on certain repayments. [1] Programming changes made between August and November 2011 stopped insufficient funds fees but let overdraft fees continue. [1]

In November 2011, the bank issued frequently asked questions saying, in substance, that an overdraft fee would not be charged on the repayment itself. [1] Because the programming had failed, the bank did charge such fees. [1] The Bureau found the statement deceptive. [1]

A second error followed. In April 2013, changes to the product introduced a programming error that began charging insufficient funds fees on some repayments again. [1] The bank discovered the problem around June 2013, corrected it on August 28, 2013, and reported it to the Bureau in November 2013. [1] The order found at least $1.9 million in such fees, and said the bank refunded approximately $1,925,000 to approximately 36,214 consumers in December 2013. [1]

Disclosure followed the decision, not the system

The deposit advance finding has a specific lesson. The bank updated its customer materials to reflect “what it believed to be its new practice.” [1] The system did not match. [1] Disclosure was written from the business decision; the code was what customers experienced.

In our reading, the control that would catch this is testing before publishing. A disclosure that says a fee will not be charged should be checked against transaction data showing the fee is no longer charged. That is a production test, run on real accounts, not a requirements review.

Change control for fee logic

Fee logic is code that moves customer money. It deserves the same change control as payment code. That means test cases written from the rule and the disclosure, a check of production results after release, and a named owner for each fee code.

The April 2013 error shows why regression testing matters. A change for one purpose broke a fix made for another. [1] A test suite that included “no insufficient funds fee on these repayments” would have failed. In our reading, the second error was a missing test, not a misread rule.

What an examiner would ask to see

Implementation failures leave evidence. An examiner reviewing a fee change can ask for the requirement, the change ticket, the test cases, the test results and a post-release check of production fees. Each document shows a step that either happened or did not.

The Regions order shows why the post-release check matters most. In both products, the bank believed a change had worked. [1] For the deposit advance product, it published materials on that belief. [1] A report of fees charged after the change, by fee code and product, would have shown the problem. [1]

Such reports are cheap to build once and run monthly. They can compare fees charged against the institution’s current fee rules and flag any fee the rules say should not occur. In our reading, a monthly exception report on fee codes is one of the simplest controls the order suggests.

Vendors complicate this for institutions that use them. When a core processor makes the change, the institution must still verify the result. Contracts can require test evidence. Institutions can run their own post-release checks on fee data. Neither depends on the vendor’s internal process.

Remediation: refunds that missed people, and a model to find them

Regions began refunding before the order. [1] In December 2012 it reimbursed 198,387 consumers a total of $34,946,530. [1] The Bureau then determined that these efforts “had not fully captured the total amount of consumer harm.” [1] Regions refunded an additional $12,891,088 in December 2013. [1]

Even that was incomplete. In January 2015, the bank identified an additional limited group of consumers incurring unlawful fees. [1] The order said the bank had failed to detect them in 2012 and 2013, so “the unlawful fees persisted until 2015.” [1] Remediation had a gap of its own.

What the order required to find everyone

The order’s answer was a model, built by a consultant and checked by the Bureau. [1] Within 15 days, the bank had to propose a consultant, describing its experience in analyzing deposit systems. [1] It had to disclose all work the consultant had done for the bank in the prior five years and any shared financial interest. [1]

The consultant had to identify every data source relevant to a consumer’s opt-in status at a given time. [1] That included the system the deposit platform consults at transaction time, systems logging notices to consumers, and any daily journal of opt-in status. [1] It had to identify every transaction code used for one-time debit card and ATM transactions. [1]

The consultant had to build a model from those sources, validate it by sampling or other methods, and refine it until validation showed it was accurate. [1] It had to interview employees with operational knowledge of the deposit system, “including technicians,” and keep detailed notes. [1] The bank had to append the notes and “all statistical codes and algorithms used in the Model” to its report. [1]

Why the order went down to transaction codes

The earlier refunds had missed people. [1] In our reading, the order’s detail closes the paths by which people could be missed: a data source not consulted, a transaction code not mapped, a status not tracked over time. Each step names a place where an earlier search could have fallen short.

Opt-in status is a history, not a flag

The order’s definition of an unlawful fee turned on the consumer’s opt-in status at the time of each transaction. [1] It covered fees where the bank “had not previously obtained” the opt-in, or where the consumer “had revoked such Opt-In.” [1] That requires knowing status on a given past day as well as today.

The rule explains why status changes. Consent lasts until the consumer revokes it or the institution ends the service. [3] A consumer may revoke at any time, and the institution must implement a revocation “as soon as reasonably practicable.” [3] A remediation search that reads only current status will misjudge every consumer whose status changed.

The order’s requirement to find “any system that maintains a daily journal” of opt-in status addresses that problem. [1] For an institution building its own controls, the point is plain. Keep a dated history of opt-in status and of each notice sent. The next remediation, or the next exam, will need it.

The requirement to interview technicians is notable. It recognizes that knowledge of how a deposit system records opt-in status may sit with the people who maintain it, not with policy owners. [1] For a remediation team, that is practical advice. The people who know where the data hides are in operations.

Validation is the step that makes the search defensible. The order required the consultant to validate the model “using sampling or other acceptable validation methods,” and to keep refining it until validation showed it was accurate. [1] A sample of accounts checked by hand against the model’s output tests whether the model finds the people it should. In our reading, a remediation without a validation step is an estimate, and the 2015 order did not accept an estimate. [1] The Redress Report also had to set out the model’s logic, parameters, assumptions and the reasons for including or excluding each data source. [1]

Making customers whole beyond the fee

The order reached secondary harm. Within 90 days, the bank had to find any negative credit reporting that would not have happened but for the unlawful fees, and have it expunged. [1] It had to find accounts closed because of negative balances caused by the fees, and correct reporting to ChexSystems. [1]

It also reached former customers. Additional redress had to be paid whether or not the consumer still held an account, by credit or by mailed check. [1] The bank could not condition redress on a consumer waiving any right. [1] After paying, it had to conduct an internal audit of its compliance with the redress obligation. [1]

The board’s role

The order made the board accountable for the process. The board had to review all submissions, including plans and reports, before they went to the Bureau. [1] It had “ultimate responsibility for proper and sound management” and for compliance with the order. [1] Compliance reports at 90 days and one year had to be board-approved. [1]

In our reading, those provisions answer the escalation failure directly. The order’s findings began with an issue that was not escalated to senior executives when a manager first identified it. [1] Its remedy required the most senior governance body to see every step. [1]

Records, complaints and later actions

The order also required records that would help the next review. The bank had to keep, for at least five years, documents showing compliance, the redress analysis and payments, and final versions of disclosures and marketing for the affected products. [1] It had to keep all consumer complaints and refund requests about overdraft or insufficient funds fees, and its responses. [1]

Complaints are an early warning that the order treated as evidence. A complaint that a customer was charged a fee the disclosures said would not apply is the same signal the manager saw in 2011. [1] In our reading, a complaint program that routes fee complaints to compliance is part of the escalation system.

The order addressed related cases. The bank had to notify the Bureau within 30 days of any final judgment or settlement in a related consumer action, with the redress paid. [1] It had to notify the Bureau of changes such as mergers or new affiliates that could affect compliance. [1]

Terms on the penalty

The order limited how the bank could treat the penalty. It could not claim a tax deduction or credit for it. [1] It could not seek reimbursement or indemnification, including under an insurance policy. [1] The penalty went to the Bureau’s Civil Penalty Fund. [1]

Those terms have an operational side. Risk and finance teams that model enforcement costs should not assume insurance or tax relief for a civil money penalty under a Bureau order with these terms. [1] Redress is a separate obligation, paid to consumers. [1]

Where the argument is weakest

The strongest objection is that we generalize from findings Regions did not admit. [1] That is true, and it limits what can be said about Regions. It does not limit what other institutions can learn. The four failures are failure modes any institution can test for, whatever happened at one bank.

A second objection is that the error was a reasonable reading of an unclear exclusion. The regulation does exclude transfers from linked savings accounts. [3] But the order found the fee at issue was for paying beyond both balances. [1] And the order found a manager reached the correct reading by August 2011. [1] The interpretive question was answerable inside the bank.

A third objection is that the bank self-reported and refunded before the Bureau acted. [1] That counts in its favor, and the order records it. [1] The penalty was $7.5 million against redress the Bureau’s page puts at approximately $49 million. [1] [2] Our point is about the months before self-reporting, when the issue stayed below Legal. [1]

A fourth objection is that operational failures like these are unavoidable at scale. Some error is. The order’s findings concern the time between knowing and acting, and the completeness of the search afterward. [1] Both are within a program’s control.

A fifth objection is cost. A consultant-built, validated model with interview notes and code appendices is expensive. [1] Few self-identified errors justify that effort. We agree the order’s process is heavy. A smaller version, a documented search across data sources and transaction codes with a sample check, scales down. The principle of searching every path holds at any size.

A last objection concerns the later Regions order, which involved a different practice. [4] We cite it only for what it shows about the same rule area and the same bank’s later findings, not to suggest the 2015 order failed. The two orders concern different fees and different facts. [1] [4]

Checks for banks and credit unions

These checks follow the four parts. Institutions should confirm the rules that apply to them with counsel and their regulators. [3]

Interpretation

  • List every overdraft-related fee code and map each to the rule section that covers or excludes it, including linked-account fees. [3]
  • Have someone outside the implementation team review scoping decisions on edge cases.
  • Treat a core processor’s default fee settings as decisions the institution must review.

Escalation

  • Make a conclusion that a fee “likely” violates a rule an escalation trigger to compliance and Legal. [1]
  • Keep an issue log that records who concluded what, and when. [1]
  • Give compliance, business lines and Legal a standing forum where such issues land. [1]

Implementation

  • Test fee logic changes against transaction data in production before relying on them. [1]
  • Check customer disclosures against actual fee behavior, not the business decision. [1]
  • Include past fixes in regression tests, so a later change cannot undo them. [1]

Remediation

  • Identify every data source and transaction code that bears on who was harmed, and validate the search by sampling. [1]
  • Interview the technicians who maintain the systems, and keep notes. [1]
  • Correct credit and account reporting caused by the fees, and pay former customers too. [1]

Records

  • Keep a dated history of each consumer’s opt-in status and each notice sent. [3]
  • Route complaints about unexpected fees to compliance as possible signs of a rule problem. [1]

With hindsight

The 2015 order has run its course. Its own terms said it would terminate “5 years from the Effective Date,” subject to conditions. [1] As checked on November 16, 2026, the Bureau’s enforcement page listed the action’s status as “Expired/Terminated/Dismissed.” [2] The page said the order required redress totaling approximately $49 million and a $7.5 million penalty. [2]

The Opt-In Rule is unchanged in substance. As checked on November 16, 2026, the eCFR text of 12 CFR 1005.17 still bars a fee for paying ATM and one-time debit card overdrafts without the consumer’s affirmative consent. [3] The exclusion for services that transfer funds from another account remains. [3] The section’s source note cites its December 2011 publication and a 2016 amendment. [3]

Regions faced a second overdraft order. On September 28, 2022, the Bureau issued a consent order against Regions Bank concerning what it called “Authorized-Positive Overdraft Fees.” [4] Regions consented without admitting or denying the findings, except facts needed for jurisdiction. [4]

The 2022 order concerned a different practice. It found the bank charged overdraft fees when a transaction had sufficient funds at authorization but settled with insufficient funds. [4] It found the bank generated at least $141 million in such fees from August 2018 through July 2021. [4] It found the bank was aware that agencies had found such fees unlawful at other institutions. [4]

The 2022 order also found the bank continued the fees while it pursued changes to generate alternative fee revenue to offset the expected loss. [4] It said the bank eliminated the fees in July 2021. [4] It found that in a 2016 internal survey, nearly seven hundred associates identified overdraft and insufficient funds fees as the hardest problem to resolve with consumers. [4]

In our reading, that last finding echoes the 2015 escalation theme in another form. Front-line staff saw customer confusion; the order found the practice continued for years. [4] The two orders involve different fees and different findings. [1] [4] Both turn on what an organization did with information its own people held.

The 2022 order required a $50,000,000 civil money penalty and a reserve of not less than $141,000,000 for redress. [4] On July 21, 2025, the Bureau filed an order terminating it. [5] That order said Regions had fulfilled certain obligations, including paying the penalty and issuing payments under the redress plan. [5] It terminated the consent order and waived any alleged noncompliance. [5]

The broader overdraft rulemaking took a different turn. On December 30, 2024, the Bureau published a final rule on overdraft credit by very large financial institutions, those with more than $10 billion in assets. [6] It was to take effect on October 1, 2025. [6] The rule said it did not change the framework for institutions with $10 billion or less. [6] It described the existing opt-in requirement for one-time debit card and ATM transactions under Regulation E. [6]

Congress disapproved that rule. A joint resolution approved on May 9, 2025 said the rule “shall have no force or effect.” [7] The opt-in requirement in Regulation E was not part of that rule and remained in the eCFR, as checked on November 16, 2026. [3] [7]

What held up from 2015 is the operational lesson. The rule Regions misread is still the rule. [3] The failures the order described, in interpretation, escalation, implementation and remediation, do not depend on any later rulemaking. [1] What changed around it is the rulemaking climate: a final overdraft rule published on December 30, 2024, and its disapproval on May 9, 2025. [6] [7]

Spotted an error? Tell us and we will check it and correct the article where needed.

  • overdraft
  • Regulation E
  • CFPB
  • consent order
  • compliance escalation
  • remediation