Reg BI Conflict of Interest Obligation

Reg BI’s Conflict of Interest Obligation requires your broker-dealer to maintain and enforce written policies and procedures reasonably designed to identify all conflicts tied to recommendations and, at a minimum, disclose or eliminate them. Operationally, you need a repeatable conflict inventory, clear disclosure and mitigation rules, and supervision that proves the program works in practice. (17 CFR § 240.15l-1)

Key takeaways:

• You must run a documented process to identify conflicts tied to recommendations and keep it current. (17 CFR § 240.15l-1)
• “Disclose or eliminate” is the floor; incentives that could cause a rep to put their interest ahead of the customer require mitigation or elimination, not just disclosure. (17 CFR § 240.15l-1)
• Examiners expect evidence of enforcement: approvals, surveillance, training, exceptions, and outcomes, not a policy binder. (17 CFR § 240.15l-1)

The Reg BI conflict of interest obligation is operational, not aspirational. The rule text is short, but the work is not: you have to translate “identify and at a minimum disclose, or eliminate, all conflicts of interest” into day-to-day controls across products, compensation, distribution, and supervision. (17 CFR § 240.15l-1)

For most broker-dealers, the fastest path to a defensible program is to treat conflicts like an inventory problem plus an enforcement problem. First, build a conflict map that is specific to recommendations, not generic “code of ethics” language. Then define decision rules: which conflicts are disclose-only, which require mitigation, and which must be eliminated. Finally, prove the rules operate through supervision, escalation, and documentation.

This page is written for a Compliance Officer, CCO, or GRC lead who needs to stand up or tighten a Reg BI conflict program quickly: what it covers, who it applies to, concrete steps, what evidence to retain, and the exam questions that create the most friction. All regulatory references in this page cite Regulation Best Interest. (17 CFR § 240.15l-1)

Regulatory text

Requirement (rule excerpt): “The broker-dealer must establish, maintain, and enforce written policies and procedures reasonably designed to identify and at a minimum disclose, or eliminate, all conflicts of interest.” (17 CFR § 240.15l-1)

What this means for an operator

• Establish: create written policies and procedures that cover conflict identification, treatment (disclosure/mitigation/elimination), supervision, and documentation. (17 CFR § 240.15l-1)
• Maintain: keep the conflict inventory, disclosures, and controls current as products, compensation, and distribution change. (17 CFR § 240.15l-1)
• Enforce: demonstrate the firm actually follows the procedures, detects exceptions, remediates issues, and disciplines or corrects behavior when needed. (17 CFR § 240.15l-1)

The practical summary to implement: identify conflicts associated with recommendations, disclose material conflicts, mitigate or eliminate conflicts that create incentives for the representative to place their interests ahead of the customer’s, and eliminate sales contests, quotas, or bonuses based on the sale of specific products within a limited time period. (17 CFR § 240.15l-1)

Plain-English interpretation (what you’re being asked to accomplish)

A “conflict” under Reg BI is any incentive, pressure, or business arrangement that could reasonably influence how a recommendation is made or which product/strategy is recommended. The obligation is not satisfied by a generic statement like “we may receive compensation.” You need:

1. A reliable way to find conflicts tied to your actual recommendation process.
2. A consistent way to treat conflicts (disclose, mitigate, or eliminate) based on their impact.
3. Evidence the firm supervises and enforces those decisions. (17 CFR § 240.15l-1)

A useful internal standard: if a conflict creates a strong incentive for the rep or firm to prefer one outcome over the customer’s best interest, you should expect to implement mitigation or elimination controls, not rely on disclosure alone. (17 CFR § 240.15l-1)

Who it applies to (entity and operational context)

Covered entities

• Broker-dealers making recommendations to retail customers under Regulation Best Interest. (17 CFR § 240.15l-1)

Where it shows up operationally

This obligation touches any workflow that can influence recommendations, including:

• Compensation and payout design (grid changes, differential payouts, bonuses).
• Product shelf and distribution (proprietary products, revenue sharing, third-party product sponsors, share class availability).
• Sales management (activity targets, campaign spiffs, recognition programs).
• Supervision and surveillance (who reviews recommendations, how exceptions are handled).
• Disclosures delivered at account opening and at the point of recommendation (17 CFR § 240.15l-1)

If you outsource pieces of distribution or product support to third parties (for example, product manufacturers, clearing firms, or marketing partners), you still own the conflict analysis for how those arrangements affect recommendations. (17 CFR § 240.15l-1)

What you actually need to do (step-by-step)

Step 1: Set scope and ownership

• Name an accountable owner (often Compliance) and define required partners: Sales, Supervision, Finance/Comp, Product, Operations, and Legal.
• Define scope explicitly: conflicts “associated with recommendations,” including firm-level and rep-level incentives. (17 CFR § 240.15l-1)

