Account
The individual product a customer holds — a current account, a loan, a policy, a mobile line or a subscription — as distinct from the customer holding it.
01 Why it matters
What depends on getting this right
Regulated cores are account-centric by design, so exposure, profitability and most obligations are recorded per account while nearly every management question is asked per customer. The account-to-customer relationship is the bridge, and it is usually incomplete.
02 Where it lives
Every system holds a different version
None of these is wrong. Each was built for a purpose and records the part of the entity that purpose needed, which is exactly why resolution is required rather than optional.
| System | What it holds of this entity |
|---|---|
| Core banking or policy admin | the account of record, its terms and balance |
| CRM | the relationship view, usually with a different identifier |
| Billing | what is charged and to whom, which can be a third party |
| Risk and finance | exposure and staging, aggregated by counterparty |
| Collections and servicing | accounts in difficulty, often held separately |
03 Match keys
What actually matches, and what only looks like it does
| Key | How well it works |
|---|---|
| Account number plus product system | Unique per system, not across the estate. |
| Resolved customer identifier | The link that makes relationship reporting possible. |
| Household or group membership | Required for exposure and share-of-wallet analysis. |
| Joint and beneficial ownership | One account may have several owners with different rights. |
04 Survivorship
When two records disagree, which value wins
Survivorship is a business decision, not a technical default. These rules should be agreed with the people who own the data and then applied consistently, because changing them later restates history.
The product system is authoritative for balance and terms
Never a downstream copy, and never a warehouse snapshot for a regulatory figure.
Status wins conservatively
Blocked, frozen or in-arrears from any authoritative source must survive over active.
Ownership relationships are modelled, not flattened
Joint accounts, powers of attorney and beneficial owners are relationships with their own attributes.
Closed accounts are retained
Attrition, tenure and lifetime value all need them.
05 The cost of not doing it
What stays broken while it is unresolved
Exposure understated
Facilities held across products and entities are not aggregated to the counterparty that owes them.
Products per customer unknown
The cheapest growth available cannot be measured, let alone targeted.
Dormancy mistaken for retention
An account that is open and inactive counts as a customer who stayed.
Regulatory aggregation manual
Returns that must be reported per counterparty are assembled in spreadsheets each cycle.
06 Metrics that divide by it
The numbers this entity carries
07 Questions
Frequently asked
Why not treat the account as the customer?
Because every relationship question — exposure, profitability, cross-sell, retention — is asked about the party, not the product. Account-level reporting answers none of them, however accurate it is.
What about joint ownership?
Model it as a relationship with attributes rather than picking a primary owner. Choosing one arbitrarily makes half of your customer-level figures wrong in ways that are impossible to audit later.
See the duplicates in your own data
We will resolve one entity on your systems, live, and show what the duplicates are costing.