How to Correct and Rebuild Old Journals

Use this guide when existing realized journals need corrected accounts or amounts. Unrealized journals use a separate scope and matching rollback action.

Unsync removes journal output so you can rebuild it. It does not correct the source transactions.

An ERP rollback can permanently delete posted entries. Get approval, keep the original journal references, and confirm that the period allows corrections. If it is closed, agree on the correction with your controller first.

The live examples use NetSuite with empty ERP history and setup warnings. The rollback pictures come from Cryptoworth's published example of the earlier Reports layout. They do not show an update completed in this demo.

Select the original calculation, accounting connection, and journal scope. This example uses Realized; Unrealized is a separate scope.

If your original run is not listed, go to section 2 to access the older calculation.

Check Outdated for records that need review against current data. If it is zero, confirm the connection and scope; do not roll back entries just because they are old.

Open History. Match the original operation's Service, Type, and Calculation, where shown. Record the affected period and journal references. Wait for running jobs; investigate failed or unclear results before retrying.

For an older calculation, open Subledger > Calculation > Access Old Calculation.

Select the original run under Old Calculation, then click Main Calculation.

Open the original report's sync-status menu and use one matching rollback action. The following menu pictures show the published rollback example. If your operation does not offer the matching action, contact support before changing journals.

Virtual journals only: choose Unsync Virtual Sync Data.

Already posted to an ERP: choose its realized-data rollback, shown here as Retry - Unsync Realized Data. A virtual unsync alone does not remove posted ERP journals.

In Unsync Data, select Date Range and enter the correction's Start Date and End Date. Use All Transactions only when the whole output must be removed.

Enter a memo with the reason and original journal or job reference.

Review the connection, rollback type, dates, and warning. Click Undo only when the removal is approved. Wait for completion and verify ERP removals in the accounting system before rebuilding.

Correct the source transaction or GL mapping. If quantities, prices, or cost basis changed, recalculate, review, and publish the approved values before rebuilding.

Return to GL Sync > Sync, select the corrected, published calculation and intended connection, then open ERP Readiness > Review.

Follow the setup links to resolve connection, account, or mapping issues. Check warnings as well as failures.

Click Re-check, review the result, then Close. Finish required setup before syncing.

Open Sync to GL and choose your connection under VIRTUAL. Review the sync dialog's scope, then confirm the virtual sync. Use the full sync workflow for the posting options.

Open History and wait for the virtual job to succeed. Match its Service, Type, and Calculation. Virtual success means the journals are prepared in Cryptoworth.

Open Journals > Journals (ERP). Review the period, journal references, accounts, and debit and credit amounts. Confirm that the replacement entries agree with the approved calculation and mappings.

When approved, return to Sync > Sync to GL and choose your connection under ERP. Check the correction's scope before confirming. This posts the replacement journals to the accounting system.

Check the replacement job in History, then verify the journal references and amounts in the ERP. Keep the original, rollback, and replacement references together. If a result is unclear, check for partial posting before retrying.

Do not delete ERP journals by hand and assume Cryptoworth knows they were removed. Use the supported rollback route so the two systems stay aligned.