If your tracker is missing days rather than whole months, look at how you chose the date range when you downloaded. Exports built from a rolling window, such as 'last 30 days', leave gaps whenever the gap between two downloads is longer than the window. Fixed calendar ranges do not.
A gap you cannot see
Say you download a 'last 30 days' file on 2 June, and the next on 5 July. The first covers the 30 days ending 2 June. The second covers the 30 days ending 5 July, which starts on 5 June. That leaves 3 and 4 June in neither file.
If a €86.40 supermarket payment happened on 3 June and a €23.00 pharmacy payment on 4 June, both are absent. The two missing payments add up to 86.40 + 23.00 = €109.40. The importer has done nothing wrong; it loaded exactly what it was given.
How can I spot a gap between files?
- Open each file and read the earliest and latest dates, not just the file name.
- Put the ranges in a list: first file 4 May to 2 June, second file 5 June to 5 July.
- Look at the join: 2 June to 5 June is more than one day, so something is missing.
- If your bank's statement shows running balances, check the last balance of one file against the first of the next.
| File | Starts | Ends | Gap before next file |
|---|---|---|---|
| First export | 4 May | 2 June | 3 and 4 June are missing |
| Second export | 5 June | 5 July | None, if the next export starts on 6 July |
Which export range should I choose?
Use a fixed range with a start and end you choose, ideally whole calendar months or the statement periods your bank prints. Choose 1 June to 30 June, then 1 July to 31 July. The end date of one file is then always the day before the start of the next, and a gap is impossible unless you skip a month.
What about overlaps?
A small overlap is safer than a gap, but you must deal with it. If two files both contain 3 June, the same €86.40 purchase can be imported twice. Always review rows before you save them, and look for repeated amounts at the same merchant on the same day. Deleting the duplicate rows leaves your totals right.
A repair plan for the missing days
- Write down the first and last missing dates.
- Export a new file with a fixed range that begins on the first missing date and ends on the last.
- Check it contains only the days you lack. If it also holds days you already have, remove the overlap before importing.
- Import, then compare the balance on the final day to the balance on the bank's own statement.
- Note the range in your coverage list.
The same arithmetic applies to any export that uses a relative window. If your bank offers 'last 90 days', a download on 1 March and another on 20 June leave a gap, because the second starts 90 days before 20 June, not on 2 March. Calculate the start date of every relative export before you rely on it, and write it down.
Another trap is processing dates. A payment made late on the last day of a month can carry the next day's date in the file. If a transaction seems to belong to a different month than you remember, look at the booking date and the value date, and choose one date type for all your files.
A note on regional statement habits
Banks and card providers differ in how they label periods and in how far back exports reach, so read the dates printed on your own files instead of assuming. This article covers records and method only; for anything concerning rules or reporting in your country, ask a local adviser.
Useful ideas start with a clearer picture of your own spending.
Explore your reports


