Data Lineage — know where every value came from

Vasco Alexandre
August 11, 2026

A registered address, a date of birth, a tax identification number. Each of them shows a single value in the case, in the same font, on the same row, with the same authority — whether it came from an official register or from a customer who mistyped it.
Data Lineage is now live in Dotfile, and it ends that ambiguity.
Two kinds of event, kept apart
The whole feature rests on one distinction, and keeping it is what makes the history readable.
- Observations are what a source reported. Registers and business data providers observe company properties; identity checks and document analysis observe individual properties. An observation never changes the value stored in the case — it is a statement about what a source saw.
- Edits are what someone changed. They carry the previous value, the new one, who made the change and through which channel: the console, the client portal or the API.
Because observations never overwrite anything, a property can hold the value currently stored plus everything the sources reported. That is how disagreement between a register and a declaration becomes visible instead of invisible.
What an analyst actually sees
An indicator appears on any property row that has a source behind it: a check mark when at least one source reported the value on screen, an exclamation mark when sources exist and none of them match, a clock when changes were recorded without an observation to compare against. The shape carries the meaning rather than a colour — a green or red mark would read as a verdict on the value itself, which is the job of your checks and your risk scoring.
Open the row and you get one card per distinct value, with the sources that reported it, their attribution and their date. On any card that is not the current value, Use value replaces the stored value with the observed one — and the replacement is itself recorded, with your name on it.
On the API too
Add `property_origin=true` when retrieving a case, a company or an individual, and the response lists every property with its current value and every source that reported one.
Two limits worth stating plainly: individuals returned by a register are not yet connected to property history, so an individual's sources are their checks; and ownership percentages have no history, because unravelling combines several providers into one figure, which is not the same thing as a source reporting a value.
Disagreement is shown, never announced. You see the cards, and you decide.
Read the documentation — or ask your Customer Success Manager to enable it on your workspace.

Ready for Anywhere?
Verify any business, enter any market, defend every decision. Every signal orchestrated, every decision traceable, from one platform.



