Convert HDFC statements to TallyPrime.
Checked against the printed balances first.

1. 1Log in to HDFC Bank NetBanking. Go to Accounts, then Enquire, then Download Account Statement (labelled Account Statement on some profiles).
2. 2Choose the account, set a period (a preset like last 6 months or your own date range, up to 5 years back) and pick PDF as the format.
3. 3Click Download and save the file. This PDF is generated on the spot and is not password-protected.
4. 4For a statement in your inbox: Accounts, then Request, then Email Statement, and choose the period. That PDF arrives protected.
5. 5In the HDFC Bank app: Accounts, tap the account, then Statements (or Email Statement) and select the period.

Then drop the file above. Several months at once is fine; each statement comes back as its own .xml file.

Statements emailed by HDFC Bank are password-protected and the email spells out the format. For savings and current account e-statements it has long been the Customer ID, and the email subject usually shows the last digits of that ID as a hint. Drop the emailed file as it is: the upload box asks for the Customer ID and unlocks the PDF in your browser, and only the unlocked copy is sent. The NetBanking download comes unprotected if you would rather skip the prompt.

HDFC's NetBanking Excel is a plain dump of the statement columns and is not something TallyPrime can post as vouchers. Drop the PDF instead, entering the Customer ID if it is an emailed e-statement, and the Tally XML pairs each Receipt or Payment voucher with a bank ledger named after HDFC Bank and the account's last four digits.

NetBanking will hand you the same statement as Excel or a delimited text file, not just PDF, and for a quick tally that is often enough. The Excel is a straight dump of the statement columns with no formatting and dates as text, so it still needs cleaning before Zoho will take it, and it is not something Tally can post as vouchers. Where the PDF wins is when someone else sent it to you: a client's emailed e-statement, or a signed branch statement for a loan file, exists only as a protected PDF, and converting it gives you clean columns plus a Tally XML voucher file.

1. 1Drop the statement on the home page and make sure the balance check is green.
2. 2Click Tally XML. Money in becomes a Receipt voucher and money out becomes a Payment voucher. Each voucher has two ledger entries whose amounts add to zero.
3. 3The XML names the bank ledger after the bank and the last four account digits (HDFC Bank 4821, for example). Its other side is a ledger named Statement Import Clearing. Both must exist in the company before you import: create them, or rename your existing ledgers to match.
4. 4Set the company period to cover the statement dates (Alt+F2), then press Alt+O, choose Import, then Transactions, and select the downloaded file.
5. 5Review the import summary and any exceptions. Open Statement Import Clearing afterwards and reclassify each transaction to the correct expense, income, customer or supplier ledger while reconciling the bank account.

• Indian number format (1,23,456.78) is read correctly.
• Password-protected PDFs are unlocked in your browser: a prompt asks for the password HDFC printed in its email, and only the unlocked copy is uploaded.
• UPI narrations are long; they are kept whole so UPI IDs remain searchable.
• Tally matches ledgers by exact name. A voucher whose ledger does not exist is listed as an exception instead of being posted, so check the two names before importing. Through the API you can pass your own ledger names.
• Voucher dates must fall inside the company period, and amounts are imported as plain numbers in the company's base currency. Widen the period first, and treat a foreign-currency statement as a job for a multi-currency ledger.
• Turning guessed categories directly into accounting ledgers can post transactions to the wrong chart-of-accounts group. The export uses one clearing ledger instead, leaving classification under your control.
• Importing the same statement twice can duplicate vouchers if duplicate handling is disabled. The XML gives every row a stable remote ID and voucher number so Tally can identify the repeat during review.

None of this is bank-specific configuration. The balance check catches these cases for every bank; this list just explains what you will see on a HDFC file.