inhand Statement Studio
InHand / What a balance check can tell you

What a balance check can tell you

InHand editorial · Updated 2026-10-09

A closing balance should agree with the opening balance plus the signed transactions. That comparison can reveal missing rows, wrong signs or incorrect amounts. It cannot establish correctness on its own: two equal errors can cancel, and an incorrect description may leave every total unchanged.

Source balances are required

For an imported CSV, Studio requires opening and closing balance summary rows in the mapped Balance column, plus the statement period in the first three records. This release does not infer missing balances. Without source opening and closing balances, CSV verification and export remain blocked. Do not create balancing figures merely to make a check pass.

Try a fictional running-balance correction

The built-in Northstar Supplies sample contains an intentional mismatch. Its second transaction has a reviewed balance that differs from the fictional source row. Compare the source and editable row, correct the balance, and rerun checks. This demonstrates the interface; it is not a real bank statement or proof of bank accuracy.

Keep transaction order and source rows

Running-balance checks follow transaction order. Studio does not silently reorder an imported file or repair the bank's convention. Compare every date, sign, amount and running balance with the original source. The CSV source view retains classified and unresolved rows; its page controls allow you to inspect all of them. A source or transaction page shows at most 100 rows, while calculations and eligible exports include the whole statement.

Investigate a mismatch

  1. Compare the date and signed amount with the source row.
  2. Confirm the CSV Date, Description, signed Amount or separate Debit/Credit, and Balance mappings.
  3. Inspect unresolved source rows and unused populated cells.
  4. Check the statement period, currency and printed opening and closing balances.
  5. Review repeated rows and the destination application's import preview.

Studio has no PDF range or crop control. PDF exports require viewing and checking all pages, independently counting source rows, confirming transactions and source summary, and exact reconciliation. Editing a working row does not change the original PDF or CSV.

Possible duplicates remain included

Two payments can have the same date, description and amount and still be real separate transactions. InHand flags that repeated identity and retains both rows in totals and exports. Studio has no row-exclusion control. Review the source and the receiving application's duplicate handling rather than assuming every repeated identity is an error.

Understand the result

Matching totals alone do not unlock export. An eligible CSV must also satisfy the period, source coverage, row classification, date, currency and evidence checks. Studio displays working rows and notices in the browser; it provides eligible CSV/QIF exports, not a downloadable review report or professional audit opinion. Review the receiving application's preview before confirming its import.

Read PDF review and CSV export options or try the interactive sample.