Follow this order: Run Calculation > Review Reports, including SoDA and Roll Forward > Run Virtual Sync > Review Journals > Lock Period. Complete the checks below before starting.
Virtual Sync creates journals inside Cryptoworth. Posting those journals to your ERP is a separate step. If ERP posting is part of your close, finish and verify it before locking.
The screenshots use a demo entity. Some show gaps, missing values, or blocked sync actions. Treat these as issues to resolve, not as examples of an approved close.
Before you start
Agree on the entity, month, reporting currency, time zone, and reviewer. Use the same cut-off date throughout the close. Keep the prior month's approved closing balances nearby.
Confirm that all wallets, exchange accounts, and manual imports are included. Wait for imports and connection syncs to finish. Review classifications, internal transfers, duplicate records, missing prices, and inventory gaps.
Open Subledger > Reconciliation. Run Sync & Reconcile when the sources are ready.
Review Data Sanity Check. Check the report time and each connection's result. A synced connection can still have a balance gap. Resolve gaps before using the records for close. A current balance check does not replace your month-end balance evidence.
1. Run the calculation for the month
In Transactions, clear filters left over from other work. Open Date to choose the month you are closing.
Enter the first day in Start and the last day in End, then click Apply. The example uses December 2025. Use your own close month and confirm the active date filter.
Open the gear beside Calculate to review the calculation settings before starting the run.
Choose the Calculation Mode and Cost Basis Flow required by your accounting policy. Keep the approved method and pooling basis consistent with the prior close unless a change has been reviewed.
Leave Publish the Result unchecked so you can review the output first. Normally, leave Use only filtered transactions as inventory unchecked too. Earlier acquisitions may be needed to calculate this month's disposals.
When the scope and settings are correct, click Calculate once. Wait for the run to finish.
Open Calculation and select the completed run for the close. Check its period and method. Record the calculation ID, or give the run a clear name such as “December 2025 close.” A run marked “Beginning - End” must not be assumed to cover only your month.
Open Checks. Resolve failures, review warnings, and inspect the affected results. If you correct source records, run the calculation again and use the new run for the rest of the close.
2. Review SoDA and Roll Forward
Use reports from the same approved calculation. Match their dates, currency, and scope before comparing totals.
For ending holdings, open More > Statement of Digital Assets. If the statement is not ready, click Generate and wait for it to load.
Review the SoDA by wallet and asset. Check the remaining quantity, book value, and fair market value. Confirm Account Treatment and Wallet Role under your reporting policy, and save approved changes. Resolve missing values and unexpected negative holdings before sign-off.
For the period's movements, open More > Roll Forward. Click Generate if needed, then check the period printed on the report.
Compare opening balances with the prior approved close. Review additions, disposals, fees, and ending balances. Use Adds and Less to inspect the activity behind the totals. Compare asset quantities separately from values, and reconcile each measure on the same valuation basis.
Review gains, losses, fees, and tax lots where needed. Explain material differences and keep the supporting records.
Once the calculation and reports are approved, click Publish Transaction Values. Wait for publishing to finish before moving to GL Sync.
3. Run Virtual Sync
Open GL Sync > Sync.
Select the approved calculation, the correct ERP connection, and the required scope. Realized is the scope for realized activity; choosing this tab alone does not post to the ERP.
Open ERP Readiness > Review. Resolve setup issues and confirm the chart of accounts and account mappings. Re-check readiness before continuing. In this demo, the NetSuite connection is not ready, so the sync choices are disabled.
When the connection is ready, open Sync to GL and choose the connection under VIRTUAL. Review the calculation and scope in any confirmation before starting.
Open History and wait for the virtual operation to complete. Check the calculation, service, type, and status. An empty history, as shown here, is not a successful sync.
4. Review the journals
Open Journals > Connected Accounting System (ERP) > Journals (ERP) to inspect the prepared ERP journal entries. Confirm that the expected rows are present before proceeding.
Check the dates, debit and credit accounts, amounts, fees, and gain or loss accounts. Debits and credits must balance. Compare the output with the reviewed calculation and your approved close adjustments.
Return to Sync and review the journal summary By classification and By GL account. Investigate missing or unexpected accounts.
If the virtual journals need corrections, undo the affected virtual operation, correct the records or mappings, then rebuild and review the output. If amounts changed, recalculate and publish the approved values first. Follow How to Review, Sync, and Correct General Ledger Journals.
If this close includes ERP posting, complete the approved ERP sync and verify the resulting journals in both systems. Virtual Sync alone does not finish that step.
5. Save the close evidence
Keep the approved calculation ID, reconciliation evidence, SoDA, Roll Forward, journal summaries, and review notes together.
In the calculation, open Exports > Individual Reports. Generate any required reports that are not ready yet.
Wait for each export to show Completed, then click Download. Open the files and check their scope and totals. Keep opening-balance support separately if the export omits it.
6. Lock the reviewed period
Lock only after the checks, report review, journal review, and required ERP posting are complete. The lock protects the reviewed transaction data from later edits.
In the current Transactions layout, you can lock the records for the month using filters and a selection. Return to Transactions, restore the exact close dates, and remove unrelated filters. Use the arrow beside the header checkbox and choose All. Check that the selection covers the full filtered month, not just one page.
Open Bulk Action > Lock.
Check the transaction count and read the warning. When the selection is approved, select the acknowledgement checkbox and click Lock. If the count or scope is wrong, close the dialog and correct the selection first.
Return to Transactions and check the lock indicators on the affected rows. Open Settings > Locked Period to review recorded lock details, including dates and filters. Keep evidence of the final lock status.
If your calculation report offers a Lock Period button, confirm its date and filter scope before using it. It can be disabled while deviations remain. See Locking the Transaction Period.
Do not assume a lock closes the period in your ERP or resolves late imports. Complete your ERP close separately and check any late records against the approved close scope.
Final check
All expected sources and transactions are included.
Reconciliation gaps and calculation failures are resolved.
The calculation, reports, and journals use the approved scope and policy.
SoDA and Roll Forward have been reviewed against supporting balances.
Virtual journals have been reviewed; required ERP posting has been verified.
Final exports and reviewer approval have been saved.
The intended records are locked, and the ERP period is closed where required.
For a later correction, record the reason and obtain approval before unlocking affected data. Repeat the calculation, report, and journal reviews, then save new evidence and lock the corrected scope again. Avoid Remove all when only one period needs attention.