Bank statements

DBS statement to CSV: three routes, from download to a clean file

Turn a DBS statement into CSV by downloading the bank's own file, converting a PDF with a spreadsheet, or cleaning the columns. Includes a small worked example.

Editorial illustration for DBS statement to CSV: three routes, from download to a clean file

To turn a DBS statement into CSV, first check whether your bank's own download offers a spreadsheet or CSV option; that is the cleanest route. If you only have a PDF, a recent desktop Excel can read tables from it, and you then save the result as CSV. Whichever route you use, clean the columns before you rely on the numbers.

Banks change their download options, so look at what your own net-banking or app offers rather than relying on a description here. This article describes the general routes and the cleaning steps that apply to any statement.

Route 1: download a spreadsheet version

Look under statements or account history for a format choice. If CSV, Excel or XLS appears, take it. These files already have one transaction per row, which saves most of the work. Save the file with a name such as 2026-10-current-account.

Route 2: convert a PDF with Excel

  1. Open Excel on a computer. Recent Microsoft 365 versions have Data, Get Data, From File, From PDF. Older versions may not.
  2. Choose the PDF, open it with the correct password if it asks for one, and select the table that holds the transactions.
  3. Load it to a sheet and check that every page's rows came across.
  4. Remove header rows that repeat on each page.
  5. Save As, choose CSV UTF-8 so the rupee sign and any non-English text stay intact.

Google Sheets cannot read a PDF directly. If you have only Sheets, open the PDF in a viewer, copy the table and paste into a sheet, then expect to fix the columns by hand.

What should a clean CSV look like?

DateNarrationDebitCredit
02-10-2026UPI payment to grocery store1,240.000
03-10-2026Salary credit062,000.00
05-10-2026ATM cash withdrawal5,000.000
07-10-2026Electricity bill payment2,310.000

Check the sums. Debits are 1,240 + 5,000 + 2,310 = ₹8,550 and credits are ₹62,000, so the net movement for these four lines is +₹53,450. If your statement's own totals differ from the sum of your cleaned rows, a line was lost or doubled.

What goes wrong in conversion?

  • Dates read as text, or flipped from day-month to month-day. Check that 03-10 means 3 October.
  • Numbers stored as text with commas. Use Find and Replace to remove commas, then convert to numbers.
  • One transaction split over two lines because the narration wrapped. Merge those rows.
  • Debit and credit in one signed column versus two separate columns. Pick one layout and stick to it.
  • The running balance column included. Keep it for checking, but drop it before import elsewhere.

Do I need CSV at all for expense tracking?

Not always. SpendixAI accepts statements as PDF, CSV or Excel, so you can upload the bank's file as it is, choose the account, and review each row before saving. A converted CSV helps when you want to analyse the data in a sheet first. Do not assume every layout will parse perfectly, which is exactly why the review step exists.

How do I check a month against the bank's own figures?

Before you trust a cleaned file, rebuild the month in a spare cell. Say the opening balance is ₹21,300, total credits are ₹62,000 and total debits are ₹58,420. Then 21,300 + 62,000 - 58,420 = ₹24,880 should match the closing balance printed on the statement. If it is ₹24,380, you are ₹500 out, which is often one ATM line or one cheque that slipped during conversion. Sort by amount and look for a round figure like that.

Before you share the file

  • Remove account numbers or names from any file you send to a friend or an adviser
  • Keep one untouched original and work on a copy
  • Name files by month and account
  • Delete spare copies from shared downloads folders
SPENDIXAI JOURNAL

Useful ideas start with a clearer picture of your own spending.

Explore your reports