Financial Services Cloud
Financial Services Cloud (FSC) is Salesforce's industry product for banking, wealth management, insurance, and asset management.
Definition
Financial Services Cloud (FSC) is Salesforce's industry product for banking, wealth management, insurance, and asset management. It extends standard Salesforce CRM with financial-services-specific data models, workflows, and integrations: household and relationship-based client views, financial accounts and goals, insurance policies and claims, retail banking workflows, and the regulatory considerations specific to financial services. FSC is licensed separately from base Sales Cloud and Service Cloud, sold to wealth advisors, retail bankers, insurance carriers, and asset managers.
The product structures around the Person Account and Household concepts: clients are individuals (Person Accounts) grouped into Households for relationship-based servicing. Financial Accounts (investment accounts, bank accounts, insurance policies) attach to Person Accounts and Households with rich attribute data. The Action Plan framework orchestrates multi-step processes like new account opening, mortgage origination, claims processing, or compliance reviews. Like Health Cloud, FSC is one of Salesforce's industry clouds tuned for the workflows and regulatory requirements of its target verticals.
How Financial Services Cloud serves banking, wealth, and insurance
The Household and Person Account architecture
FSC centers on the Household: a relationship group of Person Accounts (clients, family members, beneficiaries) plus their related entities (trusts, businesses, professional advisors). The Household view shows every member, every financial account, every relationship, every interaction in one place. This relationship-based view fits wealth management and high-net-worth banking where servicing one client means understanding their whole family financial picture. The architecture is the differentiator versus traditional CRM that focuses on individual contacts.
Financial Accounts and the data model
FSC extends with Financial Account objects: investment accounts, bank accounts, credit accounts, insurance policies, retirement accounts. Each Financial Account links to one or more Person Accounts as owners, beneficiaries, or authorized users. Roll-up summaries on the Household and Person Account show total assets under management, total liabilities, total insured value. The data model supports both wealth management (portfolio aggregation) and retail banking (account servicing) within one platform.
Action Plans for multi-step process orchestration
Action Plans are FSC''s framework for orchestrating multi-step processes. A new client onboarding Action Plan might include identity verification, account funding, beneficiary designation, suitability questionnaire, signature collection, and welcome call. Each task assigns to the right role with deadlines and dependencies. The framework also covers mortgage origination, insurance underwriting, claims processing, and compliance reviews. Action Plans replace ad-hoc task management with structured, auditable workflows.
Banker, Advisor, and Agent personas
FSC ships several persona-specific configurations. The Banker persona focuses on retail banking workflows: branch operations, deposit management, lending pipeline. The Advisor persona focuses on wealth management: portfolio review, financial planning, fee billing. The Insurance Agent persona focuses on policy servicing, claims, and renewals. Each persona has tuned Lightning record pages, related lists, and reports. Pick the persona that matches the user base and customize from there.
Integration with core banking and wealth platforms
FSC integrates with core banking systems (Fiserv, FIS, Jack Henry), wealth platforms (Pershing, Schwab, Fidelity), insurance systems (Guidewire, Duck Creek), and data aggregators (Plaid, Yodlee, MX). The integration model uses MuleSoft, the Salesforce Connect framework, or custom REST integrations. Standardized integrations exist for major platforms; smaller systems usually need custom integration work. Plan integration as the biggest implementation cost factor for any FSC deployment.
Compliance and audit considerations
Financial services operates under heavy regulation: KYC (Know Your Customer), AML (Anti-Money Laundering), suitability rules, fiduciary standards, SOC compliance, GDPR (in Europe), state-specific requirements (in the US). FSC supports the technical compliance requirements: audit trails, field history tracking, encryption, sharing model rigor. Operational compliance (policy training, exception management, regulatory reporting) is the customer''s ongoing responsibility. The platform supports compliance; it does not eliminate the operational work.
Industry-specific features and AppExchange ecosystem
Beyond the base FSC product, a deep AppExchange ecosystem provides industry-specific extensions: portfolio management for advisors, ratings integration for insurance, deal pipeline management for commercial banking, regulatory reporting tools. Most production FSC deployments use a base configuration plus several AppExchange products. Evaluate the ecosystem during initial planning; the right packages can dramatically reduce custom development.
How to set up Financial Services Cloud
Setting up FSC is a multi-quarter exercise. Plan the data model, choose the personas, configure integrations with core banking or wealth platforms, design the compliance posture, and roll out by line of business. Most successful FSC implementations engage a financial-services-specialist consulting partner with both Salesforce and industry expertise.
- Identify the business line and use cases
Retail banking, wealth management, insurance, commercial banking. Each has different workflows, data models, and integration touchpoints. The line drives every configuration decision.
- Provision FSC and install the managed package
AppExchange > Financial Services Cloud > Install. The package extends Salesforce with FSC-specific objects, page layouts, and Lightning Apps. Provisioning takes a few minutes per environment.
- Enable Person Accounts
Most FSC use cases require Person Accounts. Enable through Salesforce support if not already on. Person Account enablement is irreversible, so confirm before proceeding.
- Pick the persona configuration
Banker, Advisor, Insurance Agent. Apply the persona-specific Lightning App, page layouts, and reports. Customize for the specific organizational needs.
- Configure the Household relationship model
Build the relationship types (Primary Member, Spouse, Beneficiary, Trustee). Map how clients group into Households. Test the Household roll-up summaries with realistic client data.
- Set up Financial Accounts and integration
Connect to the source systems (core banking, wealth platform, insurance system). Define how Financial Accounts sync, what data flows, and what stays in the source. Validate with sample accounts before going live.
- Build Action Plans for key processes
Map the multi-step processes that drive the business: client onboarding, account opening, loan origination, claims processing. Build Action Plan templates for each. Pilot one process before expanding to all.
- Roll out by line of business and refine
Start with one line: wealth advisory, retail banking, or insurance. Train the team, gather feedback, iterate. Expand to other lines once the first stabilizes.
Banker, Advisor, Insurance Agent. Each comes with tuned page layouts, navigation, and reports.
Defines how clients group into Households. The foundation of FSC''s relationship-based view.
Multi-step process orchestration. Replaces ad-hoc task management for onboarding, claims, and other structured workflows.
- Person Account enablement is irreversible. Once enabled, you cannot disable it. Confirm Person Account fits the use case before flipping the switch.
- Integration with core banking, wealth, or insurance systems is the biggest cost factor. Plan integration scope carefully; underestimating integration produces budget surprises.
- Financial services compliance is operationally demanding. The platform supports the technical requirements; ongoing audit, training, and exception management remain the customer''s responsibility.
- Industry-specific consulting expertise matters. Generic Salesforce consultants miss regulatory and business considerations that specialist financial-services partners catch.
- Action Plans require careful design. Bad Action Plan templates produce friction for advisors and bankers; good ones reduce administrative burden significantly.
Trust & references
Cross-checked against the following references.
- Financial Services Cloud Product PageSalesforce
- Financial Services Cloud DocumentationSalesforce Help
Straight from the source - Salesforce's reference material on Financial Services Cloud.
- FSC OverviewSalesforce Help
- Action PlansSalesforce Help
- Household RelationshipsSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. Who can benefit from understanding Financial Services Cloud?
Q2. How does Salesforce's multi-tenant model affect Financial Services Cloud?
Q3. What architecture concept is Financial Services Cloud an example of?
Discussion
Loading discussion…