How does ml-connector access TallyPrime if it is a desktop-only application on a local LAN?

ml-connector runs a local gateway agent on the same LAN as your TallyPrime server. The agent forwards API requests to TallyPrime's port 9000 HTTP server and handles the single-user, desktop-only architecture. The gateway is installed on-premise and communicates securely with ml-connector's cloud platform.

Can Slack messages written by users create or update transactions back in TallyPrime?

No. The integration is unidirectional: TallyPrime to Slack only. Slack messages and reactions do not write back to TallyPrime. This keeps the authoritative ledger in TallyPrime and uses Slack purely for notification and team coordination.

What happens if the TallyPrime application or company is unavailable during a scheduled poll?

ml-connector waits for the next scheduled polling interval rather than aggressively retrying, since TallyPrime is a single-user desktop system and forcing multiple requests can cause inconsistent behavior. The audit trail records the failed poll so you can investigate and resync when the application is back online.

TallyPrimeSlack

TallyPrime and Slack integration

TallyPrime runs accounting, inventory, and payroll for finance teams in India and Southeast Asia. Slack is where your team communicates. Connecting the two sends purchase orders, payment vouchers, and ledger entries to Slack channels in near real-time, so the whole team sees what finance posted without logging into TallyPrime. Notifications include the voucher type, amount, accounts affected, and posting date, filtered by your business rules.

How TallyPrime works

TallyPrime exposes ledgers, groups, vouchers (purchase, sales, payment, receipt, purchase orders), and stock items through an XML/JSON-over-HTTP API on port 9000. Authentication is optional at the transport layer and relies on network-level security; company-level credentials may be required if the TallyPrime company database is password-protected. The application runs on a single desktop or LAN machine and must be running with the target company loaded for API calls to succeed. TallyPrime has no native webhooks or change streams, so polling is the only option; the minimum practical polling interval is 5 to 15 minutes. The API returns all matching records in a single response without pagination, and all dates must be formatted as YYYYMMDD. A local agent must bridge the cloud connector to the port 9000 server since TallyPrime is LAN-accessible only.

How Slack works

Slack offers users, conversations, messages, files, reactions, and team data through REST and Events APIs. Authentication uses OAuth2 Authorization Code flow, resulting in non-expiring bot tokens (xoxb- prefix) passed as bearer tokens in the Authorization header. Slack's Events API delivers workspace activity as HTTPS webhooks with HMAC-SHA256 signature verification and a 5-minute timestamp window. Webhook requests must return HTTP 2xx within 3 seconds, and Slack retries up to 3 times with exponential backoff on failure. Search methods and advanced features like Audit Logs API require Enterprise Grid. Rate limits apply per operation: chat.postMessage is capped at 1 per second per channel.

What moves between them

Vouchers and ledger entries move from TallyPrime to Slack. ml-connector polls the TallyPrime Day Book or specific voucher collections at an interval you configure, typically every 5 to 15 minutes. For each new voucher (Purchase, Sales, Payment, Receipt, or Purchase Order) or ledger entry, ml-connector formats a message with the voucher type, amount, affected accounts and cost centers, and posting date, then sends it to a designated Slack channel. The integration is unidirectional: Slack notifications do not write back to TallyPrime, and messages in Slack cannot update TallyPrime vouchers. Only new transactions detected since the last poll are sent, so each voucher appears in Slack exactly once.

How ml-connector handles it

ml-connector runs a local gateway agent on your LAN that forwards HTTP requests to the TallyPrime port 9000 server, handling the fact that TallyPrime is a single-user desktop application and cannot be reached from the cloud directly. The gateway maintains a last-seen state file (stored remotely) to detect only new vouchers on each poll. For each new transaction, ml-connector sends a formatted message to Slack using the bot token, which you create once during OAuth2 setup in your workspace. Slack's webhook signature is verified using constant-time comparison to prevent spoofing. Because TallyPrime has no native idempotency key mechanism, ml-connector deduplicates using the transaction ID and posting date as a composite key. When the TallyPrime server is offline or the company is closed, polling waits for the next scheduled interval; ml-connector does not retry aggressively to avoid overwhelming a single-user system. Every voucher sent carries a full audit trail: timestamp, voucher ID, accounts, Slack channel, and Slack message URL for traceability.

A real-world example

A mid-sized bookkeeping firm in India uses TallyPrime to maintain the general ledgers and vouchers for 40 small business clients, and uses Slack for internal team communication and client coordination. Before the integration, the accounting team manually copied high-value transactions from TallyPrime into Slack when they needed team review or client notification, which was slow and error-prone. With TallyPrime and Slack connected, every purchase invoice above a threshold posts automatically to a channel watched by the review team, every payment posted to a client channel for transparency, and every month-end reconciliation report links back to the audit trail so clients can verify entries. The manual copy-and-paste step is gone, notifications reach the team in minutes instead of hours, and the audit trail satisfies both internal compliance and client trust.

What you can do

Post TallyPrime purchase orders, payment vouchers, sales invoices, and receipts to Slack channels with amounts, account codes, and posting dates.
Filter notifications by voucher type, amount threshold, or affected ledger account so only business-critical transactions trigger Slack messages.
Include rich metadata: voucher number, cost center, customer or supplier reference, and a link back to the TallyPrime voucher ID for reconciliation.
Authenticate Slack using OAuth2 bot tokens and verify webhook signatures with HMAC-SHA256 to prevent unauthorized messages.
Maintain a full audit trail of every transaction sent to Slack, including timestamp, message URL, and retry history for compliance and dispute resolution.

Questions

How does ml-connector access TallyPrime if it is a desktop-only application on a local LAN?: ml-connector runs a local gateway agent on the same LAN as your TallyPrime server. The agent forwards API requests to TallyPrime's port 9000 HTTP server and handles the single-user, desktop-only architecture. The gateway is installed on-premise and communicates securely with ml-connector's cloud platform.
Can Slack messages written by users create or update transactions back in TallyPrime?: No. The integration is unidirectional: TallyPrime to Slack only. Slack messages and reactions do not write back to TallyPrime. This keeps the authoritative ledger in TallyPrime and uses Slack purely for notification and team coordination.
What happens if the TallyPrime application or company is unavailable during a scheduled poll?: ml-connector waits for the next scheduled polling interval rather than aggressively retrying, since TallyPrime is a single-user desktop system and forcing multiple requests can cause inconsistent behavior. The audit trail records the failed poll so you can investigate and resync when the application is back online.

Connect TallyPrime and Slack

Free to use. Add your credentials, ping your real systems, and see if we fit.

Get started