MDM Central

Master Data Management with golden records and survivorship rules — one of the four named differentiators of SuiteCentral 2.0.

What it does

Per 01-executive-summary slide 2, MDM Central is presented as “Golden Record MDM” — one of the four pillars of SuiteCentral 2.0’s differentiation. The Preston-Test README.md (not yet formally ingested) describes the broader module as “Master data management, golden records, survivorship rules.”

Per ai-governance-layer-video (02:40-02:56), MDM Central has two specific architectural properties that differentiate it from competitor approaches:

“The platform features 12 core modules and integrated master data management. MDM Central is built into the core, acting as the single source of truth across ERPs. This is a massive value add, as competitors often sell MDM as a separate, expensive product.”

Three important things this tells us:

  1. Built into the core, not a bolt-on extension. This answers the previously open question about whether MDM is one of the 12 “core” modules — it is.
  2. Single source of truth across ERPs. MDM Central reconciles data between NetSuite and Business Central, which is particularly relevant for the HintonBurdick post-acquisition story where Squire likely runs both ERPs.
  3. Competitive pricing advantage. Most MDM solutions (Informatica MDM, Reltio, Profisee, Oracle MDM, etc.) are sold as standalone products costing six to seven figures annually. By bundling MDM into the core of SuiteCentral 2.0, Squire’s acquisition cost is dramatically lower than a traditional MDM buyer’s — contributing to the 75% cost reduction claim from the same source (03:07-03:14).

The golden-record operating model (per narration-scripts mdm-central)

The Watch-track demo video for MDM Central runs ~12 seconds and frames the module’s core workflow in four beats:

“MDM Central governs master data quality with a golden-record operating model. Duplicate detection and merge workflows keep entities clean and trusted. Stewardship queues make ownership and remediation actions explicit. That creates reliable data for analytics, automation, and integration.”

Three concrete operational components:

  1. Golden-record operating model — the canonical record for each entity is promoted and maintained as the “golden” version. Other representations of the same entity are reconciled against the golden record.
  2. Duplicate detection and merge workflows — the system actively identifies potential duplicates (across or within ERPs) and surfaces merge workflows to collapse them.
  3. Stewardship queues — ownership of data-quality decisions is explicit. When the system isn’t sure what to do, the decision goes to a queue assigned to a named steward who owns the remediation.

The closing line — “reliable data for analytics, automation, and integration” — positions MDM Central as foundational infrastructure, not a point solution. Analytics, automation, and integration all depend on data quality, and all three fail silently if MDM is weak.

Why it matters (to the adoption case)

The slide-script differentiation argument is combinatorial: Golden Record MDM + Context Sidecar + NL Action Gate + Schema Drift Controls = “data governance, embedded workflow intelligence, and governed execution in one operating model.”

MDM is the data governance leg of that combination. Without MDM, there’s no canonical truth across NetSuite + Business Central, which means the AI has nothing solid to reason against. So MDM Central is foundational, not optional, for the broader pitch.

For Squire — a CPA firm whose clients are audit-heavy — golden records and survivorship rules are also a defensible audit posture. “Why does this report show one number?” → “Because the golden record says so, and here’s the survivorship rule.” That’s a compliance answer, not a hand-wave.

Status

  • Tier: production-ready
  • Test coverage: production-validated (per slide 4 production proof in 01-executive-summary)
  • Dashboard URL: /mdm-central.html (per Preston-Test README.md — not yet formally ingested)

What’s NOT yet known (from this source)

  • The actual MDM data model
  • The survivorship rule mechanism
  • How MDM integrates with the AI field-mapping engine
  • Test coverage specifics for MDM
  • Whether MDM is one of the 12 “core” or 4 “extension/platform” modules

For these, ingest:

  • Golden Record MDM Feature Guide
  • MDM Tutorial - Creating Golden Records

Sources

  • 01-executive-summary — claim 5 (named as “Golden Record MDM”, one of the four differentiators)
  • ai-governance-layer-video — claims 18, 19, 21 (built into the core, single source of truth across ERPs, 75% cost reduction framing)
  • narration-scripts — claim 26 (golden-record operating model, duplicate detection and merge workflows, stewardship queues)