The Vantage View | Salesforce

Salesforce for RIAs vs Broker-Dealers: Choosing the Right FSC Configuration | Vantage Point

Written by David Cockrum | Mar 20, 2026 11:59:59 AM

Key Takeaways (TL;DR)

  • What is it? A guide to configuring Salesforce Financial Services Cloud (FSC) for Registered Investment Advisors (RIAs) versus Broker-Dealers (BDs), two fundamentally different wealth management models
  • Key Difference: RIAs operate under a fiduciary standard (SEC/state) with fee-based revenue; BDs follow a suitability standard (FINRA) with commission-based compensation
  • Cost: $300–500/user/month for FSC licensing plus $50K–$250K+ implementation depending on firm complexity
  • Timeline: 3–6 months for RIAs; 4–8 months for broker-dealers due to additional compliance layers
  • Best For: Wealth management firms evaluating Salesforce FSC who need clarity on which configuration path matches their registration model
  • Bottom Line: The same FSC platform serves both models, but the data architecture, compliance workflows, and integration strategy must be tailored to your firm type for maximum ROI

Introduction: Why Your Firm Type Dictates Your Salesforce Configuration

If you're evaluating Salesforce Financial Services Cloud (FSC) for your wealth management firm, one of the first questions you'll face is deceptively simple: Are you an RIA, a broker-dealer, or a hybrid?

The answer fundamentally shapes every decision that follows—from how you model client households and financial accounts, to which compliance workflows you automate, to which custodial and portfolio management integrations you prioritize.

Too many firms make the mistake of treating FSC as a one-size-fits-all solution. They deploy a generic configuration and then spend months (and tens of thousands of dollars) retrofitting it to match their actual business model. The smarter approach is to understand the configuration differences upfront and build for your firm type from day one.

In this guide, we'll walk through the key differences between RIA and broker-dealer Salesforce FSC configurations, covering:

  • Regulatory and business model differences that drive configuration decisions
  • Data model and household management considerations
  • Compliance workflow design for each firm type
  • Integration strategies with custodians, portfolio systems, and compliance platforms
  • Hybrid firm considerations for dual-registered entities
  • Implementation best practices and common pitfalls

Whether you're a $500M AUM RIA, a mid-sized independent broker-dealer, or a hybrid firm navigating both worlds, this guide will help you make the right configuration choices.

What Are the Key Differences Between RIAs and Broker-Dealers?

Before diving into Salesforce configuration, it's critical to understand the fundamental business model differences that drive technology decisions.

Regulatory Framework

DimensionRIABroker-Dealer
Primary RegulatorSEC (>$110M AUM) or StateFINRA + SEC
Standard of CareFiduciary (best interest)Suitability (Reg BI enhanced)
RegistrationForm ADVForm BD / FINRA membership
Revenue ModelFee-based (AUM %, flat, hourly)Commission-based + fee-based
Product ScopeInvestment advice, planningSecurities transactions + advice
Exam RequirementsSeries 65 (or 66)Series 7 + Series 63/66
Disclosure RequirementsForm ADV Part 2 brochureReg BI Form CRS + disclosures

How These Differences Impact CRM Configuration

For RIAs, the Salesforce configuration emphasizes:

  • Client relationship depth: Comprehensive household views with financial goals, risk profiles, and planning milestones
  • AUM tracking and fee management: Fee billing calculations tied to account balances
  • Fiduciary documentation: Logging investment rationale and client communication for fiduciary compliance
  • Financial planning integrations: Connections to planning tools like MoneyGuidePro, eMoney, or RightCapital

For Broker-Dealers, the configuration prioritizes:

  • Product suitability tracking: Documenting that every recommendation meets suitability or Reg BI standards
  • Commission management: Tracking commission schedules, payout grids, and revenue attribution
  • Supervision workflows: Multi-tier approval processes for trades, communications, and account activity
  • FINRA compliance automation: Automated U4/U5 tracking, CE requirements, and branch examination support

How Should You Configure the FSC Data Model for Each Firm Type?

Household and Relationship Management

Both RIAs and broker-dealers need robust household management, but the emphasis differs significantly.

RIA Configuration:

  • Leverage FSC's Party Relationship Groups (in FSC Core) or Account-based Households (managed package) to model complex family structures
  • Map household members including spouses, children, trusts, foundations, and estate plans
  • Use the Actionable Relationship Center (ARC) to visualize multi-generational wealth relationships
  • Configure relationship types like Trustee, Beneficiary, Power of Attorney, and Estate Executor
  • Roll up AUM and financial account data to the household level for holistic views

