How to Review, Sync, and Correct General Ledger Journals

Use GL Sync to prepare journals, review their accounts and amounts, and send approved entries to your accounting software. The tab brings sync, history, journals, account setup, and integrations into one place.

Follow this order: Calculate > GL Sync > Virtual Sync > Review > Realized Sync.

The examples use NetSuite. Choose your own accounting connection and approved calculation. Some example screens show setup warnings; resolve the required checks before starting a sync.

Start with synced and reconciled transaction data, correct classifications, and fair market values. For the calculation procedure, see How to run a calculation.

In Subledger > Calculation, open your completed run. Review Checks and the calculation results. Resolve relevant issues before approving the values.

When the calculation is approved, click Publish Transaction Values. Wait for publishing to finish before moving to GL Sync.

The calculation screenshots show an example with outstanding checks. They identify the controls; the displayed result has not been approved for posting.

Open Subledger > GL Sync. Start on its Sync tab.

Use Calculation to select the run you reviewed and published. You can search by its run ID. Confirm its method and period before continuing.

Choose the accounting connection that should receive the journals.

Select Realized for this workflow. Unrealized is a separate scope.

If ERP Readiness shows issues, click Review.

Read each item and use its setup link to correct the problem. Common requirements include an active connection, an imported chart of accounts, default accounts, and the correct calculation and mappings.

For account import steps, see Importing your Chart of Accounts.

After correcting the setup, click Re-check, then close the check when you have reviewed the result.

Required setup problems can disable both sync choices. Review warnings too, since they can affect which accounts receive the journals.

Click Sync to GL to open the menu.

Under VIRTUAL, choose your accounting connection. Review the options in the sync dialog and confirm the virtual sync when the scope is correct.

Virtual Sync keeps the journals in Cryptoworth. It does not post them to your ERP. The example option is unavailable until the connection's required setup is complete.

Open History to check the operation. Match the calculation, service, and type. Wait for a successful result before reviewing the generated journals.

The example history is empty. Your operations appear here after a sync runs. A successful virtual operation does not confirm that journals were posted to the ERP.

On Sync, use By classification to review how transaction classifications feed the journals. Use By GL account to review the destination accounts.

Check the period, accounts, debits, credits, gains, losses, and fees against your approved calculation and mappings.

Open Journals, then select Journals (ERP) under Connected Accounting System (ERP). Review the Ledger Id, date, transaction type, gateway reference, and account amounts.

Use the Gateway Reference when checking whether a row came from a virtual sync or a posted ERP journal. The example ERP table has no rows because no ERP sync has been run in this demo.

For Cryptoworth's own ledger view, choose Journals (General Ledger) under Cryptoworth Ledger (GL).

If you need more space, collapse the Journals sidebar. Read the entry's ID, date, accounts, and debit and credit amounts across the row.

Keep the Ledger Id with your review notes. The example highlights 3400 so you can trace the same source transaction later. A row in the Cryptoworth ledger alone does not confirm an ERP posting.

Click the date-range button below the report title. It shows From Beginning - To End when no date range is selected.

In Date Filter, set Granularity to Date.

Use the left calendar field to choose the start date and the right field to choose the end date. The example uses 1 December 2025 through 31 December 2025.

Click Apply.

Check the range shown on the report. To return to the full view, click Clear filters.

A report filter controls what you are reviewing. Check the scope in the sync or unsync dialog separately before you submit that operation.

Read the Journal status cards on Sync.

Click a status card with a non-zero count to inspect its transactions. The example opens Not synced.

In the review list, click the transaction ID you need to investigate.

Cryptoworth opens Transactions with a Ledger ID filter. Confirm the date, asset, quantity, and connection against the journal you are reviewing.

For missing prices or inventory, follow How to Resolve Transaction Deviations. If a correction affects the calculation, calculate and review the updated data before posting it.

Return to GL Sync > Sync. Confirm the calculation, accounting connection, and Realized scope again. Open Sync to GL and choose your connection under ERP.

Review the posting options and scope, then confirm the operation when it is approved. This step sends journals to the connected accounting software.

Check the operation in History. Confirm its service, type, calculation, and successful result. Then verify the journal entries and amounts in the accounting software for the same period.

If the operation fails or its result is unclear, investigate the existing job before starting another posting attempt.

Use an unsync when journals already generated or posted need to be removed before a correction. Match the operation to the service that created the journals:

Start in History and identify the original operation by its calculation, service, type, and period. Record its details before the rollback.

For a limited correction, use a date-range scope where available and record the reason in the memo. Review the affected period before confirming the unsync. Wait for it to finish and check the result in History and, for an ERP rollback, in the connected ledger.

Correct the source data or mapping. If the calculated values change, run a new calculation, review it, and publish the approved values. Repeat Virtual Sync > Review > Realized Sync for the corrected scope.

Cryptoworth's rollback guide explains rollback scope and its effect on posted entries. Confirm the available action for your connection before executing a rollback.