TDL vs a bank statement converter — what's the difference?

What TDL is

An add-on that runs inside Tally itself

TDL (Tally Definition Language) is the language Tally is built and extended in. A "TDL for bank import" is an add-on you install into your Tally instance — it adds new menus or screens inside Tally to read a file and post vouchers, without leaving the application. Installing one means matching your exact Tally release, and most are licensed, per-machine software.

What a converter is

A separate step, before Tally ever opens the file

A converter like bank2tally runs outside Tally entirely. It takes the PDF and hands back a standard Tally XML file — the same kind of file Tally's own Import → Vouchers screen already accepts, no add-on required. Nothing is installed inside Tally, so there's no release-compatibility question, and you can open the XML in a text editor and read it before you trust it.

Which one fits

Occasional statements vs. an always-on workflow

A TDL add-on can feel more integrated if you're importing constantly and want it to live inside Tally permanently. A converter fits better if you just need to turn the PDF your bank sent this month into vouchers, without installing or licensing anything per machine — that's the case bank2tally is built for.

The real trade-offs

Integration vs. portability

A TDL add-on's biggest strength is that it lives inside Tally permanently — once installed, importing is a menu click away every time, with no separate tool to open. The cost is exactly that permanence: it has to be reinstalled or updated across a Tally release change, licensed per machine it runs on, and trusted to behave correctly since it's running inside your accounting software rather than producing a file you can inspect first. A converter is the opposite trade: nothing lives inside Tally, so there's an extra step (open a browser, upload, download), but also nothing to break when Tally updates, nothing installed per machine, and a plain XML file you can read before you trust it.

A quick way to decide

Ask what's actually recurring

If bank statement import is a daily, high-volume part of how a firm works across many machines, the case for an installed, licensed TDL add-on gets stronger — that's exactly the workflow it's built to disappear into. If it's a monthly task, or something that varies by client and by bank, paying and maintaining a per-machine add-on for that is usually more commitment than the task needs. That's the gap a browser-based, pay-per-use converter is built to fill.

Questions