Treasury Reconciliation
Pronunciation: TREH-zhur-ee rek-un-sil-ee-AY-shun
Definition
Sources can include bank statements, custody reports, exchange records, blockchain data, payment-provider files, subledgers, and the general ledger.
Overview
How it works and why it matters
Treasury reconciliation compares actual asset holdings and obligations against internal accounting records across wallets, exchanges, custodians, bank rails and provider ledgers. It explains discrepancies such as network fees, pending funds, conversions, withheld reserves and misplaced entries.
Important technical and operational details
Reconciliation verifies balances and transactions across deposits, payments, transfers, conversions, fees, and valuation entries.
Differences may result from cut-off timing, pending confirmation, fees, returns, duplicate imports, address attribution, pooled accounts, or actual error and fraud. Simply forcing totals to match through an adjustment can conceal the cause. Blockchain visibility does not replace internal ownership and purpose records.
Teams should use stable identifiers, documented matching rules, tolerances, frequencies, and aging categories. Preparation and review should be separated for material accounts. Breaks need owners, evidence, escalation, and resolution deadlines. Reconciled closing balances should connect treasury reports, subledgers, and accounting without unexplained residuals.
The scope of Treasury Reconciliation should specify legal entities, accounts and wallets, assets and currencies, valuation sources, liabilities, restrictions, time horizon, decision rights, and the cutoff at which a position is measured.
Practical decision points
Start with an inventory of every place assets can reside: bank accounts, custodians, exchange subaccounts, wallet addresses and smart contracts. Establish a consistent cutoff and reconcile each asset and network in its native units before converting values for financial reporting. Investigate gaps such as pending deposits, fee debits, internal transfers and uncollected trading proceeds. A snapshot of total USD value can conceal that the wrong token or chain holds the assets. Approval workflows for corrections should preserve a link from the adjustment to source transactions and signers so audit can reconstruct the full movement of value.
Related concepts
Further reading
Example
The ledger reports 10,000 USDC but on-chain wallets hold 9,960. The team traces 30 to a payout still awaiting provider confirmation and 10 to fees, then updates clearing accounts without erasing the underlying records.
Comparison
Matching a total balance at midnight is not enough. Reconciliation needs asset and chain identifiers, transaction-level references, cutoffs, valuations and evidence of authorized adjustments.
Key Takeaway
Reconcile wallets, custodians, fees, liabilities, and ledger entries by asset and network.
Sources
- Bitcoin.org Documentation: Wallets — Bitcoin.org (2026-07-30)
- NIST Documentation: Key Management — NIST (2026-07-30)