TallyPrime and TrueCommerce integration

What moves between them

Purchase orders and sales invoices move from TallyPrime into TrueCommerce as EDI X12 documents (850 for orders, 810 for invoices, 856 for advance ship notices). The flow is unidirectional from TallyPrime outbound. TrueCommerce functional acknowledgments (X12 997) and remittance advice (820) may be pulled back into TallyPrime for reconciliation, but this requires a separate reverse mapping. Sync cadence is polling-based on your schedule: ml-connector polls TallyPrime every 5 to 15 minutes for new or modified vouchers in the configured date range, transforms them to X12 format, and pushes them to TrueCommerce FTP or Exchange API. Inventory movements and stock transactions can also be synced to keep trading partners informed of availability.

How ml-connector handles it

ml-connector runs a local Windows agent on the same network as your TallyPrime instance to bridge HTTP access to the desktop application and manages both credential sets: TallyPrime company name, HTTP port, and optional login; TrueCommerce SFTP username and password or Exchange API key. On each polling cycle it POSTs an Export Data request to TallyPrime's port 9000 with SVFROMDATE and SVTODATE filters, parses the returned vouchers, maps ledger accounts to X12 segments (PO1, IT1, TST), and transmits the document to TrueCommerce. TrueCommerce requires specific file naming and ISA control numbers for deduplication; ml-connector handles both. Because TallyPrime must remain open and responsive and concurrent requests cause inconsistent data, polling is sequential and spaced to avoid contention. Retries on both sides use exponential backoff, and every document carries a full audit trail so failed transmissions can be replayed when TrueCommerce or the trading partner is ready to receive.

A real-world example

A mid-sized B2B distributor runs TallyPrime for accounting and inventory in India, and uses TrueCommerce to exchange orders with regional suppliers via EDI. Previously, purchase orders typed into TallyPrime were manually re-entered into TrueCommerce and emailed to suppliers, and supplier acknowledgments were printed and hand-filed. With the integration live, each purchase order in TallyPrime automatically converts to X12 850 and appears in the supplier's inbox within minutes. Supplier acknowledgments flow back through TrueCommerce and are logged in the audit trail for the finance team. The sales team can also push sales invoices to certain partners as X12 810 to expedite collections. Manual re-entry is eliminated, and the lag between order and acknowledgment drops from days to hours.

What you can do

• •Map TallyPrime purchase orders, sales invoices, and purchase requisitions into X12 850, 810, and 856 EDI documents for TrueCommerce.
• •Poll TallyPrime on your schedule (5 to 15 minute intervals) and push documents to TrueCommerce SFTP or Exchange API without manual transformation.
• •Store TallyPrime company credentials and TrueCommerce API credentials encrypted, manage both HTTP port and file naming conventions, and handle ISA control numbers for deduplication.
• •Receive and audit functional acknowledgments (997) and remittance advice (820) flowing back from trading partners through TrueCommerce, and optionally post them into TallyPrime.
• •Retry failed transmissions with exponential backoff on both sides, track every document in a full audit log, and replay failed records when the downstream system is ready.

Questions

Does the TallyPrime agent need to run on the server that hosts TrueCommerce?

No. The local agent runs on the same machine or LAN as your TallyPrime instance to access port 9000. TrueCommerce is cloud-based and accessed via SFTP or API from anywhere with internet. ml-connector bridges them by pulling from TallyPrime and pushing to TrueCommerce.

What happens if TallyPrime is not running or the company is locked?

Polling requests will fail and ml-connector will log the error. You must keep the TallyPrime application open and the target company loaded during business hours. ml-connector retries failed requests with backoff, but the user must eventually bring TallyPrime online for the sync to complete.

How does ml-connector handle TrueCommerce's lack of self-serve API tokens?

TrueCommerce credentials (SFTP username, password, or API key) are provisioned by the vendor during account setup and stored encrypted in ml-connector. You provide those credentials once at integration setup, and ml-connector uses them for all subsequent SFTP or Exchange API calls without requiring re-authentication or self-serve token refresh.