




















































































Tally ERP is a business-management and accounting solution designed to deliver double-entry bookkeeping, inventory and stock tracking, GST and statutory tax compliance, invoicing and billing, payroll, bank reconciliation, and financial reporting for small and mid-sized businesses, with particularly strong adoption across India, the Middle East, Africa and South-East Asia. Organisations use Tally to keep their books current, manage stock across multiple warehouses and godowns, file accurate tax returns (such as GST, TDS and VAT), generate compliant invoices and statutory reports, and integrate with other business systems via XML, ODBC and Tally Definition Language (TDL) to extend financial and operational workflows.
Have any questions? We’re here to help You
Integration timelines vary by complexity. For standard implementations with no customizations, connections can be live within 1-2 weeks. This includes authentication setup and basic workflow configuration. For implementations requiring custom workflows or specific business logic, timelines typically range from 2-6 weeks depending on the scope. Complex enterprise deployments with multiple systems and custom requirements may take 6-10 weeks. These timelines are significantly shorter than traditional integration projects, which often take 2-24 months.
Yes, through a combination of sandbox environments, test data, and Makini Flows. For testing different data states, use sandbox connections with predefined test scenarios. For testing system behavior like delays, errors, or specific responses, you can build test workflows in Makini Flows that simulate various scenarios. For testing with actual systems, set up dedicated test instances of your target systems. During implementation, we work with you to identify critical test scenarios and ensure your testing environment supports them. For specific edge cases or unusual system configurations, we can help create custom test scenarios.
Yes, customers can connect as many systems as needed. Each connection is independent with its own API token, allowing you to manage multiple ERP systems, CMMS platforms, or other integrations for a single customer. This is common in organizations with multiple subsidiaries, regional systems, or during migration periods when legacy and new systems run in parallel. Each connection consumes connection credits based on the system type and deployment model. There's no technical limit on the number of connections per customer. For customers using multiple instances of the same system (like regional SAP instances), each instance requires a separate connection with its own credentials and token.
The integration role must have the following essential permissions:
• Log in using OAuth 2.0 Access Tokens (Full level)
• REST Web Services (Full level)
Additionally, you should add specific permissions based on your integration needs, such as permissions for Transactions, Lists, Reports, or Custom Records.
