Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
An analyst needs to confirm that the balances printed on a bank statement are consistent with the entries shown.
For each row, previous balance plus credit minus debit must equal the printed balance; the first failing row marks where the problem starts.
The statement PDF, a calculator or spreadsheet, page-end and page-start balances, and a sample of rows inside each page.
A pass result, or the exact row where the balance breaks and the size of the difference, recorded in the credit file.
Every row’s balance on a bank statement must equal the previous balance plus the credit minus the debit. If one row breaks that rule, there is an edited figure, a missing transaction or a missing page. The break sits between the last row that adds up and the first row that does not.
Worked example: five rows
Here are five rows from a statement, starting from an opening balance of ₹1,10,000.
| Row | Narration | Debit | Credit | Printed balance |
|---|---|---|---|---|
| Opening | ₹1,10,000 | |||
| 1 | NEFT from customer | ₹25,000 | ₹1,35,000 | |
| 2 | UPI to supplier | ₹12,000 | ₹1,23,000 | |
| 3 | RTGS from distributor | ₹30,000 | ₹1,53,000 | |
| 4 | Electricity bill | ₹8,500 | ₹1,48,500 |
Now check each row:
- ₹1,10,000 + ₹25,000 = ₹1,35,000. Matches.
- ₹1,35,000 − ₹12,000 = ₹1,23,000. Matches.
- ₹1,23,000 + ₹30,000 = ₹1,53,000. Matches.
- ₹1,53,000 − ₹8,500 = ₹1,44,500. The statement prints ₹1,48,500.
The printed balance is ₹4,000 higher than it should be. Rows 1 to 3 are fine, so the problem is in row 4: either the debit amount or the printed balance has been changed, or an entry of ₹4,000 is missing. A quick total check confirms it: credits ₹55,000 less debits ₹20,500 is ₹34,500, and ₹1,10,000 + ₹34,500 = ₹1,44,500.
Why do genuine statements sometimes seem to fail the check?
Before you escalate, rule out these innocent causes:
- Same-day entry order. Banks may print several same-day entries in posting order. Follow the printed order, not the time you expect.
- Reversals. A failed transfer may be debited and then credited back. Both rows appear; the balance still adds up across them.
- Page breaks. A page may start with “balance brought forward”. Compare it with the last balance on the previous page.
- Value date versus posting date. Some statements show both. The running balance follows posting order, so the value date does not change the sum.
- Scans and OCR. If you copied numbers from a blurry scan, check you read them correctly.
If none of these explain the break, record the row and the difference and refer the file.
What is the fastest way to test twelve months?
A business account can have 150 or more entries a month, so twelve months may hold 1,800 rows. You do not need to check them all by hand.
- Page ends first. For each page, check that the last balance equals the first balance on the next page. A 40-page statement needs only 39 checks.
- Month ends next. Check that each month’s closing balance equals the next month’s opening balance.
- Sample inside pages. On each page, check 3 to 5 rows, including the largest credit and debit.
- Go row by row only where something breaks.
This catches most crude edits in under an hour. Careful edits that keep the arithmetic consistent need other checks, such as fonts, PDF properties and digit patterns.
What to read next
For the automated version of this check across thousands of rows, read balance chain verification. Detecting fabricated bank statements with digit-pattern analysis covers edits that keep the sums correct, and how to check if a bank statement is fake without software lists the other manual checks.
A bank statement analyzer runs the balance check on every row of every file. TransactIQ, a managed service on Terra Insight’s AWS Mumbai infrastructure, includes fraud and anomaly signals among its 40+ engineered credit signals, each rule-traceable for your credit team.