Questions, answered plainly

ComplyEaze Bridge is an extension for Claude Desktop that lets Claude read the TallyPrime books open on your own computer, so you can ask questions of them in plain words. It is built for CA firms and accountants. It is an MCP server; MCP is the standard way Claude connects to other programs.

It can also prepare Journal, Payment, Receipt and Contra vouchers as a file and, if you switch posting on, post them one at a time after you approve each.

• Who owes you and whom you owe, with ageing.
• The trial balance for a period.
• Profit and loss and the balance sheet. They are worked out from the trial balance. A book with stock items is expected to be refused (none has been measured yet), and a book with several currencies is refused.
• Vouchers in a date range, and the movement of one ledger.
• Purchase and debit-note vouchers that carry a tax ledger: a register of the books, not a GST return.
• Closing stock value per item at 31 March, values only, for small books: a book with many masters of any kind, ledgers included, is refused today, and so is Education mode. Only the year ending 31 March 2026 has been checked.
• Whether vouchers are already in the book, and whether your ledger names match the book, before you post.
• A password-protected PDF statement from State Bank of India, HDFC Bank or Union Bank of India, read into a file of Payment, Receipt and Contra vouchers that you import in Tally yourself.
• It creates no ledger. A statement line whose party you have not mapped, or it cannot identify, goes to a suspense ledger you name, and it asks you about the cash lines it recognises (SBI “ATM WDL” withdrawals and Union Bank “BY CASH” deposits); other cash text is treated as an ordinary party where the parser names one, and otherwise goes to the suspense ledger.

None of the reads writes to Tally.

• Post or prepare sales or purchase invoices or GST entries (it can read them), or create ledgers or other masters.
• Match your books with GSTR-1, GSTR-2B or GSTR-3B, or file anything.
• Flag tax-audit findings: that is in development and not in the download.
• Undo or delete a voucher it has posted.
• Report stock quantities, or give stock values on a book with many masters of any kind.
• Read statements from other banks, or Excel statements.
• Read a book whose base currency is not INR, or a Tally on another computer. A book with several currencies is read only in part.

ComplyEaze Bridge itself needs an exact company and, for most questions, exact dates. Claude, not ComplyEaze Bridge, turns your words into those, so how well it follows Hindi written in English letters, a spelling mistake or a missing date depends on Claude.

Check the first line of every answer for the company and the dates it used. If it does not name them, ask “which company and dates did you use?”

Examples of how people write: “tb dikhao”, “sharma traders ka outstanding batao”, “last week ka cash book”. They are examples, not commands the product recognises. Claude may ask which company or period you mean.

Check the ones you rely on. ComplyEaze Bridge hands over what Tally reports. It reports some limits and refuses some requests, but it does not check your assistant’s reasoning: Claude can pick the wrong company, period or ledger, or misread a figure. A date range can also be called complete when Tally’s own date selection leaves a voucher out.

The Terms of Use (section 8(e); see also 9.1) put the checking on you: check any figure against Tally and the underlying records before you rely on it. The README lists what has been run and what has not.

We found no feature that sends it to us. ComplyEaze Bridge reads Tally over a local connection and hands the answer to the assistant you are talking to. We found no analytics, usage tracking, crash reporting or automatic update check in it.

That comes from our reading of the published code and our own checks. It has not been independently audited. Security and privacy shows what was measured and what was not.

Your AI provider (Anthropic, if you use Claude) receives whatever the assistant reads, as part of the chat: company names, party names, amounts and, when it asks for them, details such as PAN, GSTIN and bank account numbers. Claude Desktop may also keep its own record of the conversation and results on your computer.

The extension’s “Response redaction” setting (off by default) can shorten party and ledger names or drop narrations. Neither choice hides amounts, company names, or PAN and GSTIN numbers. Masking leaves a name written inside a narration or reference as it is; dropping narrations removes narrations but not references. How long the provider keeps what it receives, whether it trains on it, and where it is processed (which may be outside India) depend on your plan and the provider’s own terms.

That is the practice’s decision, not the software’s. The Terms of Use (section 8) say you need your client’s authority to share their data with your AI provider, and that your professional duty of confidentiality and the Digital Personal Data Protection Act, 2023, where it applies, still apply.

Two more things to weigh: the provider sees what the assistant reads, and the log and the saved voucher copies on your computer are not masked or encrypted. Try it first on a test company, with a current backup.

A log of every call: the tool, the time, the company’s Tally identifier, fingerprints of the question and the answer, how many rows came back, and the last requests it sent to Tally. A fingerprint is a short code made from a text; it shows that two texts are identical without keeping either. The log is designed to hold no figures, names or narrations, though sizes in it can hint at the length of a name.

It also keeps copies of the vouchers it prepared or posted (the import journal and an imports folder), the proof of what Tally read back, every row of a bank statement you asked it to read, and a small record, with your operating-system account name, when you record a review of a posted voucher. The copies hold dates, amounts and narrations. None of these files is encrypted. ComplyEaze Bridge does not delete or trim any of them, and removing the extension may leave them.

Do not simply delete the import journal or the imports folder: ComplyEaze Bridge uses them to refuse to send a batch twice. The Privacy Policy (section 7) describes how to archive the whole folder instead. Security and privacy, section 4, lists the files; it was written for release 0.4.0.

