Convert a bank statement into a Tally import
Upload a PDF, Excel or CSV bank statement and download a workbook containing a Tally Import sheet — every transaction laid out as a double-entry voucher, ready to import into Tally. The statement is processed entirely in your browser and is never uploaded.
What the Tally import sheet contains
Once you classify the cleaned statement, the downloaded workbook gains a Tally Import sheet using a compact single-row-per-voucher layout in the column shape TallyPrime's Excel import expects.
- Money out becomes a Payment voucher: the ledger head or counterparty is debited and the bank ledger credited.
- Money in becomes a Receipt voucher: the bank ledger is debited and the income or party ledger credited.
- The bank ledger is named from the detected bank, so it matches the ledger you already keep in Tally.
- Transfers between your own accounts route to a Contra / Own Transfer ledger instead of being booked as income or expense.
- Anything still unclassified is parked in Suspense — never a silent guess — with the parked count noted above the table.
Why entries are never silently guessed
A voucher import that quietly assigns the wrong ledger costs more time to unpick than manual entry would have taken. So every row that the classifier cannot resolve with confidence is parked in Suspense and counted, rather than being pushed into a plausible-looking head.
The list of every ledger the sheet references is printed above the table, so you can create any missing ledgers in Tally before you import. Transfers between your own accounts are routed to a Contra / Own Transfer ledger — the account holder's name is read from the statement header, so a transfer to yourself is never booked as income.
Teach it once, and it remembers
Rows left in Suspense can be resolved in bulk from the worklist. Assign the correct ledger head, tick "Teach rule", and the keyword pattern is saved in your browser — every matching row in that statement reclassifies immediately, and every future statement you clean uses the same rule.
Because the classifier is rule-based rather than a machine-learning model, every classification is explainable: you can see which rule matched, edit it, and delete it. Nothing about your transactions is sent to a cloud categorisation service.
Frequently asked questions
How do I import the sheet into Tally?
Download the cleaned workbook after classifying, choose Tally from the format selector before downloading, then use Tally's own Excel import to bring the Tally Import sheet in. The columns are already in the shape it expects.
What happens to transactions it cannot classify?
They are parked in a Suspense ledger and the count is shown above the table, so nothing is silently misfiled. You can resolve them in bulk from the Suspense worklist before downloading.
Does the double-entry mapping differ between accounting packages?
No. Money out is always a Payment (debit the ledger head or counterparty, credit the bank ledger) and money in is always a Receipt (debit the bank, credit the income or party ledger). Only the row layout changes — Tally and Vyapar use one row per voucher, Zoho Books and QuickBooks use a two-line journal.
Is my statement sent to a server to generate the Tally sheet?
No. Parsing, classification and Excel generation all run in your browser. The workbook is assembled on your own machine and downloaded directly from the page.