Checks compares a calculation's results with the values and records it expects. Review it before relying on the results.
A red dot beside Checks means at least one check failed. A calculation can finish with failed checks. The demo below has unresolved issues.
1. Open the completed calculation
Go to Subledger > Calculation. Choose your completed run in Calculation run. Confirm its ID, method, and period.
2. Open Checks
Click Checks. Start with failed checks and missing data, then review warnings.
3. Read the flagged row
Read Check, Status, Expected, Actual, and Difference together.
Status | Meaning |
PASS | This comparison found no difference. Other checks may still need review. |
Fail | The compared results do not agree. |
Missing data | Required inventory or other input is incomplete. |
WARN | Inspect the records. An exclusion can be correct, such as a confirmed spam transaction. |
Expected is the target for that check. Actual is what the run found. Difference is the reported gap. Read its unit: a count, currency amount, or inventory quantity.
For example, the cost-basis check expects 0 mismatches, finds 2, and reports a $2.50 difference. A separate PASS for result coverage does not clear that mismatch.
4. Inspect the affected records
Click Review beside the check you need to investigate. The example opens Missing Inventory Deviations.
Check the asset, connection, date, and missing inventory. Search by ledger ID, asset, or transaction ID when needed, then click Search.
5. Open the source transaction
Click the transaction number in the review. The example uses #4228; use your affected record.
Confirm that Ledger ID matches the review, then inspect the source record.
6. Correct the underlying issue
Use How to Resolve Transaction Deviations for missing inventory or market prices. Review dust, spam, and ignored records before changing their treatment.
For missing history, open Subledger > Reconciliation > Data Sanity Check. Correct the records, run Sync & Reconcile, and inspect remaining gaps.
7. Recalculate with review first
Return to Transactions. Clear investigation filters and selections, set the intended scope, and open the settings icon beside Calculate.
Confirm the method and Cost Basis Flow. Leave Publish the Result unchecked, then click Calculate. Keep Use only filtered transactions as inventory unchecked unless you intend to exclude earlier lots.
8. Check the new run
Select the new completed run, then open Checks again. Confirm that the relevant issues are resolved and explain any remaining warnings before reviewing cost basis and tax lots.
Recalculating creates new results. It does not repair the original transaction history. Publishing values and GL Sync are separate actions.