1. Export to Excel and build it by hand
Export the trial balance and ledger details from Tally to Excel, place each ledger on its Schedule III line by hand or with the firm's own template, then type the figures into CompuTax or CompuBal and build the audit workings separately.
- Good for: very small books, or a one-off format nobody else needs.
- What it costs: hours per client, the same mapping repeated every year, retyping errors, and differences that surface late, when the statements don't agree with Tally.
2. An add-on inside Tally (TDL)
Some firms load a TDL add-on into TallyPrime that prints Schedule III style reports or audit lists from inside Tally.
- Good for: staying inside Tally for a report or two.
- What to check: the add-on has to be loaded on each Tally you work on, and what it covers depends entirely on how it was written. Ask whether it gives you the CompuTax import file, the tax-audit workpapers and Clause 44, and whether it proves its figures against Tally's own balances.
3. A finalisation app that reads Tally
This is what Nexvia Finalise does. It runs on the Windows PC next to TallyPrime, reads the open company directly (no TDL, no export files), proves every ledger against Tally's own closing balance, places every ledger on its Schedule III line automatically and writes the files in Excel.
- Good for: firms finalising many TallyPrime clients, especially proprietorships, partnership firms and trusts, and big books (a book of 1,07,479 vouchers pulls in about two to three and a half minutes).
- Limits today: Windows only; the statement format is the ICAI non-corporate one (a company or LLP gets the same layout with a note, not a Division I layout); TallyPrime in Educational mode can't be used; paid after the 14-day free trial.
Side by side
| Excel by hand | Tally add-on (TDL) | Nexvia Finalise | |
|---|---|---|---|
| Time per client | Hours | Depends on the add-on | Minutes |
| Schedule III mapping | By hand, every year | Depends on the add-on | Automatic, remembered for the firm |
| Checked against Tally's own balances | Only if you do it | Depends on the add-on | Every ledger, every pull |
| CompuTax / CompuBal import file | Typed in | Depends on the add-on | Written for you |
| Tax-audit workpapers and Clause 44 | Built by hand | Depends on the add-on | Written for you |
| Anything installed inside Tally | No | Yes, on each Tally | No, it only reads |
| Company (Division I) layout | Any layout you build | Depends on the add-on | Not yet (non-corporate format) |
| Cost | Staff time | The add-on's price | 14-day free trial, then a paid plan |
Which should you pick?
If you finalise a handful of tiny books a year, Excel is fine. If your clients keep their books in TallyPrime and you spend finalisation season retyping trial balances, mapping ledgers and chasing differences, try Finalise on one real client: install it on the PC that runs Tally and you'll have the workbooks in minutes. If you mainly need Division I company statements, Finalise doesn't make that layout yet.