Most advice on how to choose a Tally partner in India is written for the accountant. That makes sense: Tally is accounting and inventory software, and the finance team uses it every day. But in a lot of Indian businesses, the person who gets the phone call when Tally will not open, the remote branch cannot connect, or a custom report breaks after an update is the in-house IT person or developer. This checklist is for that person.
What SARVO's guide says to check
SARVO's buyer guide for Tally lists three partner-specific checks:
- TallyPrime experience and GST workflows
- Customisation using TDL, if you need it
- Data migration and multi-user or remote access set-up
It also recommends asking every partner five standard questions: who runs the project, what is in the written scope, how migration, testing and training are handled, what support is included after go-live, and whether you can speak to two recent clients.
Below, each check is turned into questions you can ask and evidence you can request.
How to choose a Tally partner in India: TDL customisation
TDL (Tally Definition Language) is how Tally is customised: extra fields, custom vouchers, custom reports, integrations. It is powerful, and it is also where long-term support problems come from.
Questions to ask
- Which of our requirements need TDL, and which can be met with standard TallyPrime features? Show us the list.
- Will we receive the TDL source files, or only compiled files?
- Who owns the TDL once we have paid for it?
- What documentation comes with each customisation: what it does, which vouchers or reports it touches, how it is loaded?
- When TallyPrime is updated, who checks that our TDL still works? Is that included in support?
- If another developer had to maintain this, what would they need?
Why source access matters
If you only hold compiled files, every future change depends on the original developer. That may be fine for a single small report. It is a real risk for anything that touches voucher entry or integrations. Put source access and ownership in the scope.
Data migration
Even within Tally, migration happens more than people expect: moving from an older release to TallyPrime, splitting or merging companies, moving a branch onto a central set-up, or restructuring masters.
Questions to ask
- What exactly moves: ledgers, groups, stock items, godowns, opening balances, open bills, history?
- How will you verify the migration? (Ask for specific checks, for example trial balance and stock summary matching before and after.)
- How many trial runs before the final cut-over?
- Who on our side signs off each run?
- What is the rollback plan if the final migration has problems?
Data hygiene before you start
Before migration, run a clean-up: duplicate ledgers, inactive stock items, inconsistent GST details on parties. Partners can do this, but it is cheaper if your team handles the obvious parts and the partner handles the tricky ones.
Multi-user and remote access
This is the part most likely to land on IT. Branches, work-from-home accountants and an auditor who needs access at year-end all create access requirements.
Questions to ask
- What set-up do you recommend for our number of users and locations, and why?
- Where will the data live, and who has admin access to that machine or server?
- How will remote users connect, and how is that access secured?
- How are user roles and rights set up in Tally, and who maintains them when staff change?
- What is the backup routine, where are backups stored, and when was a restore last tested?
What good looks like
A partner should be able to describe a backup routine, an access-control plan and a recovery process without hesitating. If they say "we will set it up" without specifics, write your expectations into the scope.
GST workflows
The guide lists TallyPrime experience and GST workflows as the first check. For a technical evaluator, the useful test is to ask the partner to walk through your actual documents:
- A multi-rate B2B sales invoice
- An inter-state and an intra-state sale
- A credit note
- A purchase with reverse charge if you have them
- Any e-invoicing or e-way bill requirements that apply to you
Ask which parts are standard and which depend on configuration or TDL.
Testing and training
- Which processes will be tested end to end, with whose data?
- Who on your side does acceptance testing?
- Will training be role-based (data entry, approvals, reporting) and recorded?
- Will your IT person get a separate session on backups, user management and loading TDL?
That last question is often forgotten. Ask for it explicitly.
Support after go-live
- What support is included, for how long, and through which channel?
- What response time applies to "Tally will not open" versus "a report looks wrong"?
- Who handles TallyPrime updates and checks custom TDL afterwards?
- How are support charges calculated after the included period?
When Tally is not the answer
Sometimes the evaluation reveals that the business has outgrown Tally: many branches, manufacturing workflows, or a need for deep integration with CRM and e-commerce. That is worth knowing before you invest heavily in TDL. SARVO's article on moving from Tally to an ERP covers when that move makes sense.
Building the shortlist
SARVO's guidance is to shortlist two to four Tally partners and put their answers side by side. Use the same questions for every partner so the answers are comparable, and score them on specifics: source access, a named migration check, a described backup routine, a support process.
You can browse listed Tally partners and the full checklist on SARVO's guide to how to choose a Tally partner in India, then send the same written requirement to the partners that fit.
Disclosure: I work on SARVO.
Top comments (0)