Bitwave

Bitwave brings blockchain, wallet and exchange activity into an enterprise accounting workflow. Its subledger organizes transactions for ERP synchronization, while categorization and internal-transfer detection prepare the accounting treatment. Inventory segregation and lot-based identification support the team's cost-basis configuration.

Reconcile before sending journals

During period-end work, use the reconciliation controls to identify uncategorized transactions and entries marked Needs Contact. Add the missing business context before marking the period reconciled. For larger workloads, System Jobs can run bulk reconciliation for up to ten wallets at a time.

Balances and journals do not necessarily contain the same set of transactions: balance reports include uncategorized activity, while journal entries require categorization. That difference is useful when explaining why a wallet balance appears complete but the ERP journal totals are not ready.

After review, push the transactions or journal entries to the connected general ledger. Unreconciling a period inside Bitwave does not undo entries already sent to the ERP; corrections to posted accounts need their own handling there. A team should therefore treat reconciliation and ledger posting as distinct stages.

Access and integration

Bitwave scopes the service through an agreement and onboarding rather than a public per-user checkout. Its terms use annual service periods defined in the statement of work. Connect the required wallets, exchanges and accounting system during setup, and establish the organization's accounting policies before processing reports.

The developer reference covers read and write APIs for integrations. Bitwave describes its accounting connections as non-custodial, meaning it says it does not take custody of the assets while processing their records.