How do I turn a bank statement PDF into TallyPrime vouchers?

With ComplyEaze Bridge in Claude Desktop, you give Claude a password-protected statement PDF from State Bank of India, HDFC Bank or Union Bank of India. ComplyEaze Bridge reads it and proposes Payment, Receipt and Contra vouchers. Once every ledger name is exact, it writes them to one file that you import in TallyPrime yourself. Preparing the file writes nothing to Tally. Checked against release 0.6.0 on 16 October 2026. This page describes that release and changes with later ones; the Releases page says which release is the latest.

What you decide, and where

ComplyEaze Bridge tells Claude to ask you before it prepares anything and, with posting on, before it posts anything, and never to choose a ledger for a voucher itself. It cannot check who gave an answer, so read the choices Claude shows you before the file is built.

The ledger for every party. A transaction whose party is unmapped, or cannot be identified, goes to the suspense ledger you name, and its narration carries a note to reallocate it.
What a cash line was for. For the cash lines it recognises (SBI ATM withdrawals and Union Bank cash deposits) Claude is told to ask you. The file is not built until an answer for each is supplied.
The import. You import the file in TallyPrime yourself. That step puts the vouchers in your books.
Posting, if you turn it on. Posting is a separate setting, off by default. When it is on, the extension posts one voucher, or a saved batch of 2 to 50, after a window on your computer asks you (for a batch, the window shows a summary), and a declined or unanswered window posts nothing. A statement’s file of 2 to 50 Payments, Receipts and Contras can be posted as a batch or imported by you; a batch of more than 50 is refused for posting, so prepare it in parts or import it yourself. Use one way for a batch, import or post, and not both: a hand import is not checked.

The steps

Have the statement and its password ready. The tool asks for the path to a small text file that holds the password, and never returns the password. Keep the statement and that file on a local disk, not a network drive. On a Mac the file must be readable by you alone; on Windows nothing checks who else can read it.
Tell Claude the bank (SBI, HDFC or Union Bank of India), the bank’s ledger in Tally, a suspense ledger, the last digits of the account number (at least four), and the opening and closing balances. You supply both; a Union Bank of India statement prints neither. The reader checks every running balance against them. For SBI and HDFC it also needs the statement’s total debits and total credits.
ComplyEaze Bridge refuses the whole statement if a transaction cannot be read, a running balance does not follow from the one before, or the totals do not match; no line is dropped without your choice (you can map a party to be skipped, and a date window leaves other rows out). A PDF with no text to read, such as a plain scan, is refused. These checks cover dates, amounts, the account line and, for Union Bank of India, the page footer. Nothing proves the narration or reference text, so read what it proposes.
Choose the ledgers. Claude lists each party as the statement prints it. For each, you say which ledger it belongs to, that it is a transfer between your own accounts (a Contra voucher), or that it is to be skipped, naming the ledger of the other account (a transfer between two of your own accounts is booked once, as a Contra from one statement and a skip on the other, and ComplyEaze Bridge lists each skip whose Contra it cannot find). ComplyEaze Bridge creates no ledger, so each ledger must already exist in Tally.
Check the names against the book. Only a name that matches a ledger in Tally exactly is built into the file; a near miss is shown and never changed for you. A party ledger that keeps bill-by-bill details is refused until an approval for that party is passed with the request. That approval is a value Claude supplies; it does not prove that you agreed. Tally is expected to record those vouchers On Account (measured for one party on one book), and you match them to bills by hand.
Build the file. Each voucher is a Payment, a Receipt or a Contra with two entries: the bank ledger and the ledger you chose. Its narration holds the payment mode, the reference, the ledger (for a suspense line, the party as printed), the date and the account label; for a mapped ledger it also names the party as the statement printed it, and ComplyEaze Bridge adds a tag of its own. The file is written on your computer and ComplyEaze Bridge tells you where. On a Microsoft Store install of Claude Desktop, release 0.6.0 shows the folder Windows reports for the file (seen on one computer). If Tally’s Import screen does not find it at the path shown, the 0.5.1 notes in the changelog say where to look.
Import the file in TallyPrime with the right company loaded: Gateway of Tally, then Import, then Vouchers.
Ask Claude to read the batch back. ComplyEaze Bridge reads the same dates from Tally and compares each voucher’s date and type and each entry’s ledger, amount and side. It does not compare the narration or the party. It reports the batch as verified only when every voucher is found and matches, none is cancelled or optional, and none is duplicated.

What goes to your AI provider

The statement reader writes the rows (dates, amounts, references and narrations) to a file on your computer, unmasked and unencrypted, and does not return them. The built file and the import journal on your computer hold the vouchers in full. Some of the content still reaches Claude. It receives each party’s name as printed with the number of its transactions, the last four digits of the account number (sent under every setting), the figures you typed, the path of the file it builds (which can include your computer user name), and, for each cash line it asks about, the date, the amount and the party. The totals and date span of a built file, and each voucher’s transaction id (which carries its date), reach it too, and so do the dates and amounts of a party’s transactions when a bill-by-bill ledger is refused. What it reads from your books afterwards, amounts included, goes to your AI provider as well. See where your client’s data goes.

The Response redaction setting, off by default, takes one value: shorten party and ledger names and bank account numbers, or drop narrations. It does not hide amounts, dates, references or the last four digits. From release 0.5.1, a voucher built for a mapped ledger carries the party’s name as the statement printed it in its narration; shortening names does not shorten it, and only dropping narrations removes it.

What has been tested, and what has not

Every statement PDF in the reader’s tests was generated, with invented figures, and encrypted with RC4 only; real statements often use AES, which was not tested. The SBI and HDFC layouts were copied from real statements, and the Union Bank of India layout was described from one real statement without its figures.
A file built for six vouchers by a build of release 0.5.1 was imported by hand into TallyPrime 7.1 Silver on one Windows 10 computer, and the read-back found all six. That build was not the published file, and nothing was tried on other Windows versions or other Tally editions.
The following of a transfer between two of your own accounts from one statement to the other was run once, in the lab on 15 October 2026, on one synthetic company, with the Contras imported by hand; which banks print the same reference on both statements is not measured.
It has not yet been run end to end on a real bank statement. A real HDFC statement print was refused by the reader on 6 October 2026, and the change made for it has not been tried on a real statement.
The tool always asks for a password file; a PDF with no password has not been tried.

Check what it proposes before you import it, and try it on a test company first, with a current backup.

What it does not do

Read statements from other banks, or Excel or CSV statements.
Use a Cash-in-Hand ledger as the statement’s bank ledger, or make Journal vouchers from a statement.
Recognise cash text other than SBI “ATM WDL” and Union Bank “BY CASH”; other text goes to the suspense ledger or is treated as an ordinary party.
Create a ledger, or undo a voucher that was posted.

TallyPrime has its own Bank Statement import, for the statement formats Tally lists for each bank. We have not run the two side by side, and ComplyEaze Bridge is not made by, or affiliated with, Tally Solutions.