Wallet-to-Ledger Reconciliation
Pronunciation: WOL-it tuh LEJ-er rek-un-sil-ee-AY-shun
Also known as: Crypto Wallet Reconciliation
Definition
Wallet-to-Ledger Reconciliation is the process of matching blockchain wallet balances and transactions to the organization's internal ledger records. In a payment system, teams should inventory controlled addresses, account for network fees and token contracts, map transactions to ledger entries, and investigate unknown or unconfirmed movements. The definition must identify the authoritative record, stable identifiers, relevant timestamps, owner, and permitted actions because provider, bank, ledger, and customer-facing states may differ.
Overview
How it works and where it fits
Wallet-to-Ledger Reconciliation is the process of matching blockchain wallet balances and transactions to the organization’s internal ledger records. In a payment system, teams should inventory controlled addresses, account for network fees and token contracts, map transactions to ledger entries, and investigate unknown or unconfirmed movements. Wallet-to-Ledger Reconciliation is closely connected to Balance-to-Ledger Reconciliation , Balance Ledger Entry , and Automated Reconciliation .
Its practical purpose is to prove completeness and correctness across operational and financial records before balances, revenue, liabilities, or customer outcomes are treated as final. Operationally, the implementation should inventory controlled addresses, account for network fees and token contracts, map transactions to ledger entries, and investigate unknown or unconfirmed movements. The principal risks include untracked addresses, chain reorganizations, dust, internal transfers counted as revenue, and wallet balances unsupported by ledger detail.
Wallet-to-Ledger Reconciliation should remain distinct from Balance-to-Ledger Reconciliation, Balance Ledger Entry, and Automated Reconciliation, because each can represent a different stage, record, control, or financial outcome. Timing items may be legitimate, but they remain reconciling items until evidence explains and clears them.
Testing should include partial settlements, fees deducted from proceeds, duplicate imports, late adjustments, reversals, one-to-many and many-to-one matches, missing references, currency conversion, and transactions spanning the cutoff. Useful controls include reconciled value and count, unmatched value, oldest exception, auto-match rate, override rate, duplicate rate, and time to resolution. For Wallet-to-Ledger Reconciliation, this point supports the definition’s focus on process of matching blockchain wallet balances and transactions to the organization’s internal ledger records.
The comparison must use the same entity, account, currency, time zone, cutoff, and accounting basis. Controls should keep original source records immutable, use stable match keys, explain many-to-one or one-to-many relationships, and route unresolved differences to an aged exception queue. For Wallet-to-Ledger Reconciliation, this point supports the definition’s focus on process of matching blockchain wallet balances and transactions to the organization’s internal ledger records.
Related glossary concepts
Example
A company's wallet shows 12.4 ETH, but its accounting ledger shows 12.1 ETH. The 0.3 difference might be a pending deposit, misposted gas fee, internal sweep or unrecorded transaction. Investigators compare chain-specific token and native-asset movements with ledger entries instead of forcing balances to match manually.
Comparison
Reconcile per asset, network, custody location and cutoff. Blockchain balances do not express which entity owns each unit or which invoice it belongs to. Keep unmatched items, timing differences and signed corrections traceable. An on-chain token balance may reflect a claim with separate redemption risk.
Key Takeaway
Investigate wallet and ledger differences by asset, network, timing and ownership evidence.
Sources
- ISO 20022 Universal Financial Industry Message Scheme — ISO 20022 Registration Authority (2026-08-03)
- CPMI Glossary — Bank for International Settlements (2026-08-03)
- Request IDs — Stripe Documentation (2026-08-03)