Broker-Dealer Configuration:

  • Household management is equally important but also requires registered representative assignment at the account level
  • Map the Rep-to-Client relationship with clear assignment tracking for supervision
  • Configure branch-level hierarchies (Office of Supervisory Jurisdiction/OSJ) to support supervisory structures
  • Track both client-level and rep-level compliance status
  • Include institutional relationships (e.g., fund companies, product sponsors) alongside retail clients

Financial Account Configuration

RIA Configuration:

  • Financial Account types: Investment accounts, retirement accounts (IRA, Roth IRA, 401(k) rollovers), trust accounts, 529 plans
  • Financial Account Balances: Track historical balance snapshots via the Financial Account Balance object for AUM trending
  • Financial Account Parties: Use the junction object to model multiple owners (joint accounts, UGMA/UTMA custodial accounts)
  • Custom fields for: Investment policy statement (IPS) status, target asset allocation, risk tolerance score, rebalancing frequency

Broker-Dealer Configuration:

  • All of the above, plus: Brokerage accounts, margin accounts, options-approved accounts
  • Additional custom fields for: Suitability profile, account approval status, discretionary/non-discretionary flag
  • Commission tracking fields: Gross dealer concession (GDC), trailing commissions, 12b-1 fees
  • Product-level tracking: Approved product lists, selling agreements, and alternative investment qualifications

What Compliance Workflows Does Each Firm Type Need?

RIA Compliance Workflows

RIAs face a principles-based regulatory environment. Compliance is about demonstrating you consistently act in the client's best interest.

Key FSC Workflows for RIAs:

1. Client Onboarding Action Plan

  • KYC (Know Your Customer) data collection
  • Risk tolerance assessment and IPS documentation
  • Form ADV Part 2 delivery and acknowledgment tracking
  • Custodial account opening coordination
  • Privacy policy delivery and consent tracking

2. Annual Review Workflow

  • Automated reminders for annual client reviews
  • Pre-meeting data aggregation (performance, life changes, goal progress)
  • Post-meeting documentation of discussion and recommendations
  • Updated IPS if risk profile has changed

3. Best Interest Documentation

  • Log investment rationale for significant portfolio changes
  • Track client communication history (emails, calls, meetings)
  • Document client-initiated vs. advisor-initiated transactions

4. Regulatory Filing Reminders

  • Form ADV annual amendment deadlines
  • State registration renewals
  • Custody rule compliance (surprise examinations)
  • Business continuity plan review schedules

Broker-Dealer Compliance Workflows

Broker-dealers face a more prescriptive regulatory environment with FINRA's extensive rulebook and Regulation Best Interest (Reg BI).

Key FSC Workflows for Broker-Dealers:

1. Suitability/Reg BI Review Process

  • Pre-trade suitability questionnaire automation
  • Multi-tier approval workflows (rep → supervisor → compliance)
  • Reg BI disclosure delivery and documentation
  • Cost-basis comparison documentation for product recommendations
  • Alternative product consideration logging

2. Trade Supervision Automation

  • Automated flagging of trades exceeding thresholds
  • Principal review queues with SLA monitoring
  • Exception reporting for unusual activity patterns
  • Outside Business Activity (OBA) review workflows

3. Communication Supervision

  • Email and correspondence review workflows
  • Social media and advertising pre-approval processes
  • Complaint logging, escalation, and resolution tracking
  • Client correspondence archival integration

4. Representative Compliance

  • Form U4/U5 amendment tracking
  • Continuing education (CE) requirement monitoring
  • Registration renewal automation
  • Disclosure event reporting workflows
  • Branch examination preparation checklists

5. Product Governance

  • New product due diligence workflows
  • Approved product list management
  • Selling agreement tracking and renewal
  • Alternative investment qualification verification

How Do Integration Strategies Differ?

RIA Integration Ecosystem

RIAs typically integrate Salesforce FSC with:

IntegrationPurposeCommon Platforms
CustodiansAccount data, positions, balancesSchwab Advisor Center, Fidelity Wealthscape, Pershing
Portfolio ManagementPerformance reporting, rebalancingOrion, Black Diamond, Tamarac, Addepar
Financial PlanningGoal planning, projectionsMoneyGuidePro, eMoney, RightCapital
Document ManagementSecure document storageDocuSign, PandaDoc, Box
Marketing AutomationClient communicationsHubSpot, Mailchimp, Constant Contact
ComplianceRegulatory filing, archivingRIA in a Box, SmartRIA, ComplySci

