If you have ever tried to copy-paste an HDFC Bank statement into Excel, you already know the problem: the moment you select a few transactions, the NEFT and UPI reference lines get split off into their own rows, the amounts lose their thousands separators, and the dates collapse into text strings Excel refuses to sort. This guide walks through exactly how to convert an HDFC statement PDF into a clean Excel file in under a minute, and what to check after the conversion to make sure no transactions were dropped.
What HDFC statement layouts are supported
HDFC issues e-statements in a single underlying tabular layout with the columns Date | Narration | Chq./Ref. No. | Value Dt | Withdrawal Amt. | Deposit Amt. | Closing Balance. The same template is used for:
- HDFC Savings Account statements (resident, NRE, NRO)
- HDFC Current Account statements
- HDFC Salary Account statements (Regular, Premium, Imperia)
- HDFC NRO and NRE account statements (with the IBAN block in the header)
All of these are auto-detected by uploading the PDF directly to bankstatementconvtr.com — you do not need to tell the tool which type of account it is.
Step 1: Download your statement from HDFC NetBanking
Log into HDFC NetBanking, go to Accounts → Request → Email Statement (or use the Download Statement option under your account dashboard). Pick the date range you need and select PDF as the output format. HDFC will email you a password-protected PDF; the password is documented in the email itself (typically your customer ID followed by your date of birth in DDMM format).
If you only have a password-protected PDF and cannot remove the password, open it in your browser’s PDF viewer or Adobe Acrobat, enter the password, and then use File → Print → Save as PDF to produce an unprotected copy. The converter does not accept password-protected uploads (this is a security choice, not a limitation — it means we never see your password).
Step 2: Upload to the converter
Drop the PDF onto the upload zone on the home page. Auto-detection will identify it as an HDFC statement and route it to the HDFC parser. You do not need to pick the bank manually.
If you want CSV instead of Excel (for example, because your accountant uses QuickBooks or Xero), tick the Download as CSV instead of Excel checkbox before uploading. If you want a TallyPrime-ready voucher workbook, tick the Also include Tally template checkbox — this is documented further in our Tally import workflow guide.
Step 3: Verify the conversion
Once the Excel file downloads, open it and do a quick sanity check before importing the data anywhere downstream:
- Compare the row count against the number of transactions you can see in the original PDF (a rough scroll-through is enough).
- Sum the Withdrawal Amt and Deposit Amt columns using
=SUM()and compare to the totals printed at the top of the statement (HDFC labels these “Total Withdrawals” / “Total Deposits” on the summary block, when present). - Check the last row’s Closing Balance equals the closing balance printed on the statement.
HDFC layouts vary across NetBanking releases and salary-account templates, so the converter does not run automatic reconciliation against the printed summary block for HDFC (the printed totals are sometimes off by small amounts for documented reasons like inward-NEFT charge netting). The three checks above take 30 seconds and are reliable.
If the row count or the totals look wrong, the most common causes are:
- Statements that span more than one PDF. HDFC NetBanking caps each PDF at a fixed number of pages. If your statement is split across two or three PDFs, use the Merge Statements tab and upload all of them together rather than converting individually.
- Salary credit reversals on the boundary date. When a salary credit gets reversed and re-credited the same day, both legs appear in the parsed data — which is what you want for accounting, but it can look like a duplicate at first glance.
- Image-only PDFs. If your statement is a scanned image rather than a digital NetBanking download, the converter will return zero rows. Re-download the e-statement from NetBanking to get a digital copy.
How multi-line NEFT and UPI narration is handled
An HDFC NEFT or RTGS line typically wraps across three or four rows in the PDF: the sender bank reference, the counterparty name, the IFSC code, and the customer remark. The parser stitches these continuation lines back onto the originating transaction row, so in Excel you get one row per transaction with the full reference text in the Narration column. The same applies to UPI lines (which wrap the VPA, the IFSC and the UPI reference number) and IMPS lines.
If you would prefer the wrap lines to stay on separate rows (rare, but useful for some forensic accounting workflows), pick the raw text output: save the statement as a .txt file from any PDF viewer first, then upload that. The .txt path skips wrap-line merging.
What the Excel output looks like
The Excel file has one sheet called Transactions with the columns: Date, Narration, Chq/Ref No, Value Dt, Withdrawal Amt, Deposit Amt, Closing Balance. Numbers are stored as numbers (not text), so you can sum, sort and pivot immediately. Dates are stored in DD/MM/YYYY string format so you can re-parse them for whatever locale your downstream tool uses without losing the original day-month order.
If you uploaded multiple HDFC statements together via the Merge mode, you get an additional All Transactions sheet at the front of the workbook with the rows from every statement combined and sorted by date, plus a Source File and Bank Format column so you can filter by which statement each row came from.
What if auto-detection fails?
If the converter does not recognise your PDF as HDFC (for example, because you have an old or unusual layout we have not seen yet), expand the Wrong format detected? Pick your bank manually section under the upload zone and select HDFC Bank from the dropdown. This forces the HDFC parser to run regardless of detection.
If that still produces zero rows, the most likely cause is that your statement is a scanned image of a printed PDF rather than a digitally-generated one. Image-only PDFs need OCR before they can be parsed, which the converter does not run. The fix is to ask HDFC for a fresh e-statement download from NetBanking, which is always digital.
Privacy and what happens to your file
The PDF is processed in memory during the conversion request. A usage log row is written with the bank format, page count, transaction count and file size for rate-limiting and analytics — not the transaction data itself. Full details, including what (if anything) is retained for diagnostic purposes, are on the privacy page; please read it before uploading sensitive statements.