Reconciliation Break Investigation: Turning a Difference Into an Answer

Every crypto reconciliation of real volume produces breaks. A defensible finance function is not one that never has differences — it is one defined by what it does with them: triage, root cause, correction by proper entries, documentation. This guide is that workflow, the common crypto root causes, and the discipline, hedged, because resolution sufficiency is the auditor's call.

TL;DR

• Breaks are normal at any real volume — a good function resolves and documents them, it doesn't avoid them.
• Failure mode = an unexplained number carried forward or written off without root cause.
• Common crypto root causes: uncaptured gas; internal transfers mis-treated/un-matched; timing around period-end; missing/undisclosed wallet; source divergence (API vs CSV, explorer vs node).
• Resolve via correcting/adjusting entries — original error visible, documented — never a plug or in-place edit.
• Explained reconciling item ≠ unexplained break — only an understood, in-policy difference is a reconciling item.
• Documentation is the value — undocumented resolution ≈ unresolved for assurance. Sufficiency is the auditor's. Not accounting advice.

Breaks are normal; unexplained breaks are not

Every crypto reconciliation of real volume produces differences. A good function has a defined way to investigate, categorise, resolve, and document them so a difference becomes a corrected error or a known, explained reconciling item. The failure mode is an unexplained number carried forward or written off without root cause. Resolution sufficiency is an auditor judgement (the workflow inside the reconciliation process).

Common crypto root causes

Most crypto breaks trace to one of these. Identifying which is the root cause — not just the amount — is the core of the workflow; the fix's accounting effect is framework-specific.

Resolving a break

Generally a correcting or adjusting entry that records what actually happened, original error left visible, correction documented — not editing figures in place or plugging the difference. A plug destroys the audit trail and turns an error into a hidden misstatement. The correction follows proper accounting practice and the entity's controls; the accounting effect is auditor-confirmed.

Reconciling item vs open break

When a difference is understood and explained (e.g. a known timing difference clearing next period) it can be carried as a documented reconciling item, provided it is genuinely understood and within policy/materiality. An unexplained difference is not a reconciling item — it is an open issue. The distinction is central and assessed against the entity's policy and the auditor's view.

Documentation is the value

The value of break investigation is the trail: what the difference was, the root cause, the resolution, and who reviewed it. That documentation is what makes the reconciliation defensible and prevents recurrence. A resolved break with no documentation is, for assurance, close to unresolved. The documentation standard is part of the control and supports the auditor's assessment.

Practical guidance

1. Expect breaks — judge the function by resolution, not their absence.
2. Root-cause every break — gas / internal transfer / timing / missing wallet / source divergence.
3. Resolve via correcting entries — never a plug or in-place edit.
4. Only carry understood, in-policy differences as documented reconciling items.
5. Document what/cause/resolution/reviewer — undocumented ≈ unresolved.
6. Resolution sufficiency is the auditor's — entity-/framework-specific; not accounting advice.

How vendor tools handle break investigation

Cryptio and Bitwave flag breaks, support root-cause categorisation, and track resolution and sign-off. Confirm the tool categorises by root cause and documents resolution — the tool supports the workflow; whether resolution is sufficient is the auditor's judgement.

How Wag3s helps

Wag3s Ledger flags reconciliation breaks, supports root-cause categorisation (gas, internal transfer, timing, missing wallet, source divergence), and records resolution via correcting entries with reviewer sign-off on an audit trail — while resolution sufficiency stays the auditor's. See the Ledger product page.

Further reading

• Wallet-to-Ledger Reconciliation Process
• Gas Fee Reconciliation
• Internal Transfer vs Disposal (Crypto)
• Crypto Exchange Statement Reconciliation
• Multi-Chain Reconciliation
• Crypto Audit Trail & Piste d'Audit Fiable

Sources

• Every crypto reconciliation of real volume produces differences; a defensible function investigates/categorises/resolves/documents them (corrected error or known explained reconciling item) — failure mode is an unexplained number carried forward/written off without root cause; sufficiency is an auditor judgement
• Common crypto root causes: uncaptured gas, internal transfers mis-treated/unmatched, period-end timing, missing/undisclosed wallet, source divergence (API vs CSV / explorer vs node) — identifying the root cause not just the amount is the core of the workflow
• Resolve via correcting/adjusting entries with the original visible and documented, never a plug or in-place edit (a plug destroys the audit trail / hides a misstatement); accounting effect auditor-confirmed
• Only an understood, in-policy difference is a documented reconciling item (an unexplained difference is an open issue); documentation (what/cause/resolution/reviewer) is the value and part of the control — undocumented resolution ≈ unresolved for assurance; not accounting advice