Account vs Contact in CRM: What's the Difference and Why It Matters

Accounts are companies. Contacts are people. At first glance that sounds painfully obvious. Yet in CRM projects this one distinction causes more lasting damage than almost any other: messy reports, unreliable forecasts, campaigns that reach the wrong audience, and reps who open the wrong record before a call.

If your CRM has “John Smith” stored as an account, or “Siemens” filed as a contact, your data model is broken. And a broken data model costs money: in a survey by Validity, 44% of companies estimated they lose more than 10% of annual revenue because of poor CRM data quality (Validity, The State of CRM Data Health, 2022).

TL;DR: An account is an organisation you do business with (company, subsidiary, partner). A contact is an individual person linked to that account. Keeping the two apart is the foundation of CRM data quality. In SAP Sales Cloud V2, account hierarchies and properly linked contacts prevent duplicates, make forecasts reliable and let marketing address the right people.

What is an account in a CRM?

An account represents a company, an organisation or a legal entity you do business with. Every CRM uses it as the base structure for customer records. In SAP Sales Cloud V2, the account record holds:

• Company identity: name, industry, address, tax ID
• Commercial context: revenue, payment terms, contract value
• Relationship history: all linked opportunities, quotes, orders, service cases and activities
• Organisational structure: parent-child hierarchies for subsidiaries and divisions

Say you work with Siemens. The account holds everything about Siemens as a customer. Every opportunity, every support case, every contract links back to that one record. One company, one account, one source of truth.

When Sales Cloud V2 runs alongside SAP S/4HANA, the account is also the bridge to the ERP business partner, which is why a clean account model matters twice. We explain that link in our post on SAP S/4HANA Public Cloud and Sales Cloud V2 as an integrated stack.

How do account hierarchies work?

B2B customers are rarely flat. One customer may have a headquarters, regional offices and local subsidiaries in several countries. SAP Sales Cloud V2 supports parent-child account hierarchies that mirror how these companies actually work. You can roll up revenue across divisions, track engagement at each level and assign territory ownership where it belongs. Customers who try to manage this with flat account lists end up with a mess; hierarchies fix it.

What is a contact in a CRM?

A contact represents a specific person connected to an account: the human side of the relationship. The contact record holds:

• Personal details: name, job title, department
• Communication channels: phone, email, preferred language
• Role in decisions: decision-maker, influencer, technical evaluator, end user
• Interaction history: calls, emails, meeting notes, activity timeline

Contacts only make sense when they are linked to accounts. A contact on its own is an orphaned record without business context, and it loses value quickly.

Think of a deal with a manufacturing customer. You need to engage separately with procurement (they approve the budget), IT (they evaluate the technical fit) and operations (they will use the solution every day). Three contacts, all linked to the same account. Clean contact records make sure the right message reaches the right person; without them, your rep is guessing.

Why does this distinction matter so much?

Mixing up accounts and contacts is one of the root causes of poor CRM data. This is where it goes wrong.

Duplicate records multiply. When companies and people are not clearly separated, the same information ends up in several records. Spreadsheet imports make it worse, because the errors in the spreadsheet travel straight into the CRM. Fix the model before the data arrives; cleaning up afterwards is much harder.

Reporting breaks down. Accounts carry the commercial picture: revenue attribution, contract value, pipeline. Contacts show who drives those numbers. Confuse the two and forecasts attribute revenue to people instead of companies, or engagement rolls up to the wrong entity.

Outreach misses its mark. Account-based campaigns need different data than campaigns aimed at individuals (personalised email, role-based messaging). If the data model does not separate them, the wrong audience gets the wrong message. Our guide to target accounts shows how account-level targeting builds on this model.

Handoffs between teams fail. When a deal moves from sales to implementation, or a customer escalates to support, the next team needs the company context (account) and the person to work with (contact). Mixed-up records force them to ask questions the customer has already answered.

How should you structure accounts and contacts in Sales Cloud V2?

These are the rules we apply in our Sales Cloud V2 projects.

One company, one account. Do not create separate accounts for the same company in different contexts. Use account hierarchies for subsidiaries and divisions, even when a shortcut is tempting.

Link every contact to an account. Orphaned contacts, people not linked to any company, are the data quality problem we see most often. Make the account mandatory when a contact is created.

Define contact roles. Classify contacts as decision-maker, influencer, technical evaluator, champion or end user. Reps then know whom to engage at each stage of the deal.

Handle multi-company contacts carefully. A consultant or advisor may work with several of your customers. In Sales Cloud V2 you can relate one contact to several accounts. Use that instead of creating duplicate contacts.

Clean up before you go live. If you are migrating from spreadsheets or an older CRM, audit the data first. Find companies stored as contacts and people stored as accounts, and fix them before the import. Our guide to moving from Excel to Sales Cloud V2 and the post on CRM data quality walk through that clean-up.

SAP documents the account and contact objects in the SAP Sales Cloud V2 documentation.

---

Need help structuring your CRM data model? We configure SAP Sales Cloud V2 with proper account hierarchies and contact structures, the foundation everything else builds on. Get in touch.

Frequently asked questions

What is the difference between a contact and an individual customer?

A contact is a person who belongs to a business account, which is the B2B case. An individual customer is a person who is the customer, which is the B2C case. SAP Sales Cloud V2 supports both; use contacts where several people deal with you on behalf of one organisation.

Can one contact belong to multiple accounts?

Yes. In SAP Sales Cloud V2 a contact can be related to several accounts, which is common for consultants, board members or advisors. Do not create duplicate contact records for the same person; use the relationship instead so the interaction history stays in one place.

How many contacts should we track per account?

There is no fixed number. Track everyone who influences the buying decision: the budget holder, the technical evaluator, the future user and the executive sponsor. Contact roles in Sales Cloud V2 show reps who is who.

What happens to contacts when an account is merged or closed?

When duplicate accounts are merged, the contacts move to the surviving account. When an account is closed, update its contacts rather than deleting them: the person may reappear at another company, and the interaction history remains useful.

How do accounts and contacts relate to opportunities?

An opportunity in Sales Cloud V2 belongs to one account, the buying company, and involves one or more contacts, the people in the deal. The account gives the financial context, the contacts give the relationship context. Without either link, forecasting and deal coaching lose their footing.