TallyPrime and Chargebee integration

What moves between them

Sales invoices created in TallyPrime flow into Chargebee as invoice records. Customer master data (name, billing address) flows from TallyPrime to Chargebee on a schedule. ml-connector polls TallyPrime every 10 to 15 minutes for new or updated sales vouchers and customer ledger entries, checks Chargebee for matching customers by external ID, and creates or updates Chargebee invoices tied to those customers. Reference data such as item prices can be synced once during setup. The flow is unidirectional: TallyPrime to Chargebee. Chargebee's subscription billing state stays in Chargebee; TallyPrime remains the source of accounting truth.

How ml-connector handles it

ml-connector runs a local agent on the same LAN as TallyPrime to reach the port 9000 endpoint, since the HTTP server is not cloud-accessible. It encodes TallyPrime credentials (host IP, company name, optional username and password) and polls TallyPrime's Export Data endpoint with date filters to fetch sales vouchers and customer groups since the last sync. For each voucher found, ml-connector looks up or creates a matching Chargebee customer by external ID, then creates an invoice in Chargebee with the amount, date, and line items from the voucher. TallyPrime uses no pagination, so all matching records return in one response; ml-connector compares returned voucher IDs against last-seen state to detect new records. Chargebee's rate limit (150 to 3500 requests per minute by tier) is managed by queuing invoice writes with exponential backoff on 429 responses. Because TallyPrime supports no native idempotency, ml-connector uses the voucher ID as a deduplication key to ensure duplicate Export responses do not create duplicate Chargebee invoices. Every record carries an audit trail, and failed invoice posts can be replayed once the downstream issue is resolved.

A real-world example

A software-as-a-service company in India uses TallyPrime for accounting and GST compliance and Chargebee for recurring subscription billing across hundreds of customers. Before the integration, the finance team exported customer and invoice data from Chargebee each week, entered the invoices into TallyPrime by hand, and spent days tracking discrepancies between the two systems at month close. With TallyPrime and Chargebee connected, each new customer in Chargebee is automatically added to TallyPrime's ledger, and each new subscription invoice flows into TallyPrime on the same day it is created. Month-end reconciliation now starts with customer counts already aligned and all invoices recorded, cutting manual work by 80 percent.

What you can do

• •Sync customers from TallyPrime to Chargebee, creating new customer records and updating existing ones by external ID.
• •Poll TallyPrime for sales vouchers on a 10 to 15 minute schedule and create matching invoices in Chargebee with correct line items and amounts.
• •Authenticate TallyPrime via optional username and password on the local HTTP endpoint, and Chargebee via HTTP Basic Auth with API key.
• •Manage TallyPrime's lack of webhooks and pagination by polling with date filters and deduplicating by voucher ID.
• •Handle Chargebee rate limits with exponential backoff, respect regional API endpoints, and track a full audit trail of every customer and invoice sync.

Questions

Does the TallyPrime instance need to be in the cloud, or can it run on a local server?

TallyPrime runs on Windows desktops or servers on a local network. ml-connector requires a local agent on the same LAN to reach the port 9000 HTTP endpoint, since TallyPrime is not cloud-accessible. The TallyPrime application must be running and the target company must be open for API calls to succeed.

What happens if a sales voucher in TallyPrime is edited after it has been synced to Chargebee?

ml-connector fetches TallyPrime sales vouchers by date range on each poll. If a voucher is edited, the next poll will fetch it again. ml-connector uses the voucher ID as a deduplication key, so duplicate records will not be created. If you need to update an invoice that was already posted to Chargebee, you can edit it directly in Chargebee or configure a manual replay step.

Which Chargebee objects can be synced from TallyPrime, and which direction does data move?

Customers (from ledger groups or customer masters) and sales invoices (from sales vouchers) sync from TallyPrime into Chargebee. The flow is one-way; Chargebee subscription billing state stays in Chargebee. TallyPrime remains the source of accounting truth. Reference data such as item prices can be set up once during configuration.