Convert a Bank of Maharashtra Statement to Excel
Bank of Maharashtra statement structure, the summary rows that inflate totals, and a practical verification routine.
Bank of Maharashtra statements follow the standard PSU pattern, and the standard PSU problem: the summary block is printed in the same visual style as the transaction table.
Why summary rows are so damaging
It is worth being precise about what goes wrong, because it is not obvious. Suppose a statement has ₹4,50,000 of debits, and the summary block printing that figure gets absorbed as a transaction.
Your debit total is now ₹9,00,000 — exactly double. And because the summary row also carries no balance, the balance chain has a hole in it. Both of your verification checks now fail, on a file where every actual transaction was extracted perfectly.
So the damage is not just a wrong number. It is a false alarm that makes a correct extraction look broken, which erodes trust in the check that would otherwise catch a real problem.
What a correct export looks like
| Statement element | Where it lands |
|---|---|
| Transaction rows | The Statement sheet, exactly as printed |
| Account number, holder, branch, IFSC | Left on the PDF — they are not transactions |
| Opening and closing balance | Checked against the rows on the Completeness sheet |
| Total debits and credits | Checked against the rows on the Completeness sheet, where printed |
| Page headers and footers | The header once at the top; footers left out |
The summary figures are used as checks, not as rows, and nothing that is not a transaction ends up in the transaction list. The account details stay on the PDF, which you keep beside the export.
Verifying
- Check for rows with an amount but no date The definitive sign of summary lines in the transaction list.
- Compare your debit total against the printed figure An exact doubling points straight at the summary block.
- Walk the chain Summary rows carry no balance, so they leave a visible hole in it.
- Confirm the dates fall inside the period Catching a DD/MM misreading.
Why a false alarm is costly
It is worth being explicit about the second-order damage from summary rows. They do not just produce a wrong total — they make a correct extraction fail its verification.
A check that cries wolf gets ignored, and once it is ignored it will not catch the real problem when one occurs. Filtering summary rows properly is as much about keeping verification trustworthy as about getting the totals right.
Frequently asked questions
Why did my totals come out exactly double?
The classic sign of the summary block being imported as transactions. The printed total is being counted alongside the rows it summarises.
Why does a false alarm matter if the data is fine?
Because a check that fails on correct files gets ignored, and an ignored check will not catch a genuine problem later.
Does this work with Mahabank mobile app statements?
Yes — the same layout as internet banking.
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.