Use this guide when you need to check a calculation, explain a transaction's cost basis, or prepare support for an audit. You can follow the results and their source lots in Calculation > Result, without returning to the Transactions table.
Cost basis is the cost assigned to an asset.
An acquisition adds an asset, such as a purchase.
A disposal gives up an asset, such as a sale.
A tax lot records an acquired quantity, its date, and its cost.
Start with the calculation settings, review the checks, then trace the transactions you need to explain.
Before calculating: check the data and settings
FIFO, HIFO, WAC, and the other methods follow defined rules. An unexpected result is a reason to check the input data and settings first.
Sync all relevant wallets and exchanges before calculating. Wait for imports to finish.
Review Subledger > Reconciliation and correct missing or inaccurate records.
Confirm classifications, fair market values (FMV), transfer matches, and swap matches.
Sync all wallets before running Identify internal transfer in Transactions. That job checks across connections.
Confirm the intended period, wallets, exchanges, and any selected transaction filters.
For the calculation steps, see How to run a calculation. For missing prices or inventory, see How to Resolve Transaction Deviations.
Keep these settings separate
Setting | What it controls | What to confirm |
Calculation Mode | The method used to assign cost, such as FIFO, HIFO, or WAC. | Use the exact method required by your reporting policy. |
Cost Basis Flow | How inventory is pooled. | Per Asset pools (global pooling across connections) inventory by asset across connections. Per Connection keeps inventory separate for each connection. |
Calculation objective | Whether a calculation starts a trail, continues a trail, or runs independently. | This is separate from the lot selection method. See the objectives below. |
For example, with Per Connection, a purchase in Wallet A is not simply part of Wallet B's inventory pool. Check the source records and transfer matches when you review an outgoing transaction from Wallet B.
Understand the calculation method
Method | How it assigns cost |
FIFO | Uses the earliest available acquisition lots first. |
HIFO | Uses the available lots with the highest cost per unit first. |
WAC | Uses a weighted average cost. Cryptoworth has several WAC options; use the exact variant required by your policy. |
These methods can produce different cost basis values from the same records. Record the method you used. If the method or inventory pool changes, review the new run as a separate calculation and explain the change when comparing results.
Understand calculation objectives
A calculation trail carries inventory and lot information between runs.
Objective | Purpose | When to use it |
Trailed: Start | Starts a new trail without using previous calculation results. | First-time processing or rebuilding after historical records or the cost basis method have changed. |
Trailed: Continue | Continues from the previous calculation's inventory and lots. | Processing new activity when the earlier records are unchanged and the prior calculation is correct. |
Untrailed | Runs independently and does not create a trail that can be continued. | An isolated test or investigation. |
Use Understanding Cost Basis Calculation Objectives for the objective workflow. The V3 configuration screen shown below has Calculation Mode and Cost Basis Flow; it does not show an Objective selector.
Switching from Trailed: Continue to Trailed: Start creates a new baseline instead of extending the earlier one. An Untrailed test cannot become the starting trail for a later Continue run. Keep the earlier run as a comparison when changing the objective.
Keep the run available for review
In Transactions, open the settings icon beside Calculate. Confirm the method and flow, then leave Publish the Result unchecked so you can review the run before applying its values to Transactions.
Leave Use only filtered transactions as inventory unchecked unless you deliberately want to exclude earlier lots outside the selected filters.
1. Open the calculation you want to review
Go to Subledger > Calculation. Select the completed run from the calculation list. Check its run ID, method, and period before reviewing the numbers.
Keep that run ID with your review notes and exports. When comparing two runs, check that the period, connections, method, and inventory settings match. Record any differences before comparing totals.
2. Check for issues first
Look for the red dot beside Checks. It means at least one check failed. Open Checks before reviewing the results.
Read the flagged check's status, Expected, Actual, and Difference. Use Review where available to inspect the affected records.
Review warnings in context. Some identify activity that was intentionally excluded. A completed run or a passing check does not replace your review of the source records.
If records need correction, follow How to Resolve Transaction Deviations, then run and review a new calculation. The screenshots in this guide show a sample run with flagged checks; they illustrate navigation, not an approved result.
3. Choose the question you need to answer
Open Result, then stay on Cost Basis for the transaction-level values.
Your question | Choose | What to expand |
Which earlier lots supplied this outgoing transaction's cost basis? | Review by Acquisition | An outgoing transaction. Its detail is called Lots used. |
Which outgoing transactions used this acquisition? | Review by Disposal | An incoming transaction. Its detail is called Disposals. |
Both views use the same calculation data. The view changes the direction in which you trace it.
4. Trace an outgoing transaction to its acquisition lots
Choose Review by Acquisition. Enter the outgoing transaction's ID or hash in the search field, then press Enter. Confirm the transaction's date, asset, and amount, then click + beside it.
Read Lots used to see the earlier acquisitions selected for that transaction.
Check the acquisition IDs and dates, asset, Qty used, Cost basis, and connection or pool. Scroll the table horizontally if a column is outside the visible area.
In the example, transaction 1739 uses lots from acquisitions 1733 and 1736. Their displayed costs of $2,710.04 and $11,298.14 add to the outgoing transaction's $14,008.18 cost basis.
Also review the transaction fee and taxability shown on the parent row. Include fee-related inventory use in your quantity checks; do not compare lot quantities with the main outgoing amount alone.
5. Trace an acquisition to the disposals that used it
Choose Review by Disposal. Search for the incoming transaction's ID or hash, press Enter, then click + beside that transaction.
Read Disposals to see which outgoing transactions consumed inventory from that acquisition.
In this example, acquisition 1733 supplied inventory to four outgoing transactions, including 1739. The Cost basis on a detail row is the portion assigned from this acquisition. A disposal that used several acquisitions can have a larger total cost basis on its own parent row.
Use the IDs to trace in the other direction when you need more detail. Search the disposal ID in Review by Acquisition, or an acquisition ID in Review by Disposal.
6. Investigate an unexpected result
What you find | What to check next |
An expected lot is missing | Confirm the acquisition was imported, has the correct timestamp and classification, and is available under the run's inventory settings. |
A lot from another wallet is used | Check Cost Basis Flow and the recorded transfer matches. |
The wrong acquisition order appears to be used | Confirm the run's method and the lots available at the disposal time. |
A cost or gain differs between runs | Compare run IDs, source-data changes, period, connections, method, and inventory settings. Check fees and displayed rounding too. |
The transaction is not found | Confirm the run includes it. Check the ID or hash and press Enter to apply the search. |
Correct the source problem and review a new calculation. Keep the earlier run and its ID as the reference for your comparison. Use your approved accounting policy when changing methods or settings.
7. Export support for the review
Open Exports in the same calculation. Under Individual Reports, find Calculation Detail and click Generate.
Wait for COMPLETED, then click Download in that report's row.
Use Calculation Detail for transaction-level costs, proceeds, FMV, fees, and classification context. Generate Tax Lot separately when you need the lot trace and open inventory detail.
These reports belong to the selected calculation. Keep the run ID, reporting scope, reviewed transaction IDs, exceptions, and downloaded files together. Exporting a report does not publish transaction values.
Before you approve the review
The run ID, period, connections, method, and inventory settings are recorded.
Flagged checks and warnings have been reviewed, with corrections or explanations documented.
The transactions you reviewed trace to the expected lots and source records.
Any comparison with an earlier run explains changes in data or settings.
The supporting reports come from the same reviewed run.
When the review is complete, follow your team's approval and publishing process. Publishing transaction values and running GL Sync are separate actions.