Cryptoworth flags a deviation when transaction data is missing or incomplete. For example, a transaction may have no market price, or a withdrawal may exceed the amount of an asset recorded as available.
Use the steps below to find the issue, correct the transaction data, and review a new calculation before publishing its values to the Transactions table.
1. Check your transaction data
From the sidebar, open Subledger, then select Reconciliation.
Click Sync & Reconcile to update and reconcile your connections.
Review Data Sanity Check and investigate any gaps in the transaction history. Import missing transactions or correct inaccurate records before calculating.
Open Transactions and check for missing classifications and fair market values (FMV). FMV is the asset's market value at the time of the transaction.
For missing prices, follow the No Market Data steps below.
2. Run a calculation for review
On Transactions, click Calculate.
In Calculation Configuration, select the required Calculation Mode.
Under Cost Basis Flow, select Per Asset or Per Connection, according to your accounting setup.
Clear the Publish the Result checkbox. This lets you review the calculation before its values appear in the Transactions table.
Leave Use only filtered transactions as inventory unchecked so the calculation can use earlier acquisition lots outside your current filters.
Click Calculate and wait for the calculation to finish.
3. Review the calculation checks
Open the completed calculation in the Calculation tab, then select Checks.
Review any checks marked WARN or FAIL. Compare the Expected, Actual, and Difference columns to understand the issue.
Two checks are especially useful when investigating missing inventory:
Check | What to review |
Transactions have cost-basis results | Whether every transaction included in the calculation has a cost basis result. |
Missing Inventory Deviations | Whether any disposals lack enough recorded inventory, and the missing quantity. |
To inspect how a transaction's cost basis was calculated:
Open Result.
Search for the transaction ID or hash.
Expand the outgoing transaction using the + icon.
Review Lots used to see the acquisitions, quantities, and costs used in the calculation. A lot records an amount of an asset acquired in an earlier transaction.
Use the sections below to correct the underlying issue.
No Market Data
This deviation means Cryptoworth could not find a market price for the asset at the transaction's timestamp.
In Transactions, use the Deviations filter to select No Market Data, then click Apply.
Check your Fair Market Value settings.
If a price is still missing, update the transaction's unit price using the correct price for its timestamp.
For a confirmed spam token, you can apply an Ignore classification to exclude its transactions from calculations and reports.
Missing Inventory (Negative Balance Deviation)
This deviation means the calculation cannot find enough of an asset to cover an outgoing transaction.
For example, suppose you send 28.1 MATIC, but Cryptoworth records only 10 MATIC as available at that time. The calculation is missing 18.1 MATIC of inventory.
Check the affected asset and connection for:
Missing deposits, purchases, or incoming transfers. Import any missing transaction history.
Incorrect amounts or timestamps. Correct entries that record the wrong quantity or place an incoming transaction after the outgoing transaction.
Duplicate outgoing transactions. Review and resolve confirmed duplicates.
Incorrectly ignored transactions. Restore the correct classification for genuine acquisitions that were excluded.
Restricted inventory. Check whether Use only filtered transactions as inventory excluded earlier acquisitions needed by the calculation.
Return to Subledger > Reconciliation after correcting the records. Run Sync & Reconcile and review the remaining gaps in Data Sanity Check.
4. Recalculate and publish the reviewed values
Return to Transactions and run a new calculation with Publish the Result unchecked.
Open the new calculation and review Checks again. Confirm that the relevant deviations are resolved, then review the transaction results.
When you are satisfied with the results, click Publish Transaction Values.
Wait for publishing to finish before starting GL Sync.
Running a calculation with Publish the Result unchecked does not update the values in the Transactions table. Publish the reviewed calculation to apply those values.