Investigating incorrect numbers: lineage beats vibes
When a report looks wrong, “export it again and hope” isn’t a process. How source lineage turns a disputed figure into a five minute investigation.
Incorrect numbers destroy meetings. Someone spots a total that “can’t be right,” the room splits into camps, and the only resolution is regenerating three exports that still disagree. Without lineage, every dispute is politics.
What lineage gives you
- The source system and file (or API object) behind a figure
- The individual rows that rolled into a total
- The matching decision that attached a name to a canonical entity
- A clear place to fix the rule, not just the cell
Build for investigation, not just visualization
Pretty charts without receipts train teams to argue about feelings. An operating platform should make “show me where this came from” a single click.
That’s a core design principle in Sourcebook: every record stays connected to its origin so incorrect numbers become fixable, not mysterious.
Request Access to see lineage on your imports.
Related articles
Reconciling numbers across systems without losing a weekend
When accounting, payroll, and POS disagree, you lose more than hours. You lose trust. A practical look at continuous reconciliation versus monthly archaeology.
Why business data becomes fragmented (and stays that way)
Fragmentation isn’t a tooling failure. It’s what happens when every department buys the best system for its job. Here’s why the gaps compound, and what a trusted model requires.
Building a trusted business data model
Dashboards fail when the model underneath is mush. What “trusted” actually means for locations, people, vendors, and accounts, and how growing businesses get there.