TallyPrime desktop bridge: GST reads and controlled writes
AshnaAI’s Tally tools are schema-only on the server. Execution happens on the user’s desktop. GST paths refuse to infer tax treatment, and write paths prefer review over silent ledger creation. The desktop app is required.
Method: Inspection of Tally tool descriptions and desktop-bridge contracts: GST inference bans, bank-reconciliation auto-create rules, and desktop-owned batching for deletes.
Key findings
- Tally tools are schema-only in the cloud agent. The desktop bridge executes reads and writes against the local TallyPrime company.
- GST tools explicitly forbid inferring tax treatment. Inventory tools forbid inferring accounting or GST/HSN.
- Bank reconciliation sets allowAutoCreateLedgers=false and uses whenMissing=review, so missing parties become a review item instead of a silent create.
Why the desktop owns execution
TallyPrime is a local application. AshnaAI’s cloud agent can reason about ledgers, vouchers, and GST reports, but it does not open the company file. The desktop bridge is the process that can see Tally.
That split is the first finding. Every Tally tool in the agent is a schema: arguments in, structured result out. The desktop verifies writes and handles delete dependencies.
GST and inventory guardrails
GST report, export, exception, and GSTR-2B tools are allowed. Inferring tax treatment is not. Inventory master tools can read or mutate one stock item, group, unit, or godown, but they must not invent accounting or HSN.
These bans are part of the tool contract, not a prompt suggestion. A model that “helpfully” fills a tax field is violating the tool, not completing it.
Controlled writes and review
Bank reconciliation is the clearest write policy. The desktop owns ledgers and vouchers. allowAutoCreateLedgers is false. Missing parties go to review. Capture tools gather missing fields first and tell the agent to follow nextStep instead of resending successful rows.
This is the same human-in-the-loop idea as requestUserInput, applied to accounting masters instead of chat questions.
Limitations
Without the desktop app, Tally tools cannot execute. AshnaAI also does not replace a CA’s professional judgment on GST. The product reads, reconciles, and drafts under review; it does not certify a return.
Website or ERP rebuilds are out of scope. The connector page and the Tally how-to cover setup.
Frequently asked questions
- Can AshnaAI post to TallyPrime from the browser alone?
- No. Tally execution requires the AshnaAI desktop app. The web agent sends a schema-only tool call; the desktop bridge talks to TallyPrime.
- Does AshnaAI invent GST treatment?
- No. GST tools are written to refuse inferred tax treatment. Inventory tools likewise refuse inferred accounting or GST/HSN codes.
- What happens if a ledger is missing during bank reconciliation?
- Auto-create is off. The desktop marks the party for review. The agent is told to continue with mappings instead of inventing masters.
- Can the agent delete Tally masters in one shot?
- Deletes send resolved Master IDs. The desktop batches the destructive work. The agent is not supposed to paginate or re-send successful rows.
- Is this a hosted Tally cloud robot?
- No. Company data stays on the machine that runs TallyPrime. AshnaAI does not move the company file to a third-party RPA farm.
- Where do I start as a CA firm?
- Install the desktop app, follow the Tally connector guide, then use the chartered-accountant solution page for the commercial workflow.
Related
Try this in AshnaAI. Create a free account and install the desktop app when the workflow needs local access.