Export one month first, open it, compare its totals and categories with your reports, and let your CA try importing it before you send the full year. If the single month goes in cleanly, the rest almost certainly will; if it does not, you have found the problem while it is still small and cheap to fix.
Why one month and not the full year?
A year of data hides mistakes. If a category name is wrong, it is wrong in hundreds of rows. If the file contains duplicates, they are scattered through twelve months and nobody can find them. A single month has a few dozen rows, and you can inspect it by eye in ten minutes.
It is also kinder to your CA. Asking them to import a small sample into a test copy of the books costs them very little. Asking them to undo a full-year import that went wrong costs them a lot.
What are the five things to look at?
- Row count. The number of rows in the file should match the number of transactions you expect for that month in the tracker, accounting for deleted ones.
- Total. Add up the amount column, or filter by account, and compare with the tracker's report and your bank statement.
- Dates. Check the first and last date, and confirm a date from the second half of the month reads the right way round.
- Categories. Scan the category column for blanks, duplicates and names you do not recognise.
- Accounts and currency. Every row should carry an account, and every amount should have its currency, especially if you hold foreign-currency entries.
How do I compare totals properly?
Say you exported a month and the file shows 84 rows. Your tracker's report for the same month and accounts shows 85 transactions. One row is missing. Sort by date and compare with the report until you find it. It may be a transaction dated at midnight on the last day of the month, or one saved to a different account than you assumed. In SpendixAI the Report builder can filter and group, which is handy for building the same slice to compare with the export.
| Check | Tracker says | File says | Verdict |
|---|---|---|---|
| Rows | 85 | 84 | Find the missing one |
| Total spend | ₹71,300 | ₹71,300 | Matches |
| Bank account total | ₹48,900 | ₹46,400 | ₹2,500 gap, trace it |
| First date | 1 July | 1 July | Matches |
The figures above are made up, but the habit is real: write down both numbers side by side. A mismatch you can name is easy to fix.
Can my CA test the import for me?
Yes, and you should ask. Send the one-month file and ask them to import it into a trial copy, or to tell you what would stop it importing. They know their own software's quirks. Ask for specific feedback: which columns looked wrong, which names did not match, and whether anything should be renamed in the tracker.
When is the test enough?
When the month imports without surprises, totals agree, and your CA has said the layout is fine, go ahead with the remaining months. Do them in a batch if your CA prefers, or a quarter at a time if you want another small check in between. For the same reason, repeat the one-month test any time something changes: a new account, a renamed category, or a different accounting software.
Choose the test month carefully. A quiet month with only rupee spending proves less than one that includes a refund, a foreign-currency entry and a cash payment. If your records contain unusual entries, pick a month with at least one of each, so the trial exercises the awkward cases too.
Short version
- One complete, reviewed month. No half-finished rows.
- Count, total, dates, categories, accounts.
- A message to your CA that says what you tested.
- A written note of what you changed, so the full export repeats the fixes.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