Artifact: RACI or ownership memo for conflict program governance.

Step 2: Build a conflicts inventory (the “conflict map”)

Create an inventory that is concrete and testable. For each conflict, record:

• Conflict description (what creates the incentive).
• Where it occurs (business line, product set, channel).
• Triggering event (account opening, rollover recommendation, product switch, trade).
• Who is impacted (rep, supervisor, firm).
• Treatment decision: disclose / mitigate / eliminate.
• Controls and evidence produced by the control. (17 CFR § 240.15l-1)

Examples to include (adapt to your business):

• Differential compensation between products.
• Proprietary product incentives.
• Third-party payments tied to distribution.
• Sales contests, quotas, or bonuses linked to specific products in a limited time period (must be eliminated, per the provided Reg BI summary). (17 CFR § 240.15l-1)

Artifact: Conflicts register with version control and approval.

Step 3: Define treatment rules (disclosure vs mitigation vs elimination)

Write decision criteria your supervisors can apply consistently:

• Disclose when the conflict is material and can be explained clearly in customer-facing language. (17 CFR § 240.15l-1)
• Mitigate when the conflict creates an incentive that could cause the rep to place their interest ahead of the customer’s; mitigation must change behavior risk, not just add paper. (17 CFR § 240.15l-1)
• Eliminate when the conflict is prohibited by your policy or when the only practical way to prevent harm is to remove the incentive (including eliminating certain sales contests/quotas/bonuses as described in the Reg BI summary). (17 CFR § 240.15l-1)

Common mitigation controls that exam teams understand

• Neutral compensation structures or reduced differentials for comparable products.
• Pre-approval for higher-compensation products or complex products.
• Enhanced surveillance for patterns (e.g., concentration, switching, or recommendation frequency).
• Supervisor attestations tied to specific conflict categories. (17 CFR § 240.15l-1)

Artifact: Conflict treatment standard and supervisory procedures.

Step 4: Rewrite disclosures so they map to real conflicts

Disclosures should be:

• Specific (what the conflict is, who benefits, how).
• Understandable (plain language; avoid legal boilerplate).
• Actionable (what it could mean for the customer’s decision). (17 CFR § 240.15l-1)

Tie each disclosure section back to the conflicts inventory. If you cannot map it, you likely have a disclosure gap or an inventory gap.

Artifact: Disclosure crosswalk (conflict register → disclosure document sections) and change log.

Step 5: Train, supervise, and test (“enforce”)

“Enforce” is where many programs fail. Build a supervision loop:

• Training for reps and supervisors on (a) what conflicts exist, (b) how they are handled, and (c) when escalation is required. (17 CFR § 240.15l-1)
• Supervisory review checkpoints embedded in workflows (account opening, recommendation documentation, approvals).
• Testing: periodic sample reviews against the conflict rules and documentation standards.
• Issue management: log findings, assign remediation, track closure, and adjust controls where patterns repeat. (17 CFR § 240.15l-1)

Artifact: Training materials and completion logs, supervisory checklists, surveillance reports, exception logs, remediation tickets, and management reporting.

Step 6: Operationalize with systems (where Daydream fits)

Most firms fail because conflict evidence is scattered across email, shared drives, comp spreadsheets, and separate surveillance tools. Daydream can centralize the conflicts register, link each conflict to required disclosures and controls, assign owners, and maintain an audit-ready evidence trail for “establish, maintain, and enforce” in one place. (17 CFR § 240.15l-1)

Required evidence and artifacts to retain (audit-ready list)

Keep artifacts that show design and operation:

• Board/committee or management approvals for conflict policies and material updates.
• Current written policies and procedures for conflict identification and treatment. (17 CFR § 240.15l-1)
• Conflicts inventory/register with history and rationale for disclose/mitigate/eliminate decisions.
• Disclosure documents and a crosswalk to the conflict register.
• Compensation program documentation and change approvals (especially around differential comp).
• Sales program governance records (including evidence that prohibited sales contests/quotas/bonuses tied to specific products in a limited time period were eliminated). (17 CFR § 240.15l-1)
• Supervisory procedures, review logs, approvals, and escalation records.
• Surveillance/testing plans, results, and remediation tracking.
• Training materials, attendance/completion evidence, and role-based curricula. (17 CFR § 240.15l-1)

Common exam/audit questions and hangups

Expect exam teams to probe these:

• “Show me your conflicts inventory. How do you keep it current?” (17 CFR § 240.15l-1)
• “Which conflicts do you only disclose, and why is disclosure sufficient?”
• “Where do you mitigate? What specific control reduces the incentive?”
• “How did you eliminate sales contests/quotas/bonuses tied to specific products within a limited time period?” (17 CFR § 240.15l-1)
• “Prove enforcement: show exceptions, findings, and what changed afterward.” (17 CFR § 240.15l-1)
• “How do third-party payments or arrangements affect recommendations, and how is that disclosed or mitigated?” (17 CFR § 240.15l-1)

