• Cert++
  • Practice
  • Certle
  • Review
  • Tracks
  • Checklist
  • Guides
  • Upgrade
Cert++
  1. Home
  3. Salesforce Accredited Agentforce Financial Services Professional

Salesforce Accredited Agentforce Financial Services Professional

Checklist progress

0/148Learned

Salesforce Accredited Agentforce Financial Services Professional

Study Checklist

  • Platform Administrator
  • Platform App Builder
  • Platform Foundations
  • Platform Developer
  • Platform Administrator II
  • Agentforce Sales Consultant
  • Agentforce Service Consultant
  • Platform Data Architect
  • Platform Development Lifecycle and Deployment Architect
  • Platform Identity and Access Management Architect
  • Platform Integration Architect
  • Platform Sharing and Visibility Architect
  • Heroku Architect
  • B2C Solution Architect
  • Experience Cloud Consultant
  • Agentforce Field Service and Operations Consultant
  • Agentforce Nonprofit Consultant
  • Data 360 Consultant
  • Omnistudio Consultant
  • CRM Analytics and Einstein Discovery Consultant
  • Platform User Experience Designer
  • Platform Strategy Designer
  • B2C Commerce Developer
  • JavaScript Developer
  • Omnistudio Developer
  • Platform Developer II
  • Marketing Cloud Engagement Administrator
  • Marketing Cloud Engagement Specialist
  • Marketing Cloud Engagement Consultant
  • Agentforce Sales Foundations
  • Business Analyst
  • Marketing Cloud Engagement Developer
  • Marketing Cloud Engagement Foundations
  • Agentforce Specialist
  • Agentforce Life Sciences Consultant
  • B2B Commerce Administrator AP
  • B2B Commerce Developer AP
  • Agentforce Consumer Goods AP
  • Agentforce Financial Services AP
  • Agentforce Health AP
  • Agentforce Manufacturing AP
  • MuleSoft Integration Foundations
  • MuleSoft Developer
  • MuleSoft Developer II
  • MuleSoft Platform Integration Architect
  • MuleSoft Platform Architect
  • Tableau Desktop Foundations
  • Tableau Data Analyst
  • Tableau Consultant
  • Tableau Server Administrator
  • Tableau Architect

Checklist progress

0/148Learned

Given the business needs of a customer, identify different business processes and outline encompassing system flows based on the existing environment.

0/6

  • Aligning referral intake with Lead creation, qualification, assignment, conversion, or downstream hand-offs when referrals generate Lead records
  • Documenting referral creation, disposition, SLA tracking, and conversion outcomes modeled with FSC Referral records
  • Identifying authoritative external systems—core banking, portfolio management, policy administration, mortgage LOS—which must sync with Financial Services Cloud
  • Outlining bidirectional flows for identities, holdings, beneficiaries, statuses, balances, transactions, referrals, disclosures between FSC and external finance platforms
  • Documenting how Financial Accounts, Financial Account Roles, Document Checklists, and onboarding automations initialize after client shells exist
  • Documenting Prospect-to-client progression from Lead capture through Person Account or Household Account creation in Financial Services Cloud

Given a scenario in which a customer wants a Financial Services Cloud solution, document the business needs, value, and vision of the customer to support their desired business outcomes.

0/5

Documenting success metrics and KPIs for an FSC implementation given a customer's stated business goals (e.g., advisor productivity, client retention, referral conversion rate)

Learn this concept
Unseen

Identifying the primary business drivers that differentiate FSC from standard Sales/Service Cloud for a financial services firm (e.g., relationship management, household view, regulatory requirements)

Learn this concept
Unseen

Mapping AML KYC onboarding surveillance playbook requirements Assessments Document Checklists masked fields consent collections

Learn this concept
Unseen

Selecting the correct FSC industry vertical module (Wealth Management, Retail Banking, Insurance, Mortgage, Commercial Banking) given a customer's described line of business and desired outcomes

Learn this concept
Unseen

Distinguishing between a current-state pain point (e.g., siloed data, no household view) and the FSC capability that directly addresses it during a discovery engagement

