Imported dates land in the wrong month for three common reasons: day and month were swapped when the file was read, the file uses a value date instead of the posting date, or the statement includes carry-over rows from the previous month. The first and last rows of the preview usually show which one it is.
Day and month swapped
Indian statements write dates as day, month, year, so 03/04/2026 means 3 April. Software built around the other order can read the same text as 4 March. The trick is that swaps only show up when the day is 12 or lower. A date like 27/04 cannot be read as month 27, so it stays right, while 03/04 flips.
That makes a half-wrong file: some dates are correct, others have jumped months. If your April spending suddenly looks thin and your March looks heavy, suspect this.
| Text in the file | Read correctly as | Read wrongly as |
|---|---|---|
| 03/04/2026 | 3 April 2026 | 4 March 2026 |
| 12/01/2026 | 12 January 2026 | 1 December 2026 |
| 27/04/2026 | 27 April 2026 | Cannot be misread |
Value date versus posting date
Some statements show two dates: the day a transaction was recorded and the day it took effect. A payment made late on 31 March might show a value date of 1 April. If the importer takes the wrong column, a few transactions slide across the month boundary. Check which column your statement is using, and compare against a purchase you remember well, such as an online order.
Carry-over rows from the previous month
A statement for 1 to 31 May can still begin with a row dated 30 April, such as a brought-forward balance or a late-posted item. If you also imported April, that row may be a copy of something already saved. It can also show up as a stray transaction in the wrong month.
What should I look for in the preview?
- Read the first row's date: is it inside the statement period?
- Read the last row's date: is it the final date of the period?
- Find a transaction you know, like rent or a salary credit, and confirm its date.
- Check any dates with a day of 12 or less, since those are the ones that can flip.
- Scroll for a date that jumps backwards or forwards out of order.
How do I fix it?
If the whole file has swapped dates, do not edit rows one by one. Discard that import and retry with another format of the same statement, since a CSV or Excel file may carry the date as a proper date value. If just a few rows are wrong, correct their dates in the review step before saving, or edit the transactions afterwards.
What about a quick monthly check?
Compare your tracker's total for a month with the statement's own figures for the same period. If a month is short by exactly the sum of a few transactions, those are the ones that landed elsewhere. In SpendixAI you can review rows before saving, so the first and last row check is the moment to catch it.
Does the financial year make it worse?
In India the financial year runs April to March, so a date shifted across 31 March and 1 April lands in a different year of records, not merely a different month. A payment slipping from 31 March to 1 April moves between two financial years, which matters if you tally things by year for your CA or for your own review. Pay special attention to late March and early April when you check the preview, and compare those few rows against the statement itself. Rules about how dates are treated for tax are not something to guess at, so confirm any such question with your CA.
When you export from a spreadsheet, avoid retyping dates yourself. Retyping 03/04 on a computer set to a different date order is how a correct file becomes a wrong one.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

