TallyPrime 6.0 added a live bank feed. Four banks are actually on it

TallyPrime 6.0 shipped a genuinely new capability — a live, in-app connection to your bank, not just a statement you import afterwards. But "which banks does it support" gets answered two different ways depending on where you read it, and the setup itself needs a Tally.NET ID and a mobile OTP before you ever touch a bank account screen. This is the setup in order, the bank list as Tally's own documentation states it today, and the four things it still won't tell you about a settled invoice.

Connected Banking vs Auto BRS — these are two different features

TallyPrime has shipped a bank-reconciliation feature since before Release 6.0: Auto BRS, which matches an already-imported statement file against your vouchers, ledger by ledger. That workflow is covered separately — it's import-first, works with Excel, CSV or MT940 files, and Tally documents it against a much larger bank list.

Connected Banking is new, and different in kind. Per Tally's own documentation, it's a live, in-app link to your bank account — no file to export or import for the two read functions. Once connected, TallyPrime can, for a supported account: Get Balance (current balance, on demand), Get Bank Statement (pulled directly, not uploaded), and Send Online Payments (initiate a payment from inside Tally). It requires TallyPrime Release 6.0 or later. Confusing the two is the fastest way to end up on the wrong support page when something doesn't work — a "statement import" error and a "connected banking" error come from entirely different parts of the product.

Video walkthrough by Tally Solutions — embedded with credit; the guide above is our own.

Setting it up: prerequisites, then the login flow

Connected Banking isn't a toggle you flip on a bank ledger — you first authenticate the whole feature against your Tally.NET identity, and only then connect individual accounts. Per Tally's documentation, you need:

• TallyPrime Release 6.0 or later. Earlier releases don't carry the feature at all.
• A valid Tally Software Subscription (TSS). Connected Banking sits behind an active subscription, not a one-time licence.
• A Tally.NET ID — the registered email under your licence.
• A 10-digit mobile number linked to that Tally.NET ID, for OTP verification.
• An internet connection — Tally's documentation recommends 3–5 Mbps.

There's a second route if the mobile-linking step gives you trouble inside Tally itself: log in at the Tally Solutions customer portal (customer.tallysolutions.com), open My Profile, and update the mobile number under Connected Banking Services there — it's the same OTP verification, done from a browser instead of the application.

Which banks actually support it — resolving the conflict

This is the part where sources disagree, and the disagreement is real: some independent walkthroughs describe TallyPrime's connected-banking coverage using bank-count figures well over a hundred, and name banks like HDFC as supported. Tally's own live "List of Banks Supported" documentation does not say that — and it separates three things that third-party posts often collapse into one:

If your bank isn't one of the four, Connected Banking simply isn't an option for that account yet — Auto BRS statement import is the fallback, and it's the more broadly supported feature regardless.

Four things that trip people up

"Your bank statement isn't in a valid format"

On Auto BRS import, Tally expects the file in one of a small set of structured formats — Excel, CSV, MT940 or Delimited. A statement re-saved from a PDF, or an Excel file with merged header rows or extra summary rows above the transaction table, is the most common cause of this error. Re-export a clean file from net banking rather than hand-editing headers on the last one that worked; a manually patched file is the single most reliable way to trigger this error again next month.

PDF statements aren't supported, full stop

None of Tally's documented import or feed formats is PDF. If your bank's only self-serve export is a PDF statement, you need an Excel or CSV export instead — most net-banking portals offer one alongside the PDF, even if it's not the default download button.

A batch payment is allocated in the voucher, not on the bank line

TallyPrime does let you split one payment across several bills — Bill-wise Details, using Agst Ref in the payment voucher, lets you allocate a single payment to multiple outstanding bills, in full or in part, per bill. What the bank-reconciliation layer doesn't do is carry that per-bill allocation onto the matched bank line, or tie it to the vendor GSTIN on each invoice: Connected Banking and Auto BRS both match a bank line to a voucher, not to the individual bills allocated inside it. Where one transfer covers several bills from the same vendor, the voucher already knows the split — the bank feed doesn't surface it.

"Does it work with my bank?"

Check the table above before you spend time on setup. Tally's own pages aren't even internally consistent on the count — the Connected Banking overview page names three banks, the bank list and FAQ name four — so the roster clearly does move, but Tally publishes no roadmap for when a given bank might be added. Plan around Auto BRS for any account that isn't currently listed.

What a synced bank line still doesn't tell you

Say Connected Banking pulls your statement automatically and TallyPrime matches a line to a voucher — clean, no manual import, no format error. That confirms one thing: the payment reached your bank account and corresponds to an entry already in your books. It confirms nothing about the GST side of that same payment:

Working that out across a purchase register with more than a handful of vendors, invoice by invoice, every month, is painful to do manually — not because any single check is hard, but because it means holding the bank feed, the purchase register and the GST portal open together, line by line, and Connected Banking was never built to do that; it was built to get the bank data into Tally faster.

What Recoup does with the bank data once it's in Tally

Recoup picks up from where Connected Banking (or Auto BRS) leaves off. It reconciles your Tally purchase register against your GSTR-2B, names the specific vendor and invoice behind a payment rather than just the matched voucher, and tracks the Rule 37 180-day clock per invoice on the amount still unpaid. Whichever way the bank data arrived in Tally, the GST-side questions above are the ones that still need answering — and they're the ones a bank feed, however live, was never designed to reach.

Related guides