A CSV that opens as one long column, or shows strange characters where the rupee sign should be, is almost always a delimiter or encoding mismatch, not damaged data. Open it through Excel's text import rather than double-clicking, then set the file origin to UTF-8 and the delimiter to comma.
That small change fixes most garbled expense files, including payout reports a gig worker downloads from platforms.
What are the usual symptoms and causes?
| What you see | Likely cause | Fix |
|---|---|---|
| Everything in column A | Delimiter is not what Excel expects | Choose comma, semicolon or tab in the import step |
| ₹ shows as strange letters | File is UTF-8 but opened as another encoding | Set file origin to UTF-8 |
| Dates flipped, like 03-11 read as March | Regional date setting differs | Import the date column as text, then convert |
| Long numbers shown as 4.5E+11 | Excel treated an ID as a number | Import that column as text |
| Leading zeros missing | Same cause | Import as text |
How do you open the file correctly in Excel?
- Open a blank workbook; do not double-click the CSV.
- On the Data tab choose From Text/CSV, and pick your file.
- In the preview, set File Origin to 65001: Unicode (UTF-8).
- Set the delimiter to comma, or to semicolon or tab if the preview shows them.
- If a column looks wrong, use Transform Data and set that column's type to Text.
- Load the result and check a few totals.
Older Excel versions put the same steps under From Text in the Data tab, with a wizard. The idea is identical.
Why does the same file look fine in Google Sheets?
Google Sheets detects UTF-8 and the delimiter automatically in most cases, and its import dialog lets you set both. If Excel gives you trouble, importing into Sheets and downloading as an Excel file is a legitimate workaround, though you should still check the columns afterwards.
What can go wrong for gig workers in particular?
- Platform payout files may use semicolons or tabs depending on how they were generated.
- Reference or order numbers that are long digits get turned into scientific notation, and the original number is lost once saved.
- Merging several weekly files can mix date formats.
Do your own check once a file is open: add up the amount column and compare with the total shown on the platform or statement. If they match, the data survived.
What about files from your expense tracker?
SpendixAI offers CSV downloads from reports and an export centre with a standard all-transactions file plus accounting templates. If any file looks odd in Excel, the same import steps apply, and if it still does not look right the fault could be in the file, so tell support the exact steps and what you saw.
If the file is large, say tens of thousands of rows from months of payouts, Excel may open only part of it or run slowly. Splitting by month before importing is a practical answer. Keep the first row of headings in each piece so the columns line up when you stack them afterwards. Whatever you do, work on a copy so the original download stays exactly as it came.
Also check the decimal separator. A file that uses a comma for decimals and a semicolon between columns will turn 1,350.50 into nonsense if read the wrong way, so look at a few rows with known amounts before trusting the rest.
A quick fix checklist
- Import through Data, not by double-click.
- Set UTF-8.
- Choose the right delimiter.
- Set ID and phone-number columns to text.
- Compare one total with the source.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

