Investigating incorrect numbers: lineage beats vibes
When a report looks wrong, “re-export and hope” isn’t a process. How source lineage turns disputed figures 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 row-level inputs 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 first-class action.
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, the cost isn’t just hours — it’s trust. A practical look at continuous reconciliation versus monthly archaeology.
Stop Throwing Spreadsheets at AI.
AI belongs in every modern business. Dumping messy exports into a chatbot and trusting the answer does not - and that shortcut fails quietly, then expensively.
How Dirty Data is Stopping your Business from Growing.
Regardless of whether you are operating a 6-figure business or a Fortune 500, there is one problem that everyone faces - Dirty Data, the silent growth killer.