Bank to Tally Agent

Bank statement in. Classified vouchers in Tally.

Upload the statement exactly as your bank exports it. The agent reads every line, checks the running balance, matches each entry to the right Tally ledger from rules it learns once per party, shows you only the lines it could not decide, and posts the approved vouchers into TallyPrime. Every run ends with one number: Tally closing balance equals bank closing balance.

Watch it classify a statementSend one statement, get it back classified
Built on Tally’s official interfaceNothing posts without approvalEvery voucher traceable to a statement line
bank-to-tally / ICICI_Aug.xlsposting
1,319 lines read · layout: ICICI current accountparsed
Running balance checked on every rowpass
1,241 lines matched by saved rules and party names94%
78 lines need a ledger · 5 new partiesreview
2 duplicates of already-posted vouchersskipped
Approved → 1,317 vouchers posted to TallyPrime0 errors
Tally closing 18,635.00 · bank closing 18,635.00matched
Who approved what, logged per vouchersuggests, never decides
See it working

Watch it classify a statement — and hand you only the lines that need a decision.

Twelve lines from a sample statement, in the bank’s own narration format. Each line gets a ledger, a confidence and the reason. The two or three it cannot decide land on the right, wait for a pick, and become rules.

ICICI BankStatement_XX4471_Aug.xlsinto ICICI Bank A/c 4471
Parsed
Balance check
Classified
Posted
Matched
waiting…
What you decide0 need you
Everything else posts on one approval.
TallyPrime · Ledger Vouchersconnected
Closing balance in Tally—Closing balance on the bank statement18,635.00waiting
How it fits together

Your bank, our agent, your Tally. Nothing in between that you do not control.

Your bankExcel / CSV export Bank to Tally Agentparse · balance check · classify Rules it has learnedsaved picks · bank codes · ledger names Your accountantapproves exceptions, once Connectoron Tally PC TallyPrimeon your PC Statement travels encrypted, then is purged. Only what was approved leaves this box. Outbound only. Nothing reaches Tally from outside. No connector? You get a file that Tally imports in one step.

The decoder: party pulled from the narration, bank code that already says what the line is.

Not another importer

Tally can import the statement. You still type the ledger for every line.

TallyPrime’s bank import and the Excel-to-Tally utilities move rows into Tally. They do not know that UPI/KUMAR PACKAG is a supplier, that CMS/P1007 is advertising income from abroad, or that the same party paid you fourteen times last year. So an accountant still walks every line and picks the ledger by hand. That picking is the work. That is what the agent removes.

Import utilities and Tally’s own import

  • Every line lands in a suspense or bank ledger; you classify each one by hand
  • No memory: the same party is a new decision every month
  • One company, one Tally window, one PC at a time
  • Re-import the same file and you get the same vouchers twice
  • Errors surface weeks later at reconciliation

Bank to Tally Agent

  • Each line arrives with a ledger already suggested and a confidence you can see
  • Every approval becomes a rule; the second month asks far less than the first
  • Fifty client companies from one screen, from anywhere, into each client’s own Tally
  • Duplicate guard on date, amount and bank reference
  • Closing balance matched to the paisa at the end of every run, on screen
What it does

From the bank’s export to a month you can sign off.

Reads the bank’s own file

Excel or CSV as downloaded. Layout detected per bank: ICICI, HDFC, SBI, Axis, Kotak first; more on request.

Balance check on every row

Each row’s balance must equal the previous balance plus the movement. One broken row stops the run and names itself.

Narration parsing

UPI, NEFT, IMPS, card, cheque, charges, interest, remittance codes. The party name is pulled out of the bank’s string.

Ledger matching

Saved rules first, then bank-code rules, then fuzzy match against the ledger list read from your Tally. Never a ledger that does not exist.

Exceptions only

New parties, low-confidence matches and duplicates are the only lines shown for a decision. The rest wait for one approval.

Posts to Tally

Receipt, Payment and Contra vouchers created inside Tally itself, with the bank narration and reference filled in.

Duplicate guard

Same date, amount and bank reference as a posted voucher is never posted twice, even if the same file is uploaded again.

Posting log

Which file, which row, which voucher, who approved, when. The auditor reads it backwards from any voucher.

How a month runs

Upload, review, post, match.

01 · Upload

Drop the statement from net banking. Layout detected, rows parsed, balance checked, in seconds.

02 · Review the exceptions

Pick a ledger for the few lines the agent could not decide. Each pick is remembered as a rule.

03 · Post

One click. Vouchers go into Tally through the connector on the Tally PC, or as a file you import yourself.

