What you need to know
- Entity matching and risk assessment answer different questions.
- Product context deserves separate attention.
- Test what a reviewer can explain.
Two questions in one profile
Exiger describes third-party relationship profiles combining ownership, operating locations and other information. The company says its entity-resolution tools reduce duplicate records and false positives, while customers retain control of risk models and review decisions.
Our reading is that these are separate product questions: which organization a record represents, and how that organization should be assessed. A confident answer to the second question depends on the first being understood.
A name that does not settle the question
Consider a fictional purchasing team comparing two businesses that use the same trading name. One record contains a street address; the other includes a different registered name and a missing location. A demonstration could ask the user to explain which attributes connect each record to the intended counterparty.
This is our proposed interface exercise, not an observed Exiger customer or a test we conducted. It deliberately starts with an incomplete identity. The point is to see whether the display helps a person recognize what remains uncertain before presenting a polished assessment.
The exercise could include a known duplicate and a genuinely different organization with a similar name. Those cases ask different things of the interface. Combining the duplicate would simplify the view; keeping the unrelated organization separate would preserve a distinction that the user needs.
A reviewer could note which details they had to open, which were absent and which part of the display led them toward a mistaken conclusion. That would make the demonstration more informative than simply counting the number of profiles returned.
Product context has its own role
Exiger says its risk-and-compliance profiles link companies with ownership, facilities, parts and materials, adding context to screening matches.
Our interpretation is that a company match and a product relationship should remain distinguishable in the interface.
For the fictional demonstration, the team could attach two different component descriptions to the same organization. The evaluator would then ask a colleague to identify which item the displayed assessment concerns. If the colleague cannot tell, the team has found a presentation question to resolve before treating the view as self-explanatory.
Measure the work left for a reviewer
A practical evaluation could finish by comparing the reviewer’s explanation with the fictional case prepared in advance. Did they choose the intended organization and item? Which uncertainty did they recognize, and where did they need clarification?
This would evaluate the intelligibility of a software view. It would not establish that a real transaction is permitted or that a screening system catches every relevant risk. The useful outcome is a specific list of interface questions, with examples the product team can reproduce and discuss.



