Before the Fee Rule Goes Live, Replay the Customer's Day

A practical guide for community-bank and credit-union leaders on replaying realistic customer transaction sequences before approving deposit-account fee, overdraft, posting, or...

The fee change looks small in the approval packet.

One parameter. One effective date. One disclosure update. Maybe a few lines in the core release notes. Compliance signs off, operations confirms the amount, technology moves the setting, and everyone gets back to work.

Then a customer's Tuesday arrives.

A debit card authorization lands before payroll. A deposit posts later than expected. A recurring payment uses different transaction coding. The mobile app shows one balance while the posting engine uses another. The customer changes an overdraft choice in one channel, but the old value survives somewhere else.

The parameter did exactly what it was told to do.

That is not the same as saying the institution made the right decision.

Before a community bank or credit union approves a deposit-account fee change, overdraft setting, posting rule, or account-opening choice, management should replay a realistic customer day from beginning to end. Not a clean test account with one transaction. Use the sequence, timing, channels, holds, reversals, and edge cases that make the rule consequential.

This is where a compliance decision becomes technology governance.

A fee is the end of a system story

Customers experience the charge. The institution operates the machinery behind it.

That machinery may include the core, debit card processor, ATM network, digital banking platform, account-opening system, teller application, transaction-coding logic, funds-availability rules, overdraft preference, nightly processing, notice generation, general ledger, and complaint workflow.

A rule can be correct in one place and wrong in the full journey.

Consider a customer who opted out of overdraft service for one-time debit card transactions. Where is that choice stored? Which channel can change it? How quickly does the new value reach the core and card processor? What happens when the authorization occurs while funds appear available, but settlement occurs after intervening transactions? What notice is generated? Can a service representative see the same facts the posting engine used?

If the approval packet cannot answer those questions, it is approving policy language without proving system behavior.

The board does not need to review transaction code tables. The compliance or risk committee does not need to watch a four-hour batch job for entertainment. Senior leaders do need evidence that the rule customers were promised is the rule the technology will execute.

Example one: Regulation E turns consent into a system requirement

Section 1005.17 of Regulation E addresses overdraft services for ATM and one-time debit card transactions. The rule requires affirmative consent before an institution may assess a fee for paying those transactions through an overdraft service. Its official interpretation gets operationally specific. It discusses transaction coding, electronic opt-in methods, separate consent, confirmation, revocation, and situations in which authorization and settlement occur at different times.

Source: Consumer Financial Protection Bureau, Regulation E, Section 1005.17, “Requirements for overdraft services”: https://www.consumerfinance.gov/rules-policy/regulations/1005/17/

That is not merely a disclosure problem.

It is a data-state problem.

The institution has to capture the customer's choice, distinguish the relevant transaction types, propagate the choice to the systems that make fee decisions, preserve evidence, honor revocation, and prevent another channel or conversion from quietly changing the result.

A signed form in imaging does not help much if the posting system holds the opposite value.

Before approving a rule change, replay at least three states: opted in, opted out, and no recorded choice. Then change the preference through every supported channel and verify the result through authorization, settlement, fee assessment, notice, account history, and customer-service display.

The test should prove both outcomes. The eligible fee appears when every condition is satisfied. The fee does not appear when one required condition is missing.

Testing only the permitted charge is half a test.

Example two: TD Bank shows why the interface and the stored choice must agree

In 2020, the Consumer Financial Protection Bureau announced a settlement with TD Bank involving its optional overdraft service. The Bureau found that the bank charged some consumers overdraft fees for ATM and one-time debit card transactions without obtaining affirmative consent. It also described practices involving pre-checked enrollment, incomplete explanations, and enrollment without a customer's actual decision.

The order required an estimated $97 million in restitution to about 1.42 million consumers and a $25 million civil money penalty.

Source: Consumer Financial Protection Bureau, “CFPB Announces Settlement with TD Bank for Illegal Overdraft Practices,” August 20, 2020: https://www.consumerfinance.gov/archive/newsroom/cfpb-announces-settlement-td-bank-illegal-overdraft-practices/

TD Bank is much larger than most FinEdge readers' institutions. The scale is different. The operating lesson is not.