Not unless you switch posting on. Reading, checking ledger names, reading a bank statement and preparing a voucher file write nothing to Tally.

With posting on, it can post one Journal, Payment, Receipt or Contra at a time, and only after you approve that voucher in a separate window. No ComplyEaze Bridge tool can approve it for you, but software that controls your screen could click the window, so do not let it. A post never alters or deletes a voucher; a prepared amendment file, when you import it in Tally, changes vouchers ComplyEaze Bridge built earlier. Posting is off in a new install; if you upgraded from an earlier version, check the setting.

ComplyEaze Bridge has no tool to delete or undo a posted voucher; you correct it in Tally. After each post it reads the voucher back and reports what it found. It compares some details, not every one, and a match does not mean the entry is correct.

Two more known limits can send a post to the wrong place: a company renamed to, or loaded under, the target’s name just after the last check, and a ledger renamed and replaced in the same moment. It may not be able to say where the voucher went. The README gives all three limits in full. Take a backup, and try it on a test company first.

In part. The log on your computer shows that a read or a post happened, on which company and when, and its fingerprints let you match a call to its answer. It does not hold the figures.

For a posted voucher, the saved proof holds what Tally read back. The assistant can show you recent log entries on request; otherwise the log is a plain file with no viewer or export.

• A Windows PC (x64), or a Mac with an Apple chip. Intel Macs are not supported.
• TallyPrime on that same computer. ComplyEaze Bridge connects only to its own computer, so a Tally on another PC or a server cannot be reached by typing its address. On a Mac, Tally runs inside a Windows virtual machine (a Windows window made by a program such as Parallels or VMware) with its port forwarded to the Mac itself.
• Claude Desktop, the program (not Claude in a web browser). What Claude reads from your books goes to your AI provider (see “Who else sees it?”).
• In TallyPrime, the HTTP gateway turned on: the setting that lets other programs ask Tally questions.
• In the extension’s settings, “I accept the ComplyEaze Bridge Terms of Use” switched on. Until you do, every tool refuses.

The steps are in the installation guide.

Possibly. In one test by a maintainer on TallyPrime 7.1 (not recorded in the repository), a second computer on the same network opened the Tally computer’s address and port and got Tally’s status answer, “TallyPrime Server is Running”, with no password asked. What keeps other computers out is the firewall of the computer that runs Tally, not Tally itself. We did not test what else the gateway shows.

ComplyEaze Bridge only talks to its own computer. Ask whoever looks after your computers to confirm that the firewall does not allow incoming connections to Tally’s port.

Not known. Its requests can make Tally slow or unresponsive, sometimes until Tally is restarted, and that can affect other people using the same Tally (Terms of Use, section 9.2). Nothing is recorded about how it behaves on a busy Tally with several users.

Two warnings are expected. It is not yet code-signed (it carries no publisher’s digital signature), so your computer may warn you before opening it. Claude Desktop may also show a notice that the extension is not verified by Anthropic.

To check your download, compare it with the .sha256 file (a checksum) on the same release. Each package from 0.4.0 has a build attestation recorded on GitHub, which says which workflow run and commit produced the file; it is not a code signature, no client checks it yet, and it does not show the code is safe.

It does not update itself. Install the newer release from Claude Desktop’s Extensions settings, keep its data folder, and check the posting setting afterwards: an earlier default may still be saved as on.

Remove it from the same screen. Neither action changes Tally’s gateway setting.

Partly.

• Run: reads and posts against licensed TallyPrime 7.1, mostly on made-up companies. On client books: posts in one session, with the import requests captured for nine of ten batches (a development build, not the published package), and reads through the published 0.3.0 package in one session reported by a maintainer, with no logs kept.
• Not run yet: the package of the latest release against a live TallyPrime; an earlier package, 0.3.0, was run for reads. Each release is built, started, and checked for its tool list and a sample bank statement, without Tally.

The README lists each run, the Tally edition, what was recorded and what was not.

Most of the runs the README lists used licensed TallyPrime 7.1, Silver and Gold. Research runs also used TallyPrime 7.1 in Education mode and TallyPrime Edit Log 7.0 (also in Education mode), and some reads are refused in Education mode. Tally.ERP 9 has not been tried. ComplyEaze Bridge checks the Tally product and mode before it reads.

ComplyEaze has not set a price for ComplyEaze Bridge and does not sell licences to it: there is no account with us, subscription or licence key. You bring TallyPrime on your own licence and Claude Desktop on Anthropic’s plans. What Claude reads goes to Anthropic under your account, and through ComplyEaze Bridge, ComplyEaze does not receive it (sections 4 to 6 of the Privacy Policy). We have not decided whether to charge for anything in future.

Before client work, read sections 14 and 4.4 of the Terms of Use.

ComplyEaze Bridge is made by SPMS Comply Eaze Solutions LLP (ComplyEaze) of Bhiwadi, Rajasthan, and is open source under the Apache License, Version 2.0.

The Terms of Use set out who is responsible for what, including limits on our liability. Read sections 9, 14 and 15 before you use it on client books.

Open an issue on GitHub. Say which step you were on and what the screen showed, and do not send client names or figures. Something that looks like a security problem goes to the private route in SECURITY.md, not to a public issue.