Move reviewed crypto journal entries from Cryptoworth to your accounting system. This process is also called Reverse ETL: sending prepared data from Cryptoworth into an ERP, such as Xero, QuickBooks Online, NetSuite, or Odoo.
Follow this order: Calculate > Publish reviewed values > Virtual Sync > Review journals > Correct if needed > Realized Sync.
Choice | What it does |
Realized tab | Selects the realized journal scope. Selecting the tab alone does not post journals. |
Your connection under VIRTUAL | Builds journals inside Cryptoworth for review. It does not send them to the ERP. |
Your connection under ERP | Sends journals to the connected accounting system. Use it after review. |
Unsync Virtual Sync Data | Removes the virtual output so it can be rebuilt after corrections. |
Realized Data Unsync | Rolls back journals posted to the ERP. This can delete entries in that accounting system. |
The examples use NetSuite. Choose the connection for your own accounting system. The demo has setup warnings and empty ERP history; these screenshots do not show an approved or completed posting.
1. Calculate and approve the values
Start with synced and reconciled data, correct classifications, and complete fair market values. Run a cost basis calculation for the period you need. In Subledger > Calculation, select the completed run.
Open Checks and review the results. Resolve issues that affect the journals, then review the transaction results.
When the values are approved, click Publish Transaction Values. Wait for publishing to finish before using GL Sync.
For the calculation steps, see How to Run a Calculation. The example run still has failed checks and has not been approved for posting.
2. Set the ERP sync scope
Open Subledger > GL Sync > Sync.
Under Calculation, select the reviewed, published run. Confirm the run ID, method, and period. Do not assume the first run shown is the one you intend to post.
Under Connected To, choose the accounting connection that should receive the journals.
Select Realized for this workflow. Unrealized is a separate journal scope.
If ERP Readiness shows issues, click Review.
Use the setup links to fix required issues. Check the connection, imported chart of accounts, default accounts, wallet mappings, and classification mappings.
After making changes, click Re-check. Read the updated checks, then click Close.
A fallback to a default account may allow an entry to use the wrong account for your intended reporting. Review mapping warnings even when the platform lets you proceed. If a sync option is disabled, finish the required setup first.
3. Generate virtual journals
Click Sync to GL to open the choices.
Under VIRTUAL, choose your accounting connection. Review the options and scope in the confirmation dialog, then start the virtual sync when they are correct.
Open History. Match the operation's Service, Type, and Calculation. Wait for a successful virtual result before reviewing the generated journals.
Virtual success means journals were prepared in Cryptoworth. It does not confirm an ERP posting. The example history is empty because no sync has been run in this demo.
4. Review the journals
Open Journals, then choose Journals (ERP) under Connected Accounting System (ERP).
Check the Ledger Id, Transaction Date, Transaction Type, and Gateway Reference. Scroll across the table to review the debit and credit accounts and amounts.
Confirm that:
The entries belong to the intended calculation and period.
Debits and credits use the expected accounts and balance.
Gains, losses, and fees agree with the reviewed calculation.
The gateway reference and History record identify the correct sync mode and connection.
The example ERP table is empty. A row in Cryptoworth Ledger (GL) alone does not prove that the ERP received a journal.
Return to Sync. Use By classification to review the source groupings and By GL account to review the destination accounts.
Use the report's date filter when reviewing a period. A report filter changes the view; check the scope in every sync or unsync dialog separately.
If the journals need correction, use Section 6 before posting them to the ERP.
5. Post the approved journals to the ERP
On Sync, confirm the calculation, connection, and Realized scope again. Open Sync to GL, then choose your connection under ERP.
Review the posting options and scope, then confirm the operation when approved. This is the step that sends journals to the accounting system.
Check History for the same calculation, service, operation type, and successful result. Then open the accounting system and verify the journal references, period, accounts, and amounts there.
Do not use Synced alone as proof of an ERP posting. Confirm the destination and mode as well as the entries in the ERP.
6. Correct journals with unsync and resync
Before ERP posting
If only virtual journals exist, unsync the virtual output. This leaves any ERP postings unchanged.
In History, find the original operation. Check its calculation, service, type, period, and result.
Follow the rollback procedure and choose the virtual unsync action. It shows the older Reports layout; confirm the action for your connection.
In Unsync Data, choose Date Range for a limited correction when available. All Transactions can remove all synced entries from the report. Enter a memo, check the scope, then click Undo.
Wait for completion. Correct the records or mappings. If amounts changed, recalculate, review, and publish the approved values. Repeat Virtual Sync > Review.
After ERP posting
Use the connection's realized ERP unsync for posted entries. An ERP rollback can permanently delete journals. Obtain approval and retain references first. Verify the rollback in both systems.
Correct the data and repeat Virtual Sync > Review > Realized Sync. Keep the original job, rollback, and replacement job in your close records.
If a sync fails or the result is unclear
Review the Journal status cards on Sync. Use a populated card to inspect the affected records. With issues points to records that need investigation; Outdated points to records that need review against current data.
Problem | What to do next |
A sync choice is disabled | Open ERP Readiness. Finish connection setup, account import, and required defaults. |
The intended calculation is missing or outdated | Confirm that the correct run is complete and fully published. Select it again after publishing finishes. |
Accounts are missing or wrong | Review default accounts, classification mappings, and wallet or asset mappings. Rebuild virtual journals after corrections. |
A job is still running | Check the existing operation in History before starting another one. |
A job failed or timed out | Read its error and check the ERP for entries already created. Resolve the specific error before retrying. |
Cryptoworth reports success, but no entries appear in the ERP | Confirm Service and Type. A successful virtual sync stays in Cryptoworth. Also check the ERP company, date filter, and journal references. |
Posting or rollback is rejected by the ERP | Check its period locks, account availability, and integration permissions. Follow the error returned by that accounting system. |
If the result is uncertain, check for partial posting and keep the operation details before retrying. This helps prevent duplicate entries.
For the GL Sync tab's navigation, filters, and transaction drill-down, see How to Review, Sync, and Correct General Ledger Journals.