Skip to content
Platform

Every number has a history.

When a regulator, auditor, client or board member questions a figure, the answer should take minutes rather than days. Datox records the full chain behind each reported value and makes it available from the output itself.

The chain

What is recorded behind a single reported value

  1. Source

    the file, document, table or API response received

  2. Extraction

    the exact cell, row or document region read, with confidence

  3. Transformation

    the mapping and calculation applied, and its version

  4. Validation

    the rules that ran and their results

  5. Review

    the exception raised, the decision made and the reason given

  6. Output

    the field in the delivered report or submission

Explainability

From the report, back to the evidence

Lineage is only useful if it is reachable from where the question is asked. In Datox, a reported value can be opened to reveal the reasoning and the underlying evidence rather than a technical log.

Available from any reported value

  • View source, open the original document region or source record.
  • Explain this value, see the mapping, calculation and inputs in plain terms.
  • Validation history, which checks ran and what they returned.
  • Review history, comments, exception decisions and approvals.
  • Version, the logic that was in effect for that reporting period.
Why it matters

Traceability changes the cost of a question

In manual reporting, defending a number means finding the person who prepared it and hoping the working file still exists. Lineage removes that dependency and makes reporting reviewable by people who did not produce it.

  • Audit and assurance requests answered from the platform.
  • Regulator or client queries resolved without reopening old spreadsheets.
  • Handover between team members no longer loses institutional knowledge.
  • AI-assisted steps remain reviewable because their evidence is stored.