Skip to main content

Best Practices for Month Close.

Written by Customer Success Team

"Closing the books" in Cryptoworth is the process of verifying, reconciling, calculating, reporting, syncing, and locking your digital asset accounting data for a specific period. The goal is to make sure your crypto subledger is complete, accurate, and ready to support your ERP, financial statements, and audit trail.

This workflow should be completed before month-end reporting, ERP sync, audit review, or any final sign-off on digital asset balances.

Phase 1: Data Verification

Before performing accounting work, confirm that Cryptoworth has complete and current data from every relevant source.

1. Confirm Data Sources Are Synced

Action: Go to the relevant entity, then review connected wallets, exchanges, custodians, and third-party integrations from the Accounts or Connections area.

Goal: Confirm that every expected wallet, exchange, API connection, and manual import is present and synced before running calculations.

Why it matters: Cryptoworth calculations should not be run while data is still syncing. If transactions are still being imported, your balances, cost basis, reports, and journals may be incomplete.

2. Verify Wallets, Exchanges, and API Connections

Action: Review all public wallet addresses, exchange integrations, Fireblocks or custodian connections, and any manually imported transaction sources.

Check for:

  • Disconnected APIs

  • Missing wallets or addresses

  • Incomplete CSV imports

  • Incorrect wallet or connection grouping

  • Exchange accounts with stale data

  • Recently added wallets that have not finished importing

Goal: Every source that held or moved crypto during the period should be connected, synced, and included in the correct entity.

Phase 2: Reconciliation

This is the core close step. You must confirm that Cryptoworth's computed ledger balance matches the reported balance from the blockchain, exchange, or connected data source.

Action: Navigate to Reconciliation and run a Reconciliation Check.


Goal: Sync all the connections to the present and initiation a comparison of the reported balance from the blockchain or API source against Cryptoworth's computed balance.

Expected result: Reported Balance - Computed Balance = 0.

If there is a mismatch: Investigate missing transactions, duplicate transactions, unsupported assets, bridge activity, smart contract interactions, staking activity, manual import issues, or ignored transactions. Contact Support Team via Intercom or Telegram/Slack channel if you have a dedicated support group.

Action: From the Transactions page, open the calculation settings and run the calculation for the entity and period.

Select the calculation method that matches your accounting policy, such as:

  • FIFO

  • LIFO

  • WAC

  • WAC Perpetual

  • HIFO

Optional settings to review:

  • Audit logs

  • Connection-level calculation

  • Tax lots

  • NFT cost basis

  • Asset-base calculation

  • Recalculation of acquisitions or dispositions

Goal: Produce updated reports for the period using the approved cost basis method and calculation settings.

3. Resolve Transaction Deviations

Action: Go to Transactions, run a calculation, then use the Deviation filter to locate transactions with issues.

Common deviations:

  • No Market Data: Cryptoworth cannot find fair market value for the asset at the transaction time.

  • Negative Balance Deviation: The ledger has insufficient inventory to support a send, withdrawal, or disposal.

Fix No Market Data: Review fair market value settings, manually update the unit price if needed, or ignore spam assets when appropriate.

Fix Negative Balance Deviations: Review missing transaction history, incomplete CSV uploads, timestamp issues, ignored transactions, duplicate records, and inventory tracking settings. Use Sanity Check and Reconciliation to identify the source of the missing inventory.

Phase 3: Classification and Valuation

Once the data reconciles, make sure every transaction has the correct accounting treatment, fair market value, and cost basis.

1. Confirm Fair Market Values

Action: Review transactions with missing or incorrect fiat(Cost and Proceed) values.

Goal: Every transaction that affects accounting reports should have an accurate fair market value at the transaction date and time.

Fix: Update fair market value settings or manually adjust unit prices for assets that do not have reliable market data.

2. Review Classifications and Chart of Accounts

Action: Review transaction classifications, labels, and Chart of Accounts mappings.

Check for:

  • Revenue

  • Expenses

  • Fees

  • Swaps

  • Transfers

  • Internal Transfers

  • Staking rewards

  • NFT activity

  • DeFi activity

  • Realized gains and losses

  • Unrealized gains and losses

