The five bank entry mistakes that cause the most rework in Tally are: keying the wrong amount, posting to the wrong ledger, entering the same transaction twice, skipping the bank reconciliation, and leaving entries parked in Suspense. Every one of them is cheap to prevent and expensive to find.
Here is how each one happens, what it costs when it slips through, and the check that catches it before your client does.
If you are new to posting a statement in the first place, start with how to enter a bank statement in Tally step by step — which voucher type each row needs, and why a cash withdrawal is a Contra rather than a Payment.
| Mistake | What it costs you | The check that catches it |
|---|---|---|
| Wrong amount keyed | Bank balance drifts; found months later | Closing balance in Tally vs the statement |
| Wrong ledger | Distorted P&L, wrong tax position | Scan the P&L for odd or round-sum entries |
| Same transaction twice | Overstated expense, understated balance | Sort the bank ledger by amount |
| No bank reconciliation | Errors surface at audit, not at entry | Banking > Bank Reconciliation, monthly |
| Entries left in Suspense | Year-end guesswork on real transactions | Suspense A/c balance must be zero |
1. Keying the wrong amount
The most common data entry error is not a wild mistake. It is a transposition — ₹45,900 typed as ₹49,500 — or a decimal shift, ₹1,000 entered as ₹10,000. Both look plausible on screen, which is exactly why they survive review.
A transposition has a useful signature. When two digits swap places, the difference between the right figure and the wrong one is always divisible by 9. In the example above the gap is ₹3,600, and 3,600 ÷ 9 = 400. So when your bank balance is out by an odd amount, divide the difference by 9 before you start reading every line. If it divides cleanly, you are almost certainly hunting a transposition rather than a missing entry.
The check: compare the closing balance on the bank ledger in Tally against the closing balance printed on the statement, for the same date. Do this per statement, not per quarter. A single month with 60 lines is searchable; a quarter with 200 is not.
2. Posting to the wrong ledger
A wrong amount moves one number. A wrong ledger moves the shape of the accounts. If you are unsure which ledger a row should hit, the accounting entry behind each kind of statement row sets out both sides. Four cases account for most of it:
- Loan EMIs posted to a single ledger. An EMI is two things — principal repayment against the loan liability, and interest, which is an expense. Post the whole EMI to the loan account and you understate expenses; post it all to interest and you never reduce the loan.
- Own-account transfers entered as Payment. Moving money from your current account to your OD account is a Contra (F4), not a Payment (F5). Entered as a Payment it inflates expenses and creates a party balance that does not exist.
- Bank charges mixed with bank interest. They are different ledgers and, at assessment time, treated differently. Combining them makes the charge invisible.
- Tax payments treated as expenses. GST and TDS remittances settle a liability. They are not a cost of doing business, and posting them as one overstates expenses twice over.
The check: open the Profit & Loss and look at Bank Charges and any miscellaneous expense head. Round-sum figures and unusually large single entries are almost always something that belongs elsewhere.
3. Entering the same transaction twice
Duplicates rarely come from carelessness. They come from process. Two people work the same month. Or a statement is downloaded on the 28th, entered, and downloaded again on the 2nd for the full month — so the overlapping days go in a second time.
The effect is quiet: expenses are overstated, the bank balance in Tally sits below the real one, and nothing looks wrong on any single screen.
The check: open the bank ledger and sort by amount. Genuine repeat payments of the identical amount on nearby dates are rare enough that every pair deserves a look. Recording the cheque or UTR number in the narration makes this a two-second decision instead of a phone call.
4. Skipping the bank reconciliation
Bank reconciliation in Tally lives at Gateway of Tally > Banking > Bank Reconciliation. Most people treat it as a formality to be done before the audit. It is the opposite: it is the only routine check that finds all four of the mistakes above.
The value is not in the ticks. It is in what refuses to tick. After a clean month, the only unreconciled items should be cheques you have issued that the payee has not banked yet. Anything else on that list — a payment the bank does not show, a receipt the bank shows and you do not — is an error waiting to be explained at year end.
The check: run it monthly, not annually, and read the unreconciled list rather than clearing it.
5. Leaving entries parked in Suspense
Suspense A/c is a parking slot for a transaction whose correct ledger was not known at the time of entry. Used properly it is fine. The mistake is treating it as a destination.
An entry goes into Suspense on the 12th because nobody recognised the payee. Nobody returns to it. At year end someone with no memory of the transaction moves the whole balance into Miscellaneous Expenses, and a real, classifiable payment becomes a rounding error in the accounts.
This is where narration earns its keep. A narration reading “NEFT” tells you nothing in March. “NEFT to Sharma Traders, inv 114, UTR N021…” tells you the ledger without opening anything else. Write the narration for the person who will read it six months from now, because that person is you.
The check: Suspense A/c should show a zero balance at every month end. If it does not, the month is not closed.
The ten-minute monthly check
Run these five in order at the end of each month and the year-end close stops being an investigation:
- Tally’s bank closing balance against the statement’s closing balance.
- If they differ, divide the difference by 9 before reading lines.
- Sort the bank ledger by amount and look for repeated pairs.
- Run Banking > Bank Reconciliation and read what will not tick.
- Confirm Suspense A/c is zero.
Why these mistakes keep coming back
Notice what the five have in common. Four of them are created at the keyboard, and the fifth exists because someone did not have enough information at the keyboard. They are not knowledge problems — every accountant reading this already knows a contra from a payment. They are volume problems. At 40 lines a month you catch your own errors. At 400 across six clients, you do not.
That is the case for taking the keying out of the loop. When the statement is imported rather than typed, the amount is whatever the bank printed, the date is whatever the bank printed, and the transposition class of error stops existing.
Try it on your own statement — 20 free pages, no card.
SmartXtract reads bank statements as PDF, Excel or CSV, including scanned copies and password-protected files. Every row is checked against the statement’s own running balance, so a misread figure is caught rather than carried forward. It then suggests a Tally ledger for each narration, which you review and approve — the ledger decision stays yours, because that is the one mistake on this list that judgement still has to make.
Approved entries post into Tally through Tally Connector, a free Windows app, as Receipt, Payment or Contra vouchers. If a batch goes in wrong, Undo Import reverses the whole thing. There is no XML file to build — see why the Tally XML step is not needed.
Frequently asked questions
Why does my Tally bank balance not match my bank statement?
In order of likelihood: a cheque issued but not yet presented, a transaction entered twice, an amount keyed wrongly, or a bank charge the bank applied that you have not recorded. Check the unpresented cheques first — those are legitimate. Then divide the remaining difference by 9; if it divides cleanly, you are looking for a transposed figure.
Should a transfer between my own bank accounts be a Payment or a Contra?
A Contra (F4). Contra vouchers are for movement between your own bank and cash accounts, where no income or expense occurs. Entering it as a Payment (F5) inflates expenses and creates a party balance that should not exist.
What should I do with entries sitting in Suspense A/c?
Clear them the same month, while the transaction is still identifiable. Use the narration, the UTR or cheque number, and the counterparty name on the statement to find the right ledger. Do not carry a Suspense balance into the year-end close — by then nobody remembers what the payment was for.
How do I find a duplicate entry in a Tally bank ledger?
Open the bank ledger and sort by amount rather than by date. Identical amounts on nearby dates cluster together, and genuine repeat payments of the exact same figure are uncommon enough that every pair is worth checking. Recording the cheque or UTR number in the narration settles it immediately.
Can I import a bank statement PDF into Tally directly?
No. TallyPrime reads Excel, CSV and MT940 for bank statement import — it cannot read a PDF. The PDF has to become one of those formats first. See the full walkthrough on importing bank statements into Tally automatically, or the Excel and CSV route.
Does importing a statement remove these mistakes completely?
It removes three of the five. Wrong amounts, wrong dates and duplicated rows all come from keying, and importing takes the keying away. Bank reconciliation still has to be run, and the choice of ledger still needs your review — a narration reading “NEFT DR 45000” does not tell any software whether it was a supplier payment or a loan repayment. Honest position: importing removes the mechanical errors and leaves you the judgement ones.
Conclusion
None of these five mistakes is difficult to avoid. They persist because the checks that catch them are done annually instead of monthly, and because manual keying keeps regenerating the same errors faster than review can find them.
Fix the process and the checks get shorter every month. Start free with 20 pages and run one month’s statement through it before you decide.
