BBajel ProjectsExecutive Cockpit

Customer Master · Golden Record

The single view of the client the legacy ERP & tender systems never had — the same account, mastered across the Bajel ERP and every tender / project system, resolved into one.

Bajel Projects Limited · FY26 (Mar'26, standalone audited anchor)
Bajaj Group's power-transmission & distribution EPC and tower/monopole manufacturing arm
1,400 employees · 1+ plants & units · 6 export markets
Executive read· the answer, then the moves

13 fragmented records across 5 source masters resolve to 6 golden records — a 54% duplicate rate collapsed on merge. Reconcile the 6 clients with conflicting payment terms to stop cash leakage and unlock the 6 cross-system accounts.

6 of 13 records resolved to golden · 7 duplicates collapsed · 6 term conflicts open

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

    The same client sits on Net terms in the ERP and Milestone / LC terms in a tender system across 6 accounts — direct cash leakage and credit risk a single master removes.

    What's driving it
    • 6 clients carry conflicting terms
    • 54% duplicate rate across 5 systems
    FYI
    • Conflicts surfaced to credit and BD
    • Total exposure netted across systems
  2. 2
    Collapse the 7 remaining duplicate recordsWatch
    Why it matters

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

    What's driving it
    • 7 duplicates collapsed on merge (54%)
    • 13 records across 5 source masters
    FYI
    • Match → merge → survive → reconcile
    • Borderline matches queued for a steward
  3. 3
    Activate 6 cross-system accounts for cross-sellOpportunity
    Why it matters

    6 golden records are already served across ≥2 systems — the resolved master is the cross-sell base no single ERP / tender system could see alone.

    What's driving it
    • 6 accounts served across ≥2 systems
    • 6 golden records mastered
    FYI

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

💎 Equity story & re-ratingStep 6 of 7 · resolve the golden record (MDM)Programs & Capability 360Equity Story & Re-ratingAll journeys
🌐 Enterprise 360 modules· on Customer MasterBrowse all 31 views ▾
● LiveBuilt forBD / Key Accounts· one account, one teamCredit / Finance· one set of terms & exposureData / MDM· dedupe & survivorship

Each segment and tender system kept its own client list, so PGCIL, the state utilities and Adani 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 (Bajel ERP + tender / project system fragments) · entity resolution · survivorship rules
5
Source masters
Bajel ERP + tender / project systems
13
Raw client records
across all systems
6
Golden records
after AI resolution
54%
Duplicate rate
collapsed on merge
6
Cross-system accounts
mastered across ≥2 systems
6 clients carry conflicting payment terms across systems — the same client on Net terms in the ERP and Milestone / LC terms in a tender system. 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

Power Grid Corp (PGCIL)

resolved from 3 source records · master = Bajel ERP / SAP
Consolidated AR
₹900 Cr
Survivorship terms
Net 45
Sources merged
3
Term conflict
Yes — review
Match confidence
96%
Source records merged into the golden record
Source systemName as storedIDTermsARMatch
Bajel ERP / SAPPower Grid Corporation of India LtdACCT-40011Net 45₹420 Crmaster
0PGCIL / utility tender portalPGCIL (TBCB)TBCB-7701Milestone₹300 Cr96%
0Project ERP / PrimaveraPower Grid (line packages)PRJ-5501Milestone₹180 Cr92%

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

Cross-segment signal: Power Grid Corp (PGCIL) is served across 3 Bajel 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 'Power Grid Corporation of India Ltd', 'PGCIL (TBCB)' and 'Power Grid (line packages)' 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 Clients & Utilities 360 show one account, Cash 360 net one exposure, and the cross-sell engine see that a client already buys from two segments — the same entity-resolution layer that powers the project-grain and order/tender views.