Frequent implementation mistakes (and how to avoid them)

1. Generic conflicts inventory
   Fix: anchor every conflict entry to a recommendation workflow or incentive mechanism. If you cannot identify a trigger, it will not be supervised. (17 CFR § 240.15l-1)

2. Disclosure-only posture for high-incentive conflicts
   Fix: define criteria for when mitigation is mandatory and document the rationale per conflict category. (17 CFR § 240.15l-1)

3. No evidence of enforcement
   Fix: require artifacts from supervision (approvals, surveillance outputs, exceptions, remediation). Treat absence of evidence as a control failure. (17 CFR § 240.15l-1)

4. Comp changes happen outside compliance visibility
   Fix: add a formal change-control gate for comp grids, bonuses, and sales programs with compliance review and conflict impact assessment. (17 CFR § 240.15l-1)

5. Third-party arrangements not connected to recommendations
   Fix: map third-party compensation and support arrangements into the conflict register and disclosures; require business owner attestations. (17 CFR § 240.15l-1)

Enforcement context and risk implications

No public enforcement cases were provided in the approved source catalog for this page, so this section is intentionally omitted.

Operational risk is still clear from the text: if you cannot show your program is “reasonably designed” and you cannot show you “enforce” it, you risk findings that can drive remediation, supervisory undertakings, or restrictions on sales practices. (17 CFR § 240.15l-1)

Practical 30/60/90-day execution plan

First 30 days (stabilize and inventory)

• Confirm accountable owner, governance cadence, and required stakeholders.
• Collect current policies, disclosures, comp plans, product shelf lists, and sales program materials.
• Build the first version of the conflicts register focused on top recommendation pathways and compensation drivers.
• Identify any sales contests/quotas/bonuses tied to specific products in a limited time period and stop them pending review. (17 CFR § 240.15l-1)

Days 31–60 (decide treatment and embed supervision)

• Finalize disclose/mitigate/eliminate decision rules and document rationale.
• Update disclosures and create a crosswalk to the conflicts register.
• Implement supervisory checkpoints: pre-approval criteria, heightened review lists, and escalation standards.
• Launch targeted training for supervisors first, then reps, focused on the firm’s actual conflicts. (17 CFR § 240.15l-1)

Days 61–90 (test, evidence, and iterate)

• Run a first testing cycle: sample recommendations, validate documentation, verify disclosures delivered, and confirm mitigation controls operated.
• Open and close remediation items with documented fixes (procedure updates, comp adjustments, training refresh, supervision changes).
• Produce management reporting that links conflicts to findings and corrective actions.
• Consider consolidating the register, disclosures, ownership, and evidence trail in Daydream to reduce audit friction and keep updates controlled. (17 CFR § 240.15l-1)

Frequently Asked Questions

Does Reg BI require us to eliminate all conflicts of interest?

No. The requirement is to identify conflicts and at a minimum disclose or eliminate them, supported by written policies and procedures that are enforced. For conflicts that create strong incentives to put a rep’s interest ahead of the customer’s, mitigation or elimination is expected per the Reg BI summary. (17 CFR § 240.15l-1)

What’s the difference between “disclose” and “mitigate” in practice?

Disclosure tells the customer about the conflict in a clear way. Mitigation changes the incentive or adds controls that reduce the likelihood the conflict will influence recommendations, such as neutralizing comp differentials or adding pre-approval and surveillance. (17 CFR § 240.15l-1)

What documentation do we need to prove we “enforce” the policies?

Keep evidence that supervision and testing happened and produced outcomes: approvals, exception logs, surveillance results, remediation tickets, training completions, and documented discipline or corrective actions where applicable. A policy alone rarely satisfies the “enforce” expectation. (17 CFR § 240.15l-1)

How should we handle third-party payments tied to distribution?

Treat them as conflicts associated with recommendations, map them in the conflicts register, and decide whether disclosure alone is sufficient or whether mitigation is required. Keep the underlying third-party agreements and the rationale for your treatment decision. (17 CFR § 240.15l-1)

Are sales contests always prohibited under Reg BI?

The provided Reg BI summary calls for eliminating sales contests, quotas, or bonuses based on the sale of specific products within a limited time period. Your procedures should explicitly prohibit those programs and include monitoring to detect workarounds. (17 CFR § 240.15l-1)

We already have a conflicts policy for our adviser business. Can we reuse it for the broker-dealer?

You can reuse structure and concepts, but you still need broker-dealer procedures that are specific to recommendations and the broker-dealer compensation and product environment. Examiners will look for BD-specific conflicts, disclosures, and supervision evidence tied to Reg BI. (17 CFR § 240.15l-1)