Preview totals are calculated from rows that pass the local parsing checks. Rows with date, amount, description or currency problems are excluded from those totals, so the totals can differ from the complete bank export while errors remain.
- Read the number of rows with problems beside the preview totals.
- Inspect the Problems column and fix the source mapping or confirmed data issues.
- Recheck totals after the problematic rows have been resolved or intentionally excluded.
Do not add a balancing row to force a partial preview total to match the statement. First determine whether invalid rows explain the difference.
Use the correct comparison
Compare money in with source inflows and money out with source outflows. A net change alone can hide equal errors on both sides. Also check the first and last dates to confirm the same period is being compared.
The later server check can still hold rows for duplicates, start dates or closed periods. Local preview totals therefore describe parsed source activity, not a guarantee of the amount that will ultimately enter the books. Use the finished Results log to confirm the actual imported outcome.
Was this article helpful?
Tell us whether this answered the question you came with.