Two systems can show the same closing wallet balance while disagreeing about how it was reached. One may omit a transfer and an equal offsetting movement, classify fees incorrectly or assign the assets to the wrong client. Institutional reconciliation therefore needs to explain both the stock and the activity. The objective is an accountable record linking every material movement to an asset, owner, business instruction and settlement state.
Use three views of the same activity
A practical reconciliation compares network observations, service-provider records and the institution’s books. Each sees something different. A chain shows activity at addresses and contracts; a custodian adds account allocation and service status; the internal ledger records business purpose and legal ownership. None is a complete substitute for the others. Our article on what onchain data can reveal explains why visible movement does not itself identify the beneficial owner.
Lukka describes ingestion, normalisation and reconciliation across onchain and offchain sources as part of its institutional data platform. This is a vendor description of the data problem and its product approach. It does not establish that an institution’s records are complete. The control still needs source coverage, ownership mapping and evidence that differences are investigated.
A transaction hash is a starting key
One network transaction can represent several economically meaningful movements. Contract execution may transfer more than one asset, pay a network fee and change a position in a protocol. Capture the transaction identifier together with the chain, event or movement identifier, asset definition and account allocation. Otherwise systems can duplicate or omit activity when they interpret the same transaction differently.
Ethereum’s transaction documentation explains fields such as sender, recipient, value, data and fee-related parameters. Those fields describe the network instruction, not the entire accounting treatment. A contract call needs interpretation in the context of the contract and resulting state changes. Distinguish the source evidence from the classification applied to it, so that an interpretation can be corrected without overwriting the raw record.
Reconcile internal transfers without inventing revenue
A movement between two wallets belonging to the same institution changes the location of an asset. It may still create fees and operational records, but it should not be mistaken for an external inflow and an unrelated outflow. Establish a controlled wallet inventory that identifies entity, purpose and custody arrangement. Review additions and changes so ownership assumptions do not rely on an analyst remembering which address belongs to which team.
Custodian omnibus accounts require another layer: the network balance may cover several clients while the provider’s subledger allocates it. Reconcile the relevant account statements and client obligations rather than expect a single public address to prove each allocation. Our discussion of proof of reserves explains the limits of balance evidence. A matched public balance does not settle whether the internal ownership records are correct.
Make timing differences visible
Pending transfers, unconfirmed deposits, exchange settlement and delayed provider exports can produce legitimate breaks. Label them by cause and age, assign an owner and define the condition for resolution. An unexplained item should not become acceptable merely because it appears repeatedly. Preserve the history of investigation and require approval for manual classifications or write-offs.
Build a closing process that reports source completeness, unresolved material breaks and changes in interpretation. Test a fee-only difference, an internal transfer, a duplicated event, a failed transaction and a movement reclassified after review. The Suzanne Morsfield speaker profile provides related accounting context. A useful reconciliation produces more than a matching number: it explains why the assets and obligations recorded by the institution agree with the evidence, and names the exceptions that remain.
A break needs evidence for its resolution
For each material exception, retain the source records, the explanation, any adjustment and the reviewer’s approval. A manual journal can make the books balance without resolving the underlying discrepancy, so distinguish a temporary accounting treatment from a verified correction. Track how long items remain open and whether the same source generates recurring breaks. The resulting pattern can reveal a missing wallet, a provider export issue or a classification rule that needs revision. Those findings should feed back into source coverage and processing controls before the next reporting close.