Brokered Deposits Compliance Checklist for Banks and Fintech Partners
On August 23, 2024, the FDIC published a proposal to revise brokered-deposit rules. On March 3, 2025, it withdrew that proposal. This page is not about implementing the withdrawn NPRM. It is the practical operating guide for banks and fintech partners that need to review a live deposit program under the still-operative December 2020 framework.
The focus here is simple: can the bank explain the deposit flow, defend the partner role, show who owns the relationship, and produce the records an examiner or counsel will ask for without rebuilding the file from scratch?
Where Programs Usually Break
Brokered-deposit problems usually start as business-process problems. A program can look clean on a slide deck and still be hard to defend if the bank cannot show who sourced the funds, how the customer was reached, what the partner is allowed to do, and how the bank controls the flow of money. That is why the review has to start with operations, not labels.
- The money flow is unclear.
- The intermediary role is not documented well enough.
- The contract stack does not match how the product actually works.
- The bank cannot quickly produce the right records during an exam or review.
If any of those points are fuzzy, the bank is already behind. The goal is not to make the file sound sophisticated. The goal is to make it easy to defend.
The Checklist
1. Map the deposit flow end to end
Start with the mechanics. Identify where the deposit comes from, who touches it, who markets it, who decides on account opening, and who controls the customer experience. If the flow cannot be explained in one clean chain, the program needs work before it needs more growth.
For review purposes, the team should be able to point to the exact moment the customer relationship becomes a deposit relationship, the exact party that introduces the customer, and the exact systems used to move the funds. That map should live in the file, not only in the heads of product or treasury staff.
2. Define the intermediary role precisely
Many disputes in this area come from loose language. Teams often say a partner is only a marketing vendor when the actual file shows the partner is doing much more than that. Clear role definitions help answer the broker question before it becomes a post hoc argument.
Make the role statement specific enough that a non-lawyer can tell whether the partner is introducing, assisting, placing, onboarding, routing, or servicing. If the same partner is doing multiple jobs, separate those functions in the memo so the analysis does not blur together.
3. Review contracts, disclosures, and incentives together
The contract cannot say one thing while the sales deck says another. That mismatch is where programs get exposed. Review the commercial terms, the customer-facing disclosures, the incentive model, and any language about account placement or transfer rights as one package.
- Check whether the agreement matches the actual deposit journey.
- Check whether fees or incentives could change the regulatory analysis.
- Check whether the bank can explain the partner relationship in plain English.
This is also where legal, compliance, treasury, and vendor-management teams need to sit at the same table. If each group reviews the relationship from a different angle without a shared summary, the final file usually becomes inconsistent.
4. Preserve the records the examiner will ask for
A strong file usually includes the vendor agreement, product memo, board or committee approval, deposit-source documentation, and a simple internal explanation of why the program fits the bank’s funding strategy. Without those records, a team can be technically right and still lose the narrative.
The file should also show who approved the structure, when the approval happened, what changed afterward, and whether any changes triggered a re-review. If the relationship has evolved since launch, the documentation should show that evolution rather than pretending the program has stayed static.
5. Build a refresh cycle
Programs change. Marketing changes. Vendors change. Customer journeys change. If the team never rechecks the file, the bank can drift into a structure that no longer matches the documentation. A quarterly or semiannual review is usually more valuable than a one-time legal memo that gets filed and forgotten.
Use the refresh to confirm whether the partner scope, incentive structure, onboarding flow, and service model still match the original analysis. If they do not, the issue should be fixed in the file and, if necessary, in the operating process.
Operational Review Sequence
For live programs, the cleanest way to run the review is in sequence. First, confirm the deposit map. Second, test the partner role. Third, compare the paper to the reality. Fourth, check the approval history. Fifth, decide whether the program should continue as-is, be re-documented, or be paused.
- Step 1: pull the current product flow diagram and customer journey.
- Step 2: pull the latest bank-partner agreement and any amendments.
- Step 3: pull customer disclosures, scripts, FAQs, and marketing materials.
- Step 4: pull treasury, compliance, and vendor-management approvals.
- Step 5: confirm who owns remediation items and the next review date.
This sequence matters because it keeps the team from jumping straight to legal conclusions before the operational facts are confirmed. A bad map can make a good legal opinion useless.
Who Should Own What
Bank counsel should own the legal classification and the escalation path. Compliance should own the control testing and file discipline. Treasury should own the funding rationale and concentration review. Vendor management should own the third-party lifecycle record. Product and operations should own the actual customer journey and the change log. Fintech partners should own the accuracy of their materials and the behavior of their frontline teams.
If no one owns the relationship after launch, the program will age badly. The best file in the world will not stay current if it does not have an assigned owner, a review cadence, and a place to send exceptions.
What Fintech Teams Need To Document
Fintech partners need a different kind of review because the legal risk is often embedded in how the partner presents the product and how the bank treats the partner’s role. A clean partnership memo should explain whether the partner is merely introducing customers, assisting with onboarding, or operating in a way that could be read as deposit placement activity.
The memo should also say who can change scripts, who approves customer-facing language, who reviews referral compensation, and who signs off on product changes before launch. If the partner can influence the customer experience, the bank should know exactly how that influence is controlled.
If the bank cannot explain that boundary, the product should not move to scale yet. That is especially true where a rapid growth plan depends on deposits sourced through digital channels.
Board And Committee Reporting
Good governance does not stop at the contract. The board or the relevant committee should receive a short, repeatable summary that covers the product’s purpose, current deposit volume, partner concentration, key exceptions, open remediation items, and any material changes to the flow or control structure. The point is not to overwhelm directors with detail. The point is to prove the bank knows what it owns.
A useful reporting package answers three questions: is the program still within appetite, are the controls still current, and is the file still consistent with the way the product actually runs?
What To Ask Before Launch Or Renewal
- Can the team describe the deposit flow without a legal translation layer?
- Does the partner have any authority to place or move funds?
- Are the customer disclosures consistent with the legal analysis?
- Is there a single owner for the relationship after launch?
- What changes would require the file to be reopened?
- Has anyone compared the live process to the 2020 framework baseline recently?
If the answer to any of those questions is “not sure,” that is a signal to pause and tighten the file before the relationship grows further.
Share your details and we’ll follow up shortly.
Red Flags In A Brokered-Deposit Program
Most bad files show the same warning signs. The bank cannot explain the partner role in plain English. The sales deck overstates what the partner does. Incentives change faster than the legal review. Or the funding strategy depends on a channel that nobody rechecks after launch. Once those issues stack up, the program becomes difficult to defend even if nobody can point to a single dramatic failure.
- The contract says one thing, but the customer journey does another.
- The bank cannot produce a current source-of-funds map.
- Marketing language and legal language do not match.
- No one owns the periodic refresh of the relationship.
A separate warning sign is when the team starts talking about the withdrawn 2024 proposal as if it were a live implementation project. That framing is off. The right question is whether the current program is being governed well enough under the existing framework.
What A Clean File Should Show
A clean file should let someone unfamiliar with the program answer five questions quickly: who solicited the deposit, what the bank approved, how the customer got to the account, whether incentive payments exist, and why the structure fits the bank’s funding profile. If the answers are buried across too many emails or version-controlled documents, the team has not built a durable record yet.
That file standard is especially important where a bank is using a fintech partner to scale deposits. A program can be commercially successful and still be under-documented. The point of this checklist is to keep those two ideas from drifting apart.
Questions To Ask During A Live Review
- Are the current deposit flows the same as the ones described in the original memo?
- Has the partner changed its scripts, landing pages, or service model?
- Do treasury, compliance, and vendor management all have the same version of the relationship summary?
- Has the bank re-tested the escalation path for exceptions?
- Are there any new concentrations, volume spikes, or channel shifts that need board visibility?
Those questions keep the review practical. They also help the team stay focused on the living program rather than on a stale legal snapshot.
Why It Still Matters After Withdrawal
The March 3, 2025 withdrawal ended the immediate rulemaking, but it did not end the underlying questions about liquidity, concentration, and third-party deposit sourcing. For that reason, this page is designed as an operational checklist rather than a debate over the withdrawn NPRM.
It is the page to use when the question is not “what did the rule say?” but “is this program actually documented well enough to survive review?”
Frequently Asked Questions
Does the withdrawal mean brokered deposits no longer matter?
No. It means the 2024 proposal is not live law, not that the underlying funding-risk questions disappeared. The 2020 framework still matters, and the file still has to work under that baseline.
Who should use this checklist?
Bank counsel, compliance teams, treasury, vendor management, and fintech product owners who need a practical file review tool.
What is the best next step if the file is weak?
Fix the contract, clarify the role definitions, rebuild the deposit-flow map, and reopen the record before the program scales further.
What should be in the next annual review?
The next review should confirm the current product flow, the partner’s actual role, any material changes to incentives or scripts, and whether the board or committee still has a current summary of the program.
