Cross-tool identity resolution evidence gaps: what a link review expects versus what customer systems keep

Short answer

Eight items let a reviewer trust a link between records in different systems: the native ID in each system, a cross-reference field, a migration map for retired tools, a merge log with retired IDs, a shared strong key, the matching rule used, the rights basis of each source, and a downstream record that confirms the link. Companies usually keep native IDs and some shared keys. Merge history, written matching rules and the rights basis are the common gaps. Each one leaves a reviewer unable to say why two records were joined.

Visual briefFull-size diagram
Eight rows of ten blocks each compare expected and available evidence per 10 fictional customer links; native IDs and shared keys are nearly full, while merge logs, matching rules and rights basis show many outlined empty blocks.
Illustrative estimate for a fictional equipment rental company. Outlined blocks are evidence a reviewer expects but the archive lacks.

This gap analysis belongs to the guide to cross-tool identity resolution, which links one customer across an ERP, a CRM, a retired billing tool and a help desk. Here the focus is on what a review expects to see behind links like those, what customer archives usually hold, and how to describe the difference.

A reviewer asks two things of every link: what evidence joined these records, and did anything later prove the join right? Methods vary. Salesforce describes exact matching alongside fuzzy methods such as edit distance and Jaro-Winkler; the Fellegi-Sunter model explained in Splink's documentation weighs agreement on each field. Each method leaves different evidence, and the review needs to see it.

#Expected evidenceWhat it lets a reviewer say
1Native ID in each systemWhich records are being joined
2Cross-reference field (one system storing another's ID)Someone deliberately linked them
3Migration map for each retired systemOlder history can be attributed
4Merge log with retired and surviving IDs and datesWhich activity belonged to which record before a merge
5Shared strong key such as a tax ID or contract numberThe link rests on an exact match
6Matching rule or data dictionary, with the years it appliedHow scored links were made, and whether the rule changed
7Rights basis for each source systemJoined records may be used together
8Downstream confirmation such as an applied payment or a contract number on both sidesThe link held in practice

Typically held, usually missing

EvidenceWhat companies usually keepWhat usually goes missingHow it goes missing
Native IDsAlwaysRarelyOnly when a system is deleted
Cross-reference fieldFor key accountsSmaller accounts and older yearsTyped in by sales ops when someone remembered
Migration mapThe latest migrationEarlier mapsDeleted after go-live
Merge logSurviving record onlyThe retired ID and merge dateTools that keep only the winner
Shared strong keyTax ID on ERP accountsThe same key in the CRM or help deskNever collected outside finance
Matching ruleA steward's habitAny written ruleLives in one person's head
Rights basisContracts on fileWhich terms applied to which system's recordsNobody mapped contracts to systems
Downstream confirmationApplied paymentsDisputes that broke a linkDisputes handled outside the system

Rules nobody wrote down are worth a word. A data steward who merged on "same domain plus similar name" for years leaves a consistent archive, but no one can audit the rule, and the method shapes which links exist at all. Salesforce, for example, notes that its fuzzy methods support only Latin characters and recommends exact matching for international data, so a company with customers in several scripts may have quietly linked fewer of them. Ask whether a matching rule or data dictionary exists, and for which years.

A fictional 400-person equipment rental company runs one ERP and one CRM and absorbed three regional branches with their own billing tools. Its finance systems lead was asked, for every 10 customer links across systems, roughly how many carry each item. These are estimates from a call, not system counts.

EvidenceExpected per 10 linksAvailable per 10Missing per 10Cause given
Native IDs10100None
Cross-reference field1073Branch customers never got the field filled
Migration map1064One branch's map was deleted after integration
Merge log1037The CRM kept only surviving records until 2022
Shared strong key1082Cash customers have no tax ID on file
Matching rule1028Merges followed a coordinator's judgment
Rights basis1046Branch customer terms never compared
Downstream confirmation1091Payments applied to the linked account

The archive is better than the merge log row suggests. Most links rest on a shared key and are confirmed by payments, so they can probably be trusted. The weak spots are concentrated: one branch's history before integration, merges before 2022, and the question of whether branch customer terms allow joining their records to the main CRM. That last point needs the rights review, not the introducer. The guide to identity mapping after an acquisition covers the same break when a whole company is absorbed.

Writing the gap into an introduction

One sentence per gap, with scope and cause, is enough. Some templates:

  • Merge log: "The CRM logged retired IDs on merges only from 2022; earlier merges kept the surviving record alone."
  • Migration map: "Mapping files survive for two of the three acquired branches; the third was deleted after integration in 2020."
  • Matching rule: "Merges were made by one coordinator using domain and name; the rule was never written down."
  • Rights basis: "Branch customers signed different terms that have not been compared with the main contract."

Those sentences give SourceX a starting scope. They also protect the introducer, because nothing in them overstates what the company holds.

Gaps that stop an introduction

Record gaps narrow the usable share of links. These conditions stop the introduction until they change.

ConditionEffectIntroducer's move
Under 50 full-time employees at peak (contractors excluded)Fails eligibilityDo not introduce
A parent group or franchisor controls the customer systemsThe company cannot license themFind who can authorize
No documented operating historyFails eligibilityDo not introduce
No authorized contactNobody can open a discussionIdentify the CEO or owner-CEO

Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.

What stays unknown until SourceX reviews it: how many links survive checking, whether joined records can be used together under their original terms, buyer interest and any offer. Help desk history that may not survive a tool change is covered in whether to migrate closed tickets to a new help desk; separation between customers' data in shared systems in MCP multi-tenant security; and de-identification of support records in anonymizing support tickets. To screen first, use the identity resolution qualification scorecard; for what the company prepares later, see the review packet contents list. Other record families are under data types.

Next step

Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If the company passes the gates and you can describe its link gaps in a few honest sentences, register as a partner, check who qualifies and read the terms before you introduce the owner.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Is a link without a recorded reason worthless?

No. It may be correct, and downstream records such as applied payments can still confirm it. But a reviewer has to treat it as an estimate until something proves it, so describe how many links lack a basis.

Should the company re-run matching before a review?

No. New matching produces new links, not evidence of the historical ones. Describe what exists; SourceX's review decides what can be used.

Do gaps in a help desk matter if the ERP is clean?

They narrow what can be joined. Clean ERP and CRM links still support order and contract history; the help desk side may need to be left out or scoped to records with a confirming key.

Sources

  1. moj-analytical-services.github.io/splink/topic_guides/theory/fellegi_sunter.html
  2. help.salesforce.com/s/articleView
  3. help.salesforce.com/s/articleView
  4. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment