What is Data Normalisation?
The short answer
Data normalisation converts values to a consistent representation for a defined use.
Data Normalisation: 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
Preserve original values and source-specific identifier rules before removing characters or changing formats. 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 data normalisation. The reviewer’s task is to preserve original values and source-specific identifier rules before removing characters or changing formats. The outcome is recorded together with the supporting evidence; an unresolved question stays open rather than being converted into a positive result.
A pipeline strips a leading zero from a registration identifier. Keep the source representation and validate source-specific rules before normalising identifiers.
Distinctions that matter
Data Normalisation belongs to the entity matching & transformation topic family. Read Entity Resolution 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
- Matching keys and namespaces
- Conflicts and candidate evidence
- Evaluation labels and outcomes
The review should produce
An explainable match, non-match or unresolved result that can be reviewed and reversed when necessary.
Across this family
Define whether records refer to the same legal entity before choosing a matching technique. Similar names, websites and addresses may describe related businesses rather than duplicates. Evaluate the cost of incorrect links and preserve ambiguity when the evidence cannot distinguish candidates.
A note from practice
Normalisation improves comparability while preserving the original value and transformation rule. Removing meaningful characters or legal-form distinctions can increase apparent consistency while damaging identity evidence.
Limits and common mistakes
The practical boundary is important: Preserve original values and source-specific identifier rules before removing characters or changing formats. 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?
How is Data Normalisation different from Fuzzy Matching?
What should the result of the review contain?
Continue learning
Related topics
- Entity matching & transformationEntity ResolutionEntity resolution determines whether different records refer to the same real-world entity. For company data, it connects names, identifiers, addresses and other evidence while distinguishing similar but unrelated businesses. A resolved match should be explainable, especially when it changes ownership, risk or a commercial workflow.
- Entity matching & transformationData DeduplicationData deduplication identifies and handles records treated as duplicates under a defined identity policy.
- Entity matching & transformationFuzzy MatchingFuzzy matching compares values using similarity measures rather than requiring exact equality.
See the registry record behind every answer.
Primary, government-sourced data on 600M+ companies in 200+ countries, with full source attribution.