Business Account
A Business Account in Salesforce is the standard B2B-style Account record representing a company, organisation, or institution rather than an individual.
Definition
A Business Account in Salesforce is the standard B2B-style Account record representing a company, organisation, or institution rather than an individual. It is the default Account shape: a single Account record represents one company, and Contacts (individual people) hang off the Account through their AccountId field. In a pure B2B org, every Account is a Business Account; the distinction only becomes important when Person Accounts (the B2C variant) are also enabled. Then Business Account and Person Account coexist in the same org, and both record types share the Account object's underlying schema while differing in how Contact-side data is represented.
Business Account is what Salesforce CRM was originally built around. The standard data model assumes Accounts are companies with Contacts, Opportunities, Cases, and Activity related to the company. Sales reps work Opportunities tied to Business Accounts. Service Agents work Cases tied to Business Accounts and the Contacts within them. Reporting rolls up to the Business Account. When a Salesforce org enables Person Accounts, the model bends to support direct-to-consumer scenarios; Business Accounts remain available for the B2B side of the business. Understanding the Business Account versus Person Account distinction is foundational to any data model decision in Salesforce.
How Business Accounts shape the Salesforce B2B data model
The default Account structure
A Business Account holds the company's name, industry, annual revenue, ownership, address, parent-company lookup, and many other firmographic fields. Contacts attached through AccountId represent the people inside the company. Opportunities, Cases, Activity, Files, and Notes all link back through their parent lookup, with the Business Account as the customer hub.
Business Account versus Person Account
Business Account is the B2B shape (company + contacts). Person Account is the B2C shape (one record represents one individual, with no separate Contact). Enabling Person Accounts is a one-way org setting; once on, Business Accounts and Person Accounts coexist. Most B2B orgs leave Person Accounts off; B2C orgs require them; orgs serving both audiences typically enable Person Accounts and run both kinds in parallel.
Record Type implications
When Person Accounts are enabled, Account Record Types differentiate Business Accounts from Person Accounts. Page layouts, validation rules, and automation can vary per Record Type. The distinction matters because what is sensible for a B2B Account (Industry = Healthcare, AnnualRevenue = 50M) does not apply to a B2C individual.
Account Hierarchy on Business Accounts
Business Accounts can form parent-child hierarchies through the ParentId field. A holding company is the parent; subsidiaries are children. Salesforce shows the hierarchy on the View Account Hierarchy page and supports rollup queries. The hierarchy is essential for global enterprise accounts; it does not apply to Person Accounts.
Account Teams and Business Accounts
Business Accounts are the parent for Account Team Members (the AE, SE, CSM, and Executive Sponsor assigned to the account). Each Team Member has a role and access level. Account Teams shape collaboration around enterprise B2B selling and are less commonly used on Person Accounts.
Reporting and dashboards on Business Accounts
Most B2B reports start from Account: Pipeline by Account, Activity by Account, Coverage by Account. Custom report types let admins join Account to its Contacts, Opportunities, Cases, and custom related objects. The Business Account is the central join target in B2B reporting.
Industries solutions and Business Accounts
Financial Services Cloud, Manufacturing Cloud, Communications Cloud, and other Industries products extend the Business Account model with industry-specific fields and related objects (Financial Account, Production Plan, Service Contract). Business Account remains the central anchor; industries fields layer on without changing the Account-Contact-Opportunity backbone.
Common pitfalls
Three patterns recur. Enabling Person Accounts in a pure B2B org adds complexity with no payoff. Mixing B2B and B2C reporting on the same dashboard without filtering by Record Type produces confusing aggregates. And neglecting Account Hierarchy in enterprise sales results in scattered relationships that should be a single rolled-up account view.
How to use Business Accounts effectively
Business Accounts come out of the box. The work is configuring them for the specific B2B model the org runs, defining Record Types if Person Accounts are also enabled, and building the right hierarchy and team structures.
- Confirm the Account model
Decide whether the org runs B2B only (Business Accounts), B2C only (Person Accounts), or both. The decision drives Record Type setup and Person Account enablement.
- Configure Record Types if needed
When both kinds coexist, configure Business Account Record Types with the B2B fields, validation rules, and page layouts. Restrict B2C fields to Person Account Record Types only.
- Set up Account Hierarchy
For enterprise accounts, populate the ParentId field. Build hierarchy-aware reports that roll children up to the parent for a unified view.
- Configure Account Teams
For complex B2B sales, enable Account Teams. Define the standard roles (AE, SE, CSM, Executive Sponsor) and add team-based sharing rules.
- Build B2B-specific reports and dashboards
Pipeline by Account, Activity by Account, Coverage by Account. Filter by Record Type to exclude Person Accounts when reporting is B2B-specific.
- Enabling Person Accounts is one-way. Once on, the option cannot be cleanly disabled, so confirm the business need before flipping the switch.
- Mixing B2B and B2C reporting without Record Type filters produces confusing aggregates. Filter explicitly.
- Account Hierarchy is opt-in; ParentId is null by default. Without explicit hierarchy population, enterprise accounts look fragmented.
- B2B-specific automation (Account Teams, Industries fields) does not apply to Person Accounts. Plan automation per Record Type.
Trust & references
Cross-checked against the following references.
- Accounts OverviewSalesforce Help
- Person Accounts OverviewSalesforce Help
Straight from the source - Salesforce's reference material on Business Account.
- Account HierarchySalesforce Help
Hands-on resources to go deeper on Business Account.
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. What does a Business Account represent?
Q2. In a B2B scenario, how are people at a company typically modeled?
Q3. When might you NOT want to use Business Accounts?
Discussion
Loading discussion…