An integration KODO could offer to its users

KODO’s requirement came from its role as a software provider. Tally Experts provided integration services that KODO could offer to users as an automated connection with Tally.

The scope extended beyond sending a single transaction type into an accounting system. KODO needed a broad set of Tally-related data to flow in both directions. It also needed to synchronize historical data, so the integration requirement covered existing records as well as the ongoing connection.

This made two-way Tally integration for software providers the relevant use case. The business problem was specific to a platform serving users who needed their software and Tally to exchange information automatically.

Two-way synchronization and included records

Tally Experts implemented two-way Tally data synchronization for KODO. In this project, two-way meant that data could flow between the connected software and Tally in both directions.

The required scope covered:

• 01Ledgers and stock items
• 02Sales and purchases
• 03Expenses
• 04Payments and receipts

That range matters when reviewing the project. KODO needed a connection covering both master records, such as ledgers and stock items, and the listed business transactions. Describing the work only as invoice transfer would leave out much of the stated requirement.

KODO’s requirement combined two-way movement with a defined list of records. When assessing a similar solution, set out the direction required for each record type and the responsibilities of the two connected systems.

Historical data synchronization

Historical data synchronization was a separate requirement in KODO’s project. Users needed the integration to handle data that already existed, alongside the requirement for an automatic Tally connection.

For another software provider, that distinction should be raised when describing the requirement. A request for automatic integration does not, on its own, explain whether existing records must also be synchronized. KODO explicitly needed this capability, and it formed part of the implementation.

A comparable requirement should state which existing records need to be included and the period they cover. Historical synchronization belongs in the initial discussion, because it defines a different part of the scope from the ongoing exchange of new data.

Handling Tally session expiry

KODO also faced a connection requirement linked to a user’s Tally login session, which was limited to a specific duration. The solution needed to account for that expiry rather than depend on the user manually logging in again.

This feature addressed a specific dependency in the automated workflow. The data synchronization capabilities determined what could move between systems, while the re-login feature addressed the session expiry condition affecting the connection.

What the solution enabled

KODO received an automated Tally integration capability it could offer to its users. The implementation covered two-way synchronization, historical data synchronization and automatic re-login after session expiry, across the required business data.

The resulting benefit was a broader automated connection with Tally, with the specified expiry step handled through re-login. Our Tally API integration services can be assessed against a software provider’s own data categories, direction of exchange and connection requirements.