Connecting an agent to Tally, Zoho and your ERP

Where the data really lives

A mid sized auto components maker in Rajkot runs its accounts on TallyPrime, its sales pipeline on Zoho CRM, and its production planning on an older ERP that a local vendor customised years ago. Purchase orders start in the ERP, supplier invoices are posted in Tally, and customer follow ups happen in Zoho. Nothing talks to anything else except through Excel exports that someone in accounts prepares on Monday mornings.

When this company asks for an invoice matching agent, most of the real work is in the plumbing: getting the agent to read the purchase order from one system, the goods receipt from another, and to prepare a voucher in a third, without anyone handing it a spreadsheet.

Start with a read and write map

Before connecting anything, draw a simple table with three columns: the system, what the agent needs to read, and what the agent may write.

For the invoice matching agent it might look like this.

• ERP: read purchase orders and goods receipt notes. Write nothing.
• Tally: read ledgers, vendor masters and existing vouchers. Write purchase vouchers, but only as drafts or into a holding company for review.
• Zoho CRM: read nothing for this agent.
• Email inbox: read invoices from one shared address. Write replies only to the accounts team, never to suppliers.

This map becomes the agent's permissions. Anything not on it, the agent cannot touch. Most of the risk in connecting AI to business systems comes from giving it broader access than the task needs, usually because it was quicker to set up.

Connecting to Tally

TallyPrime can exchange data over XML on a local HTTP port, and it also supports ODBC for reading. In practice this means the machine running Tally, often a desktop in the accounts office, has to be reachable by the agent. There are three common set ups.

A small connector inside the office

A lightweight service runs on a machine in the same network as Tally, talks to it over the local port, and sends only the required data out over a secure connection. This keeps Tally off the public internet. It does depend on that machine being switched on, which is a real issue in offices where the accounts PC is shut down at six.

Tally on a server or a hosted provider

If your Tally already runs on a server or with a hosting provider, the connector sits next to it. This is more reliable and is what we suggest once an agent becomes part of the daily routine.

Exports as a starting point

For a trial, scheduled exports from Tally into a shared folder are acceptable. The agent reads the files. It is slower and less current, but it lets you test the agent on real data before investing in a live connection.

Whichever route you take, decide carefully about writing. A wrong entry posted into the live company affects GST returns and the books. We recommend that the agent writes vouchers as drafts that a person reviews and accepts before they post.

Connecting to Zoho

Zoho's applications, including Zoho CRM, Zoho Books and Zoho Desk, offer REST APIs that use OAuth for access. You create a client in the Zoho developer console, grant only the scopes the agent needs (for example read access to leads, or write access to notes but not deletion), and store the tokens in the platform's secure settings, never inside a prompt.

Zoho applies API call limits that depend on your edition and number of licences. An agent that checks every deal every five minutes can use up the day's allowance before lunch. Pull changes on a sensible schedule, or use webhooks so Zoho tells the agent when a record changes.

Connecting to a larger or customised ERP

Most current ERPs, including SAP Business One, Microsoft Dynamics 365 and Oracle NetSuite, expose web services or REST APIs. Older or heavily customised systems often do not. For those, the options are usually:

• Read from a reporting database or a read only replica, if the vendor provides one. Never point an agent at the live production database with write access.
• Use the ERP's own import formats for anything the agent needs to create, so that the ERP's validations still run.
• Ask the original vendor for a small API layer. This is sometimes the cleanest route and often cheaper than people expect.

Whatever the route, the agent should follow the ERP's normal rules. If a purchase order needs approval above a limit in the ERP, the agent should not be able to skip that.

Keep identities and credentials clean

Create a separate user for the agent in each system, with its own name, so that every change it makes is visible in that system's own audit trail as made by the agent. Do not reuse a staff member's login. When the staff member leaves, the agent breaks, and you lose the ability to tell who did what.

Store credentials in the platform's secret store, rotate them on a schedule, and make sure the agent's prompts and logs never contain them.

Test with real but safe data

Ask for a copy of the Tally company or a test environment in the ERP. Run the agent against last month's invoices, where you already know the right answers. Compare its matches with what your team actually posted. Only connect to live data once the results on old data are good enough for the reviewers to trust.

Limits to plan for

Integrations are usually the slowest part of an AI project. Customised ERPs, Tally installations on office desktops, and missing APIs can each add weeks. Data quality problems also surface here: duplicate vendor masters in Tally, items named differently in the ERP and on supplier invoices, GSTINs missing from half the vendor records. The agent will expose these. Budget time to clean them.

Some connections need custom work. If your ERP needs a new API layer or a connector built from scratch, the Code Colonies team can build it on 2good terms, at INR 199 an hour with a minimum of 150 hours and payment after you accept the work.

Checklist

• A read and write map for every system the agent touches
• A separate user for the agent in each system
• Credentials kept in a secret store, out of prompts and files
• Writes go to drafts or a review step first
• API limits checked for Zoho and other cloud systems
• A test run on last month's data before going live

Integrations lists the connectors and adapters available on AksharAI and how custom ones are added.