Tally will not chase an overdue invoice for you. TallyPrime can share a document to WhatsApp by hand, but nothing inside Tally wakes up at 10am on Monday and messages the 60 parties who are past due — for that you push outstanding data out of Tally into a WhatsApp Business API account, which on RichAutomate costs ₹0.30 per utility message with no setup fee and no monthly minimum.
Tally runs the books of a very large share of Indian SMBs, and the single most expensive gap in most of those books is receivables. The ledger already knows exactly who owes what and since when. The reminder still goes out as a phone call from an accounts person, or not at all. This guide covers the four honest ways to close that gap in 2026, what each one really costs, and where it is not worth doing.
What Tally can and cannot do on WhatsApp today
TallyPrime ships a WhatsApp sharing feature — you can push an invoice, statement or reminder out of Tally to a party's number. That is genuinely useful and it is free with your licence. It is also document sharing, and that is the whole boundary.
What it does not give you:
- Scheduled dunning. No "every Monday, message every party overdue by more than 15 days" rule.
- Inbound replies. When the party answers "paid yesterday, ref 4471", that message does not come back to anyone who can act on it.
- Delivery and read status you can report on. You cannot tell your collections review which reminders actually landed.
- Multiple people on one number. Accounts, dispatch and sales cannot share a single business number with assignment between them.
Those four gaps are exactly what the WhatsApp Business API adds. It is not a better version of Tally's sharing button — it is a different layer that sits beside it.
Four ways to connect Tally to WhatsApp
Be sceptical of anyone selling a "native Tally WhatsApp connector". Tally is a desktop-first accounting product; every route below is some form of getting data out of it and into an API. The honest question is not whether there is a connector, it is how much plumbing you are willing to own.
| Route | How it works | Effort | Automated? | Best for |
|---|---|---|---|---|
| TallyPrime sharing | Operator opens the voucher and shares it to WhatsApp | None | No — one document, one click, one human | Under ~30 invoices a month |
| TDL add-on | A Tally Definition Language extension adds a button or menu inside Tally that calls an external API | Needs a TDL developer | Partly — usually still operator-triggered | Firms with an existing Tally partner |
| ODBC / XML export + script | A scheduled job pulls outstanding or sales data from Tally and posts it to the WhatsApp API | A few hours for anyone who writes scripts | Yes — fully unattended | Most SMBs with any IT help |
| Export to sheet + campaign | Export outstandings to CSV, upload as a campaign | None | Semi — one upload per cycle | Teams with no developer at all |
For the majority of Indian businesses the third row is the right answer and the fourth is the right starting answer. Run the CSV route for a month, see whether recovery actually improves, and only then pay someone to automate it. If you want to model the message spend before committing, the WhatsApp API cost calculator takes volume and template mix and returns a monthly figure.
What Indian businesses actually automate from Tally
Five flows cover almost every real deployment we see:
- Outstanding reminders. Party name, amount, days overdue, and a payment link. This is the flow that pays for the whole project.
- Invoice delivery on creation. The PDF reaches the party in seconds instead of end-of-day email that nobody opens.
- Payment received confirmation. Cheap, and it removes an entire category of "did you get my payment" calls.
- Dispatch and e-way bill updates. Especially for distributors and traders where the buyer's own dispatch depends on it.
- Ledger or statement on demand. The party messages your number, a bot returns their current balance.
The last one is the only flow that needs real chatbot logic. The first four are one-way template sends and are much simpler than most vendors imply. Distribution businesses running this against Tally usually pair it with the patterns in our WhatsApp API guide for pharma distributors, and practices billing on behalf of clients tend to start from the CA firm setup.
Want the receivables flow running against your Tally data? Start a 14-day trial with 100 free credits — no card, no setup fee.
Get a 1-minute BSP audit on WhatsApp
Drop your WhatsApp number — we line-item your current invoice against Meta India rates in under 60 seconds. India-hosted, DPDP-compliant.
The template rules that decide whether this works
This is where Tally-to-WhatsApp projects fail, and it has nothing to do with Tally.
Any message you send to someone who has not messaged you in the last 24 hours must be a pre-approved template. Meta reviews templates and sorts them into categories, and the category sets the price. A payment reminder or invoice delivery is a utility template — it is about an existing transaction, and it is the cheap category. "Diwali offer, 20% off" is marketing, roughly four times the price, and it is subject to per-user marketing limits.
Three rules worth internalising before you write a single line of code:
- Keep reminders strictly transactional. The moment you bolt a promotional line onto a payment reminder, Meta can recategorise the template as marketing and your unit cost jumps.
- Opt-in matters. Your parties are existing customers with an active ledger, which is the strongest opt-in basis there is — but record how and when you got consent. Nobody can promise you immunity from a block or a quality downgrade, and any vendor who does is selling you something they do not control.
- Replies are free for 24 hours. Once a party answers your reminder, a service window opens and everything you send back inside it is free-form and unbilled per message.
What it actually costs
RichAutomate is usage-only. ₹0 setup, ₹0 monthly floor, no per-seat charge — put your whole accounts team on one number without the bill moving. Two billing modes:
| Mode | You pay | Meta charges | Suits |
|---|---|---|---|
| Client Pay | ₹0.10 per message platform fee | Billed directly to your own WABA by Meta | Higher volume, or you already hold a WABA |
| SaaS Pay | ₹0.30 per utility/authentication message, ₹1.20 per marketing message — inclusive | Nothing separate; one INR invoice | Most SMBs — one predictable bill |
A worked example. A distributor sends 400 outstanding reminders a month plus 250 invoice deliveries — all utility. On SaaS Pay that is 650 × ₹0.30 = ₹195 a month, all in. Recovering a single ₹40,000 invoice two weeks earlier pays for the year. The full breakdown across providers sits in our WhatsApp Business API cost guide for India.
One thing to plan for: GST registration is effectively mandatory to go live. You can run the 14-day trial and build the whole integration without it, but Meta's business verification will not complete without GST documentation, so a business that is not yet registered cannot move into production.
Setting it up in six steps
- Pick the number. It must not be active on the consumer WhatsApp app — moving a number to the API removes it from that app and old chats do not come across. Most firms use a fresh accounts-department SIM.
- Create the account and verify. Business name exactly as on the GST certificate, then Meta business verification.
- Get templates approved. Start with two: payment_reminder and invoice_delivery, with placeholders for party name, amount, days overdue and reference. Approval is typically a day or two.
- Get the data out of Tally. Either a scheduled ODBC/XML pull of the Bills Outstanding report, or a manual export to CSV while you are testing.
- Send. Either upload the CSV as a campaign, or call the REST API from your script — see the API documentation for the send-template and campaign endpoints.
- Close the loop. Point a webhook at your system so replies and delivery status come back, and route inbound to whoever handles collections.
Steps 1 to 3 are the ones with external waiting time. The actual integration work in steps 4 and 5 is usually an afternoon.
When not to do this
If you raise fewer than about 30 invoices a month, TallyPrime's built-in sharing is enough and this whole exercise is overhead. If your receivables problem is a handful of large accounts rather than a long tail, a phone call from a human beats any automation. And if your Tally data is not clean — party phone numbers missing or stale in a third of your masters — fix the masters first, because a reminder engine pointed at bad numbers just generates failed sends and drags your quality rating down.
Where it does pay is the long tail: hundreds of small parties, predictable cycles, and an accounts team currently spending its mornings on the phone. Teams already running a CRM alongside Tally should also read our Zoho CRM WhatsApp integration guide, since the same API layer serves both.
Ready to test it against your own outstandings? The trial gives you 100 free credits for 14 days — enough to run a full reminder cycle before you decide.