Kotak Statement to CSV: A Practical Guide

Somebody has asked you for Kotak Mahindra Bank transactions in a spreadsheet. It might be your accountant closing the books, a lender assembling a loan file, or you at eleven at night trying to reconstruct a year of UPI spending before filing returns. What you have is a PDF, possibly password-protected, possibly six hundred rows long.

Kotak is unusual among Indian banks in how mobile-first its customer base is. A Kotak 811 account is often somebody's default UPI wallet, which means statements are long, repetitive, and unforgiving of a converter that guesses. This guide covers both routes to CSV, the Kotak-specific things that go wrong, and how to prove the result is right.

Quick answer

Two paths:

1. Kotak's own statement download. Logged into Net Banking or the Kotak mobile app, you can pull a statement for a date range and save it. This is the better option when you have login access and the period you need is still offered online.
2. Convert the PDF. For emailed e-statements, older periods, closed accounts, or a statement a client forwarded you, the PDF is the only artefact that exists. Upload it to BankStatementKit and the transactions come out as CSV, balance-checked against the statement's own printed totals.

Rule of thumb: if you can log in and the date range is available, take the bank's file. Everything else goes through the PDF.

Turn a Kotak PDF into a verified CSV

Option 1: Kotak's built-in statement download

Try the native route first — data straight from the bank needs no extraction at all.

1. Log in to Kotak Net Banking, or open the Kotak mobile app and sign in with your CRN and MPIN.
2. Go to the account you want and open its statement or transaction history section.
3. Set the period you need — a preset range or custom from/to dates.
4. Download the statement, choosing a spreadsheet-friendly format if one is offered for that period.

Where the built-in download stops

The native download is genuinely the fastest route, right up until it isn't:

• History windows. Online statement history reaches back only so far, and the periods people need for loan files and tax assessments are usually the older ones.
• You need working login access. A closed account, an account you've stopped operating, or a PDF a client emailed you leaves no login to use.
• Emailed statements arrive as PDFs. If you're registered for e-statements, what lands in your inbox each month is an encrypted PDF, not a spreadsheet.
• Consolidated statements bundle accounts. A single statement covering several relationships needs splitting before it's useful per-account.
• Downloads often need cleanup. Header rows, merged cells and text-formatted amounts routinely have to be fixed before another tool will import the file.

All five roads end at the same place: a PDF.

Option 2: Convert the Kotak PDF statement to CSV

1. Locate the statement PDF — from Kotak's monthly email, or downloaded from Net Banking.
2. Upload it. If it's encrypted, supply the password when prompted; the file is decrypted in memory and never written to disk.
3. Transactions are read into seven standard columns: Date, Narration, Reference, Value Date, Debit, Credit, Balance.
4. Read the verification label, then download the CSV.

Convert a Kotak statement now

About the password

Kotak's emailed statements are encrypted, and the rule is not the same for an account statement as for a credit card statement. The email that carried the PDF states which format applies to your document — that is the authority worth trusting, over any blog post including this one.

Why Kotak PDFs trip up generic converters

Sheer repetition. A month of an 811 account can be several hundred UPI rows whose descriptions differ only in a reference string. Converters that deduplicate on "looks like the previous row" quietly delete real transactions, and because the rows are near-identical, nobody notices by reading. This is a volume problem that only a balance check catches.

Debit and credit are separate columns. Kotak prints withdrawals and deposits as a Dr/Cr pair rather than one signed number. Collapse the two carelessly and every debit in the file flips sign — an error invisible on screen and fatal downstream.

Long references that wrap. UPI and IMPS entries carry long identifier strings. Where those spill past the column width onto a second physical line, a line-by-line reader invents a phantom transaction with no amount attached. Continuation lines have to be folded back into the row they belong to, which means reading the page as a table rather than as text.

Prove the CSV matches the statement

This is the step most people skip and the only one that turns a guess into a fact. A Kotak statement gives you two independent checks:

1. The running balance chain. Each row prints a balance. For every row, previous balance minus debit plus credit must equal the printed balance. One dropped or duplicated transaction breaks the chain at precisely the row where it went wrong.
2. The printed totals. The statement's opening and closing figures have to agree with your extracted rows: opening plus total credits minus total debits equals closing.

Doing this by hand on a six-hundred-row 811 statement is not a ten-minute job. BankStatementKit runs both checks on every conversion and labels the output VERIFIED, DISCREPANCY or FAILED, with a discrepancy pointing at the row where reconciliation stops.

FAQ

The bottom line

If you can log in and your period is available, take Kotak's own download. For emailed e-statements, older periods, closed accounts and client-supplied files, convert the PDF — and insist on a conversion you can verify, because on a long 811 statement a single silently dropped UPI row looks exactly like a statement that converted perfectly. More on the layout on the Kotak statement converter page.