An incorrect ledger name after a bank import is usually a classification issue, not a reason to discard the entire statement. The right fix depends on whether the error is in the source mapping, the Tally company, or the import batch itself.
First identify the scope. One wrong voucher can be edited directly. A repeated wrong mapping across a month is often safer to correct in the reviewed source and re-import under controlled conditions.
Step 1: Identify what is actually wrong
- Wrong ledger name: the amount and narration are correct, but the counterparty or expense ledger is not.
- Wrong ledger master: the intended ledger does not exist, is misspelled, or is duplicated in the company.
- Wrong voucher type: an internal transfer was treated as a Payment or Receipt instead of Contra.
- Wrong extraction: date, amount, sign, or narration is incorrect and must be checked against the PDF first.
Do not repair an extraction error by changing the ledger. Re-open the source row and confirm the statement data before posting a correction.
Choose the safest correction path
| Situation | Preferred action |
|---|---|
| One or two low-risk vouchers are wrong | Edit the vouchers in Tally and record the reason |
| Many rows share the same wrong mapping | Correct the reviewed source and use a controlled re-import |
| The intended ledger does not exist | Review the chart of accounts before creating or selecting a ledger |
| The batch was imported twice | Identify the duplicate batch before editing individual vouchers |
| Amounts or dates are wrong | Return to extraction review and verify the original PDF |
If you correct vouchers inside Tally
- Filter the bank ledger or date range to find the affected vouchers.
- Open the voucher and compare the narration and amount with the source statement.
- Change the ledger to the exact approved ledger name.
- Check tax, cost centre, bill reference, and narration fields where relevant.
- Save a note of who reviewed the change and why.
Editing is reasonable for a small exception. For a large batch, manual correction can introduce a second set of inconsistencies and make it harder to prove that every row was treated the same way.
If you correct the source and re-import
When the same wrong ledger appears across many rows, use the reviewed transaction list as the control point. Replace the provisional or incorrect name, export a corrected XML, and plan the Tally cleanup before importing again.
- Back up the company or follow the firm's import-control procedure.
- Identify and remove, reverse, or otherwise isolate the original batch according to the client's policy.
- Confirm that the corrected XML contains the intended ledger names.
- Import once and review the import result before moving to reconciliation.
The pre-import ledger replacement guide explains how to avoid this class of cleanup in future batches.
Prevent the problem on the next statement
Keep a client-specific ledger map for recurring customers, suppliers, bank charges, loans, and internal accounts. Review new narrations instead of applying the map blindly. Use exact ledger names and make the reviewer sign off on material or ambiguous rows.
Before exporting, follow the three-pass transaction review. If the statement is still in PDF form, begin with the bank statement to Tally XML workflow and fix classifications before they become vouchers.
Final verification
- The affected ledger balances now reflect the intended transactions.
- No duplicate voucher or duplicate ledger was created during correction.
- The bank closing balance still agrees with the source statement.
- Related vouchers such as internal transfers and fees were checked together.
- The correction and supporting evidence are retained with the engagement file.