Business Account
A Business Account in Salesforce is the standard Account record that represents a company, organisation, or institution rather than a single individual.
Definition
A Business Account in Salesforce is the standard Account record that represents a company, organisation, or institution rather than a single individual. It is the default shape of the Account object. One Account record stands for one company, and the people who work there are stored as separate Contact records linked through the Contact's AccountId field. In a business-to-business org, every Account is a Business Account by definition.
The term only becomes meaningful once Person Accounts, the consumer variant, are switched on in the same org. At that point Business Accounts and Person Accounts live side by side on the one Account object, separated by record type. A Business Account keeps the classic company-plus-contacts structure, while a Person Account folds an account and a contact into a single record for an individual. Knowing which model an org uses is the first decision behind almost every Account, Contact, and Opportunity choice you make.
How the Business Account model fits together
The company-and-contacts data structure
A Business Account stores firmographic detail about the organisation. Standard fields include Account Name, Account Owner, Industry, Annual Revenue, Type, Ownership, Account Site, Rating, and the Billing and Shipping addresses. Several of these, such as Industry, Annual Revenue, Ownership, and Account Site, are meant for companies and have no sensible meaning for an individual consumer. The people who work at the company are not stored on the Account itself. They are separate Contact records, and each Contact points back to its company through the AccountId lookup. This one-to-many link is the backbone of B2B CRM in Salesforce. From the Account you can reach every Contact, and from a Contact you can reach the parent company. Opportunities, Cases, Activities, Files, and Notes all hang off the same hub through their own parent lookups. The result is a single customer record that pulls together everyone you deal with at that company and everything that has happened with them. Reps open the Account and see the whole relationship in one place, which is exactly what the original Salesforce data model was designed to deliver.
Business Account versus Person Account
The cleanest way to understand a Business Account is to compare it with its consumer counterpart. A Business Account is the B2B shape: a company record with separate Contact records for its people. A Person Account is the B2C shape: one record that combines account and contact data to represent a single individual, so there is no detached Contact to manage. Salesforce documents this difference directly. When Person Accounts are used, an individual is one Person Account record, whereas without them an individual needs a standard Account plus a Contact together. Most pure B2B orgs never turn Person Accounts on, because the company-and-contacts model already fits how they sell. Consumer-facing businesses such as a doctor, a hairdresser, an estate agent, or a retail bank usually need Person Accounts because their customer is a human being, not an organisation. Orgs that serve both audiences commonly enable Person Accounts and run both kinds in parallel on the same Account object. Picking the wrong model early is expensive to undo later.
Record types keep the two kinds apart
Once Person Accounts are enabled, record types are what separate a Business Account from a Person Account in the same org. Salesforce requires you to create at least one record type for Person Accounts, and Business Accounts sit under their own record type. Record type is far more than a label. It drives which page layout a user sees, which picklist values are available, and which automation runs. That separation matters because the data each kind needs is genuinely different. A Business Account layout surfaces Industry, Annual Revenue, and Parent Account, while a Person Account layout surfaces individual fields like birthdate and personal email. Validation rules and flows can branch on record type so that a rule sensible for a company does not fire on an individual. The IsPersonAccount flag on the record gives admins and developers a reliable way to tell the two apart in formulas, reports, SOQL, and integrations. Designing record types, layouts, and automation around this split is core work whenever an org runs both models, and it keeps the company side and the consumer side from interfering with each other.
Account hierarchies for enterprise customers
Business Accounts can be arranged into parent-and-child hierarchies through the Parent Account lookup, which maps to the ParentId field on the Account object. A holding company sits at the top, its operating divisions or subsidiaries sit below it, and those can have children of their own. Salesforce renders this structure on the View Account Hierarchy page so a rep can see the whole corporate family from any node in it. Hierarchies are central to enterprise selling. A global customer might be one legal parent with dozens of regional entities, each running its own buying process, yet leadership still wants a rolled-up view of total pipeline and revenue across the group. Parent and child links make that roll-up possible and give account teams a shared map of where every relationship lives. This is a company-only concept. Person Accounts represent single individuals, so the parent-child hierarchy does not apply to them in the same way. Leaving hierarchy unpopulated on large B2B customers is one of the most common reasons related records end up scattered and hard to report on.
Account teams and collaborative selling
A Business Account is the anchor for Account Team Members, the named group of people who work a single account together. A team typically includes the account executive, a sales engineer, a customer success manager, and sometimes an executive sponsor. Each team member is assigned a role that describes what they do on the account and an access level that controls how much they can see and edit. Account teams matter most in complex B2B selling, where many people from different functions touch the same large customer over a long sales cycle. The team makes that staffing visible on the record and grants access without forcing admins to build sprawling sharing rules for every individual deal. Reps can also report on team membership to see coverage across the book of business. Like hierarchies, account teams are a B2B-oriented feature and are far less common on Person Accounts, where the relationship is usually one customer rather than a cross-functional pursuit. When an org sells enterprise deals, configuring account teams on Business Accounts keeps collaboration and record access tidy.
Reporting that starts from the Account
In a B2B org, most reporting begins at the Business Account. Pipeline by account, open cases by account, and activity coverage by account are everyday questions, and the Account is the natural grouping for all of them. Custom report types let an admin join the Account to its Contacts, Opportunities, Cases, and any custom related objects, which makes the Account the central join target across the model. When an org runs both Business and Person Accounts, reporting needs a little care. A dashboard that mixes companies and individuals without filtering by record type produces aggregates that blend two very different populations and mislead the reader. The fix is to filter B2B reports by the Business Account record type, or use the IsPersonAccount field, so company numbers stay separate from consumer numbers. Done well, Account-centred reporting gives sales and service leaders a clear view of where revenue, effort, and risk sit across the customer base, and it scales naturally as the hierarchy and related records grow underneath each Business Account.
Industries clouds build on the same anchor
Salesforce Industries products extend the Business Account model rather than replace it. Financial Services Cloud, Manufacturing Cloud, Health Cloud, and similar solutions add industry-specific fields and related objects on top of the standard Account. A bank using Financial Services Cloud still has Business Accounts for its corporate clients, with extra objects such as Financial Accounts attached. A manufacturer using Manufacturing Cloud layers sales agreements and account forecasts onto the same Account. The Account-Contact-Opportunity backbone does not change underneath these clouds, so skills and integrations built on the standard model continue to apply. This is why understanding the plain Business Account first pays off. Whatever industry layer sits on top, the company record, its contacts, its hierarchy, and its teams behave the way they always have. The industry features add depth for a particular sector while the Business Account remains the central place where the customer relationship is recorded, keeping the model consistent from a small B2B org all the way up to a large regulated enterprise.
How to create a Business Account
Creating a Business Account is the everyday act of adding a company to your CRM. In a B2B-only org every new Account is a Business Account automatically. In an org that also uses Person Accounts, pick the business record type so Salesforce treats the record as a company rather than an individual.
- Open the Accounts tab
From the App Launcher or navigation bar, go to the Accounts tab and click New. The tab lists existing Accounts and is the starting point for adding a company.
- Choose the business record type
If your org has Person Accounts enabled, a record type prompt appears. Select the Business Account record type so the company page layout and fields load. In a B2B-only org this step is skipped.
- Enter the company details
Fill in Account Name and the firmographic fields you rely on, such as Industry, Annual Revenue, Type, and the Billing address. Set Parent Account if the company belongs to a larger corporate family.
- Save and add Contacts
Save the Account, then add the people you work with as Contacts on the record. Each Contact links back through AccountId, building the company-and-contacts structure that the rest of the model depends on.
The company name and the only field Salesforce requires to save a Business Account. Use a consistent naming convention to avoid duplicates.
Required only when Person Accounts are enabled. Choosing the business record type marks the record as a company and loads the right layout and fields.
The user who owns the account. It defaults to the creator and drives sharing, reporting, and assignment, so set it deliberately on shared accounts.
- Enabling Person Accounts is a one-way org change. Confirm the business genuinely sells to individuals before turning it on, because it cannot be cleanly reversed.
- In a mixed org, always filter B2B reports by the Business Account record type. Blending companies and individuals on one dashboard produces misleading totals.
- Populate Parent Account for enterprise customers from the start. Scattered child records that should roll up to a parent are a frequent source of reporting pain.
Prefer this walkthrough as its own page? How to Business Account in Salesforce, step by step
Trust & references
Cross-checked against the following references.
Straight from the source - Salesforce's reference material on Business Account.
- Account FieldsSalesforce
- Person Account Record Types | SOAP API Developer GuideSalesforce
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. How are individual people typically modeled under a Business Account?
Q2. What does enabling Person Accounts in a Salesforce org do to Business Accounts?
Q3. Which feature lets Business Accounts roll up a holding company and its subsidiaries?
Discussion
Loading discussion…