Cleanse and enrich incoming records

Standardize incoming business records and enrich them with trusted firmographic and company information.

Agent integration prerequisite: The agent requires read/write access to first-party master records across CRM and ERP systems, including permission to propose record merges and updates.

1. Identification with the D‑U‑N‑S Number

Prompt

"See process 1 (Data Management Identification) — resolve input record to a verified D‑U‑N‑S."

MatchToolCompany Entity Resolution

What comes back

Matched: Meridian Precision Components, Inc. — D‑U‑N‑S ••••••035, at 2800 Industrial Pkwy, Ste 100, Austin, TX 78744, US. Match method: name + address + registration number. Confidence: high.

2. Consolidation of similar/same datasets

Prompt

"Can you identify any similar or duplicate datasets by either the same D‑U‑N‑S, similar Name, Address we should consider as duplicate entries?"

MatchToolCompany Entity Resolution

What comes back

Two records likely represent the same entity:

Record	Source	Name	Address	D‑U‑N‑S	Match evidence
A	CRM	Meridian Precision Components, Inc.	2800 Industrial Pkwy, Austin TX 78744	••••••035	Exact D‑U‑N‑S + name match
B	ERP	Meridian Precision Comp	2800 Industrial Parkway, Austin TX	(none)	Name similarity 92% + address similarity 96%

Recommendation: consolidate onto Record A (CRM) as the surviving record — it holds the verified D‑U‑N‑S and complete registered name — and merge Record B's ERP-specific IDs and supplier codes into it.

3. Elimination of duplicates

Prompt

"Eliminate duplicates based on the consolidation analysis."

What comes back

Proposed action: surviving record is A (CRM) — Meridian Precision Components, Inc., D‑U‑N‑S ••••••035. From Record B (ERP) merge the ERP supplier ID (SUP-04821), payment terms (Net 30), and cost-center assignment. Conflict resolution: use Record A's verified registered name and verified D&B address (with suite number). The agent awaits confirmation before executing the merge.

4. Append relevant data

Prompt

"Please give me the foundational data set for D‑U‑N‑S ••••••035 including Name, Addresses, Hierarchy information (Parent, Domestic Ultimate, Global Ultimate)."

DataToolOwnershipToolCompany InformationHierarchies & Connections

What comes back

Identity — D‑U‑N‑S ••••••035 · Primary and registered name: Meridian Precision Components, Inc. (registry match) · Address: 2800 Industrial Pkwy, Ste 100, Austin, TX 78744, US · Phone: +1 512-555-•••• · Website: meridianprecision.com · Status: Active.

Hierarchy — Immediate parent and domestic ultimate: Meridian Holdings NA, Inc. (D‑U‑N‑S ••••••612, Wilmington, DE) · Global ultimate: Meridian Industrial Group, Ltd. (D‑U‑N‑S ••••••397, London, UK) · Family tree: 14 entities across 6 countries.

Go deeper: Beneficial ownership, principals, financial data, and full family-tree detail are available with enterprise access.

5. Support data questions

Prompt

"Can you explain me what a global ultimate is?"

OwnershipToolHierarchies & Connections

What comes back

A Global Ultimate is the highest entity in a corporate family tree — the top-level parent that ultimately controls all subsidiaries worldwide. For Meridian Precision Components (D‑U‑N‑S ••••••035), that is Meridian Industrial Group, Ltd. (D‑U‑N‑S ••••••397), headquartered in London, UK. Meridian Precision operates in Austin, TX and reports to Meridian Holdings NA (Wilmington, DE) as its immediate parent, but the ultimate controlling entity for the 14-entity, 6-country family is the London group. This linkage matters for consolidated reporting, enterprise analytics, and total group-exposure views.

6. Update data

Prompt

"Update the surviving record with the appended foundational data."

What comes back

A field-by-field change set for the surviving CRM record: registered name → Meridian Precision Components, Inc.; address → 2800 Industrial Pkwy, Ste 100, Austin, TX 78744, US; phone → +1 512-555-••••; website → meridianprecision.com; D‑U‑N‑S → ••••••035; parent D‑U‑N‑S → ••••••612; global ultimate D‑U‑N‑S → ••••••397; industry → SIC 3599 / NAICS 332710; employees → 342. The agent awaits confirmation before writing to CRM and ERP.

Above is an illustrative example using a synthetic company with representative D&B data elements.

Try This Workflow

Try It Now

More enterprise master data guides

Find a D‑U‑N‑S Number

Resolve a company name to a D‑U‑N‑S^® Number with match confidence.

View guide

Verify identity and registration details

Pull identity, contacts, registration numbers, industry codes, and stock listings.

View guide

Identify and resolve incoming records

Match incoming business records to the correct entity and unique D‑U‑N‑S^® Number.

View guide