Join our Community of Marketers.
Imagine you are a financial advisor helping a married couple plan for their future. David has a savings account, Sarah has a checking account, and they share an investment account. They also have a home loan and want to save money for their daughter’s education.
If you look at David’s records alone, you won’t see the family’s complete financial situation. The same problem occurs if you only review Sarah’s accounts.
Salesforce Financial Services Cloud (FSC) helps financial institutions solve this problem by connecting customers, household members, financial accounts, and their relationships.
Instead of keeping every customer’s information separate, it gives financial advisors a more connected view of the people they serve.
But how does Salesforce organize these relationships? What is the difference between a household and a financial account? And how does Salesforce know who owns a shared investment account?
Let’s understand these concepts through simple examples.
What Is a Household in Salesforce Financial Services Cloud?
A household is a group of people whose personal or financial lives are connected.
For example, consider the Davidson family:
- David Davidson: Works full-time and manages the family’s main expenses.
- Sarah Davidson: David’s wife, who has her own savings and investments.
- Emma Davidson: Their daughter, who has an education savings goal.
In Financial Services Cloud, these three people can be connected through a group called the Davidson Household.
The household helps the financial advisor understand the family as a connected group rather than three unrelated customers.
It can also provide a combined view of selected financial accounts, goals, activities, and other information when the appropriate features are configured.
A household may have relationships with people outside the immediate family, such as an accountant, attorney, or financial advisor.
These people can be represented as related contacts without necessarily becoming household members.
Why Are Households Important for Financial Advisors?
Imagine David and Sarah want to invest in a retirement plan.
David has $25,000 in savings, while Sarah has $15,000. They also share an investment account worth $80,000.
If the advisor only reviews David’s savings, the recommendation may be based on incomplete information.
By viewing the household and its related financial records, the advisor can better understand the family’s available resources, existing obligations, and long-term goals.
The important point is that a household helps organize financial relationships. It does not replace the individual customer records.
How Does Salesforce Store Household Relationships?
Salesforce uses connected objects to represent customers, households, and the relationships between them.
An object is simply a place where Salesforce stores a particular type of information.
For example, an Account record might represent a customer, while another record represents a household.
Here are the main objects involved in the standard Financial Services Cloud household data model.
| Salesforce Object | What It Does |
| Person Account | Represents an individual customer, such as David or Sarah. |
| Business Account | Can represent a group, such as the Davidson Household. |
| Account Contact Relationship | Connects individuals to household records and stores membership details. |
| Party Relationship Group | Stores information describing a group, such as a household. |
| Contact Contact Relationship | Represents relationships between individual contacts. |
How Do These Objects Work Together?
Let’s look at the Davidson Household.
First, Salesforce stores David, Sarah, and Emma as individual customer records.
Next, a Business Account represents the Davidson Household.
Account Contact Relationship records connect the family members to that household.
When Person Accounts are used, the relationships reference their underlying Contact records.
The Party Relationship Group object can provide additional group information in the supported standard data model.
Think about these objects in three parts:
Person Accounts: Who are the customers?
Account Contact Relationships: Which people belong to the household?
Household Business Account: Which group connects those people?
The Party Relationship Group adds information about the group itself.
This structure allows Salesforce to maintain individual customer records while also showing how customers belong to a household.
The accompanying diagram illustrates this relationship alongside the separate financial account ownership model.
Salesforce explains the underlying group structure in its official Financial Services Cloud household documentation.
What Is the Difference Between Primary Member and Primary Group?
Two important household settings are Primary Member and Primary Group.
They may sound similar, but they serve different purposes.
- Primary Member
The Primary Member identifies the main person to contact about matters affecting the household.
For example, David might be the Primary Member of the Davidson Household.
If the financial advisor needs to discuss a family-related financial planning appointment, David may be the first contact.
However, being the Primary Member does not mean David owns all the financial accounts associated with the household.
It also does not automatically give him access to Sarah’s private financial records.
- Primary Group
The Primary Group identifies the group in which a member’s selected information is rolled up.
Sarah might be connected to multiple groups, but she can have only one Primary Group for this household membership behavior.
If the Davidson Household is Sarah’s Primary Group, selected financial information can contribute to that household’s summaries when the rollup settings allow it.
Here is the easiest way to remember the difference:
| Setting | Main Purpose |
| Primary Member | Identifies the main household contact. |
| Primary Group | Determines the group used for the member’s selected information rollups. |
Remember: Primary Member is about the main contact. Primary Group is about where information is summarized.
What Are Financial Accounts in Salesforce Financial Services Cloud?
A Financial Account represents a financial product or account associated with a customer.
Common examples include checking accounts, savings accounts, investment accounts, credit cards, and loans.
For example, David might have:
- A checking account for monthly expenses.
- A savings account for emergencies.
- An investment account for retirement.
- A home loan with an outstanding balance.
Each financial product can be represented using a Financial Account record.
These records can contain information about the financial product, such as its type and status.
Other related records may store balances, transactions, and additional details.
What Is the Difference Between Account and Financial Account?
This is one of the most important distinctions for beginners.
A regular Salesforce Account represents a customer, organization, or group.
A Financial Account represents a financial product.
For example:
David Davidson = Person Account
David’s savings account = Financial Account
David is the customer. His savings account is the financial product.
Salesforce needs to store both records and connect them correctly.
If you are still learning Salesforce objects, relationships, and junction objects, our article about understanding data modeling for the Salesforce Platform App Builder exam explains the basic concepts.
How Are Financial Accounts Connected to Household Members?
Now imagine David and Sarah share an investment account.
Both are owners of the same financial product.
How should Salesforce represent this relationship?
In the standard Financial Services Cloud data model, Salesforce uses the Financial Account Party object.
Financial Account Party connects a person or organization to a Financial Account and records that party’s role.
Consider these example records:
| Financial Account | Related Customer | Role |
| David’s Savings | David | Owner |
| Sarah’s Checking | Sarah | Owner |
| Joint Investment | David | Owner |
| Joint Investment | Sarah | Owner |
The roles shown are illustrative. Available values can vary by implementation.
Notice that the joint investment account appears twice in the relationship table.
That does not mean Salesforce needs two separate investment account records.
There is one Financial Account for the investment, with two Financial Account Party records identifying David and Sarah as owners.
This structure helps the financial institution manage joint accounts and other relationships without unnecessarily duplicating the underlying financial product.
What Is Financial Account Role?
Salesforce supports both standard Financial Services Cloud objects and objects from the managed package.
The managed package uses a different approach to some financial account relationships.
For example, it includes Primary Owner and Joint Owner fields on the Financial Account record.
It also uses Financial Account Role to represent other people or organizations involved with a financial account, such as beneficiaries and trustees.
The distinction is important when designing an implementation or answering a certification question.
| Feature | Standard Data Model | Managed Package Model |
| Financial product | Financial Account | Financial Account |
| Account ownership | Financial Account Party | Primary Owner and Joint Owner fields |
| Additional related parties | Financial Account Party | Financial Account Role |
| Financial balances | Financial Account Balance object | Balance fields on Financial Account |
The important lesson: Financial Account Party and Financial Account Role are not interchangeable names for the same object.
Their use depends on the data model.
Salesforce provides a detailed comparison in its official Financial Account Management Standard Objects documentation.
How Does Salesforce Track Balances, Transactions, and Investments?
Financial advisors need more than a list of accounts. They also need information about balances, transactions, and investments.
In the standard Financial Services Cloud data model, several related objects support these requirements.
- Financial Account Balance
Financial Account Balance stores information about different types of financial balances.
For example, a credit card may have an available credit balance, while a loan may have an outstanding principal balance.
These values represent different financial measurements.
Storing balance information in related records helps Salesforce distinguish between them.
- Financial Account Transaction
Financial Account Transaction stores details about activities associated with a financial account.
For example, a customer might deposit money, withdraw funds, make a payment, or transfer money between accounts.
These transaction records help advisors understand account activity when the appropriate data is available.
- Securities Holding
For investment accounts, Securities Holding can represent financial securities held within an account.
For example, Sarah’s investment account might contain shares in several companies.
Securities Holding can help represent those positions in the standard data model.
One important point is that Salesforce does not automatically know a customer’s current bank balance or investment activity.
Financial institutions must provide that information through supported integrations, data imports, or other configured processes.
How Do Household Financial Rollups Work?
A household rollup brings selected financial information together to provide a combined view.
Let’s return to the Davidson family.
Their financial information looks like this:
| Financial Information | Amount |
| David’s Savings | $25,000 |
| Sarah’s Savings | $15,000 |
| Joint Investment Account | $80,000 |
| Total Listed Financial Assets | $120,000 |
| Outstanding Home Loan | $40,000 |
If these are the only assets and liabilities included in our example, the net balance would be:
$120,000 – $40,000 = $80,000
This is the net balance of the listed financial assets and liabilities, not necessarily the household’s complete net worth.
For example, the calculation does not include the value of their home or other assets they may own.
The example simply demonstrates how selected financial records can contribute to a household summary.
Why is Rollup Configuration Important?
Creating a household does not automatically guarantee that every financial record will appear in its summary.
The relevant membership relationships, rollup settings, and financial account records must be configured correctly.
Administrators also need to prevent shared financial accounts from being counted twice.
David and Sarah’s joint investment account is worth $80,000.
It should not automatically become $160,000 in the household summary simply because both customers are related to it.
The calculation must follow the correct account ownership and aggregation rules.
Standard Rollups vs. Managed Package Rollups
Salesforce supports different approaches to aggregating household information.
Managed package record rollups aggregate related records at the client or group level. A record is associated with a single household for this rollup mechanism.
Standard Record Rollup Definitions provide more flexible aggregation. They can support aggregating the same record into multiple groups and applying filter conditions.
Financial summaries also use different mechanisms.
The managed package provides Rollup By Lookup rules for financial calculations. The standard model provides Financial Summary Rollup capabilities based on Data Processing Engine definitions.
These mechanisms should not be confused with ordinary household membership settings.
For administrators, the practical lesson is simple:
Before troubleshooting a missing household balance, identify which data model and rollup feature the organization uses.
Then check the relevant membership, financial relationships, rollup definitions, and calculation rules.
How Can Financial Advisors Use Household Relationships?
Understanding household relationships helps advisors make better use of customer information.
Imagine David and Sarah are saving for Emma’s university education.
If the advisor reviews David’s records alone, the family may appear to have limited savings.
But a household view could reveal Sarah’s savings, their shared investments, outstanding loans, and education goals.
That information can lead to a more useful financial planning discussion.
Household relationships can help advisors understand financial responsibilities, identify relevant financial goals, and prepare personalized recommendations.
However, being connected within a household is not the same as having permission to see every household member’s confidential information.
A spouse, dependent, or other relative does not automatically gain access to financial records because of a relationship recorded in Salesforce.
Financial institutions must apply appropriate permissions, record-sharing controls, and privacy requirements.
What Should Salesforce Administrators Check When Household Data Is Incorrect?
Even a well-designed household model can produce incomplete information if records or settings are wrong.
Here are some common issues.
- Missing Household Membership
Sarah may have a Person Account, but she may not be correctly associated with the Davidson Household.
The administrator should review the relevant Account Contact Relationship record.
- Incorrect Primary Group
Sarah may belong to several groups, but the Davidson Household may not be her configured Primary Group.
This could affect which selected records contribute to household summaries.
- Missing Financial Account Relationships
The joint investment account may exist, but David or Sarah may not be properly connected to it.
In the standard data model, the administrator should check the Financial Account Party records.
- Incorrect Rollup Configuration
The necessary rollup features may not be enabled or configured to include the required records.
The administrator should review the specific rollup mechanism rather than assuming every household uses the same aggregation rules.
- Outdated Financial Information
The account relationships may be correct, but the balances may be outdated.
Administrators should investigate the relevant data integrations, update processes, and balance records.
- Inappropriate Data Access
Household membership does not replace Salesforce security.
The organization must still control which users can view or modify financial information.
Professionals responsible for these systems should understand the relationship between data models and security. Our guide to designing Salesforce data architecture for scale and security provides additional background.
Why Are Household Relationships Important for Salesforce Certification Preparation?
Household relationships and financial account data are useful concepts for professionals studying Salesforce Financial Services Cloud.
Certification-style scenarios may ask candidates to identify the appropriate object, describe how financial relationships should be represented, or investigate missing household information.
The best preparation approach is to understand the business requirement before choosing an object or feature.
Scenario 1: Two Customers Own One Investment Account
A financial institution has two customers, David and Sarah.
Both own the same investment account.
The institution uses the standard Financial Services Cloud data model and wants to record both owners without creating duplicate Financial Account records.
Which object should represent their ownership relationships?
Correct Answer: Financial Account Party
Financial Account Party connects customers to the underlying Financial Account.
The institution can maintain one investment account record and use separate Financial Account Party records for David and Sarah.
Each record describes the customer’s relationship to the financial product.
If the institution instead uses the managed package model, it can use the Primary Owner and Joint Owner fields to identify the account owners.
The correct implementation depends on the data model.
Scenario 2: Financial Information Is Missing from a Household
Sarah belongs to the Davidson Household, but her financial information does not appear in the expected household summary.
What should the administrator investigate?
First, check Sarah’s household membership and Primary Group setting.
Next, confirm that the financial account relationships are correct.
Finally, review the configured rollup definitions or managed package settings to determine whether Sarah’s information should be included.
The important lesson is that a customer can belong to a household without every related record automatically appearing in the household summary.
Scenario 3: A Spouse Requests Access to Another Member’s Financial Records
Sarah is a member of the Davidson Household.
She asks to see all the details of David’s personal financial accounts.
Does her household membership automatically grant access?
No.
Household relationships describe how customers are connected. They do not, by themselves, establish authorization to view confidential financial information.
The organization must follow its permissions, sharing configuration, and applicable privacy requirements.
This scenario helps distinguish data relationships from data access rights.
Key Concepts to Remember
| Concept | What to Remember |
| Household | A group of connected people or entities. |
| Primary Member | The main contact for the household. |
| Primary Group | The group used for selected member rollups. |
| Account Contact Relationship | Connects individuals to household records. |
| Financial Account | Represents a financial product. |
| Financial Account Party | Represents financial account parties and roles in the standard model. |
| Financial Account Role | Represents related-party roles in the managed package. |
| Household Rollup | Combines selected information using configured aggregation rules. |
These concepts are more useful when understood through practical examples rather than memorized as isolated definitions.
Final Thoughts
Salesforce Financial Services Cloud helps financial institutions understand customer relationships and financial information in a more connected way.
A household groups related people. Account Contact Relationship records describe household membership. Financial Accounts represent financial products, while Financial Account Party or the managed package ownership fields and roles describe who is associated with those products.
Configured rollups can then help advisors see selected financial information at the household level.
For Salesforce administrators, accurate relationships, correct rollup configuration, and proper data access controls are essential.
For certification candidates, the most useful skill is understanding which object or feature solves a particular business requirement.
Remember three simple ideas:
A household tells you who is connected.
A Financial Account tells you what financial product exists.
A financial account relationship tells you how a customer is connected to that product. Understand these three concepts, and the Salesforce Financial Services Cloud data model becomes much easier to work with.