Preparing bank statement data for Sage import

Confirm the exact Sage product and import route

“Sage import” is not one universal format. The product, version, country configuration and chosen bank or cashbook workflow affect the required columns. Obtain a current template or test export from the target environment before mapping statement data.

Agree the field mapping

Typical decisions include transaction date format, debit and credit representation, account or bank code, reference length, tax treatment and description limits. Decide whether the running balance is imported, retained only for validation, or omitted from the target file.

Normalise without erasing evidence

Dates and amounts should be consistent, but the original description should remain available during review. If rules shorten descriptions or assign references, keep those transformations explicit so an accountant can understand how the import row was produced.

Use a controlled test batch

1. Convert and review a short representative period.
2. Check opening and closing balances against the statement.
3. Import into a safe test or reversible workflow.
4. Confirm signs, dates, references and duplicate handling.
5. Only then repeat the process for the full period.

Keep responsibilities clear

Extraction software prepares data; it does not make accounting judgements. An authorised user should approve mappings, resolve warnings and confirm the import result. This separation matters when bank descriptions are ambiguous or transactions need ledger allocation.