Banking workflow
Import statements
Use the dedicated bank import route. Where an opening balance and statement closing balance are supplied, Balansix can use them to strengthen the continuity and reconciliation checks.
Duplicate protection should work at transaction-line level so a partly overlapping statement can be handled safely rather than rejected or accepted only by file hash.
Running balance
The displayed running balance should start from the relevant opening bank position and roll through posted/statement activity. If it diverges from the bank statement, investigate the first point at which the balances stop agreeing.
Gaps, overlaps and skipped lines
Review warnings for duplicated dates/lines, statement overlaps and gaps. Use the skipped/missed-lines view for transactions that were not accepted or posted. A zero posting queue does not prove the statement is complete.
How to investigate a difference
- Confirm the opening bank balance.
- Find the first date the Balansix running balance differs from the statement.
- Check duplicates, overlaps and skipped/missed lines around that date.
- Check whether an item was posted to the wrong bank account or date.
- For Document-Led clients, check settlement matching and any bank-only coded exceptions.
- For Bank-Led clients, confirm every statement line has one accounting outcome.
Close the reconciliation
Complete the reconciliation only when the accounting balance and statement balance agree and any continuity warnings affecting the period are resolved. Keep the statement evidence linked to the reconciled period.