TallyPrime + Salesforce integration

We deploy a lightweight agent next to Tally that polls its XML port and forwards changes to Salesforce over an outbound HTTPS connection, typically every 5 to 15 minutes while Tally is running. Salesforce-to-Tally actions are queued via Platform Events and applied on the next cycle, so a voucher usually appears in Tally within minutes of the opportunity closing. True sub-second sync is not possible with Tally’s architecture, and we say so upfront.

We map Salesforce fields to Tally ledger and voucher attributes, including GSTIN, state code, stock group and godown. Duplicates are prevented by storing the Tally ledger GUID on the Salesforce Account and matching on GSTIN or PAN for existing customers. Tally rejections (missing HSN, inactive item, period locked) are captured with the error text and shown in a Salesforce list view for correction.

Yes. We can expose the on-premise Tally bridge and the Salesforce API through a custom MCP server so an assistant can check a customer’s outstanding balance, list recent invoices and update the opportunity in one conversation. Write access to Tally is scoped tightly and can require approval.

A standard scope covering ledgers, stock items, opportunity-to-voucher, invoice and outstanding sync usually takes a few weeks, including building the Salesforce custom objects and testing against a copy of your Tally data. Custom TDL, multiple Tally companies or complex tax scenarios extend the timeline to around two months.