How to Roll Up Transactions and Restore the Original Entries

A roll-up combines matching transactions into summary entries. It can make a high-volume ledger easier to review. For example, you can group small receipts into one entry per week.

Cryptoworth keeps the original transaction data so you can undo the roll-up.

Transaction roll-ups change the subledger records used by calculations. They are separate from journal grouping or reversing an ERP sync.

A tax lot is an amount of an asset acquired at a set time and cost. FIFO uses the oldest eligible lots first. HIFO uses the eligible lots with the highest unit cost first.

Rolling up transactions can change the dates and costs represented by the summary entries. This can change which lots a later disposal uses, even when the total asset quantity stays the same.

Here is a simple illustration, with fees left out:

The last row illustrates the risk of combining lots. It is not a prediction that every roll-up will produce that result. Actual results depend on the transactions, summary dates, calculation scope, and lot-selection method.

Recalculate and compare cost basis, lot use, and realized gains or losses after a roll-up or undo. Do not assume FIFO or HIFO results will stay unchanged.

Go to Subledger > Transactions and open Crypto Transactions.

Filter the ledger to the connection, asset, and period you want to work on. Select the matching transactions.

The example selects two SOL receipts from sol.one in the same week. Check the selected count before you continue.

In the selection toolbar, open Bulk Action, then click Advanced rollup.

Choose Daily, Weekly, or Monthly under Granularity. Add a memo that explains the purpose of this roll-up.

Review the selected count and transaction preview. Click Roll Up only when the scope is correct.

If you intend to include every matching record, return to the table and use its Select All option first. Selecting visible rows may cover only part of the filtered ledger.

The job enters a queue. Go to Subledger > History, then choose Roll Ups under Transactions.

Wait for Success. Review the job's granularity, Date Selection, and transaction count.

In this example, First Transaction uses the first receipt's timestamp for the weekly summary. Scroll the history table horizontally if you cannot see Status.

Return to Transactions and review the summary entry. Look for the R marker beside its connection.

The two example receipts total 0.007415684 SOL. The table shows the rounded summary amount. A lower row count alone does not confirm that the accounting result is correct.

An automation finds matching transactions and rolls them up on a schedule. Its granularity is the size of each summary period. Its run frequency is how often Cryptoworth checks for work.

For example, weekly granularity with a daily run checks every day but still groups transactions by week.

Go to Subledger > Automations > Roll Up. Click + Roll Up Automation.

Enter an Automation Name and a useful Memo. Choose the roll-up granularity, then click Next.

Set Run Frequency, the day if shown, and Time of Day. Use the portfolio time zone shown below the time field.

Leave Include the current, incomplete period off if you want each period to finish before it is rolled up. Read the coverage message, then click Next.

Leave Apply to all transactions - Select All (no filters) off for a limited rule. Click Add Filter, open Select filter, and choose Wallets or Exchanges.

In the new connection filter, click Select.

Select the connections this rule should use, then click Choose.

Add the other filters you need, such as Assets, Classifications, or Transaction Type. Select their values.

The example limits the rule to one wallet, one asset, and Incoming transactions. It leaves the broad Apply to all transactions option off.

Add a Date Range filter if the rule should cover only part of the history. Set From and Until as needed, then click Next.

Without a start date, the first run can include all earlier matching history. An Until date also limits future coverage. Leave it blank if the rule should keep covering later completed periods.

Review First run, First run covers, the filters, and the estimated transaction count. Use View matching transactions to check the records before saving.

The estimate uses the data available now. Each scheduled run uses the live matching records when it starts.

Choose what to do if a run finds missing cost basis. Keep Skip that run and try again next time selected if the calculation needs to be completed first.

The form warns that rolling up a period with missing cost basis resets cost basis and proceeds for that period. Choose Roll up anyway only when that result is part of your approved workflow. Click Confirm when the schedule and scope are ready.

After scheduled runs, review their jobs in History > Roll Ups. Check the automation, period, transaction count, and Status. If you need to undo an automated roll-up, change or remove the rule's scope before its next run so it does not group those records again.

Use Unroll when you want to restore selected summary entries while keeping other roll-ups.

In Transactions, select only the summary rows marked R. Open Bulk Action > Unroll.

Unroll starts immediately. It does not open a second confirmation dialog. Review your selection before clicking it.

Wait for the action to finish, then refresh the transaction table. Check that the original records are back and the selected summary has gone.

In the example, the two separate SOL receipts return and the filtered row count goes from 263 back to 264.

If Unroll is disabled, clear the selection and select only rolled-up rows. A mix of original and rolled-up transactions cannot be unrolled together.

Use job revert when you want to undo all remaining summary entries from the selected roll-up jobs. The same controls work for manual and automatic jobs.

Open Subledger > History > Roll Ups. Select the checkboxes for the jobs you want to undo, then click Revert Selected.

The button shows the number of selected jobs. The example uses one job; you can select several eligible jobs for a bulk revert.

Check the number of jobs in Revert Selected Roll Ups. Click Revert to return their transactions to the main ledger.

Read the result for each job. Accepted means the revert request was accepted; it does not replace the final status check.

Close the result and refresh Roll Ups. Wait for each accepted job to show Reverted.

Review any skipped or failed jobs separately. An already reverted job has no enabled selection checkbox.

Return to Transactions. Confirm that the original records have returned and the summary entries from those jobs are gone.

A roll-up, Unroll, or job revert changes the records used by a calculation. Run a new calculation for the affected period and review the result before publishing transaction values.

Compare these items with the unchanged calculation or export you kept:

If the change does not fit your reporting policy, restore the original transactions and calculate again. Review any entries already sent to an ERP through your normal correction process; a transaction roll-up revert is not an ERP reversal.