Before importing
- Select the correct client and bank account.
- Use a statement file that contains a continuous date range.
- Keep the bank's original transaction dates and descriptions.
- Do not remove rows simply because they are transfers or look non-business. Classification happens after import.
Map the bank columns
Map date, description/reference and amount fields. If the file has separate debit and credit columns, map both. If it has one signed amount column, map the single amount field and confirm the sign convention in preview.
Possible duplicates and overlaps
Balansix evaluates transaction lines so an overlapping file does not have to be accepted or rejected only as a whole. Possible duplicates remain visible for review. Treat an amber duplicate warning as a check, not an instruction to delete automatically.
Large statements
High-volume imports are processed server-side. The grid may show a manageable page/window while search, filters and bulk actions still operate against the matching dataset. Avoid repeatedly clicking a posting action while a batch is already processing.
After import
Review the imported lines, coding/matching status and statement continuity. For Bank-Led clients, continue to bank analysis and posting. For Document-Led clients, use bank lines primarily to settle existing customer/supplier accounting before bank-only coding exceptions.