Convert a Bank of Baroda Statement PDF to Excel
Bank of Baroda statement layouts, the continuation-line behaviour that inflates row counts, and how to confirm your export is complete.
Bank of Baroda statements convert well once continuation lines are handled. That single behaviour accounts for most of the bad output people see from generic tools.
Why your row count comes out too high
Bank of Baroda narrations are long, and they wrap. A single NEFT transfer can occupy three visual lines on the page: the transfer details on the first, the beneficiary on the second, the remitting bank on the third. Only the first line carries a date and an amount.
A converter that treats every visual line as a transaction turns a 150-row statement into 380 rows, most of them fragments with empty date, debit, credit and balance columns. The file looks superficially complete and is unusable.
The rule that fixes it is simple: a line with no date is a continuation of the row above it, and should be appended to that row's description rather than emitted separately.
Verifying the result
- Count the transactions Compare against the count printed on the statement, where Bank of Baroda provides one.
- Sum the debits and credits Each should match the corresponding printed total.
- Walk the balance chain Opening balance, minus debits, plus credits, row by row, should land on the printed closing balance.
The chain and the totals catch different failures. The chain proves the amounts were read correctly; the totals prove no rows were lost. A file can pass one and fail the other.
What the export contains
| In the file | What you get |
|---|---|
| Bank of Baroda's own columns | Every heading as printed, in the same order: DATE, PARTICULERS, CHQ NO., WITHDRAWALS, DEPOSITS, BALANCE in the statement we checked |
| Dates | Exactly as printed, DD-MM-YY, with nothing reformatted |
| Narration | The full text, with the second and third lines of a wrapped NEFT narration joined back into one cell |
| Amounts | Each in the column Bank of Baroda printed it in, commas and all |
| A Completeness sheet | Every row checked against the printed running balance, and the statement's own totals where it prints them |
Joining the wrapped lines is the one thing the reader does to the text, and it is what keeps a 150-row statement at 150 rows. Nothing is renamed, reordered or rounded — not even a heading: the statement we checked spells its narration column PARTICULERS, and so does the spreadsheet.
An example in Bank of Baroda's layout
A made-up example. Every row below is invented — SAMPLE names, round amounts — and set out the way the Bank of Baroda statement we checked sets out its table: the same six headings, spelling included, in the same order, with dates as DD-MM-YY. The second transaction's narration wraps onto two more lines.
| DATE | PARTICULERS | CHQ NO. | WITHDRAWALS | DEPOSITS | BALANCE |
|---|---|---|---|---|---|
| 01-04-25 | NEFT-SAMPLE EMPLOYER LTD-SALARY | 40,000.00 | 45,000.00 | ||
| 02-04-25 | NEFT-000000000001-SAMPLE | 8,000.00 | 37,000.00 | ||
| SUPPLIER CO | |||||
| SAMPLE BANK | |||||
| 04-04-25 | CHQ PAID-SAMPLE LANDLORD | 000001 | 15,000.00 | 22,000.00 |
What the Excel or CSV gives back. The same six headings in the same order, every figure exactly as printed, and both wrapped lines joined back into their narration — three transactions, three rows, not five.
| DATE | PARTICULERS | CHQ NO. | WITHDRAWALS | DEPOSITS | BALANCE |
|---|---|---|---|---|---|
| 01-04-25 | NEFT-SAMPLE EMPLOYER LTD-SALARY | 40,000.00 | 45,000.00 | ||
| 02-04-25 | NEFT-000000000001-SAMPLE SUPPLIER CO SAMPLE BANK | 8,000.00 | 37,000.00 | ||
| 04-04-25 | CHQ PAID-SAMPLE LANDLORD | 000001 | 15,000.00 | 22,000.00 |
NEFT and RTGS narrations
Bank of Baroda NEFT rows carry the remitting bank, the beneficiary and a UTR — the unique transaction reference that identifies the transfer across the banking system.
The UTR is the field to keep. If a payment is ever disputed or needs tracing, it is the identifier the bank will ask for, and it is far easier to find in a spreadsheet column than by reading through a stack of PDFs.
Frequently asked questions
Does this handle the eBOB app export?
Yes. The app and internet banking produce the same PDF layout.
What is a UTR and should I keep it?
Unique Transaction Reference — the identifier for an electronic transfer. Keep it: it is what a bank asks for when tracing or disputing a payment.
Why does my export have blank rows?
Those are continuation lines being emitted as separate transactions instead of being merged into the row above.
Related posts
- Convert a UCO Bank Statement to Excel or CSV
- Convert a Yes Bank Statement to Excel
- Convert a Bank of India Statement to Excel
Convert a statement now
Bank Statement PDF to Excel, or see every format. More in the guides.