Definition: Comparison of the ledger summary from the first recorded transaction (genesis) with the current balance.
Purpose: Ensure that no gaps or missing transactions exist in the account or wallet.
Example: The sum of all inbound and outbound Ethereum transfers for a wallet equals 1.337 ETH, which matches the current wallet balance of 1.337 ETH.
Use case: Relevant for any company performing digital asset accounting.
How to do it in TRES: Check the reconciliation status of your wallets.
A ✅ Reconciled status confirms there are no gaps. An ⚠️ unbalanced status requires further review to identify and resolve missing transactions.
Sub-System Reconciliation:
Definition: Comparison of two ledgers from distinct sources.
Purpose: Identify matches and mismatches between two sources containing the same data group, typically operational records versus financial records.
Example: A payment provider compares its internal transaction records with the blockchain reality.
Use case: Relevant for payment providers, OTC desks, and exchanges.
How to do it in TRES: Use the Multi-source reconciliation product, an add-on to FinOS. This feature highlights details when comparing two databases, making it easy to spot differences, as shown in the image below.
Definition: Comparison of a balance retrieved from an archive node against both the Running Balance and the Reversed Balance.
Purpose: Confirm that there are no gaps in an account or wallet at a specific point in time.
Example: Ensuring that the ETH wallet balance on January 1, 2025, is accurate in order to present it correctly in financial statements.
Use case: Relevant for any company performing digital asset accounting. Particularly important when presenting balances externally, as it provides a reliable cross-check of balance accuracy.
How to do it in TRES: Create a balance snapshot (time capsule) as of the target date and time (for example, January 1, 2025, 00:00). This snapshot compares the historical sum of transactions with the historical balance retrieved from the archive node.
Roll Forward Reconciliation
Definition: Tracking balances and cost basis over reporting periods, with a detailed view explaining the changes between opening and closing balances.
Purpose: Provide transparency into how balances evolve across periods, ensuring that every change is supported by underlying transactions and cost basis adjustments.
Example: Comparing the opening ETH balance on January 1, 2024, with the closing balance on January 1, 2025, and showing the detailed inflows, outflows, staking rewards, and revaluations that explain the change.
Use case: Relevant for any company performing digital asset accounting. Particularly valuable for financial reporting and audits, where clear explanations of period-over-period balance movements are required.
How to do it in TRES: Export a Roll Forward report to compare balances across defined reporting dates, such as January 1, 2024, and January 1, 2025. The report provides a breakdown of all balance movements that explain the transition between these dates.
Definition: Verification that transactions collected via the API for a defined period match the balances and activity expected in the system.
Purpose: Ensure that transaction data retrieved from blockchains or third-party sources is complete, accurate, and consistent with reported balances. This protects against missing records or gaps during financial reporting periods.
Example: A company runs data collection for an ETH wallet between June 1, 2025, and July 9, 2025. The reconciliation confirms that all inflows, outflows, and fees were captured and that the closing balance matches the blockchain reality, with no reconciliation difference.
Use case: Relevant for any company performing digital asset accounting. Especially important when preparing reports for specific time periods, such as month-end or year-end closes.
How to do it in TRES: Data collection reconciliation is performed via the API. Follow the detailed steps in the following link.