Record linkage is the statistical methodology for joining records from two or more datasets that are believed to correspond to the same entity when a common unique identifier is absent. It uses probabilistic algorithms, such as the Fellegi-Sunter model, to calculate match likelihoods based on the agreement patterns of quasi-identifiers like names, addresses, and dates of birth.
Glossary
Record Linkage

What is Record Linkage?
Record linkage is the statistical methodology for joining records from two or more datasets that are believed to correspond to the same entity when a common unique identifier is absent.
To scale to large datasets, record linkage employs blocking keys to partition data and reduce the number of pairwise comparisons. In synthetic identity detection, this technique is essential for identifying fragmented identity elements that have been combined to fabricate a non-existent persona across disparate financial systems.
Core Characteristics of Record Linkage
Record linkage is the statistical methodology for joining records from two or more datasets that are believed to correspond to the same entity when a common unique identifier is absent. The following characteristics define its operational framework.
Deterministic vs. Probabilistic Matching
Record linkage operates on a spectrum between two fundamental paradigms:
- Deterministic Linkage: Requires exact or near-exact agreement on a predefined set of matching keys (e.g., SSN + DOB). It is fast and transparent but brittle in the face of data quality issues.
- Probabilistic Linkage: Uses the Fellegi-Sunter model to calculate likelihood ratios for each field's agreement or disagreement. It tolerates errors, missing values, and inconsistencies by weighing the discriminatory power of each attribute.
Most production systems use a hybrid approach, applying deterministic blocking followed by probabilistic scoring.
Blocking and Indexing for Scalability
Pairwise comparison of all records across datasets is computationally intractable (O(n*m)). Blocking partitions records into mutually exclusive blocks using a blocking key—a derived attribute like Soundex-encoded surname or ZIP code prefix.
- Only record pairs within the same block are compared, reducing the comparison space by orders of magnitude.
- Sorted Neighborhood Method: Sliding window over sorted keys to catch near-misses that cross block boundaries.
- Canopy Clustering: Uses cheap, approximate distance metrics to create overlapping blocks for high-dimensional data.
Effective blocking is the single most critical performance optimization in large-scale entity resolution.
Field Weighting and Agreement Patterns
Not all attributes are equally informative. The Fellegi-Sunter model assigns each field two probabilities:
- m-probability: The likelihood that a field agrees given the pair is a true match. High for stable identifiers like SSN; lower for volatile attributes like address.
- u-probability: The likelihood of chance agreement among non-matches. A rare surname has a low u-probability and thus high discriminatory power.
The agreement weight for a field is log₂(m/u). Agreement on a highly discriminatory field contributes a large positive weight; disagreement yields a negative weight. The composite weight across all fields determines the match decision.
Classification and Thresholding
The composite weight for each record pair is compared against two thresholds to produce a tripartite classification:
- Match: Weight exceeds the upper threshold. Records are automatically linked.
- Non-Match: Weight falls below the lower threshold. Records are automatically rejected.
- Clerical Review: Weight falls between thresholds. These ambiguous pairs require human adjudication.
Thresholds are tuned based on the cost asymmetry of false positives (incorrectly merged identities) versus false negatives (missed fraud links). In financial fraud detection, minimizing false negatives is typically prioritized to avoid missing synthetic identity clusters.
Transitive Closure and Clustering
Record linkage is not merely pairwise. When record A matches B, and B matches C, transitive closure dictates that A, B, and C all belong to the same entity cluster.
- Connected Components: A graph-based approach where records are nodes and match decisions are edges. Each connected component becomes a resolved entity.
- Hierarchical Clustering: Agglomerative or divisive methods that build entity trees based on similarity matrices.
- Correlation Clustering: Optimizes a global objective function, minimizing disagreements between pairwise similarity scores and final cluster assignments.
Transitive resolution is essential for collapsing multiple fragmented identity records into a single golden record.
Evaluation Metrics for Linkage Quality
Assessing record linkage performance requires metrics adapted from information retrieval:
- Precision: The fraction of declared matches that are true matches. Low precision means false merges that corrupt entity profiles.
- Recall: The fraction of true matches successfully identified. Low recall means missed links, leaving synthetic identity fragments undetected.
- F-Measure: The harmonic mean of precision and recall, providing a single balanced metric.
- False Match Rate: The proportion of non-matches incorrectly linked, critical for compliance in financial applications where erroneous identity merging can have regulatory consequences.
Ground truth for evaluation is typically established through manual clerical review of a statistically representative sample.
Frequently Asked Questions
Precise answers to the most common technical questions about the statistical methodology used to join records belonging to the same entity when a unique identifier is missing.
Record linkage is the statistical methodology for joining records from two or more datasets that are believed to correspond to the same real-world entity when a common unique identifier is absent. The process works by comparing a set of quasi-identifiers—such as names, dates of birth, and addresses—across record pairs and calculating a similarity score for each attribute. These individual scores are aggregated into a composite match weight, typically using the Fellegi-Sunter model, which classifies pairs as matches, non-matches, or potential matches based on likelihood ratios. To avoid the computationally prohibitive quadratic explosion of comparing every record to every other record, the process employs blocking keys to partition the data into mutually exclusive blocks, ensuring only records within the same block are compared. Modern implementations often replace exact string comparisons with fuzzy matching algorithms like Jaro-Winkler or Levenshtein distance to tolerate typographical errors and formatting inconsistencies.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Master the interconnected techniques that form the foundation of modern entity resolution and synthetic identity detection pipelines.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us