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

Accounts are companies. Contacts are people. Prima vista, that sounds painfully obvious. But I reckon we’ve seen more CRM implementations go sideways over this one distinction than any other single issue. It cascades. Messy reports. Broken forecasts. Marketing campaigns hitting the wrong audience. Sales reps fumbling conversations because they’re looking at the wrong record.

If your CRM has “John Smith” sitting as an account, or “Siemens” filed as a contact, your data model is broken. And broken data models cost real money.

TL;DR: 44% of companies believe they lose more than 10% of annual revenue due to poor CRM data quality (Validity, 2022). The account-vs-contact distinction is the foundation of CRM data integrity. Accounts = organisations (companies, subsidiaries, partners). Contacts = individual people linked to those accounts. In SAP Sales Cloud V2, proper account hierarchies and contact linking prevent duplicate records, improve forecast accuracy, and enable personalised outreach.

What Is an Account in a CRM?

The global CRM market hit $73.4 billion in 2024 (Grand View Research, 2024). Every CRM in that market uses accounts as the base structure for organising customer records. There’s a good reason for that.

An account represents a company, an organisation, a legal entity you do business with. In SAP Sales Cloud V2, the account record holds:

• Company identity: name, industry, address, tax ID
• Financial context: annual revenue, payment terms, contract value
• Relationship history: all linked opportunities, orders, service tickets, 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 ticket, every contract links back to that one account record. One company, one account, one source of truth. Neat and clean.

How Do Account Hierarchies Work?

In B2B sales, organisations are rarely flat. A single customer might have a corporate HQ, regional offices, and local subsidiaries scattered across 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. I’ve seen customers try to manage this with flat account lists. It’s a mess. Hierarchies fix it.

What Is a Contact in a CRM?

Sales reps spend only 28% of their time actually selling (Salesforce, 2024). A big chunk of the wasted time? Hunting for the right person to talk to. That’s a contact data problem, plain and simple.

A contact represents a specific person connected to an account. It’s 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’re linked to accounts. A contact floating on its own is an orphaned record. No business context. It loses value fast.

Think about a deal with a manufacturing client. You need to engage separately with procurement (they approve the budget), IT (they evaluate the technical fit), and operations (they’ll actually use the thing daily). Three different contacts, all linked to the same account. Crisp contact records make sure the right message reaches the right person. Without that, your rep is guessing. And guessing wastes everyone’s time.

Why Does This Distinction Matter So Much?

44% of companies believe they lose more than 10% of annual revenue due to poor CRM data quality (Validity, 2022). The account-vs-contact confusion is one of the root causes. Here’s where it goes wrong.

Duplicate records multiply. When companies and people aren’t clearly separated, the same information ends up in multiple records. A peer-reviewed study found 94% of business spreadsheets contain errors (Poon et al., Frontiers of Computer Science, 2024). That messiness transfers straight into CRM systems fed by spreadsheet imports. Fix the model before the data pours in. Trying to clean it up after the fact? That’s 5-10x harder.

Reporting breaks down. Accounts carry the financial picture: revenue attribution, contract value, deal pipeline. Contacts tell you who’s driving those numbers. Confuse the two and your forecasts show revenue attributed to people instead of companies, or engagement metrics rolled up to the wrong entity. Your CFO won’t be impressed.

Outreach misses its mark. Marketing campaigns targeted at accounts (ABM) need different data than campaigns targeted at contacts (email personalisation, role-based messaging). If your data model doesn’t separate them, your campaigns hit the wrong audience with the wrong message. Money burnt.

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

How Should You Structure Accounts and Contacts in Sales Cloud V2?

CRM delivers $3.10 for every dollar spent when the data model is solid (Nucleus Research, 2024). That return starts with getting the foundation right. Here’s what we’ve learned across dozens of implementations.

One company = one account. Don’t create separate accounts for the same company in different contexts. Use account hierarchies for subsidiaries and divisions. It’s tempting to take shortcuts here. Don’t.

Link every contact to an account. Orphaned contacts (people not linked to any company) are the single most common data quality problem we see. Make the account field mandatory for contact creation. Problem solved.

Define contact roles. Use V2’s role fields to classify contacts: decision-maker, influencer, technical evaluator, champion, end user. This helps reps know exactly who to engage at each deal stage. I reckon this alone saves hours per week for active sales teams.

Handle multi-company contacts carefully. A consultant or advisor might work with multiple client companies. In V2, you can link one contact to multiple accounts through relationship assignments. Use this instead of creating duplicate contact records. Duplicates are the enemy.

Clean up before you launch. If you’re migrating from spreadsheets or an older CRM, audit your data first. Find records where companies are stored as contacts and vice versa. Fix these before import. Cleaning up after the fact is 5-10x harder, and that’s a conservative estimate.

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

Frequently Asked Questions

What’s the difference between a contact and a person account?

A contact is always linked to a business account: it represents a person within a company (B2B). A person account combines contact and account fields into a single record to represent an individual consumer (B2C). SAP Sales Cloud V2 supports both. Use contacts for B2B relationships where multiple people interact with your company through one organisation. Use individual customer records for B2C scenarios where the person is the customer.

Can one contact belong to multiple accounts?

Yes. In SAP Sales Cloud V2, contacts can be linked to multiple accounts through relationship assignments. This comes up all the time with consultants, board members, or advisors who serve multiple companies. The rule: never create duplicate contact records for the same person. Use V2’s relationship model to capture the multi-company connection instead. Keeps interaction history consolidated and your data crisp.

How many contacts should we track per account?

No fixed rule, but in our experience B2B deals typically involve 6-10 stakeholders. Track anyone who influences the buying decision: the budget holder, the technical evaluator, the end-user champion, the executive sponsor. In SAP Sales Cloud V2, contact roles and buying centre mapping help you organise these relationships. Reps stop guessing who to call.

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

When you merge duplicate accounts in V2, associated contacts get reassigned to the surviving account. When an account is closed (customer churned or got acquired), contacts should be updated but not deleted. They may become relevant again if the person moves to a different company. V2’s relationship history preserves the interaction timeline even after account status changes. Spot on for keeping your institutional memory intact.

How do accounts and contacts relate to opportunities?

Opportunities in V2 are linked to both an account (the company buying) and one or more contacts (the people involved in the deal). The account provides financial context: deal size, revenue attribution. The contacts provide relationship context: who’s the decision-maker, who’s blocking the deal, who’s your champion. Skip either connection and you’re flying blind.