Mapping a bank transaction to a Tally ledger is an accounting decision, not just a text-matching exercise. The narration gives clues, but the correct ledger also depends on whether the transaction is a receipt, payment, transfer, charge, loan movement, or a personal item.
A reliable mapping process starts with the extracted bank row and ends with an evidence-backed ledger choice. This is especially important when a statement PDF has abbreviated narrations or when a client uses several similar ledgers.
The four inputs to a good ledger decision
- Direction: debit and credit determine whether money left or entered the bank account.
- Narration: names, UTRs, cheque numbers, UPI handles, and bank codes narrow the possibilities.
- Context: prior entries, invoices, vendor lists, loan schedules, and client explanations supply meaning.
- Materiality: high-value or unusual items deserve stronger evidence than a routine recurring charge.
A practical mapping table
| Transaction pattern | Likely ledger family | Decision point |
|---|---|---|
| Credit from a customer name or invoice reference | Trade receivable or customer ledger | Match the remittance to an open invoice |
| Debit to a supplier with an invoice trail | Trade payable or supplier ledger | Check the purchase invoice and payment allocation |
| Debit with “charges”, “service fee”, or “SMS” | Bank Charges or bank expense | Separate interest, fee, and tax where required |
| Credit or debit between own accounts | Other bank ledger | Confirm both accounts belong to the same books |
| Salary batch or employee transfer | Payroll payable or employee advance | Match payroll register and settlement status |
| Cash withdrawal or deposit | Cash ledger | Confirm the physical cash movement and business purpose |
Use narration as a clue, not as proof
A narration containing “AMAZON” could be office supplies, resale inventory, a personal purchase, or a subscription. “SALARY” could be payroll, a contractor payment, or an advance. Start with the text, then verify the accounting purpose.
For recurring rows, compare the previous month's approved ledger. Consistency is useful, but it should not override a changed circumstance. A vendor can become a customer, an EMI can finish, and a transfer can move to a new bank account.
Decision tree for ambiguous rows
- Can the counterparty be identified from the narration or reference?
- Does an invoice, payroll register, loan schedule, or bank advice support the match?
- Is the movement between two ledgers already in the company, making it a possible Contra voucher?
- Could it be personal, related-party, or a director transaction that needs a separate review?
- If two answers remain plausible, keep it provisional and ask for evidence rather than guessing.
The Payment, Receipt, and Contra guide is useful when the ledger choice and voucher type are connected.
Keep ledger names consistent
Select the exact ledger already used in the client company. Avoid creating “Rent”, “Office Rent”, and “Office Rental” for the same expense unless the chart of accounts intentionally distinguishes them. When working from a bank statement PDF, use the review screen to replace provisional names before export rather than correcting a long list of vouchers after import.
Read the ledger replacement before Tally import guide for a repeatable review method. If the client uses HDFC, SBI, ICICI, Axis, or another supported bank, the bank-specific converter guides can help with the statement-download step.
Review before you export
- Sort by amount to inspect material items first.
- Group repeated narrations to identify consistent patterns.
- Compare opening and closing balances with the bank statement.
- Flag duplicate dates, amounts, and references.
- Leave a review note for every classification that relies on client confirmation.
Doxify can extract transactions from bank statement PDFs and export reviewed XML or CSV. It helps surface the rows that need a decision; the CA still owns the ledger classification and final review.