Skip to content
Governance & data lineage

Know what data means, where it moved, who can use it.

ReturnValue connects business meaning, technical lineage, ownership, access, and evidence use in one understandable governance layer.

Evidence-grade intelligence · Human validation · Traceable decisions
Governance / evidence viewIllustrative view
field-to-finding lineage
Source fieldpayment_amount
Governed transformversion 4.2
Finding impactauthorized use
  • OwnershipExplicit by source
  • AccessTenant isolated + RBAC
  • LineageField to finding
  • ApprovalHuman controlled
The ReturnValue approach

Governance that follows the evidence.

Policies and controls remain attached as evidence moves from source to calculation, finding, investigation, and outcome.

01

Business context

Define ownership, purpose, period, sensitivity, and acceptable use in language teams understand.

02

Technical lineage

Trace transformations, joins, mappings, calculations, and versions from field to final impact.

03

Controlled action

Apply role-based access, approvals, separation of duties, and explicit human validation.

How lineage flows

Every output, traceable to its source.

Lineage is the record of how data moves from raw input to final claim. ReturnValue tracks that movement automatically, as part of the platform, and builds it into core workflows instead of a separate tool you switch into. Open any insight or export, and the path that produced it is one click away, from source to claim.

The lifecycle runs in six steps, captured automatically: discover, connect, transform, surface, trace, and govern. You do not configure these; they are emitted as the work happens. Sources are catalogued as they are added, and each one gets a stable identity that the rest of the system refers back to. Joins between sources are recorded with their keys, conditions, and the analyst who created them.

Type changes, derivations, and aggregates are tracked at the column level, not just at the dataset level, and insights, datasets, and exports inherit the lineage of the inputs that produced them. There is nothing to wire up: open any output and follow its lineage back through transforms and joins to the original sources.

Stable source identity
Sources are catalogued as they are added, and the identity assigned there is what every downstream reference points back to.
Recorded joins
Join keys, conditions, and the analyst who created the join are captured with it.
Trace on demand
Useful for review, debugging, and answering where did this come from without re-running the work.
Shared backbone
Set who can ingest, transform, and publish. The lineage graph and the governance graph share the same backbone.
Connected investigation

See the path behind the number.

Lineage is not a separate technical diagram. It is available wherever a user needs to evaluate the reliability of a financial conclusion.

  1. 01SourceOriginal evidence
  2. 02TransformGoverned processing
  3. 03DeriveCalculation created
  4. 04UseFinding supported
  5. 05RetainOutcome governed
Evidence in context

Clarity at every decision point.

Trust grows when business context and technical lineage tell the same story.

Illustrative view. Values shown are examples, not customer data.

Field-to-finding lineage

100% traced
  1. Source fieldpayment_amount
  2. Transformversion 4.2
  3. Findingauthorized use
See ReturnValue in your environment

Follow your first financial signal.

Governance — Platform | ReturnValue.ai