Identify the respondent and the record
The relevant respondent is Choice Financial Group, Fargo, North Dakota, the insured state nonmember bank commonly branded Choice Bank. The FDIC and North Dakota Department of Financial Institutions issued FDIC-23-0086b on December 18, 2023. December 13 was the consent-agreement date, not the order's effective date. The order was publicly released in the January 2024 enforcement cycle, which can cause inconsistent shorthand dates. [1][2]
The agencies recorded BSA-related findings from the June 2023 examination; the bank consented without admitting or denying violations. The original order says its provisions remain effective until modified, terminated, suspended or set aside. For this September 27, 2026 review, the original text and release record were verified, but a complete current-status result could not be obtained from the dynamic FDIC order database. No later termination was located. Accordingly, this article analyzes the documented order and does not certify that every provision remains active today. [1][2]
Distribution revenue comes with a continuing service obligation
A partner can bring specialized technology and customers a bank would not otherwise reach. The bank also needs enough information to understand the resulting activity and fulfill its responsibilities. The economic question is whether the arrangement funds that continuing work, rather than whether the partner can generate openings quickly.
A program with modest revenue can still require a distinct integration, customer-risk assessment and exception process. Those fixed costs matter when comparing a small specialized partner with a larger standardized program. Customer count alone cannot reveal which relationship is more complex or more valuable.
The operating problem the order addresses
The order connects board oversight with customer identification, due diligence, suspicious-activity monitoring, independent testing, staffing and partner activity. It calls for a lookback covering specified third-party relationships and for validation addressing data gaps in monitoring systems. The supervisory concern is not solved merely by buying an AML platform: the platform needs a complete, reliable view of the activity it is intended to monitor. [1]
The underlying customer-identification regulation requires a bank program reasonably designed to identify customers, with risk-based verification and records. That is a general legal framework; the particular remediation deadlines and governance arrangements in Choice's order are respondent-specific. Other institutions should not copy a 's timetable and describe it as a universal regulatory deadline. [3]
Map the customer through every provider
Analytical recommendation: construct a data map from application to account creation, transaction processing, alert generation and investigation. Identify the institution's actual customer under the relevant arrangement, the identifiers used by each provider and the linkage between them. A bank can receive the correct aggregate settlement balance while lacking the customer-level detail needed for monitoring.
The critical evidence is completeness. Reconcile record counts and monetary totals, then inspect rejected files, duplicate identifiers, late events and records with missing fields. A technically successful API response may contain only a subset of expected activity. Daily monitoring of ingestion success should therefore include business-population reconciliation, not merely server uptime.
Contracts can allocate operational tasks, but the bank must assess whether it can obtain the information necessary to perform its responsibilities. Establish delivery standards, correction duties, retention, audit access and escalation rights. Test those rights before a partner becomes financially stressed, when cooperation and access can become harder.
Program pricing should reflect the work the partner creates
A simple transaction fee may be easy to administer while underpricing unusual review and support needs. A more detailed price can better reflect costs but also make the product harder for the partner to forecast. The commercial design should make material obligations visible without creating incentives to suppress legitimate questions or reports.
A useful analysis separates shared infrastructure, program-specific work and costs driven by actual exceptions. It should also examine whether the bank can independently access the records on which the pricing assumptions depend. A profitable forecast built on incomplete activity data is difficult to evaluate, even before considering supervisory requirements.
Worked example: the silent monitoring gap
Hypothetical partner program: 50,000 accounts generate two million monthly transactions. A data transformation drops 1% of transactions with an unrecognized transaction type. The system still processes 1.98 million records and can appear healthy, yet 20,000 transactions are missing. If the missing type is concentrated in cash-equivalent transfers, the risk significance may be much larger than its numerical share.
Assume investigators normally review 500 alerts monthly. A lower alert count after the mapping change could look like improved customer quality or better rule tuning. It may instead reflect missing inputs. Before celebrating efficiency, reconcile the input population and compare alert rates within consistent transaction categories. The example illustrates a mechanism; it is not a claim about Choice's actual systems or transaction volume.
A corrective plan would restore the records, identify the affected dates, rerun appropriate scenarios and assess whether past investigations or required reports need revision. The lookback should be governed by a documented scope and legal assessment, not a blanket instruction to file a report on every exception.
Staffing and independent challenge
Recommended capacity planning starts with work arrival, handling time, complexity and deadlines. A partner that doubles transaction volume may increase investigation work faster than volume if it introduces new products or geographies. Use scenario-based staffing estimates and review actual queue aging. A low total backlog can conceal a small group of highly aged, difficult cases.
Independent testing should challenge whether the risk assessment reflects real business activity and whether data and rules implement it. Review both high-risk alerts and samples that did not alert. Testing only the output queue cannot identify all activities excluded before scoring. Preserve enough historical configuration to recreate what the system saw at the relevant time.
Board oversight should receive a concise view of unresolved control gaps, overdue remediation, data completeness and material partner changes. Attendance at a meeting is not evidence that a significant weakness was understood. Minutes and decision records should show what was challenged, what resources were committed and why remaining risk was accepted or reduced.
Exit rights need usable information behind them
A contract may permit a relationship to end while leaving the bank dependent on the departing partner to explain balances and transactions. Practical portability requires interpretable records, consistent identifiers and a funded plan for continuing essential customer service. An export that cannot be reconciled is a weak substitute for operational readiness.
Those capabilities also help during ordinary complaints and planned system changes. They can reduce repeated work while preserving the benefits of specialized distribution. The historical order supports attention to partner oversight; it does not establish that every Choice program is unprofitable or that a current termination can be inferred from an incomplete database search.
Economics and limits of the case
Partner distribution can generate useful scale and fee income, but monitoring, data engineering and customer support are real unit costs. A program that appears profitable before these costs may not remain attractive after realistic oversight is included. Common dependencies also matter: multiple brands using one processor may create a single failure point despite a large partner count.
There is a legitimate tradeoff between catching more suspicious patterns and imposing excessive friction on ordinary customers. Better data and targeted rules can improve that tradeoff; indiscriminate alert expansion can overwhelm investigators. Evaluate quality, timeliness and documented disposition rather than treating the largest alert count as the best program.
An official termination or modification would change the legal-status conclusion. Demonstrated data completeness, effective lookback execution and sustained testing would strengthen the operational conclusion. Public materials do not reveal all remediation results, and this case study does not infer a . Its lasting lesson is that a bank must be able to reconstruct partner activity with sufficient detail to make and evidence its own compliance decisions.
Sources
- FDIC and North Dakota DFI, Choice Financial Group consent order FDIC-23-0086b, effective December 18, 2023Official sourceBack to text: ↑1↑2↑3
- FDIC, enforcement release orders, January 26, 2024; current-status search reviewed September 27, 2026Official releaseBack to text: ↑1↑2
- eCFR, current 31 CFR 1020.220, bank customer identification; reviewed September 27, 2026Official textBack to text: ↑