To verify a PDF to Excel conversion, check that opening balance plus total credits minus total debits equals the closing balance printed on the statement. If the two differ, compare running balances row by row to find the missing or duplicated transaction.
The three-line proof
Every bank account obeys one equation: the closing balance is the opening balance, plus everything that came in, minus everything that went out. Your converted sheet either satisfies it or it does not. Say a hypothetical statement shows an opening balance of ₹42,500.00 and a closing balance of ₹59,350.00.
| Item | From the statement | From your sheet |
|---|---|---|
| Opening balance | 42,500.00 | typed in once |
| Total credits | 78,200.00 | =SUM($D$3:$D$500) |
| Total debits | 61,350.00 | =SUM($C$3:$C$500) |
| Expected closing | 59,350.00 | opening plus credits minus debits, using the cells above |
The arithmetic: 42,500 plus 78,200 is 1,20,700, and minus 61,350 gives 59,350. If your sheet's totals reproduce 59,350.00, the conversion has not lost or invented value. If it gives some other number, the difference is a clue in itself.
What does the difference tell me?
Say the sheet works out to ₹64,350.00 against a printed ₹59,350.00. The sheet is ₹5,000.00 too high, and that gap points to one of two stories:
- A debit of ₹5,000.00 went missing, so the outflow is understated.
- A credit of ₹5,000.00 was read twice, so the inflow is overstated.
A gap that is a round, recognisable amount usually means one row. A messy gap such as ₹4,873.50 can mean several rows, or an amount that was misread, such as 1,250.00 read as 12,50.00.
How do I find the exact row?
Use the running balance column printed on the statement. Put the opening balance in E2 as a plain number, start transactions on row 3, with Debit in C, Credit in D and Balance in E, and add this in F3, filled down:
- =ROUND(E2-N(C3)+N(D3)-E3,2)
For a healthy row this returns 0: the previous balance, less the debit, plus the credit, should be the balance on this row. Filter column F for anything other than 0. The first non-zero row sits just after the point where something went wrong. The size of that number is the size of the gap, so look at the rows just above the first flagged row for a missing or doubled entry of that amount.
Which errors does the test miss?
A row where a debit and credit were swapped but the printed balance was read correctly will show up, because the balance will not follow. A row where two amounts moved in opposite directions by the same value in the same row will not. Finish by checking the row count: if the statement has a transaction count, compare it with =COUNT($E$3:$E$500); if it does not, count the printed lines on one or two pages and compare page by page.
On a long statement, run the proof page by page. The closing balance printed on page 1 must equal the balance at the top of page 2, so if page 3 fails the test while pages 1 and 2 pass, the problem sits on page 3. That saves you from hunting across two hundred rows.
Fixing and recording the repair
- Fix the missing or duplicated row from the PDF itself, not from memory.
- Rerun the F column until every value is 0 and the totals agree with the statement.
- Note in a cell at the top that the sheet was reconciled, with the statement period.
If you would rather not do this by hand each month, SpendixAI shows the parsed rows for review before saving, so you can still compare against the statement totals. It cannot promise that every layout comes through perfectly, so the closing-balance check is worth keeping as a habit.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

