Reconciling a bank statement against your ledger
Bank reconciliation compares the bank’s record with your business ledger and explains every difference. It finds missing expenses, duplicate income, bank fees, delayed UPI settlements, transfers and entry mistakes. A match should be confirmed by the owner or reviewer; software can suggest candidates but should not silently decide.
Use a statement downloaded directly from the bank through a safe process. Hisab AI does not need a net-banking password, OTP or scraping access. Import a supported file, map columns, review duplicates and confirm only after the data looks correct.
Choose a clear period and opening balance
Reconcile one account and one period at a time. Start with the bank statement opening balance and confirm it matches the previous reconciled closing balance. If it does not, solve the earlier gap before matching the new month.
Include every statement line in the period, not only sales receipts. Interest, fees, tax deductions, failed transfers, cash deposits, loan movements and owner transfers all affect the balance.
Keep pending transactions separate. A cheque issued this month but not cleared can appear in the ledger without appearing on the bank statement. A UPI receipt late at night may settle the next day. These are timing differences, not necessarily errors.
Prepare the ledger before matching
Finish daily entries and review obvious duplicates. Ensure bank and UPI payment modes are correct. Record known bank charges and interest from statements if they were not captured during the month.
Do not enter the bank statement total as one transaction. Reconciliation needs the individual lines. Also do not treat every incoming transfer as sales. It may be owner capital, a loan, a refund, a transfer between business accounts or collection of an older udhar balance.
Use stable references: invoice number, customer, supplier, amount, date and bank reference suffix. Do not store more bank detail than the task requires.
Worked example: matching a settlement and fee
The ledger shows three UPI sales:
- 28 July: ₹1,200
- 28 July: ₹850
- 29 July: ₹950
Gross receipts are ₹3,000. The bank statement on 30 July shows a merchant settlement of ₹2,970 and a separate description that indicates ₹30 of fees.
The correct reconciliation is not to reduce each sale or enter ₹2,970 as new revenue. Keep sales at ₹3,000, match them to the settlement batch, and record ₹30 as a payment-processing expense according to the business’s accounting method. Net bank increase is ₹2,970.
The same statement includes ₹5,000 from the owner’s personal account. That is capital introduced or an owner transfer, not sales. It also includes a ₹1,500 customer payment against an old invoice. That is a collection linked to the receivable, not another invoice.
Once classified, statement closing balance and ledger bank balance can agree without inflating revenue.
Match carefully, not just by amount
An exact amount within a few days is a useful suggestion, but it is not proof. Two customers may pay ₹1,000 on the same day. Match using amount, date, direction, reference, counterparty where reliable and the underlying business event.
For grouped settlements, link several receipts to one bank line. For split settlements, link one business event to multiple lines if provider evidence supports it. Preserve the relationship so future reviewers understand why totals match.
Avoid automatic matching when confidence is low. Put uncertain lines in “needs review.” A slower correct reconciliation is better than a fast wrong one that hides a duplicate.
Categorise unmatched bank lines
Common unmatched debits:
- Bank or payment fees
- Loan repayment
- Interest
- Supplier auto-debit
- Tax payment
- Refund
- Owner withdrawal
- Transfer to another business account
Common unmatched credits:
- Owner funds introduced
- Loan proceeds
- Customer payment not recorded
- Refund from supplier
- Interest credit
- Transfer from another business account
Create the missing ledger entry only after confirming its nature. A description such as “NEFT CR” is not enough by itself.
If a statement line belongs to another person or account by mistake, investigate with the bank and record the final outcome. Do not classify unknown money as sales to make the report look complete.
Handle duplicates before saving
An import may repeat a file or overlap dates with an earlier import. Detect candidates using bank account, transaction date, amount, direction and reference. Do not delete based only on same amount and date, because legitimate repeats exist.
Show the user which rows appear duplicated and why. Keep an import identifier and source-file hash or equivalent safe metadata where the architecture supports it. Review before save.
If the same statement is imported twice, the second import should not double every transaction. If rows were edited, use a controlled conflict process rather than silently overwriting reconciled records.
Prove the closing balance
After matching, calculate:
Ledger opening balance + recorded bank inflows − recorded bank outflows = ledger closing balance.
Compare with the statement closing balance, adjusted only for clearly documented timing items under the selected method. The remaining difference should be zero or explained line by line.
Do not create a general “bank adjustment” merely to reach zero. If an adjustment is genuinely required, document its cause, approver and supporting evidence.
Sign off the period with reconciliation date, reviewer and unresolved items. Lock or flag confirmed matches so later edits trigger a warning.
Reconcile on a useful schedule
High-volume businesses may reconcile daily or weekly. A smaller shop should usually do it at least monthly and before preparing tax or loan information. Delaying several months makes descriptions harder to recognise and missing bills harder to recover.
Combine the bank process with daily cash and UPI closing. Daily checks prove operational receipts; monthly reconciliation proves settlement and bank movements.
Store statement files securely. Do not include bank credentials, and exclude sensitive bank details from ordinary exports or AI requests. Backups must remain scoped to the authenticated owner.
Practical takeaway
Reconcile one account and period, verify the opening balance, match lines using more than amount, classify unmatched movements, detect duplicate imports and prove the closing balance. Treat transfers, loans and old-customer collections according to their real nature rather than as sales.
Start with the latest complete month and resolve every unmatched line before moving backward. Use UPI and cash reconciliation to improve daily data and record-retention guidance to keep the evidence supporting each match.