How to Generate and Review Journal Summary Reports

A Journal Summary groups journal amounts by classification or GL account. Use it to check where crypto activity goes in your accounting system.

Start with a reviewed calculation and prepared journals. See the GL Sync workflow if you need to build them first. Generating a report does not create journals or post them to your ERP.

The screenshots use a NetSuite demo with no ERP journals. Choose your own connection. An empty report is not proof that syncing is complete.

Go to Subledger > GL Sync > Sync.

Select the reviewed Calculation and the correct Connected To account. Use Realized for this workflow; Unrealized is a separate scope. Selecting either tab does not start a sync.

Open Journals. Under Connected Accounting System (ERP), select Journal Summary by Classification (ERP). Use the ERP section when checking output for your accounting connection.

Click Generate Report.

Choose Date under Granularity. Enter the start and end dates, then click Apply. The example uses September 1 to 30, 2026; use your review period.

Wait for the report to load. Confirm its Period, accounting connection, and calculation method and time before reading the amounts.

Check Classification and GL Account, then review both sides of the journal amounts.

Compare accounts and amounts with the approved calculation and mappings.

Investigate unexpected accounts or unclassified activity. Balanced debits and credits alone do not prove that every expected transaction was included.

Select Journal Summary by GL Account (ERP), then click Generate Report.

Choose Date, enter the same start and end dates, then click Apply. Check the dates again after switching reports.

Review GL Account, Debits, Credits, and Balance. Compare the same accounts and period when checking these amounts against your ERP.

When the report has journal rows, click Export.

In ERP Log Export, choose CSV under Report Type, then click Export. Check the downloaded file's period and amounts before keeping it as review evidence.

Keep the calculation ID, accounting connection, report period, and reviewer notes with the file. If no file is produced, check that the report contains the expected rows first.

Return to Sync. Review Journal status and any ERP Readiness warnings. These cards count transactions; summary rows group amounts and are not transaction counts.

Investigate Not synced, Outdated, or With issues records. Confirm that Ignored records were excluded on purpose.

Click a status card with a non-zero count to inspect its records. The example opens Not synced. Check transaction IDs, dates, and classifications, then close the review.

Check timestamps in this list against your review period; do not assume the summary's date filter also narrowed the status review.

Open History. Match the operation's Date Time, Service, Type, Status, and Calculation. An empty history does not confirm a successful sync.

A successful Virtual Sync means journals were prepared in Cryptoworth. ERP posting needs a successful ERP operation and matching journal references and amounts in the accounting system.