Learn this concept
Unseen

Given a set of existing business processes and flows, understand the current state of business architecture and determine how to leverage Financial Services Cloud capabilities.

0/6

  • Mapping books-and-records holdings and participant relationships from a legacy CRM to Financial Accounts and Financial Account Roles in FSC
  • Mapping legacy client and household entities to FSC Person Accounts, Household Accounts, and Account-Contact Relationships for retail banking and wealth personas
  • Mapping institutional or business counterparties to Business Accounts versus Commercial Accounts and related party roles in Financial Services Cloud
  • Assessing whether a financial firm's existing client hierarchy (individual, household, business) is best served by FSC Person Account, Business Account, or mixed account models
  • Determining which FSC features can replace custom-built processes in a legacy system versus which require customization or third-party solutions
  • Assessing the customer's current data quality, deduplication challenges, and data governance maturity to determine the scope of pre-migration data cleansing work needed before loading records into FSC
  • Associating treasury, lending, deposit, fiduciary, treasury services, merchant, escrow, or similar institutional Banking Financial Accounts with sponsoring Commercial Accounts
  • Associating adversely impacted Household Person Accounts Policies Financial Accounts demonstrating product exposures investigations remediation
  • Choosing appropriate FinancialAccount record types (Investment Account, Bank Account, Insurance Policy, Loan) based on described client financial product holdings
  • Designating Primary Group Member markers on Household memberships and interpreting how rollup seeds and Household reporting honor that designation
  • Designing a document management solution using FSC Document Checklist and Document Checklist Item objects to track required documents for client onboarding, Know Your Customer (KYC) workflows, or mortgage applications at each process stage
  • Designing Assessments questionnaires capturing AML suitability risk tolerance questionnaires linked Contacts Household Person Accounts onboarding stages
  • Applying Account Contact Relationship roles such as Authorized Signatory, Beneficial Owner, Director, and Guarantor in commercial onboarding workflows
  • Determining the correct use of Account-Contact Relationship (ACR) vs Contact-Contact Relationship (CCR) to represent a client's family members and their roles in FSC
  • Distinguishing between internal FinancialAccount records (assets managed by the firm) and External Financial Account records (held-away assets the firm does not manage) in FSC, and when to use each to build a complete client financial picture
  • Explaining how household rollups expose advisor-visible totals while Household members keep distinct Person Accounts and Financial Accounts where privacy rules require segregation
  • Identifying the correct use of Reciprocal Roles in FSC Contact-Contact Relationships to represent bidirectional relationships (e.g., Spouse/Spouse, Parent/Child, Attorney/Client)
  • Modeling holdings-level detail with FinancialHolding records under FinancialAccount when positions instruments must appear on relationship graphs
  • Evaluating archival regulatory analytics needs storing Financial Account Transaction detail rows authored inside Salesforce
  • Modeling client product interest and next-product-to-buy affinity data using Interest Tags (PersonInterest) on Contact records in FSC, and how advisors use this data to prioritize outreach
  • Modeling Household Accounts and Account Contact Relationships connecting dependent Person Accounts to a household rollup shell
  • Modeling insurance Claims tied to claimant Accounts or Contacts with links to Policies, Household context, and impacted Financial Accounts for investigations
  • Modeling Opportunities as pipeline vessels aligning investment loan insurance product pursuit stages forecasting revenue recognition
  • Modeling Insurance Policies and Coverage child records anchored to Household or Person Accounts for risk segmentation servicing
  • Modeling LoanApplicant demographic employment credit party records feeding underwriting validations exceptions queue
  • Modeling transactional cash flows debits credits fees with Financial Account Transaction rows distinct from summarized holdings snapshots
  • Modeling pledged collateral LoanApplicationProperty records alongside LoanApplicantIncome evidence supporting underwriting ratios
  • Recording quantified objectives using Financial Goal records linked to Household or Person Accounts for planning conversations
  • Relating Goals and Plans to advising Contacts versus Household rollup owners for servicing reports and segmentation
  • Propagating actionable Assessment findings onto Financial Goal Financial Plan records shaping advisor fiduciary documentation packages
  • Selecting between Person Account and Business Account record types in FSC when a customer has both individual retail clients and institutional/business clients
  • Selecting FinancialAccount as the umbrella object for brokerage, IRA, annuity, transactional deposit, and similar client-visible products described during requirements
  • Relating Opportunities to Financial Accounts seeded post close Financial Account Roles servicing teams retain continuity Household views
  • Selecting Integration Procedure FlexCards remote orchestrations projecting transactions transiently when volumes compliance favor external systems authoritative ledger
  • Selecting Commercial Accounts or legal shells that mirror onboarded entities and treasury servicing hierarchies described by the bank
  • Selecting the appropriate FSC Life Events and Milestones objects to capture client life changes (marriage, retirement, home purchase) that trigger advisor engagement
  • Structuring Complaint records tied Cases intake acknowledgement interim response SLA tracking supervisory routing
  • Using Financial Account Role records to relate contacts (and non-human participants where applicable) as primary owners, joint owners, trustees, beneficiaries, or related roles
  • Structuring Financial Plan containers that group Goals, timelines, review cadences, and fiduciary checkpoints
  • Anchoring Residential Loan Applications borrower Coborrowers Person Accounts compliance milestones LOS integrations
  • Choosing between role hierarchy, sharing rules, and FSC's Relationship Group sharing to grant a branch manager visibility into all client accounts managed by advisors in their branch
  • Designing the authenticated and guest user sharing model when integrating FSC with an Experience Cloud portal, ensuring portal clients can access only their own Financial Accounts, Insurance Policies, and Documents while preventing cross-client data exposure
  • Determining the field-level security requirements for sensitive financial data (account balances, SSN, policy numbers) for different user profiles in FSC
  • Determining the appropriate OrgWide Default (OWD) sharing settings for FSC core objects (FinancialAccount, FinancialHolding) given a requirement for advisors to see only their own clients' data
  • Selecting the correct FSC Permission Sets and Permission Set Groups to grant advisor versus branch manager versus compliance officer access levels
  • Understanding that FSC uses Apex Managed Sharing (programmatic sharing) to enforce its relationship-based record access model and the implications for custom sharing rule design
  • Configuring referral stage lifecycles representing acceptance disqualification fulfillment conversion confirmations audit evidence
  • Choosing between OmniStudio FlexCards and standard Lightning Web Components for surface-level client financial data presentation on the FSC record page
  • Configuring authenticated Experience Cloud sharing sets so Household and portal users see only Accounts, Financial Accounts, Insurance Policies, Documents, and Assessments they are entitled to view
  • Configuring referral source fields attribution models aligning marketing branches wealth retail insurance partner programs
  • Configuring referral type picklists delineating intra line business warm introductions remediation escalations regulatory referrals
  • Designing Interaction Summary intake patterns covering attendees topics decisions disclosures follow ups escalation paths
  • Determining which CRM Analytics for FSC (Einstein Analytics) app and dashboard template best fits a described reporting requirement (e.g., Wealth Management, Retail Banking, Insurance)
  • Determining when to use FSC's native Action Plans versus Salesforce standard Tasks and Activities for advisor-client engagement workflows
  • Identifying when OmniStudio OmniScripts are the appropriate tool for guided, multi-step client onboarding or service workflows in FSC versus standard Flow
  • Selecting Change Data Capture topics when cores publish deltas seconds tolerances Financial Accounts must mirror intraday snapshots
  • Relating Interaction Summaries Household Person Contacts Financial Accounts Opportunities Cases surfaced conversation threads
  • Selecting Experience Cloud UX that exposes financial summaries, valuations, Household rollups, and guided workflows using FlexCards or OmniScripts
  • Selecting secure messaging document upload Collaboration referencing Document Checklists eSignature bridging external vaults
  • Selecting scheduled SOAP REST reconciliation jobs nightly tolerances supervisory controls prefer batched deltas versus streaming flood
  • Selecting Platform Events when partner microservices portals analytics hubs fan out enrichment beyond Financial Accounts single consumer chain
  • Configuring multi-language support in FSC for a firm with advisors and clients in multiple locales, including translation workbench considerations for custom FSC fields
  • Configuring the FSC Geographic Territory Hierarchy (Region, Division, Branch) and assigning users to branches to enforce branch-level data visibility
  • Planning Corporate multi-currency activation schedules exchange-rate governance before advisors book multicurrency Households transactions
  • Explaining how multi currency posting affects Financial Account balances, Household rollup displays, dashboards, and CRM Analytics currency bridging expected by supervisory finance stakeholders
  • Designing intake triage classifications Complaint Case statuses SLA acknowledgements interim responses escalate supervisors
  • Designing onboarding automations that seed starter Financial Accounts Financial Account Roles Document Checklists when net new Persons activate
  • Designing Prospect Lead conversion choreography mapping queues assignment rules culminating Person Household Account shells regulators expect
  • Designing the future-state claims process for an FSC Insurance implementation, from first notice of loss through claim adjudication and payout, mapping each step to FSC objects
  • Designing the future-state financial review process (annual review) using FSC Action Plans and Interaction Summaries to ensure consistent advisor behavior
  • Designing the future-state referral management process in FSC, specifying how referrals are created, assigned, tracked, and closed across advisor teams
  • Determining the appropriate ETL/data loading tool (Data Loader, Informatica, MuleSoft) given constraints on data volume, transformation complexity, and bidirectional integration requirements for FSC
  • Handling the mapping of legacy 'joint account' relationships to FSC's FinancialAccountRole object with multiple role types (Primary Owner, Joint Owner, Beneficiary)
  • Planning a data quality and deduplication strategy before migrating client records into FSC to avoid duplicate Person Accounts and Household Accounts
  • Sequencing FSC data migration loads in the correct dependency order: Accounts (Households, Person Accounts) → Contacts → Financial Accounts → Financial Account Roles → Financial Holdings
  • Using External IDs on FSC objects during data migration to maintain referential integrity when loading related records (e.g., linking FinancialAccountRole to both Contact and FinancialAccount via external ID)
  • Identifying a dependency between an FSC data migration story and a downstream rollup configuration story when sequencing sprints for an FSC implementation
  • Prioritizing FSC implementation user stories using a given prioritization framework (MoSCoW, Business Value) when there are dependencies between data model setup and UI configuration stories
  • Activating Interest Tag catalogs synonyms align marketing demand generation programs referencing regulatory marketing compliance
  • Configuring Action Plan Templates in FSC for a recurring client annual review process, including the tasks, task owners, and days-from-start sequencing
  • Configuring Complaint object record types, status picklist values, page layouts, and assignment rules in FSC to route incoming complaints by type (suitability, service quality, product) to the correct handling team or queue
  • Configuring Interaction Summary record types and subject picklist values in FSC to support structured meeting notes for advisors
  • Configuring Life Event types and icons in FSC Setup to match the firm's client engagement model (e.g., Birth of Child, Retirement, Home Purchase)
  • Configuring Reciprocal Role definitions for Contact-Contact Relationships in FSC to ensure bidirectional relationship labels are accurate (e.g., Parent/Child, Trustee/Beneficiary)
  • Creating custom fields on the FinancialAccount object to capture firm-specific data (e.g., risk tolerance, advisory fee model) while adhering to FSC data model best practices
  • Configuring the FinancialAccount object's record types and page layouts to present relevant fields for Investment Accounts versus Checking Accounts versus Insurance Policies
  • Defining Goal record types page layouts branching wealth bank insurance methodologies referenced planning workshops
  • Configuring Document Checklist Templates in FSC Setup to define required documents for each stage of a mortgage application or client onboarding workflow, and activating the templates for the correct record types
  • Linking Goals Financial Accounts surfaced progress indicators Highlights panels FlexCards executive storytelling leadership reviews compliance supervision
  • Embedding Interest Tags Lightning components Coaching advisors annotate propensity signals Contact pages CRM Analytics downstream
  • Assigning the correct FSC Permission Sets (FSC Standard User, FSC Admin, Insurance, Mortgage) to users based on their job role and required feature access
  • Assigning least privilege Financial Services permission sets licensed Experience authenticated users aligning module entitlements disclosures
  • Configuring profile-level object and field permissions for FSC-specific objects (FinancialAccount, FinancialHolding, InsurancePolicy) to enforce read-only vs edit access by role
  • Tightening site sharing restricting portal Household Person Financial Account Insurance Documents cross household lateral movement thwarted supervisory expectations
  • Setting up the FSC App and configuring navigation items for advisor users, including selecting the correct record home page for Person Account vs Household Account
  • Setting up OmniStudio FlexCards on the FSC Account record page to surface financial summary data from related Financial Account records
  • Configuring the FSC Lightning Record Page layouts for the Account (Household) page using the correct FSC standard components: ARC, Financial Account list, Rollup components
  • Building a Record-Triggered Flow in FSC to automatically create a FinancialAccount record and a FinancialAccountRole (Primary Owner) when a new Lead is converted to a Person Account
  • Choosing between a Record-Triggered Flow and an OmniStudio OmniScript to automate a multi-step client onboarding process in FSC, given a requirement for a guided user interface
  • Using OmniStudio DataRaptors to read and transform Financial Account data from external sources and populate FSC object records via Integration Procedures
  • Using Flow to automate the creation of Action Plan records when specific Life Events (e.g., Retirement) are logged on a client's FSC record
  • Using OmniStudio FlexCards to build a contextual data panel on the FSC Account record page that surfaces data from external financial systems without storing it in Salesforce
  • Identifying when a Screen Flow is preferred over an OmniScript for advisor-facing guided processes in FSC (e.g., when the process is simple and OmniStudio licensing is not available)
  • Building Lead Assignment Rules in FSC to automatically route incoming leads to the appropriate queue or advisor based on lead criteria (e.g., state, product interest, asset threshold)
  • Configuring Lead record types and page layouts in FSC to differentiate between retail banking leads, wealth management leads, and insurance leads, each with relevant fields
  • Creating Lead queues in FSC for each line of business and configuring the correct queue membership (users and roles) to ensure leads are routed to the right team
  • Determining whether to use a Lead Web-to-Lead form, a manual Lead entry process, or an integration-driven Lead creation process to support a customer acquisition campaign for an FSC client
  • Mapping Lead conversions onto Person Contacts preserving marketing attribution compliance questionnaires onboarding Document Checklists
  • Selecting post-conversion spawning Opportunities Referrals Work Orders guaranteeing downstream desks inherit context escalation paths
  • Configuring an Integration User profile in FSC with the minimum required object/field permissions to push Financial Account balance updates from a portfolio management system
  • Identifying the correct API field names for FSC managed package fields (using FinServ__ namespace prefix) when configuring an integration mapping in MuleSoft or a similar middleware
  • Determining which FSC fields should be mapped to corresponding core banking fields (e.g., FinancialAccount.Balance → core system account balance) to support a nightly batch integration
  • Creating and populating External ID fields on FSC objects (Account, Contact, FinancialAccount) to support upsert operations from a core banking integration
  • Configuring ARC node actions (Quick Actions, Global Actions) to allow advisors to create related records (e.g., Referral, Interaction Summary) directly from the ARC visualization
  • Configuring FSC Rollup Summary settings to aggregate Financial Account balances to the Household Account (Contact) level, including selecting the correct rollup type (Assets, Liabilities, Total AUM)
  • Configuring the Actionable Relationship Center (ARC) on the FSC Household Account page to display the correct node types (Person Account, Financial Account, Insurance Policy) and relationship filters
  • Determining the impact of adding a new household member to an existing Household Account on existing rollup values and ARC display
  • Enabling and configuring FSC Householding, including setting the Primary Group Member flag on Account-Contact Relationship records and understanding its effect on rollup calculations
  • Scheduling and monitoring FSC rollup recalculation batch jobs in Salesforce Scheduled Jobs, understanding the impact of data volume and rollup configuration complexity on batch processing time, and identifying when rollup values may be stale
  • Troubleshooting an ARC configuration where related Financial Accounts are not appearing as nodes for a Household Account, identifying the most likely cause (missing configuration, sharing issue, or missing relationship type)
  • Understanding the difference between FSC Rollup__c (managed package rollups) and standard Salesforce Roll-Up Summary fields, and when each is appropriate for FSC implementations
  • Configuring Branch Management sharing so that a branch manager can access all client records (Person Accounts, Financial Accounts) owned by advisors in their assigned branch
  • Creating criteria-based or owner-based sharing rules for FSC objects when the role hierarchy alone is insufficient to grant cross-team visibility (e.g., a compliance team needing read access to all Financial Accounts)
  • Understanding the limitations of manual sharing for FSC objects and when to use Apex Managed Sharing or sharing rules instead
  • Configuring FSC's built-in sharing mechanism for Financial Accounts so that the Primary Financial Account Owner (advisor) has read/write access while the client's household members have read-only access
  • Designing dashboards combining rollup sourced Assets Under Management liability balances referral KPI tiles executive reviews coaching cadences regulators request
  • Reporting referral volume aging sourced advisors receiving teams diagnosing pipeline hygiene cross division programs SLA adherence
  • Using report filters and groupings on FSC Financial Account records to report on total client assets by account type, owner (advisor), or branch
  • Creating a report type for FSC objects (e.g., Financial Accounts with Financial Holdings, Contacts with Account-Contact Relationships) that is not available as a standard report type
  • Reporting conversion uplift monetary attribution comparing wealth retail mortgage insurance cohort dashboards leadership storytelling supervisory reviews
  • Designing dashboards enumerating Household coverage active Persons Advisors books segmentation filters leadership pulse
  • Determining when to use CRM Analytics (Einstein Analytics) for FSC versus standard Salesforce reports and dashboards based on data volume, multi-object join requirements, or predictive analytics needs
  • Enabling and configuring the Person Account model as a prerequisite for FSC when the org was previously using Contact-only architecture
  • Sequencing enablement prerequisites industry activation installing Financial Services managed artifacts validating Person Accounts before turning feature toggles
  • Sequencing post-install Financial Services administration pages that activate Householding, Household rollups, Actionable Relationship Center, Assessments, and Branch Management per rollout waves
  • Configuring FSC Settings (FinancialServicesCloud custom settings or Setup menu) to enable Householding, Rollups, ARC, and other core FSC features
  • Migrating Financial Services configuration packages Change Sets Salesforce CLI pipelines sequencing destructive changes mitigations rehearsal cutovers

