# How to add WhatsApp to TallyPrime > Source: https://netray.co/integrations/tally-whatsapp > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Integrations ## Short answer TallyPrime has no WhatsApp API of its own, so the usual path is a small service that reads Tally over its XML/HTTP port (or ODBC), sends approved templates through the WhatsApp Business Platform, and writes confirmations back as vouchers. Keep Tally on the local network and let only the bridge talk to Meta. ## System TallyPrime ## Capability whatsapp ## Intro Most TallyPrime users already live on WhatsApp. Customers ask for a statement, a payment reminder or a copy of an invoice on chat, and an accountant copies figures out of Tally by hand. Some TallyPrime releases offer built-in sharing of documents over WhatsApp, which is fine for one-off invoices but does not give you scheduled reminders, templates, replies or an audit trail. The structural fact to design around is that Tally is a desktop application with a data folder, not a server farm. Its integration port only answers while the application is running with a company loaded, and a single company is served at a time by default. A WhatsApp integration therefore needs a lightweight bridge on the same network that polls or is triggered, rather than Tally pushing events out. ## Use Cases ### Outstanding payment reminders **Description:** Query the bills receivable for each party, group by ledger, and send an approved reminder template with the bill list and due dates, skipping parties flagged as disputed. ### Invoice and statement delivery **Description:** After a sales voucher is saved, render the invoice PDF from a print or export step and send it to the mobile number held on the party ledger. ### Payment confirmation capture **Description:** When a customer replies with a UTR or a screenshot, the bridge creates a draft receipt for the accountant to approve instead of posting it blindly. ### Purchase order acknowledgement **Description:** Send a supplier the PO details and record the Yes or No reply against the order for the purchase team. ### Owner snapshot on request **Description:** An authorised number sends 'cash' or 'sales today' and receives balances computed from Tally reports, with the numbers read-only. ## System Surface HTTP/XML interface: TallyPrime can listen on a configurable port (9000 is the common default) and accept XML requests for Export Data, Import Data and Execute actions. Enable it in the client/server configuration settings; exact menu names differ by release. ODBC: Tally exposes collections such as ledgers and vouchers to ODBC clients on the same port, useful for read-only lookups from scripts and BI tools. TDL (Tally Definition Language): custom reports, collections and fields can be added so a single request returns exactly the outstanding list or party phone number you need. Voucher import: sales, receipt, payment and journal vouchers can be created by posting XML with a TALLYMESSAGE and VOUCHER structure, with ledger names matching exactly. File exports: PDF, Excel, XML and, in recent releases, JSON exports of reports and vouchers can be produced by users or scripts as a fallback. ## How It Works ### Enable the Tally port and pin the company **Detail:** Turn on the HTTP server in Tally's connectivity settings, keep the target company loaded and prevent the PC from sleeping. Decide which machine runs Tally unattended. ### Store phone numbers properly **Detail:** Put the WhatsApp number in a consistent field on the party ledger (a UDF via TDL, or the mobile number field) in E.164 format so the bridge can read it. ### Register on the WhatsApp Business Platform **Detail:** Use the Cloud API directly or a business solution provider. Verify the business, add a number not used on the consumer app, and submit utility templates for reminders and invoices. ### Build the bridge **Detail:** A small service (Python or Node) sends the XML export request, parses the response, applies rules (overdue by N days, not messaged in 7 days) and calls the messaging API. ### Handle opt-in and replies **Detail:** Record consent per party, expose a webhook for inbound messages, and map replies to drafts or a queue rather than direct posting. ### Write back with approval **Detail:** Create receipts or notes via Import Data only after a human approves, and log every message with the Tally voucher or bill reference. ## Example Flows ### Weekly overdue reminder run **Trigger:** Monday 10:00 scheduled job on the Tally host **Steps:** - Request the bills receivable report for the loaded company over XML. - Filter bills overdue more than 15 days and parties with consent recorded. - Send the reminder template with the party name, total and oldest bill. - Log delivery status from the webhook against the ledger. **Result:** Collections staff see a sent and read list and chase only the parties who did not respond. ### Payment screenshot to draft receipt **Trigger:** Customer replies with a payment proof image **Steps:** - Webhook receives the media and sender number. - Bridge matches the number to a ledger and its open bills. - A draft receipt is queued with amount and reference for review. - Accountant approves and the bridge posts the receipt voucher. **Result:** Receipts are entered faster while a person still checks the bank credit before posting. ## On Prem Tally data never has to leave your premises: the bridge runs on a machine that can reach the Tally port, and only the message text and any attached PDF go out to the WhatsApp provider. If even that is too much for sensitive parties, send a short templated nudge with no figures and ask the customer to open a secure link or call. Replies can be classified by a local open-weight model so the content of free-text messages is not sent to a third-party AI service. Keep the Tally host on a segmented network and expose only the webhook receiver, not the Tally port, to the internet. ## Security - Never expose the Tally HTTP port to the internet; it has no authentication of its own, so keep it on a private network or bind it to localhost. - Store the WhatsApp access token in a secrets store, not in the script or a shared drive. - Send financial details only to numbers with recorded consent and verified ownership. - Require human approval before any voucher is created from an inbound message. - Log message ids and voucher references so disputes can be traced. ## Options ### Tally add-on or marketplace connector **Fit:** Small firms that only want reminders and invoice sharing with no custom rules. **Effort:** Days to configure; check whether it needs Tally to stay open and where data is stored. ### In-house bridge on the XML port **Fit:** Teams with a developer who can maintain a small service and a Meta business account. **Effort:** Two to four weeks including template approval and testing. ### Partner build with Netray **Fit:** Multi-company groups, reply handling, or a need to keep message understanding on private models. **Effort:** Scoped per project; usually a few weeks for reminders plus approval-based receipt capture. ## Pitfalls - Tally must be running with the right company loaded; a closed app or a company switch silently breaks scheduled jobs. - Ledger names must match exactly when importing vouchers, including trailing spaces and case. - Free-form messages outside the 24-hour customer window require approved templates. - Sending reminders without consent risks number quality drops and blocks. - Single-user Tally serves one request at a time, so heavy polling can slow the accountant using it. ## Faq ### Does TallyPrime support WhatsApp natively? **Answer:** Some releases can share documents such as invoices over WhatsApp from the application, but there is no scheduled messaging, template management or reply handling. For automated reminders and two-way flows you build or buy a bridge that uses Tally's XML or ODBC interface and the WhatsApp Business Platform. ### Can I send payment reminders automatically from Tally? **Answer:** Yes, with a bridge. It requests outstanding bills from Tally, filters by overdue days and consent, and sends an approved template. Tally itself will not trigger this, so a scheduler on the Tally machine or a nearby server is needed. ### Can WhatsApp replies create vouchers in Tally? **Answer:** They can, but it is safer to create drafts that a person approves. The bridge imports a receipt voucher via XML after approval. Automatic posting from chat text risks wrong ledgers and duplicates. ### Do I need the official WhatsApp Business API? **Answer:** For automated business messaging at any scale, yes. Unofficial automation of a consumer or Business app number breaches the terms and tends to get numbers banned. Use the Cloud API directly or through a solution provider. ### Will it work with TallyPrime Server or multiple users? **Answer:** It can, but you must point the bridge at the instance that serves the company and confirm how your licence handles concurrent requests. Test load with the accountants working, since polling competes with their activity. ## Search terms tally whatsapp integration, whatsapp for tallyprime, tally whatsapp api, send tally invoice on whatsapp, tally payment reminder whatsapp, tally outstanding reminder automation, tallyprime xml whatsapp, tally whatsapp business api --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json