PNB Statement to CSV: Stitching a Year Together
You need Punjab National Bank transactions in a spreadsheet, and you need the whole period, not most of it. Maybe it's a home loan application that wants twelve months, an ITR filing, or an accountant who has asked for the year in one file. What you have instead is a folder of monthly PDFs, each one encrypted, plus whatever you managed to pull from Net Banking in short bursts.
That fragmentation is the defining feature of a PNB conversion job. Everything else — reading the columns, keeping debits and credits apart — is normal work. The hard part is assembling the pieces without losing a row at a seam or counting one twice.
Quick answer
There are two routes:
- PNB's own download. From Net Banking or the PNB ONE app you can pull a statement for a date range and save it. Best when you have login access and the period you want is short enough to come out in one go.
- Convert the PDFs. For emailed monthly e-statements, older history, closed accounts, or a statement someone forwarded you, the PDF is what exists. Upload each one to BankStatementKit and get CSV back, balance-checked against the statement's own printed totals.
Rule of thumb: use the bank's file for recent, short ranges; convert PDFs for anything long or historical — which for PNB is most real requests.
Convert a PNB PDF to a verified CSV
Option 1: PNB's built-in statement download
If you can log in, try this first.
- Log in to PNB Internet Banking, or open PNB ONE and authenticate.
- Go to the accounts area and open the account statement option.
- Select the account and a date range.
- Download the statement in the format offered for that period, and open it in Excel or Google Sheets.
Separately, you can register for PNB's e-statement service — through Internet Banking, your branch, the contact centre, or SMS — after which PNB emails you a monthly statement. Registering discontinues the physical statement, though branches can still issue duplicates.
Where the built-in download stops
- Possibly short slices. PNB does not publish a per-download date limit, and third-party guides claiming one are unreliable, but a twelve-month requirement commonly arrives as several files rather than one. Check what your own date picker allows.
- History limits. Beyond the online window you're back to branch requests or whatever e-statement emails you've kept.
- Login access required. Closed accounts, dormant accounts and client-supplied statements leave nothing to log into.
- Amalgamation-era records. Statements spanning the 2020 merger of Oriental Bank of Commerce and United Bank of India into PNB can carry the older identifiers, and pre-merger history is not always in one place.
- The e-statement itself is a PDF. Registering for email statements gives you convenience, not a spreadsheet.
Nearly every one of those ends in the same artefact: a PDF.
Option 2: Convert the PNB PDF statement to CSV
- Gather every PDF covering your period — monthly e-statements, downloaded slices, or both.
- Upload the first one and supply its password if prompted. It's decrypted in memory and never written to disk.
- Transactions are read into seven standard columns: Date, Narration, Reference, Value Date, Debit, Credit, Balance.
- Check the verification label, download the CSV, and repeat for each remaining file — then concatenate in date order.
Start converting PNB statements
About the password
PNB emails statements as encrypted PDFs. The rule differs by product, and the email that delivered the file states the one that applies to your document — that is the source worth trusting.
Why PNB PDFs trip up generic converters
The seam problem. This is the one that actually costs people money. When a year arrives as four three-month files, the boundaries are where errors hide: the last row of one file and the first row of the next can overlap, or a transaction on the boundary date can appear in both. Naive concatenation double-counts it; naive de-duplication deletes a legitimate repeated payment. The only reliable fix is to reconcile each file independently first, then check that each file's closing balance equals the next file's opening balance.
Split debit and credit columns. Like most Indian bank statements, a PNB statement keeps withdrawals and deposits apart rather than using one signed amount. Collapsing them without tracking which column a figure came from flips the sign on every debit, and the file looks fine until something downstream refuses to balance.
Legacy and merged-entity formats. Statements from different periods and different originating branches are not always laid out identically, so a converter tuned to one specimen can misread another. That is an argument for reading the page as a table and then verifying the result, rather than pattern-matching a fixed template.
Prove the CSV matches the statement
With multi-file periods, verification is not optional — it's the only thing standing between you and a quietly wrong year.
- The running balance chain, per file. Each row prints a balance. Previous balance minus debit plus credit must equal the printed balance, every row. A dropped or duplicated transaction breaks the chain exactly where it happened.
- The printed totals, per file. Opening balance plus total credits minus total debits must equal the closing balance shown on the statement.
- The seam check, across files. File one's closing balance must equal file two's opening balance. If it doesn't, something fell between the two downloads.
BankStatementKit runs the first two automatically on every conversion and labels the output VERIFIED, DISCREPANCY or FAILED. The third is a one-minute manual check once you have the CSVs in front of you, and it is well worth doing.
FAQ
PNB only gives me a few months per download. How do I get a full year?
Download each slice, convert each PDF separately, then concatenate the CSVs in date order. Check that each file's closing balance matches the next file's opening balance before you merge, and remove genuinely duplicated boundary rows. Converting file by file means a problem is localised to one slice rather than hidden in the annual total.
Can I convert my monthly PNB e-statement emails instead?
Yes, and for older periods that's often the only option. Each monthly PDF converts on its own and produces its own CSV. You'll need the password for each — they're encrypted — and the same seam check applies when you join twelve months together.
What's the password on my PNB statement PDF?
It varies by product, and PNB states the applicable format in the email that delivered the statement. Check there rather than relying on a third-party list, and have the password to hand at upload since the file can't be opened without it.
Will the CSV import into Tally, Zoho Books or QuickBooks?
The output is standard CSV with Date, Narration, Reference, Value Date, Debit, Credit and Balance columns. All three accept a CSV bank import with a column-mapping step. There's no direct Tally XML or QBO export.
Is uploading a bank statement safe?
The PDF is processed in memory and never stored. Conversion history is kept 30 days and you can delete it whenever you like. Uploads are limited to 20MB or 50 pages, and scanned statements fall back to OCR automatically. Questions? Contact us.
The bottom line
PNB conversions are less about any one clever bit of parsing and more about assembling a period correctly. Take the bank's download when the range is short and you can log in; convert the PDFs for everything else — and verify each file before you join them, because a year stitched from unverified slices is a year you cannot defend. Layout details are on the PNB statement converter page.
Build a PNB year you can stand behind
Every conversion is balance-checked against the statement's own printed totals, and your first one is free with no account required.
Convert a PNB statement