Reconciliation Break Investigation: Turning a Difference Into an Answer

This spoke is the workflow that runs whenever any of the other pillar reconciliations turns up a difference. Every crypto reconciliation of real volume produces breaks, so a defensible finance function is not one that never has differences. It is defined by what it does with them: triage, root cause, correction by proper entries, documentation. The focus here is that workflow and the handful of root causes most crypto breaks trace back to. Because resolution sufficiency is the auditor's call, this stays hedged.

In short

• Breaks are normal at any real volume. A good function resolves and documents them rather than avoiding them.
• The failure mode is an unexplained number carried forward or written off without a root cause.
• Common crypto root causes: uncaptured gas; internal transfers mis-treated or unmatched; timing around period-end; a missing or undisclosed wallet; and source divergence (API versus CSV, explorer versus node).
• Resolve via correcting or adjusting entries that leave the original error visible and documented, never a plug or in-place edit.
• An explained reconciling item is not an unexplained break: only an understood, in-policy difference is a reconciling item.
• Documentation is the value; an undocumented resolution is, for assurance, close to unresolved. 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 either a corrected error or a known, explained reconciling item. The failure mode is an unexplained number carried forward or written off without a 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, with the original error left visible and the correction documented, rather than 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 (for example a known timing difference clearing next period) it can be carried as a documented reconciling item, provided it is genuinely understood and within policy and materiality. An unexplained difference is not a reconciling item; it is an open issue. The distinction is central and is assessed against the entity's policy and the auditor's view.

Documentation is the value

The value of break investigation is the trail it leaves: 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 purposes, close to an unresolved one. 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, or 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 the difference, the cause, the resolution, and the reviewer; undocumented is close to unresolved.
6. Resolution sufficiency is the auditor's, being entity- and framework-specific. Not accounting advice.

Configuring a tool for break investigation

Tools such as Cryptio and Bitwave flag breaks, support root-cause categorisation, and track resolution and sign-off. The tool supports the workflow; whether a resolution is sufficient remains the auditor's judgement. Worth confirming:

• it categorises a break by root cause (gas, internal transfer, timing, missing wallet, source divergence), not just by amount;
• it resolves via correcting entries that leave the original visible, rather than allowing an in-place edit or a silent plug;
• it records the resolution and the reviewer on an audit trail, so a resolved break is documented rather than merely closed.

A tool that lets someone overwrite a figure to make a break disappear is working against the control, however tidy the result.

Where Wag3s fits

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. Whether a resolution is sufficient stays the auditor's call; Ledger supports the investigation and documentation rather than passing that judgement. 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

Notes on sources

Break investigation is an operational controls discipline rather than something set by an external standard, so there is no canonical authority to cite. The workflow here reflects ordinary reconciliation practice applied to crypto: every reconciliation of real volume produces differences, a defensible function investigates, categorises, resolves, and documents them, and the failure mode is an unexplained number carried forward or written off without a root cause. Resolution by correcting entries (with the original left visible) rather than a plug is standard accounting practice. Whether a given resolution is sufficient, and the accounting effect of the fix, are judgements for the entity's accountant and auditor. This is not accounting advice.