TallyPrime and Twilio integration

What moves between them

Transactions flow one direction: from TallyPrime to Twilio. ml-connector polls TallyPrime's Day Book or voucher collections on a schedule, extracts purchase and sales vouchers, and sends SMS notifications to customer phone numbers stored in TallyPrime ledgers. Payment reminders go out when invoice due dates approach. Each SMS is sent via Twilio's REST API, which returns a message SID for audit logging. Because TallyPrime is read-only in this flow, ml-connector never writes back to TallyPrime.

How ml-connector handles it

ml-connector requires a local agent running on the same machine or network segment as TallyPrime to bridge requests to port 9000, since TallyPrime's HTTP server is LAN-only and not internet-accessible. It polls TallyPrime's Export Data endpoint with date-range filters (SVFROMDATE, SVTODATE) and compares returned voucher IDs against last-seen state to detect new transactions. Phone numbers are extracted from ledger master records in TallyPrime. For each new invoice or payment, ml-connector constructs the SMS text, calls Twilio's REST API with the Account SID and Auth Token, and logs the returned message SID to the audit trail. Twilio's 2FA and Verify endpoints can also send one-time codes to customers for payment confirmation. TallyPrime's single-user desktop design means concurrent requests may cause inconsistent behavior, so ml-connector keeps all polling sequential and respects the practical 5-15 minute polling window.

A real-world example

A mid-market retail and wholesale business in India runs TallyPrime for accounting and inventory across three branch offices. When invoices are issued, the accounting manager manually sends SMS reminders to wholesale customers reminding them when payment is due; when payments arrive, he sends confirmation texts one by one. With TallyPrime and Twilio connected, each new sales voucher triggers an automatic SMS to the customer with invoice number, amount due, and due date. When a payment voucher posts, a confirmation SMS goes out immediately. The manager no longer spends 30 minutes per day on manual SMS; customers get instant notifications and payment reminders are consistent.

What you can do

• •Send SMS notifications from TallyPrime when sales and purchase vouchers post, with invoice number, amount, and due date.
• •Automatically send payment due-date reminders to customers stored in TallyPrime ledger master records.
• •Validate Twilio webhook signatures and receive inbound message status callbacks for delivery tracking and failed-SMS alerts.
• •Bridge TallyPrime's local HTTP server through a managed local agent so cloud Twilio can reach it securely.
• •Poll TallyPrime sequentially on a configurable schedule with full audit logging of every voucher ID and message SID.

Questions

Does ml-connector need a local agent to reach TallyPrime?

Yes. TallyPrime's HTTP server runs only on port 9000 and is LAN-accessible, not internet-facing. ml-connector requires a local agent running on the same machine or network as TallyPrime to bridge API calls to it. This agent is lightweight and runs continuously.

Which phone numbers get SMS notifications, and where do they come from?

Phone numbers are stored in TallyPrime ledger master records (customer ledgers). ml-connector reads these during polling and uses them as the SMS destination. If a customer ledger has no phone number, no SMS is sent for that transaction. You control which ledgers receive notifications through a mapping configuration.

What happens if Twilio SMS fails or TallyPrime is unavailable during a poll?

ml-connector logs the failure with the voucher ID and message SID to the audit trail and retries the SMS on the next poll cycle. If TallyPrime is offline, polling pauses and resumes when the application is available again. Every attempted record is logged so you can see exactly what succeeded and what failed.