04 · Match

Tally closing balance against the statement’s last line. Equal to the paisa, or the run tells you which row is not.

Measured, not estimated

A full year of a real account. Two minutes. Matched to the paisa.

Before offering this we ran it on our own books: one ICICI current account, twelve months. The parser passed the balance check on every row, every voucher posted without an error, and Tally’s closing balance equalled the bank’s. That is the test we run on your first statement too, and we show you the screen.

Bank statement 18,635.00 TallyPrime ledger 18,635.00 Dr matched
0statement lines, one real account, Aug 2025 to Jul 2026
0vouchers posted into TallyPrime through its interface
0posting errors. Zero exceptions, zero ignored lines.
0closing balance in Tally, equal to the bank’s closing line

What we do not promise: that every line classifies itself in month one. Rules are learned from your approvals, so the first month asks more questions than the third. We say that in the proposal.

Run it on one of your statementsWatch the demo
Guardrails

Accounts are the one place a confident guess is worse than a blank.

The agent suggests. A person approves. Nothing reaches the books any other way, and the auditor can trace every voucher back to the statement line it came from.

Nothing posts without approval

Suggested ledgers wait for a yes. Low-confidence lines are shown, never auto-posted.

Only ledgers that exist

The ledger list is read from your Tally. New ledgers are created only when you say so.

Books never leave the office

The connector runs on the Tally PC and talks to Tally locally. It only ever calls outward. Nothing on the internet can reach your Tally.

Statements encrypted, then purged

Stored encrypted for a retention window you choose, 30 days by default, then deleted. Never mixed between clients.

Every voucher traceable

Narration carries the source file and row. The posting log records who approved, and when.

Undo is one batch

Each posting is a batch. A wrong rule is reversed as one batch in Tally, not voucher by voucher.

YOUR OFFICE TallyPrimeon this PC Connectortray app one PC, your books stay here No inbound port.No router change. outbound HTTPS only nothing comes in iHayz service queue · rules · log statement encrypted purged after 30 days
Connector

Your Tally never faces the internet. The connector only ever calls out.

A small tray program on the PC that runs Tally asks our service every few seconds whether approved vouchers are waiting, downloads them, posts them to Tally on the same machine, and reports back. It makes the same kind of connection a browser makes. Nothing is opened on your router, and nothing on the internet can reach Tally.

If Tally is closed or the PC is off, the queue waits. The moment Tally opens with the company loaded, everything drains, in order, with the log to prove it.

Outbound HTTPS onlyOne key per company, revocableQueues while Tally is closedImport-file fallback
Questions

Before you ask.

Does it need access to our Tally from the internet?

No. A small connector runs on the PC that runs Tally and talks to Tally on that same machine. It only makes outward calls to our service, the way a browser does. Nothing is opened on your router and nothing on the internet can reach Tally. If you prefer no connector at all, the agent gives you a file that Tally imports in one step.

Which Tally versions work?

TallyPrime, any release, licensed or rental. Tally.ERP 9 works too. One setting inside Tally has to be switched on once; we walk you through it in writing.

Will it post something wrong into the books?

It cannot post on its own. Every line carries a suggested ledger and a confidence; you approve the batch. Lines below the confidence line are shown for a decision, never auto-posted. A wrong batch is reversed as one batch.

How does it know which ledger a payment belongs to?

Three ways, in order. Rules you have approved before. Bank codes that already say what a line is: charges, interest, RBI purpose codes on foreign receipts. Then a match of the party name in the narration against the ledger names read from your Tally. Anything that does not clear the bar is an exception for you.

Which banks?

ICICI is live. HDFC, SBI, Axis and Kotak are next in that order. Any other bank is a one-time layout built from your sample file. Every layout passes the same running-balance check before a single voucher is created.

Where do our statements go?

To our servers, encrypted, kept for the retention window you choose and then deleted. Your full accounts never leave your Tally; only the statement, the ledger names and the balances travel. Clients are isolated from one another.

We keep books for forty companies. One login?

Yes. One workspace for the firm, one company per client Tally, one screen for all of them. The Firm Plan covers unlimited companies, and the rule library is shared across the firm so a supplier learned in one client’s books is recognised in another’s.

Knowledge base

How this works in practice.

Your data, your accounts, your keys · How an engagement runs, start to finish · How pricing and scope work

Send one bank statement. We return it classified, with the balance proof.

Within one business day you get your own statement parsed and matched, the exceptions it would have asked you about, the price for your firm, and the date it could be running.

Send a statement