Digital Asset Reconciliation: How One Company Examined On-Chain and Exchange Balance Differences

When reviewing the accounting results in FinTax, the finance team needed to compare system balances with its offline working papers, checking that transaction classifications, journal entry rules and asset conversion methods used a consistent basis.

Recorded Transactions Still Required Balance Reconciliation

Before the review meeting, most of the relevant transaction data had been imported and recorded, but system balances for some projects and assets still differed from the offline records. The differences did not have a single cause: activity within the exchange needed to be distinguished from on-chain transfers when assigning projects; the conversion of wrapped and staked tokens to underlying assets was not yet fully aligned; and the entry direction and asset account for one intercompany repayment needed correction. Reconciliation therefore required more than comparing balances. It also required examining the business meaning of transactions, rule configurations and measurement methods.

The client needed to clarify how transactions should be classified, which rules required adjustment and how balances should be compared before moving forward with month-end accounting on the basis of accepted reconciliation results. FinTax and the client team worked through exchange activity, rules for specific transactions and asset conversion methods to address these requirements.

Exchange Activity and On-Chain Transfers Needed Different Project Classifications

With exchange transaction records and on-chain address data already imported, the teams first clarified the project classification for exchange activity. Trading and investment activity within the exchange would be assigned to the exchange project, while transfers between the exchange and on-chain addresses would continue to be identified by their specific projects. For wrapped and staked tokens, the focus was on checking whether the system's period-end conversion logic was consistent with the underlying-asset basis used in the offline working papers.

Journal Entry Rules and Business Inputs Shaped Subsequent Accounting

The intercompany repayment was identified as a specific correction item: its journal entry direction needed to be adjusted, and the asset account needed to be changed to the account for the relevant token. A transaction involving a composite asset already had a split rule configured, but the business team still needed to provide the final allocation ratios before the results could be updated and used for month-end revaluation. The teams agreed to address balance differences for the main assets first, then refine the project-level classifications. Month-end revaluation and report preparation would proceed once the reconciliation results were accepted.

Balance Reconciliation Produced Specific Adjustments and Priorities

The review translated balance differences into specific items involving project classifications, business inputs, journal entry rules and asset conversion methods, establishing a sequence for further adjustments. At this stage, most transaction data had been imported and recorded, and differences requiring further work had been identified. Rule corrections, missing inputs and balance confirmation remained part of the subsequent work.

Discuss Digital Asset Reconciliation with FinTax

If your team also needs to reconcile on-chain and exchange records, contact FinTax to discuss your requirements for transaction classification, accounting rules and balance reconciliation.