What is Reference Data?

Company data & APIs
Master company data
3 min read

The short answer

Reference data supplies controlled values or classifications used to interpret other records.

Reference Data: why it matters

Automated company-data workflows need clear meanings and traceable transformations. An operation that runs successfully can still produce a result that is unsuitable for the intended business question.

How to assess it in practice

Maintain versions and mappings so changes in codes do not silently alter historical reporting. Start by defining the question the team needs to answer. Identify the relevant record or evidence, check its scope and date, and retain the reasoning behind the result. If evidence conflicts, keep that conflict visible for review.

Worked example

Illustrative workflow: a team reviewing a business adds a separate check for reference data. The reviewer’s task is to maintain versions and mappings so changes in codes do not silently alter historical reporting. The outcome is recorded together with the supporting evidence; an unresolved question stays open rather than being converted into a positive result.

Illustrative scenario

An industry taxonomy changes its categories. Preserve the older code version and use a documented mapping rather than rewriting history without a trace.

Distinctions that matter

Reference Data belongs to the master company data topic family. Read Master Data Management (MDM) alongside it to understand the adjacent question. Each page has its own intended scope; shared context does not make the concepts equivalent.

Evidence and review output

Review these

Entity model and stable keys
Field authority and survivorship
History and downstream mappings

The review should produce

A governed company representation that preserves the evidence behind selected values and relationships.

Across this family

A shared company model needs explicit entity boundaries, attribute ownership and conflict rules. Separate original sources from mastered values and commercial accounts. Governance makes the record usable across teams; placing data in one table does not by itself resolve contradictory meanings.

A note from practice

Reference data uses governed codes, versions and meanings to classify or interpret other records. Manage retired values and mappings explicitly so historical records remain interpretable.

Limits and common mistakes

The practical boundary is important: Maintain versions and mappings so changes in codes do not silently alter historical reporting. Do not substitute a related label for this check or assume that missing information is a negative finding. Source-specific and jurisdiction-specific rules require their own review.

Frequently asked questions

Which evidence should I review?

For this topic, focus on entity model and stable keys, field authority and survivorship, history and downstream mappings. The relevant source and dates should be retained with the finding.

How is Reference Data different from Master Data Management (MDM)?

Master data management governs the consistent identification and maintenance of core business entities across systems. The distinction matters because the evidence needed for that concept may not resolve the question addressed on this page.

What should the result of the review contain?

A governed company representation that preserves the evidence behind selected values and relationships. Preserve material conflicts instead of replacing them with an unexplained success flag.

Continue learning

Explore Master company data

See the registry record behind every answer.

Primary, government-sourced data on 600M+ companies in 200+ countries, with full source attribution.

Book a demo Talk to us