Deterministic matching
The definition as the field writes it comes first, weaknesses and all. What Entity Bind does about it comes last, in its own paragraph, so you can take one without the other. Filed under matching methods.
How two records are compared and how the comparison is made cheap enough to run. Blocking, deterministic rules, probabilistic scoring, string distance.
every figure, with its population →What deterministic matching means
A deterministic rule is a stated condition: same LEI, or same registration number within the same register plus a name sanity check, or same VAT number. If the condition holds the pair matches; if it does not, the rule says nothing and the pair falls through to something else. There is no probability and no threshold to tune.
Its strength is that it is auditable and cheap. A reviewer can read the rule, agree or disagree with it, and reproduce the verdict by hand; the machine reaches it without a model call, without network egress, and in constant time. Its weakness is brittleness: deterministic rules are silent on the records that lack the identifier, which in most real files is the majority of them.
The dangerous form is deterministic matching on a weak key. Name plus country is a rule, and it is wrong often enough to be unusable in registers with dense name collisions. Registration number without its issuing authority is a rule, and it produces confident false positives across jurisdictions that reuse number ranges.
Entity Bind runs deterministic identifier rules third in its cascade, after normalisation and retrieval, and checks register shape rather than string equality. Conflicting strong identifiers are a decisive non-match rather than a shrug. A record arriving with a company number or an LEI resolved at 100% (317/317) on the representative fixture of 2026-08-29, at one credit and no model spend.
Where this shows up in Entity Bind
Three pages where this term stops being vocabulary and starts changing an answer, a payload or a price.
- What is entity resolution?Entity resolution decides which records in one or more datasets refer to the same real-world entity, and joins them under a single stable identifier.Open
- How it worksThe seven-stage cascade in order, what each stage can settle on its own, and what it hands to the next.Open
- The API referenceThe REST surface: payloads, the decision outcomes, the error model, the usage block and the ceiling on the confidence field.Open
The fastest way past a definition is a file: which of your rows are the same company, which of your existing matches we would not have made, and what we could not decide.
Start freeThe terms next to this one
Each with its own sentence, because the next question is usually about the word beside this one.
Probabilistic matching
Probabilistic matching scores a candidate pair by weighing the agreement and disagreement of several fields into a single number, then applies thresholds to that number rather than to any one field.
Company number
A company number is the identifier a register assigns to a company at incorporation, and it is unique only within the register that issued it — never within a country and never globally.
LEI (Legal Entity Identifier)
The LEI is a 20-character ISO 17442 code identifying a legal entity that participates in financial transactions, issued through the Global LEI Foundation and published as open reference data.
Match weight
A match weight is the log-scaled contribution one comparison makes to a pair's score, positive when agreement is evidence of a match and negative when disagreement is evidence against.
False positive
A false positive in entity resolution is a pair of records asserted to be the same entity when they are not — the error class that corrupts data rather than merely leaving it untidy.
- GuideCompany identifiers explainedCompany number, LEI, CIK, ticker, SIREN and SIRET, DUNS, VAT, EUID and ISIN. What each identifies, who issues it, what it does not guarantee, and which ones actually decide a match.
- IdentifierLEIOne LEI names one legal entity worldwide, and most companies hold none. An agreeing LEI settles a match with no model call, a conflicting one against.
- IdentifierCompany numberA company number names a registration, not a company: 220 of 232 jurisdictions run more than one register, so it decides only once the register is named.
The other 12 terms on this shelf
How two records are compared and how the comparison is made cheap enough to run. Blocking, deterministic rules, probabilistic scoring, string distance.
Internal fixtures only. The historical 2026-08-29 per-tier recording covers 317 GB companies with identifier-rich arrivals seeding the catalogue first; the context tier includes country and registered-town prose. Its legacy replay has no full-prompt-verified calls and cannot certify current calibration. The September 5 CI reports cover 1,176 labelled pairs and 705 records over 250 companies using offline stubs. These are not independent customer holdouts or live production validation; the 99% minimum-input product target remains unmet. Scope is company and organisation identity only — not people, vessels, bank-account ownership, sanctions or emissions. Results may not be used for eligibility decisions about individuals, including employment, credit and tenancy.
Start with your own company records.
Create your workspace, verify your email and run your first company file. The Free plan needs no card. Create API keys in your workspace when you need an integration.
300 credits. No card.
For a guided review of your file, explore the Merge Safety Sprint →