Key RIA Integration Patterns:

  • Multi-custodial data aggregation: Many RIAs use multiple custodians. MuleSoft or middleware solutions aggregate account data from Schwab, Fidelity, and Pershing into a single FSC view.
  • Portfolio system bi-directional sync: Account balances and performance data flow from Orion/Black Diamond into FSC, while client profile updates push back to the portfolio system.
  • Planning tool integration: Sync client goals and financial plans between planning software and FSC to create a true 360° view.

Broker-Dealer Integration Ecosystem

Broker-dealers have a more complex integration landscape:

IntegrationPurposeCommon Platforms
Clearing FirmsTrade execution, settlementPershing, National Financial, RBC Correspondent
Order ManagementTrade entry, routingFlyer, Broadridge, SS&C
Supervision/ComplianceTrade review, communicationsNICE Actimize, Global Relay, Smarsh
Commission ManagementPayout calculationsBroadridge, InvestCloud, custom systems
RegistrationRep licensing, CE trackingFINRA Gateway, RegEd, Kaplan
Marketing/CompliancePre-approved contentHearsay, FMG Suite, Broadridge Advisor

Key BD Integration Patterns:

  • Real-time trade supervision: Trades flow from order management systems into FSC for principal review, with automated routing based on trade type and threshold.
  • Commission reconciliation: Clearing firm payout data integrates with FSC for commission tracking, grid management, and rep compensation analysis.
  • Compliance platform integration: Supervision platforms feed review status and exceptions back into FSC for a unified compliance dashboard.

What About Hybrid Firms?

Many firms are dual-registered—operating both an RIA and a broker-dealer under the same umbrella. This is increasingly common as the industry shifts toward fee-based models while maintaining commission-based product access.

Hybrid FSC Configuration Considerations

  1. Dual Account Tracking: Configure financial accounts with a field indicating whether business is conducted through the RIA or BD channel. This drives which compliance workflows apply.
  2. Role-Based Page Layouts: Create separate Lightning page layouts for advisors operating in RIA vs. BD capacity, showing relevant compliance fields and action plans for each.
  3. Revenue Attribution: Build custom objects or fields to separate fee-based revenue (RIA) from commission revenue (BD) at the advisor and household level.
  4. Compliance Workflow Routing: Use Salesforce Flow to dynamically route compliance tasks based on the registration channel. An AUM-fee account change triggers RIA workflows; a commissioned product sale triggers BD workflows.
  5. Supervisory Hierarchy: Map both the RIA's Chief Compliance Officer (CCO) structure and the BD's OSJ/branch supervisor hierarchy, ensuring the right approver reviews the right activity.

What Are the Best Practices for Each Firm Type?

Best Practices for RIA Salesforce FSC Implementations

  1. Start with household architecture. RIAs live and breathe by household relationships. Get your relationship groups, contact roles, and AUM rollups right before anything else.
  2. Invest in custodial integration early. Your advisors will only adopt FSC if they can see real-time account data without toggling to custodian portals.
  3. Automate the annual review cycle. Build action plans for pre-meeting prep, meeting documentation, and post-meeting follow-up. This alone can save each advisor 5–10 hours per month.
  4. Configure Einstein for client engagement scoring. Use AI to identify clients at risk of attrition or those with opportunities for deeper engagement (e.g., next-gen wealth transfer planning).
  5. Build your tech stack for growth. Choose integrations that scale as your AUM grows. MuleSoft-based integrations handle multi-custodial complexity better than point-to-point connectors.

Best Practices for Broker-Dealer Salesforce FSC Implementations

  1. Map your supervision structure first. Before configuring anything, document your OSJ hierarchy, approval chains, and exception thresholds. This drives your entire workflow design.
  2. Build suitability documentation into the workflow. Don't make compliance an afterthought. Embed Reg BI documentation requirements directly into the sales process so reps complete them naturally.
  3. Automate trade supervision queues. Use Salesforce Flow and approval processes to route trades to the right principal reviewer based on product type, dollar amount, and risk level.
  4. Leverage role-based security aggressively. Broker-dealers have strict information barriers. Use FSC's field-level security, record-level security, and sharing rules to enforce need-to-know access.
  5. Plan for compliance reporting from day one. FINRA examinations require specific reports. Build dashboards that answer common exam questions: trade supervision turnaround times, complaint resolution rates, and exception handling metrics.

