Multi-program organization
Making operational and financial data traceable
A governed lineage model connected activity, invoice detail, accounting entries, and reporting without pretending imperfect source data was clean.
Representative engagement · Client identifiers withheld
Situation
Program, customer, and finance teams were looking at different grains of the same activity. Reports could total correctly while still failing to explain which operational record produced a specific accounting line.
What was actually happening
The problem was not a missing dashboard. Identity and transaction lineage broke between operational detail, household-level records, journal lines, and reporting dimensions.
The focal point
Define the smallest durable transaction identifier and preserve it through every transformation instead of trying to reconstruct attribution at the reporting layer.
System designed
- Mapped the source record, transaction, journal line, and reporting grains.
- Defined explicit identifiers, dimensions, and exception states.
- Separated confirmed lineage from inference and unknown attribution.
- Designed reconciliation views that exposed gaps instead of hiding them.
Evidence of improvement
- — A traceable data contract from operational record to accounting output.
- — A documented exception path for records that could not be attributed safely.
- — A reporting design grounded in source evidence rather than dashboard assumptions.
What this made possible
With lineage defined, the organization could automate reconciliation and improve reporting without compounding ambiguity.