← All articles
BasicsAugust 13, 2026·7 min read

Reading a Bank Statement: Debits, Credits, and Running Balance Explained

A plain-English guide to every part of a bank statement — the header, the transaction table, debits and credits, the running balance, and the summary figures.

A wallet with cash and a signed document, representing financial transactions.
Photo by Jakub Zerdzicki on Pexels

A bank statement looks simple until you have to reconcile one, and then the small ambiguities matter: which column is money in, what "value date" means, why the balance jumps around, and whether that "B/F" line is a transaction. This is a plain-English tour of a statement, part by part, so that every figure on the page means something specific to you.

The header: what account, whose, and when

The top of a statement identifies the account and the period. You will typically find:

  • Bank and branch details, and sometimes a SWIFT or routing code.
  • Account holder name and a masked account number — usually only the last few digits, for security.
  • Account type — savings, current, checking, credit card.
  • Statement period — the start and end dates the statement covers.
  • Currency — critical, and easy to overlook on a multi-currency relationship.

None of this is a transaction, but all of it is context. The period bounds what should be in the table; the currency governs how to read every amount below.

Opening and closing balance

Two figures frame the whole statement:

  • Opening balance — what was in the account at the start of the period. It should equal the previous statement's closing balance.
  • Closing balance — what was in the account at the end.

These often appear as their own lines in the transaction area, sometimes labelled balance brought forward (B/F) and balance carried forward (C/F). Here is the crucial point: these are not transactions. They are markers of the account's state at a moment in time. When you extract or reconcile a statement, they must be treated as metadata — figures the statement reports — and never counted as debits or credits. Counting a "balance brought forward" as a transaction is one of the most common ways a statement's totals get thrown off.

The transaction table

The heart of the statement is the table of transactions. Its columns vary by bank, but the roles are consistent:

  • Date — when the transaction posted. Some statements add a separate value date, the date the funds actually became available, which can differ by a day or two.
  • Description / narration — who and what: the payee, a reference, the payment method. Long descriptions sometimes wrap across two or three lines; it is still one transaction.
  • Reference — a cheque number, transaction ID, UTR, or similar, where the bank provides one.
  • Debit and credit, or a single amount — the money itself, covered next.
  • Balance — the running balance after this transaction.

Debits and credits: which way did the money go?

This is where people trip up, partly because banks use different conventions.

  • A debit is money leaving your account: a payment, a withdrawal, a fee. From your perspective, your balance goes down.
  • A credit is money coming in: a deposit, a transfer received, a refund, interest. Your balance goes up.

(A brief note on why this can feel backwards: from the bank's point of view your deposit is a liability they owe you, so their bookkeeping labels can seem inverted. On your statement, though, the plain-English rule holds — debit is out, credit is in.)

Banks show direction in several ways:

  • Two columns — separate Debit and Credit columns, with each transaction populating one.
  • One amount with a flag — a single amount column plus a DR/CR indicator.
  • Signed amounts — one column where negative means money out.
  • Withdrawals / Deposits — the same idea with friendlier names.

They all mean the same thing. When you process a statement, the goal is to normalise every convention into one consistent debit/credit model so you are never guessing.

The running balance

After each transaction, the running balance shows what was in the account at that point. It is the statement's own internal check: each balance should equal the previous balance plus a credit or minus a debit.

That relationship is quietly powerful. If the running balance ever breaks the pattern — a jump that the transaction between two rows does not explain — either a transaction is missing or an amount is wrong. Reading down the balance column and confirming it moves consistently is a fast way to sanity-check a statement before you rely on it.

The running balance is also the best single view of your cash position over time. Its lowest point tells you how close to zero you came; its trend tells you whether your buffer is growing or shrinking.

The summary figures

Many statements end with totals: total debits, total credits, and the transaction count for the period. These are worth using as a checksum. When you extract the transactions yourself, your computed totals should match the statement's stated totals. If the statement says 142 transactions and 142 is what you have, and the debit and credit totals agree, you have strong evidence nothing was missed or duplicated.

And of course, the totals should satisfy the identity that ties the whole statement together:

Opening balance + total credits − total debits = closing balance

Putting it together: a worked reading

Imagine a savings statement for the month. The header tells you it is your account, in rupees, covering the 1st to the 31st. The opening balance line reads ₹48,000 — matching last month's close. Down the table, a salary credit of ₹1,42,500 pushes the running balance up; a rent debit of ₹28,000 brings it down; a scatter of card purchases and a couple of fees nibble at it through the month. The closing balance reads ₹92,300.

Check the identity: ₹48,000 opening, plus ₹1,42,500 in credits, minus ₹98,200 in debits, gives ₹92,300 — exactly the closing balance. The statement is internally consistent. You did not have to trust it; you verified it, using nothing but the figures on the page.

The takeaway

A bank statement is not complicated once you know what each part is for. The header sets the context, the opening and closing balances frame the period without being transactions, the table records the events, debits and credits capture direction, and the running balance and totals let you check the whole thing hangs together. Read it that way — and especially keep balance lines out of your transactions and verify the closing balance — and you will read any bank's statement with confidence, whatever labels they happen to use.

Turn your statement into clean data

Upload a bank statement and get verified transactions, cash flow and accounting-ready exports — no login required to start.

Analyze my statement