Tip: Use automation rules and bulk classification tools where appropriate, but review the output before close.

After the ledger is reconciled and calculated, prepare reports and sync the approved accounting output to your ERP or general ledger.

Go to Reports page > Click on Sync > Sync Realized Data

If user wants to sync Unrealized Gain/Loss Data,

Go to Reports page > Click on Sync > Sync Unrealized Data

1. Review Reports

Action: Go to Reports after running the calculation.

Recommended reports for close:

  • Historical Balance By Connections Report

  • Unrealized gain/loss report

  • Tax lots report

  • Journal summary by GL account

  • Transaction export

  • Snapshot Report

Goal: Confirm that ending balances, cost basis, realized gains/losses, and unrealized gains/losses match expectations.

2. Reconcile Cryptoworth to the General Ledger

Action: Compare Cryptoworth reports against the corresponding balances in your ERP, such as QuickBooks or NetSuite.

Core check: The cost basis or asset balance in Cryptoworth should match the corresponding digital asset account in the general ledger.

Example:

Asset

Cryptoworth Cost Basis

GL Account

GL Balance

Difference

BTC

$120,000

Digital Asset - BTC

$120,000

$0

ETH

$80,000

Digital Asset - ETH

$75,000

-$5,000

If there is a difference: Review missing journals, duplicate journals, incorrect account mappings, date filters, classification issues, or transactions booked to the wrong GL account.

Action: Open the active ERP integration and confirm all accounts are mapped correctly.

Default/Historical Level Mapping:

Connection Level Mapping :

Asset Level Mapping:

Check:

  • Asset accounts

  • Revenue accounts

  • Expense accounts

  • Fee accounts

  • Realized gain/loss accounts

  • Unrealized gain/loss accounts

  • Entity or class mappings, if used

Goal: Make sure each transaction type posts to the correct account before syncing.

4. Sync Approved Journals or Reports

Action: Sync the approved data to your ERP using the relevant Cryptoworth integration workflow.

Verification: Confirm the synced journals appear in the ERP and match the Cryptoworth report totals for the close period.

Phase 5: Finalization

Once data has been verified, reconciled, calculated, reviewed, and synced, finalize the period.

1. Export Close Support

Action: Export final reports from the Reports page.

Recommended close package:

  • Transaction export

  • Unrealized gain/loss report

  • Tax lots report

  • Journal summary by GL account

  • Reconciliation support

Goal: Preserve a complete audit trail for the period.

2. Lock the Period in Cryptoworth

Action: From the Reports page, use Lock Period after the period calculation is complete.

Important: The Lock Period option may be disabled if ledger deviations remain unresolved.

Goal: Prevent accidental changes to reconciled historical transaction data.

3. Close the Period in the ERP

Action: After Cryptoworth data has been synced and verified in the ERP, close or lock the accounting period in the ERP according to your normal finance process.

Final step: Confirm that no additional crypto journals, manual adjustments, or late imports are expected for the period.

Close Checklist

  • All wallets, exchanges, custodians, and manual sources are connected and synced.

  • Ledger Health has been reviewed.

  • Sanity Check has been completed.

  • Reported balances match computed balances or variances are documented.

  • Duplicate transactions have been reviewed.

  • Unregistered transactions and assets have been resolved.

  • No Market Data deviations have been corrected.

  • Negative Balance Deviations have been resolved or documented.

  • Fair market values have been reviewed.

  • Cost basis calculation has been run using the approved method.

  • Classifications, labels, and Chart of Accounts mappings have been reviewed.

  • Reports have been generated and exported.

  • Cryptoworth balances reconcile to the ERP.

  • Approved journals or reports have been synced.

  • The period has been locked in Cryptoworth.

  • The period has been closed in the ERP.

Important Reminder

This document is for operational guidance only and does not constitute accounting, tax, legal, or investment advice. Crypto accounting workflows depend on each organization's accounting policy, reporting requirements, jurisdictions, ERP configuration, and audit expectations. Work with a qualified accounting professional before finalizing your close process.

Did this answer your question?