Data reconciliation in finance: why numbers differ

The most frustrating disagreements in finance are rarely between right and wrong.

They are between two correct numbers that do not match.

Same issuer. Same reporting period. Different answer.

Short answer: two correct financial numbers usually differ because they used different source versions, timestamps, definitions, or methods. A reference system captures those details and turns the disagreement into a repeatable comparison.

The comparison scenario

Two teams deliver numbers that are both defensible in isolation:

• One uses a data vendor's normalized feed.
• The other parses primary filings and applies its own mapping.
• One runs a model on Monday; the other on Wednesday.
• One includes amendments; the other excludes them.

Each output is "correct" given its definition. The problem is that the definitions are different, and nobody realizes until a meeting asks, "Which number do we use?"

This is where data reconciliation best practices tend to break down:

• The comparison is ad hoc.
• The logic lives in spreadsheets or private notebooks.
• The answer changes next time because the context changed again.

The internal politics layer

This is the moment where internal trust gets stressed.

PMs, heads of data, and engineering leads are forced into a build vs buy data pipelines debate they did not ask for:

• "We should trust the vendor."
• "We should trust our internal pipeline."
• "We should trust whoever can explain it fastest."

The conversation shifts from data to politics. And the cost of reconciliation shows up every time another discrepancy appears.

Why this matters for AI and automation

If humans argue, agents fail.

When you start asking "can you audit AI outputs?" or explore explainable AI for finance, you quickly hit the same core issue: AI provenance. Every output needs a trace back to source inputs, timing, and methodology.

If the system can't explain a delta between two outputs, it isn't safe to automate.

Automation demands a repeatable comparison layer with source records and method evidence attached, not just a delivery mechanism.

Reference systems as neutral arbiters

The only reliable way to resolve competing "correct" numbers is to introduce a reference system.

A reference system:

• Runs in parallel with your existing process.
• Captures the exact inputs, timing, and methodology used.
• Produces a comparison artifact whenever outputs differ.
• Creates a durable audit trail you can reuse later.

In practical terms, it enables parallel run vendor comparison without forcing a full migration. You can keep your existing pipeline while a neutral reference system checks it.

What the resolution looks like

When two correct numbers disagree, a reference system gives you answers like:

• "Both are correct; one used an amended filing published 48 hours later."
• "Both are correct; one used a different definition of total debt."
• "Your vendor is lagging the primary source by 72 hours; the delta is timing."

Instead of debating whose number wins, you can explain why they differ, then decide which definition is right for the decision at hand.

The goal: fewer debates, more confidence

The point is not to stop discrepancies. It is to make them explainable.

When you have a reference system, disputes get resolved faster, decisions get defended more easily, and internal trust goes up.

To see how this works in practice, review how we structure verification and reference execution.

---

Common questions

Why do two correct financial numbers differ?

Two correct financial numbers can differ because they use different source versions, reporting timestamps, inclusion rules, vendor mappings, amendments, or calculation methods.

What is a reference system in data reconciliation?

A reference system runs beside the existing process, captures source inputs and methodology, and produces a comparison artifact when outputs disagree.

How do source trails help AI audit work?

Source trails give each output a source, timestamp, and method record, so humans and agents can explain a delta instead of trusting the latest dashboard state.

---

Related: What is Regulatory State?: why state matters more than filings

How we make it defensible: Evidence Packs: the artifact behind every outcome