A customer choice can fail at several points. The employee explanation can be wrong. The screen can steer the answer. A box can be selected before the customer acts. The stored value can disagree with the document. A later system can assess a fee without checking the evidence behind the preference.

That means the approval test cannot stop with “the disclosure was reviewed.” Someone should open an account, make the choice, inspect the stored value, complete representative transactions, review the resulting fee decision, and retrieve the evidence exactly as compliance, audit, or an examiner would.

The best test account is not the one that makes the demo go quickly. It is the one most likely to expose a disagreement between promise and execution.

Example three: FFIEC maintenance guidance expects controlled change

The FFIEC Development, Acquisition, and Maintenance booklet tells examiners to review change-management processes, including change types, authorizations, and related risk assessments. It also points to configuration practices that validate implementation, maintenance documentation, security monitoring, and reporting to the board and senior management.

Source: FFIEC IT Examination Handbook, “Development, Acquisition, and Maintenance,” Section VII, Maintenance: https://ithandbook.ffiec.gov/it-booklets/development-acquisition-and-maintenance/vii-maintenance/

A deposit rule deserves that discipline because the change crosses business, compliance, technology, and customer experience.

The approval record should identify the requested behavior, affected products, systems and vendors, test scenarios, authorized change, effective date, backout method, reconciliation owner, and monitoring period. It should also state what result would stop deployment.

“Technology tested it” is too vague.

Tested what? Against which account states? In which channels? Using what transaction sequence? Compared with which policy and disclosure? Who reviewed the output? What happens if the first production day shows an unexpected fee pattern?

Small configuration changes are where organizations are tempted to replace evidence with familiarity. The field has been there for years. The vendor says the option is standard. The same team changed it last time.

All reassuring. None of it is a test result.

Put a customer-day replay in the approval packet

A useful packet can stay concise. Include five exhibits.

Describe the intended customer outcome in plain language. Name the products, transaction types, consent states, balances, timing rules, exceptions, and disclosures involved.

Show where the decision is captured, stored, transmitted, evaluated, posted, displayed, noticed, and reported. Include vendor systems and batch interfaces. One unexplained handoff is enough to change the result.

3. The replay scenarios

Use realistic sequences that include authorizations, holds, deposits, recurring items, reversals, delayed settlement, preference changes, and insufficient funds. Include one scenario that should produce a fee and several that should not.

4. The evidence comparison

Place the customer's recorded choice, system setting, transaction history, fee decision, notice, account statement, and service-screen view side by side. They should tell the same story.

5. The first-week control

Define who reviews fee volumes, reversals, complaints, exceptions, opt-in changes, and unusual product or channel patterns after launch. Name the threshold that pauses the rule and the person with authority to use it.

This is not an argument that every fee change belongs on the board agenda. It is an argument that material customer-impact rules deserve governance proportional to their consequence.

A committee can approve the policy. A vendor can configure the field. A disclosure can describe the choice.

The customer still experiences one connected day.

Replay that day before the rule goes live. It is much cheaper to find the contradiction in a test account than in a complaint file.

Board and executive discussion questions

1. Which deposit, overdraft, or transaction-fee rule creates the greatest customer or member impact if our systems apply it differently than our policy and disclosures describe? 2. What realistic transaction sequence would we require management to replay before approving the next material rule change, and what result would stop deployment? 3. During the first week after launch, which fee, reversal, complaint, or preference-change pattern would trigger an immediate pause and review?

Sources

• Consumer Financial Protection Bureau, Regulation E, Section 1005.17, “Requirements for overdraft services”: https://www.consumerfinance.gov/rules-policy/regulations/1005/17/
• Consumer Financial Protection Bureau, “CFPB Announces Settlement with TD Bank for Illegal Overdraft Practices,” August 20, 2020: https://www.consumerfinance.gov/archive/newsroom/cfpb-announces-settlement-td-bank-illegal-overdraft-practices/
• FFIEC IT Examination Handbook, “Development, Acquisition, and Maintenance,” Section VII, Maintenance: https://ithandbook.ffiec.gov/it-booklets/development-acquisition-and-maintenance/vii-maintenance/