Short answer
Compare the displayed date with the actual source file. If the source date is correct and the correct date column was mapped, Balansix should display that same date.
What to check
- Open the original CSV or Excel statement.
- Confirm the imported row contains the expected date before mapping.
- Check that the correct date column and date format were selected.
- Re-import a small test only if the mapping was wrong.
- If a correctly mapped source date still displays differently, report the example to support.
Important
Do not change a correct bank statement date simply to compensate for a display difference. The source statement should remain the accounting evidence.
Useful support information
Include the source date, displayed date, bank import screen and a screenshot or sample row without unnecessary confidential information.
Common causes
Most date differences come from the file rather than the software. UK banks usually export dates as day/month/year. If a file is read as month/year order, 03/04 becomes 4 March instead of 3 April, and days after the 12th may fail or shift.
Some exports also include more than one date, such as a transaction date and a posting or value date. Mapping the wrong column moves items near a month end into the wrong period, which can affect reconciliations and VAT returns.
Frequently asked questions
Which date should I map?
Use the date that appears on the bank statement the client would give you, usually the transaction or posting date shown on the statement itself.
Should I edit the CSV file before importing?
Only to remove obvious non-transaction rows such as headers or balances. Do not change the transaction dates.
How do I check a re-import is safe?
Import a small sample first and compare a few lines, including dates after the 12th of the month, with the original statement.