Prepare for the Exam

Play Today's Certle
Back to track

Study Community

Ask questions and get the latest info from other Salesforce Accredited Agentforce Financial Services Professional studiers. 593 members and growing.

Go to Discord

Identifying the primary business drivers that differentiate FSC from standard Sales/Service Cloud for a financial services firm (e.g., relationship management, household view, regulatory requirements)

Explainer

Learn More

Practice Question

Keep going

Next conceptMapping AML KYC onboarding surveillance playbook requirements Assessments Document Checklists masked fields consent collections

Checklist progress

0/148 (0%)

0 of 148 concepts learned

Tip: You can filter concepts by status.

Prepare for the Exam

Play Today's Certle
Back to track

Study Community

Ask questions and get the latest info from other Salesforce Accredited Agentforce Financial Services Professional studiers. 593 members and growing.

Go to Discord

Explainer

Financial Services Cloud extends the standard Salesforce platform to meet the unique compliance and relationship needs of financial institutions. It provides purpose-built data models and tools for sectors like banking and wealth management to unify customer views and automate financial tasks.

Core information
  • FSC extends Sales and Service Cloud with sector-specific data models for banking, wealth management, and insurance to capture complex financial accounts and relationships.
More details and nuances
  • Households are represented as Business Accounts rather than Person Accounts, requiring a Party Relationship Group with the type Household to function correctly.