TallyPrime Banking and Reconciliation: A Practical Workflow for Accountants

Start with a clear reporting question

A bank reconciliation explains why the bank statement and the bank ledger differ at a chosen cutoff. Some differences need a missing or corrected voucher; others are genuine timing differences. The practical skill is to distinguish these cases and retain evidence, rather than forcing every line into a match or changing balances merely to make a report look complete.

Core concepts to learn

Build a practice scenario

1. Select one fictional bank account, a statement period and the matching bank ledger in a practice company.
2. Confirm the opening position and carry forward any genuinely unreconciled earlier transactions through the appropriate setup.
3. Match existing book entries to statement lines, then separate timing differences from items requiring accounting review.
4. Prepare the two-sided balance calculation below, check the remaining exceptions and record the evidence for every resolution.

Use sample, authorised or fictional data. Do not publish credentials, business data, account numbers or customer information in a portfolio. If a task has financial, security or production impact, include a review or approval step before any change.

What good work looks like

Confirm the release, ledger and starting point

TallyHelp’s current automatic reconciliation workflow applies to TallyPrime Release 6.0 and later. The available screens also depend on the bank, statement format and configured reconciliation mode. Use documentation for the installed release rather than assuming an older Tally.ERP 9 screenshot matches your system.

Confirm the company, account identifier, currency and bank ledger before importing anything. Set a deliberate reconciliation beginning date and review transactions outstanding before it. Opening BRS is intended for earlier unreconciled items; it is not a convenient place to insert an unexplained balancing amount. Retain the prior reconciliation that supports the opening position.

Import statement data without duplicating the accounting

For supported statement files, TallyHelp documents Alt+O, Bank Statement, selection of the bank ledger and file, and a preview before completing import. Its import guidance specifies native supported bank downloads and excludes PDF statements and Excel or CSV files converted from PDF. Check the current supported format for your bank rather than renaming a file extension.

Importing statement lines and creating accounting vouchers are different operations. If payments and receipts are already in the books, start by matching them. Automatically creating another voucher for every imported line can duplicate transactions that were previously recorded through the normal business workflow.

Record the statement period, file name and import result. Check a few deposits, withdrawals and references against the original statement before processing a large batch. If the wrong account or period was imported, use the documented correction workflow after reviewing the existing reconciliation state; do not erase valid vouchers to hide an import mistake.

A worked reconciliation with four explained differences

Use a fictional month-end example with positive bank balances. The bank statement closes at ₹1,04,000. The bank ledger in the books closes at ₹1,00,000 before adjustments. Investigation identifies a ₹12,000 customer deposit recorded in the books but not yet credited by the bank, and ₹15,000 of issued cheques recorded in the books but not yet presented.

The statement also includes ₹500 of bank charges absent from the books and a ₹1,500 direct customer receipt not yet recorded. Assume these are the only differences and that the customer receipt is supported by a valid invoice reference. The following calculation explains both balances at the same cutoff.

The ₹12,000 deposit and ₹15,000 cheques are already recorded in the books. Their appearance in the next statement should support reconciliation, not a second receipt or payment voucher. The ₹500 charge and ₹1,500 receipt require appropriate supported entries because they were absent from the books. Follow the business’s normal accounting review for classification and posting date.

This example does not require the unadjusted statement and book totals to be identical. It requires the difference to be completely explained. Keep the original balances, the adjustments and the outstanding timing items visible so another person can reproduce the calculation.

Review matches using more than the amount

Two customers may each pay ₹5,000 on the same day. Amount alone cannot identify the correct invoice. Compare the bank reference, payer information, date, instrument detail and supporting receipt. When a bank line covers several invoices, document the allocation rather than inventing a single invoice that happens to equal the total.

Separate bank-only entries, book-only entries, duplicate candidates and uncertain matches. A book-only payment may be an unpresented cheque, a failed transfer or a posting to the wrong account. Each possibility needs different evidence. A bank-only credit may be a customer collection, a transfer or another event; the statement description is a starting point, not always sufficient accounting classification.

When correcting an incorrect match, preserve the reason and inspect both transactions again. Matching is a link between evidence; it does not certify that the original expense ledger, tax treatment or invoice allocation was correct. Reconciliation review and voucher-quality review complement each other.

Manual bank dates and month-end follow-up

In the documented manual workflow, open Bank Reconciliation or its summary, choose Manual Recon where needed, and enter bank dates supported by the statement. The book voucher date and bank-clearing date can differ. Do not change a valid business posting date simply to imitate when the bank processed it.

For a deposit still outstanding at month-end, inspect the next period’s statement and record the eventual credit date. If it does not clear as expected, assign an owner to investigate. Repeatedly carrying the same unexplained item forward is not the same as completing the review.

If the opening balance still differs, inspect the previous period and Opening BRS before searching only the current month. TallyHelp also documents configuration and missing-bank-allocation issues that can affect what appears in reconciliation reports. Confirm scope and setup before creating a new adjusting entry.

What the reviewer should receive

Keep the statement cutoff, book balance, statement balance, adjustments, outstanding list and supporting references together. For each unresolved item, record its age, amount, proposed explanation, owner and next action. Show which entries were posted and which items remain genuine timing differences. A screenshot displaying no obvious exception is weaker evidence than a calculation that someone else can trace.

Does reconciliation automatically clear the books? No. It can identify or match transactions, but missing entries and incorrect classifications still need the appropriate accounting action.

Should I change the opening balance to remove a difference? Only correct an opening balance when evidence establishes that it is wrong. First investigate earlier unreconciled items and the reconciliation period.

Can a zero unexplained difference end the review? It completes the arithmetic check, but still inspect unusual old items, duplicate candidates and unsupported matches. Equal totals alone do not establish that every transaction was assigned correctly.

Official TallyHelp references

• Bank reconciliation overview and release requirements
• Bank reconciliation setup and Opening BRS
• Import supported bank statements
• Manual bank reconciliation

Frequently asked question

What should a beginner practise after learning TallyPrime banking reconciliation?

Build one small, documented exercise that uses the concepts safely, validate the result, and explain the decisions and limitations. Repeating this cycle makes learning more reliable than collecting disconnected tutorials.