How Do Implementation Timelines and Costs Compare?

RIA Implementation

PhaseTimelineFocus Areas
Discovery & Design3–4 weeksHousehold model, integration requirements, compliance workflows
Build & Configure6–8 weeksData model, automations, custodial integration
Testing & Training3–4 weeksUAT, data migration, advisor training
Go-Live & Optimization2–4 weeksPhased rollout, feedback incorporation
Total3–5 months

Typical RIA Investment:

  • FSC Licensing: $300–500/user/month
  • Implementation: $50K–$150K (depending on integrations and customization)
  • Ongoing support: $2K–$8K/month

Broker-Dealer Implementation

PhaseTimelineFocus Areas
Discovery & Design4–6 weeksSupervision hierarchy, compliance requirements, integration mapping
Build & Configure8–12 weeksData model, supervision workflows, compliance automation
Testing & Training4–6 weeksCompliance UAT, FINRA readiness, multi-branch training
Go-Live & Optimization3–4 weeksBranch-by-branch rollout, compliance verification
Total4–8 months

Typical BD Investment:

  • FSC Licensing: $300–500/user/month
  • Implementation: $100K–$250K+ (more complex compliance requirements)
  • Ongoing support: $5K–$15K/month

Frequently Asked Questions

Can the same Salesforce FSC org support both RIA and broker-dealer operations?

Yes. Dual-registered firms can run both models in a single FSC org by using record types, custom fields, and dynamic page layouts to differentiate between RIA and BD business. Salesforce Flow routes compliance workflows based on the channel. This is a common configuration for hybrid firms and is more cost-effective than maintaining separate orgs.

What version of FSC should I use—Managed Package or FSC Core?

Salesforce is investing all future development in FSC Core (native platform). New implementations should use FSC Core unless specific third-party integrations require the managed package. FSC Core offers more flexible householding (Party Relationship Groups), better financial account ownership modeling (junction objects), and historical balance tracking.

Do RIAs need Salesforce Shield for compliance?

While not strictly required, Salesforce Shield (Platform Encryption + Event Monitoring + Field Audit Trail) is strongly recommended for RIAs managing sensitive client data. The Field Audit Trail feature provides 10-year data change retention, which is invaluable for regulatory examinations. Most firms managing $500M+ AUM consider Shield essential.

How does Reg BI compliance work in Salesforce FSC for broker-dealers?

Reg BI compliance is implemented through custom workflows and action plans that document: (1) the disclosure obligation (Form CRS delivery), (2) the care obligation (suitability analysis, cost comparison), (3) the conflict of interest obligation (compensation disclosure), and (4) the compliance obligation (supervisory review). These can be automated through Salesforce Flow with approval processes for principal review.

What custodial integrations are available for RIAs using FSC?

Schwab Advisor Center, Fidelity Wealthscape, Pershing, and Raymond James all offer Salesforce FSC integrations. These bring in account balances, positions, transactions, and alerts. For multi-custodial firms, MuleSoft integration provides a unified data aggregation layer that normalizes data across custodians into a single FSC view.

How do I handle branch-level supervision in Salesforce for a broker-dealer?

FSC includes Branch Management capabilities that support multi-location supervision. Configure Branch Unit records to represent offices, map registered representatives to branches, and use approval processes that route based on branch and OSJ hierarchy. Supervision dashboards can be scoped by branch to give principals visibility into their specific team's activity.

What's the ROI timeline for each firm type?

RIAs typically see measurable ROI within 6–12 months, primarily through advisor time savings (5–10 hours/week) and improved client retention from better service. Broker-dealers often see ROI within 12–18 months, with the biggest gains coming from reduced compliance costs, faster supervision turnaround, and decreased regulatory risk exposure.

Ready to Configure FSC for Your Firm Type?

Vantage Point specializes in Salesforce Financial Services Cloud implementations for wealth management firms of all types—RIAs, broker-dealers, and hybrid firms. Our team understands the regulatory nuances that drive configuration decisions and builds solutions that scale with your business.

Contact Vantage Point to schedule a discovery session and get a configuration roadmap tailored to your firm type.

About Vantage Point

Vantage Point is a technology consultancy specializing in CRM strategy and implementation for regulated industries. We help wealth management firms, financial advisors, banks, and insurance companies leverage Salesforce Financial Services Cloud, HubSpot CRM, MuleSoft integration, Data Cloud, and AI-driven personalization to modernize client engagement and streamline operations. Learn more at vantagepoint.io.