Connect Tally to the WhatsApp messages your dealers already send
Your dealers order in a chat. Your accounts desk keys the same order into Tally. This is how to stop doing that twice without moving off Tally.
Most distribution businesses in India run their books in Tally and run their day in WhatsApp. Neither is the problem. The problem is the gap between them, and that gap is usually a person: someone reads an order out of a chat thread, types it into Tally, raises the invoice, and sends a photo of it back into the same thread.
That person is doing three to four hours a day of work a connector can do, and they are the point at which a quantity gets mistyped and nobody notices until the dealer disputes the bill.
What actually syncs
Connekt talks to Tally over its XML interface — the same one Tally exposes for any third-party integration. Nothing is scraped and no file is imported by hand.
| What | Direction | When |
|---|---|---|
| Sales orders captured from WhatsApp | Connekt → Tally | On confirmation |
| Sales invoices raised against your rate list | Connekt → Tally | On invoice |
| Receipts and payments recorded in Tally | Tally → Connekt | On the sync cycle |
| Dealer ledger balances and outstanding | Tally → Connekt | On the sync cycle |
| Stock items and rate lists | Tally → Connekt | At setup, then on change |
Your ledgers stay yours. Connekt maps onto the ledgers and stock items you already have rather than creating a second chart of accounts. If you stop using Connekt tomorrow, Tally is exactly as it was — with the vouchers it wrote still in place.
What it means on a normal Tuesday
A dealer sends “need 120 cartons, deliver Thursday” to your WhatsApp Business number. Connekt reads it, applies the rate list that dealer is on, and replies in the same thread with a confirmed order — number, quantity, value, delivery date.
The invoice is raised against that order and written into Tally as a sales voucher under that dealer’s existing ledger. When your accounts team records the payment in Tally, the dealer’s outstanding figure in Connekt changes, so the next time they ask “balance kitna hai?” the answer is current rather than last-week’s.
Nobody typed the order twice. There is one timestamped record of what was agreed, which is what settles a dispute in seconds instead of an afternoon of scrolling.
What you need before setup
- Tally Prime or Tally.ERP 9, with the XML/HTTP interface enabled
- A machine running Tally that stays on during business hours
- A WhatsApp Business number — a new one, or an existing one migrated to the API
- Your dealer list and your current rate card, in any format you already keep them
Setup is done with you on a call rather than handed over as a document. Connecting Tally is part of the one-time onboarding — see what that costs.
Where the limits are
Worth knowing before you plan around it. Tally’s interface only answers while Tally is open, so a machine that gets shut down at 6pm stops syncing at 6pm — orders captured after that are queued and written when it reopens. And because Tally is usually on a local network, the connector needs a route to it; on a single-branch setup that is straightforward, across several branches it is worth a conversation on the call.
If your books are in Zoho Books instead, that connector is cloud-to-cloud and has none of these constraints — here is how that one works.
Common questions
Does this work with Tally Prime, or only older versions?
Tally Prime and Tally.ERP 9 both expose the same XML interface over HTTP, so both work. Tally has to be running, with that interface enabled, on a machine Connekt can reach.
Does Tally have to stay switched on?
Yes, while syncing. Tally’s XML interface only answers while the application is open, so it runs on a machine that stays on during business hours — usually the accounts desk or a small always-on PC. Anything Connekt captures while Tally is closed is queued and pushed when it comes back.
Which direction does the data flow?
Both. Orders and invoices raised from WhatsApp are pushed into Tally as vouchers; ledger balances and payments recorded in Tally come back so the dealer sees a current outstanding figure when they ask.
Will it create duplicate vouchers?
Each Connekt invoice carries its own reference and is matched on that reference before anything is written, so a retried sync updates the existing voucher rather than adding a second one.
What happens to our existing ledgers and stock items?
They stay as they are and remain the source of truth. Connekt maps its dealers to your existing ledgers and its products to your existing stock items during setup rather than creating a parallel set.
Is the Tally connector included in the price?
The software is. Connecting it is one-time setup work — included on Scale, included as your first integration on Growth, and charged once on Starter. See the pricing page for the current figures.