Bank statement to Tally vouchers: check the ledger names first

The single biggest reason a whole import gets rejected, our documentation says, is that nobody checked the ledger names against the book.

ComplyEaze Bridge is an extension for Claude Desktop that reads the TallyPrime on your own computer. Before it builds a voucher file from a bank statement, it checks the ledger names in your mapping against your live book. Take a made-up book with two ledgers, “Demo Traders Pvt Ltd” and “Sample Hardware (9876543210)”. Suppose the mapping names four ledgers. Each comes back as one of four things.

Status. ComplyEaze Bridge is still being developed and is not yet code-signed, and our README records no run of this tool itself on a real bank statement, so try it on a test company, with a backup. If you have 0.3.0 or 0.4.0, remove it and install 0.4.1 or later first. What Claude reads from a statement goes to your AI provider; “Your client’s data”, under the limits, says what.

Six steps, and who does each

1. Read the statement

You tell Claude which PDF to read, which file holds its password, and the last digits of the account number. Keep both files on the computer’s own disk, not on a network drive, and on Windows restrict who can read the password file yourself.

The tool refuses the whole statement unless the account number ends with the digits you gave and the running balances, the closing balance and the debit and credit totals (where the statement prints them) match the figures you supply. These balance and total checks are arithmetic on the figures you supplied. They do not tell you whether a party or a ledger is right.

The full list of proposed vouchers goes into a file on your computer, every row, unmasked, and it stays until you remove it (section 7 of the Privacy Policy says how to archive it). Claude gets a summary, and it goes to your AI provider like any other result; “Your client’s data”, under the limits below, says what the summary holds.

2. Say who each party is

Claude writes a mapping: for each name printed on the statement, which ledger it is. You decide. A party you leave out, or one the tool cannot identify, goes to the suspense ledger you name, tagged so you can find it later. A transfer that another account’s Contra already carries can be skipped.

Cash gets its own question. Only SBI “ATM WDL” withdrawals and Union Bank “BY CASH” deposits are recognised as cash. For those, it asks what the cash was for, and it will not build the file until you have answered every one. “I don’t know” is an answer; it goes to suspense, tagged.

Other cash text is not recognised, so it gets no question. It is treated as an ordinary party, or goes to suspense as unidentified. That covers, for example, SBI cash deposits and HDFC cash text. Look for those lines yourself.

3. Check the ledger names against the book

This is the step our documentation is talking about. The ledger names in your mapping are what ComplyEaze Bridge checks: it reads your live ledger list and compares. The spelling printed on the statement is not checked unless Claude passes it in. The check goes after the biggest cause the documentation names. It does not promise Tally will accept the file.

A long number, as in the example above, counts when it is a run of eight or more digits standing alone, or a code of at least eight letters and digits with at least three digits and two letters. Dates and period labels do not count.

Fix the names, then go on. The assistant can misread a name or pick a wrong ledger, so you choose the ledger and you check the choice.

4. Prepare the file

It writes a voucher file on your computer, with Payment, Receipt or Contra vouchers. It sends it nowhere. Where the statement carries a bank reference, the tool writes it into the voucher’s narration, and the files have no separate voucher number or reference.

It refuses to build a row it already knows it sent or found posted. That knowledge has holes.

So read a batch you imported by hand back straight after you import it, and look in Tally before you import again.

5. Get it into Tally

Import the file yourself. Open the right company, then Gateway of Tally, Import, Vouchers. ComplyEaze Bridge does not do this step. It can post a voucher itself, but only one per batch, so that route does not suit a statement with several rows (the limits are below).

6. Read it back, then look in Tally

Ask Claude to read the batch back from Tally. A read-back asks Tally to show what it now holds. ComplyEaze Bridge compares the date, voucher type and entries and reports anything missing, different or duplicated. A match does not mean the entry is correct, complete or compliant, and it does not compare every field. Open Tally, check the bank ledger against the statement, and look at what went to suspense.

Before you try it

You need TallyPrime and Claude Desktop on the same computer, Windows (x64) or an Apple Silicon Mac (on a Mac, TallyPrime runs in a Windows virtual machine, with the connection forwarded locally). You need ComplyEaze Bridge installed, with the Terms of Use accepted in its settings, the company open in Tally, and a password-protected PDF statement from SBI, HDFC or Union Bank of India. No other bank is read.

Limits to know before you rely on it

Posting is one voucher per batch.

The published extension does not turn on batch posting, so it refuses a batch of more than one voucher, and a batch built from several statement rows holds several.

If you post a single voucher, it waits for you.

Posting starts off, and an upgrade may keep it on, so check the setting. Each voucher waits for your approval in a separate window, and the approval lasts at most fifteen minutes. No ComplyEaze Bridge tool can approve it, but software that can control your screen could click the button, so close such software first.

Leave companies and ledgers alone until the post lands.

A rename, replacement or reload at that moment can send the voucher elsewhere.

ComplyEaze Bridge cannot undo a posted voucher.

You fix mistakes in Tally.

Party amounts land On Account.

Bill-wise allocation is not supported. It does not post sales, purchase, tax or inventory entries.

Education mode and the approval window.

On TallyPrime Education, voucher dates must be the 1st, 2nd or 31st, and we have not yet run posting on Education. We have not run each way of declining in the Windows approval window (we tried one) in a controlled test.

Large books.

Reads on very large books can fail or take longer than the assistant waits. Requests can make Tally slow or unresponsive, sometimes until it is restarted, including for other people on a shared Tally.

Your client’s data.

What Claude reads goes to your AI provider, which for Claude is Anthropic. From a statement, Claude gets each party’s name as printed, how many rows, what is proposed, the figures you gave it and, for each cash line it asks about, the date, amount and party. Later steps can return dates, amounts and ledgers; a batch of one voucher shows its date and amount. The Privacy Policy lists bank-statement contents among the things that can be sent. A setting can mask party names. It is off by default and it never masks amounts. You need your client’s authority to use their data this way, and your confidentiality duties still apply.

The README lists the rest. Nothing here is accounting, tax, audit or legal advice.

To try it on a test company, start from the download page and its release notes.

ComplyEaze Bridge is not a product of, or endorsed by, Tally Solutions, Anthropic or ICAI. Email contact@complyeaze.com · Questions and answers · Download and release notes · Terms of Use · Privacy Policy · Security and privacy · Security policy