W/P C-4Working paper · Tax audit FY 2025-26

Working paper, row 1
Finding	Vouchers	Date	Amount	3CD clause · Sec.
Cash to one payee over ₹10,000 in a day	Pay 1187, 1188	14 Nov 2025	₹24,600	21(d)(A) · 40A(3)

ComplyEaze Bridge — approve one voucher

Create ONE Receipt in "Demo Traders Pvt Ltd (synthetic)" Company GUID: 3f9a6c1e-52b7-4d08-a1e4-7b20c9d5e386 Company number: 200417 Books from: 1-Apr-2025 Tally: http://127.0.0.1:9000 Date: 12-Mar-2026 Voucher number: Tally assigns it Reference: (none) Narration: (none) Dr 124600.00 "Example Bank Ltd" Cr 124600.00 "Nevrika Agro Foods" Total debit: 124600.00 Total credit: 124600.00 Checked in Tally: every Dr ledger is bank/cash; every Cr ledger holds no money. Batch: bridge-8e41d2a7-0c6b-4f93-b5a8-1d7e93c04f26 Ledgers checked by identity against the build; narrations sent as prepared, nothing added. Do not post a file already imported manually. Pause other edits/imports; keep this company and Tally mode as is until ComplyEaze Bridge finishes. After a timeout, reconcile this batch; do not rebuild or resend it. ComplyEaze Bridge posts now or if asked again within 15 min, unless cancelled, refused or restarted.

Post voucher Cancel

