What is Fuzzy Matching?
The short answer
Fuzzy matching compares values using similarity measures rather than requiring exact equality.
Fuzzy Matching: 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
Validate ambiguous cases and do not treat a high similarity score as proof of entity identity. 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 fuzzy matching. The reviewer’s task is to validate ambiguous cases and do not treat a high similarity score as proof of entity identity. The outcome is recorded together with the supporting evidence; an unresolved question stays open rather than being converted into a positive result.
A high string score links two businesses named Central Trading. Country and registration evidence show they are different legal entities.
Distinctions that matter
Fuzzy Matching 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
Fuzzy similarity is a candidate-generation or scoring technique, not proof of identity. Combine name similarity with discriminating fields and evaluate failures involving common names and cross-border records.
Limits and common mistakes
The practical boundary is important: Validate ambiguous cases and do not treat a high similarity score as proof of entity identity. 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 Fuzzy Matching different from Deterministic 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 & transformationData NormalisationData normalisation converts values to a consistent representation for a defined use.
See the registry record behind every answer.
Primary, government-sourced data on 600M+ companies in 200+ countries, with full source attribution.