VValvoline CumminsExecutive Cockpit

Customer Master · Golden Record

The single view of the customer the siloed source systems never had — the same account, mastered across SAP, the DMS, OEM portals and e-com feeds, resolved into one.

Valvoline Cummins Private Limited · FY25 (Apr'24–Mar'25, audited)
Leading MNC / private aftermarket lubricants brand in India — single-digit share, premiumising
500 employees · 1 plant + regional DCs · 6 export markets
Executive read· the answer, then the moves

24 fragmented records across 8 source masters resolve to 10 golden records — a 58% duplicate rate collapsed on merge. Reconcile the 9 customers with conflicting payment terms to stop cash leakage and unlock the 10 cross-division accounts.

10 of 24 records resolved to golden · 14 duplicates collapsed · 9 term conflicts open

Do now — ranked by urgency
  1. 1
    Reconcile 9 customers with conflicting payment termsAct now
    Why it matters

    The same buyer sits on Net 30 in one brand and Net 60 in another across 9 accounts — direct cash leakage and credit risk a single master removes.

    What's driving it
    • 9 customers carry conflicting terms
    • 58% duplicate rate across 8 systems
    FYI
    • Conflicts surfaced to credit and sales
    • Total exposure netted across brands
  2. 2
    Collapse the 14 remaining duplicate recordsWatch
    Why it matters

    24 raw records reduce to 10 golden — finishing survivorship gives every team one account, one team, one set of terms.

    What's driving it
    • 14 duplicates collapsed on merge (58%)
    • 24 records across 8 source masters
    FYI
    • Match → merge → survive → reconcile
    • Borderline matches queued for a steward
  3. 3
    Activate 10 cross-segment accounts for cross-sellOpportunity
    Why it matters

    10 golden records are already served across ≥2 segments — the resolved master is the cross-sell base no single source system (SAP, DMS, OEM portal, e-com) could see alone.

    What's driving it
    • 10 accounts served across ≥2 segments
    • 10 golden records mastered
    FYI

    Golden record is the join key for Customer 360 and Cash 360

💎 Shareholder value & JV returnsStep 6 of 7 · resolve the golden record (MDM)Integration & Programs 360Shareholder ValueAll journeys
🌐 Enterprise 360 modules· on Customer MasterBrowse all 31 views ▾
● LiveBuilt forSales / Key Accounts· one account, one teamCredit / Finance· one set of terms & exposureData / MDM· dedupe & survivorship

Each segment and channel system kept its own customer list, so distributors, OEM accounts and fleet operators each exist several times across the systems — with different names, IDs and even payment terms. Until they're resolved, no one can see the true relationship, total exposure, or cross-sell base. This is the golden record AI builds on top of the mesh.

Data backing: customer_source (SAP + DMS / OEM / e-com fragments) · entity resolution · survivorship rules
8
Source masters
SAP + DMS / OEM / e-com systems
24
Raw customer records
across all systems
10
Golden records
after AI resolution
58%
Duplicate rate
collapsed on merge
10
Cross-segment accounts
mastered across ≥2 systems
9 customers carry conflicting payment terms across systems — the same buyer on Net 30 in one brand and Net 60 in another. That's direct cash leakage and credit risk a single master removes.
One customer, every system

Pick a customer → see its fragments merged

The ★ master survives; the rest merge with a match confidence. Conflicting terms are flagged in red.

Customers · # source records
★ Golden record

National distributor network (~450)

resolved from 3 source records · master = VCPL SAP / ERP
Consolidated AR
₹340 Cr
Survivorship terms
Net 30
Sources merged
3
Term conflict
Yes — review
Match confidence
95%
Source records merged into the golden record
Source systemName as storedIDTermsARMatch
VCPL SAP / ERPPrimary distributors (national)ACCT-40033Net 30₹180 Crmaster
0Distributor Mgmt System (DMS)Distributor network — DMSDMS-3301Net 30₹120 Cr96%
0E-com marketplace feedDistributor drop-ship (e-com)ECM-501Net 15₹40 Cr90%

Conflict: payment terms differ across systems (Net 30 vs Net 15). Survivorship keeps the master's Net 30; the others are flagged for credit to reconcile — exactly the kind of leakage a single view removes.

Cross-segment signal: National distributor network (~450) is served across 3 VCPL systems / segments. That's a relationship to coordinate (one account team, one set of terms) — and a cross-sell base already inside the house.

How AI builds the golden record

Match → merge → survive → reconcile

1 · Match

Fuzzy + LLM matching on name, address and tax ID links 'CV fleet operators' (SAP), 'Fleet — via distributors' (DMS) and the marketplace record to one entity — with a confidence score, not a blind merge.

2 · Merge

Records above the confidence threshold collapse into one; borderline matches are queued for a human steward.

3 · Survive

Survivorship rules pick the winning value field-by-field (most-recent, most-complete, or the governed source) to form the golden record.

4 · Reconcile

Conflicts — different terms, duplicate AR — are surfaced to credit and sales, and total exposure is netted across the brands.

The golden record is the join key for everything else: it lets Customer 360 show one account, Cash 360 net one exposure, and the cross-sell engine see that a customer already buys from two segments — the same entity-resolution layer that powers the primary-sales and order-book views.