A replica of the approval window’s text as release 0.4.2 words it, taken from the program’s code, not from a screenshot of that release. Release 0.5.0 words the one-voucher window differently, and no replica of that wording has been made; the 0.5.0 section of the changelog says what changed. The frame is that of the Mac window in release 0.3.0. On Windows the same text sits under its own title with Yes, No and Cancel; that window was run once, on a candidate build of 0.4.0: one decline and one approved post. On Windows the window also takes the keyboard: in one test of the published 0.6.0 a typed y approved it while Tally was in front (#1780), so when you ask for a post, stop typing in Tally until you have answered it with the mouse.

Demo book: Demo Traders Pvt Ltd (synthetic), FY 2025-26.

Ask your client's Tally books in plain English.

ComplyEaze Bridge is a local MCP server that lets Claude read your TallyPrime books, and post only what you approve; the README lists the limits. For Indian CAs.

Download for Claude Desktop

Windows x64 and Apple Silicon Macs · Claude Desktop extensionNot yet code-signed, still being developed, and may contain errors: try it on a test company, with backups.What has been run against a real TallyPrime, and what has not.

In development, not in the download The coloured tabs: flagging findings by clause.

Who owes you, and for how long.

Five parties over 90 days, ₹7,86,300 in all.

Reads the trial balance, ledgers, vouchers and outstandings. Ask as you would ask a colleague.

In development, not in the download A finding, tied to its voucher.

Payment 1187 to Demo Packaging Supplies, flagged 40A(3).

One finding per row, cited to its clause. Its accuracy is not yet proven.

From bank statement to a voucher file.

142 statement lines, 139 matched to your ledgers.

3 near-miss ledger names wait for your decision; a voucher file is built once every name in it is exact. ComplyEaze Bridge creates no ledger. It reads password-protected PDF statements from four banks so far.

Nothing posts until you approve it.

One approval for each post, of one voucher or a saved batch; one attempt, no automatic retry.

Here one receipt is prepared as its own one-voucher file and posted. Posting is off by default in a new install. A voucher is posted this way or imported in a file, never both.

The published 0.6.0 package posted one Contra to a synthetic company on one Windows computer on 16 October 2026 (#1780) and read it back; the programs in the published Windows 0.6.1 and 0.7.0 files have each had one read-only run (27 and 30 October 2026, nothing posted); a candidate build of 0.6.0, made by our checks, posted a Journal, a Receipt, a Contra and a Payment and then a batch of three to TallyPrime 7.1 Silver on one Windows 10 computer on 16 October 2026, and a package from the release workflow, from the same source, posted one more Journal there; each read back as posted; a candidate build of 0.4.0 posted one approved Journal on Windows 11 on 1 October 2026.

One receipt, prepared as its own file, is posted. Shown: a replica of the approval window’s text as release 0.4.2 words it (release 0.5.0 words it differently), in the frame of release 0.3.0’s window on a Mac. Windows asks Yes, No or Cancel; that window was run for each of the six posts of 16 October 2026, on one computer, with builds of 0.6.0 made by our checks, and once on a candidate build of 0.4.0. That window also takes the keyboard: in one test of the published 0.6.0 a typed y approved it while Tally was in front (#1780), so when you ask for a post, stop typing in Tally until you have answered it with the mouse. The published 0.6.1 and 0.7.0 packages have not been used to post; the published 0.6.0 package posted once (#1780).

Every voucher checked back in Tally.

Import the file of the other 141 in Tally yourself; ComplyEaze Bridge reads every voucher back. Found in Tally 142 of 142.

Every call leaves a receipt.

Every read and every post, including refusals, is logged on your computer.

What Claude reads goes to your AI provider. Party and ledger names can be shortened or narrations dropped first; amounts are always sent.

Read back, and on record.

Every voucher read back. Every call on record.

At a glance, release 0.7.0

You can ask: who owes you and whom you owe, with ageing of the open bills; the trial balance for a period; the vouchers in a date range, found by number, reference, narration or amount and added up by ledger, month, voucher type, group or primary group (checked on one synthetic book, not a large one); Tally’s own Cash Flow for whole months, shown only when its net total ties to the trial balance (not a cash flow statement under AS 3; tried on two synthetic books); one ledger’s opening, debits, credits and closing; and Tally’s own month-wise Sales or Purchase Register for whole months (not tied to the vouchers; read on one synthetic book); Tally’s own Negative Stock and Negative Ledgers lists for a window (being listed is not a finding; synthetic books only); and the vouchers of one type that Tally marks Uncertain in its GSTR-1 (a Sales type, measured on one synthetic book).
Partly, with limits: profit and loss and the balance sheet, which on a book with stock items are read only when Tally’s own closing stock closes every gap (one synthetic book measured) and which a book with several currencies does refuse; closing stock value per item at a month’s last day and its closing quantity (compared with Tally’s own Stock Summary for an item on a line of its own, the item list’s own for an item inside a stock group), on small books only, checked on two lab books; and a password-protected PDF statement from the banks the Download page lists, read into a file of Payment, Receipt and Contra vouchers that you check and import in Tally yourself. It creates no ledger, it cannot build onto a Cash-in-Hand ledger, a line it cannot place goes to a suspense ledger you name, and it has not yet been run on a real bank statement.
Not in release 0.7.0: GST returns or GSTR-2B matching; making sales or purchase invoices or GST entries; tax-audit flags (one test, the cash share of receipts and payments against the s.44AB(a) limit, is off by default and not yet run against a live TallyPrime); Tally’s Funds Flow and Ratio Analysis reports.
“You can ask” means it answered on the books and builds we ran it on, which the README lists (not every read has its own recorded run); the program in the published Windows 0.7.0 file has had one read-only run against TallyPrime 7.2 Silver, on one Windows computer and one synthetic company on 30 October 2026, started by our test client, not from Claude Desktop; it read Tally’s status, listed the companies and read the ledger masters; nothing was posted; the Mac file has not been run against TallyPrime. Very large books can fail or take longer than the assistant waits, and a book with several currencies is read only in part. What it reads goes to your AI provider (where your client’s data goes). Check any figure you rely on against Tally. The Download page has the longer list and what has not been tried, and the Questions page has the full table.

Set it up in five steps.

In TallyPrime, press F1, then Settings, then Connectivity, then Client/Server configuration. Set “TallyPrime acts as” to Both, note the Port number (usually 9000), save, then close and reopen TallyPrime.
In Claude Desktop, open Settings, then Extensions, then Advanced settings, and click Install Extension. Choose the downloaded .mcpb file. In our test, Claude Desktop showed its own notice that the extension is not verified by Anthropic, then asked us to confirm.
Read the Terms of Use linked in the settings that open (if none open, open Settings, then Extensions, then ComplyEaze Bridge), then tick “I accept the ComplyEaze Bridge Terms of Use”. Until you do, ComplyEaze Bridge does not read from Tally.
Type your Tally port (usually 9000). Leave the Tally host as localhost and leave posting off.
Click Save, then quit Claude Desktop completely and open it again. Ask “Which company is open in Tally?” Claude Desktop may ask your permission before it uses a tool; in our test we chose Allow once.

Download for Claude Desktop

Windows x64 and Apple Silicon Macs · Claude Desktop extensionNot yet code-signed; your computer may warn you.

What it can do: every tool it installs, which of them are read-only, and the two that appear only with posting on.
Where your client’s data goes when Claude reads Tally: what Claude reads goes to your AI provider, and nothing hides the amounts.
Ten questions before you connect Claude to Tally.
Bank statement to Tally vouchers: check the ledger names first.
Who approves a post to TallyPrime, and what is still weak.
Questions, answered plainly and all posts.

In development, not in the downloadFlagging findings by clause.