Connect Your Tally SMS Module to a DLT-Ready SMS Gateway

What a Tally SMS module does in TallyPrime

TallyPrime is extended with TDL, Tally's own customisation language. A Tally SMS module is a TDL add-on, usually a .tcp file from a Tally partner, that you load from F1: Help, TDLs & Add-ons, then F4: Manage Local TDLs. Once enabled, it adds options to send an SMS when a voucher is saved, or from a ledger or outstanding report. Tally's developer reference shows the method these add-ons use: the TDL calls the SMS provider's URL in the background, with the number and message filled in.

Modules differ in one important way. Some are tied to a few named SMS providers and only ask for that provider's key. Others have a field for a custom gateway URL, often called SMS URL or API URL, with placeholders for the mobile number and the message. Our HTTP API is that kind of URL. If you are buying a module, ask the Tally partner whether it accepts a custom URL before you pay. We do not sell a Tally module ourselves.

• Sales invoice SMS with bill number, amount and current balance
• Payment receipt SMS once a receipt voucher is saved
• Outstanding reminders to one party or many from the outstanding report
• Payment advice to suppliers after a payment voucher
• Dispatch alerts with the delivery note or LR number

How to fill in the gateway URL

The example URL on this page works with GET or POST and answers in plain text. Replace YOUR_KEY with the API key from your panel and KOVAIM with your own approved 6-letter header, written without the operator prefix or the -S suffix. Keep route=T for invoices, receipts and reminders, which are service messages. Then swap <mobile> and <message> for the placeholders your module uses. One module writes them as ##MOBILE## and ##MESSAGE##, another uses a different form, so copy them from its own settings screen.

Two small details save hours later. First, store party mobile numbers in the ledger as 10 digits, or with 91 in front, without spaces or dashes. Our API reads the last 10 digits, so a space inside the number breaks it. Second, if your module writes Tamil or Hindi text, it must send that text in the text parameter in place of message, or the API replies -40. On success you get a message ID back as plain text, which most modules keep in their log.

• api_key: your key from API Management in the panel
• sender_id: your approved header, for example KOVAIM
• phonenumber: the module's mobile placeholder (to and sendTo also work)
• message: the module's message placeholder (text for Indian languages)
• route: T for service messages, P for promotional ones
• No template ID is needed in the URL: the platform matches each message against the approved templates saved under your sender ID in the panel.

Matching DLT templates to voucher messages

Every business SMS in India must match a content template approved on a DLT portal, word for word, with only the {#var#} parts changing. Most Tally modules let you edit the message text for each voucher type. Register that exact text with {#var#} in place of the party name, voucher number, date and amount, then paste the approved wording back into the module. A changed word or a missing full stop is enough for the SMS to be rejected.

Each variable can hold up to 30 characters, and Tally ledger names often run longer. A name like Sri Murugan Hardware and Electricals Pvt Ltd will not fit, so use a shorter alias or a short-name field if your module offers one. Add each approved template under your sender ID in our panel as well. Our platform checks every message against those templates, so one URL can serve invoice, receipt and reminder messages. A message that matches none of them fails, and the reason shows in your MIS report.

• Template: Received Rs {#var#} from {#var#} on {#var#} vide receipt {#var#}. Thank you. - Kovai Metals
• Sent: Received Rs 25,000.00 from Sri Ganesh Hardware on 30-10-2026 vide receipt KM/R/882. Thank you. - Kovai Metals
• Each {#var#} value: 30 characters or fewer, spaces included

Birthday wishes and offers follow promotional rules

Some modules can greet parties on birthdays or anniversaries, and many owners add an offer to the wish. A message that promotes a product or an offer is promotional. It needs a promotional template, a promotional header that operators mark with -P, and route=P in the URL with the promotional sender set on your account. Promotional SMS reach only numbers that are not on DND or that have given consent, and only during the daytime hours allowed for them.

Keep promotional and service messages apart in the module, with separate URLs if it allows that. Mixing them is the usual cause of codes -18 and -19. For a yearly greeting list, you can also export ledger names, mobile numbers and dates from Tally to Excel and send the wishes from our web panel on the day. That keeps your voucher alerts on the service route and your offers on the promotional route, each with its own template and report.

When a Tally SMS does not arrive

Start with the reply the API gave. Most modules keep a log or show the response after sending. A negative number such as -7, -10 or -17 means the request was refused before any SMS was queued, so nothing was charged. The table on this page lists the codes you are most likely to see from Tally and what to check for each. Most come from a typo in the key or sender ID, a lowercase route, or a ledger with no mobile number.

If the module received a message ID but the party did not get the SMS, open the MIS report in our panel and search for the number. A failed status usually points to a template mismatch, a promotional message to a DND number, or a phone that was switched off. Test every new template with your own number before you switch it on for all parties. Our support team on +91 95851 60363 can look at the request with you and point to the field to fix.