Connecting Zoho Books to your Indian bank feed — and making the match hold up

Getting the feed connected is the easy half. The half that matters for tax is what happens after the transactions land — whether each payment is matched to a purchase invoice, dated, and traceable. That match is the evidence base for the Rule 37 180-day test and for the payment side of your ITC file. This is the setup, in order, and the three places it usually breaks.

Do this first: decide feed or import, per account

Zoho Books offers two ways to get bank data in. Pick one per bank account, not once for the org:

• Direct bank feed — Zoho pulls transactions on a schedule after you authorise the connection. No file handling.
• Statement import — you export from net banking and upload the file. Manual, but it works for every bank and every account type.

Do not spend a week trying to force a direct feed on an account where it isn't offered. A disciplined weekly import beats a feed that silently stops refreshing — and a feed that silently stops refreshing is the failure mode that costs you a month-end.

As at July 2026, the banks Zoho names for connected banking in its India help documentation are ICICI Bank, Axis Bank, SBI, Kotak Mahindra Bank, HSBC, Standard Chartered and Yes Bank. That roster changes without announcement, and a bank absent from the documentation can still appear in the in-app bank search, so treat the table above as an order of attempt, not a specification. The authority is Zoho's own Banking help section plus what the Add Account search actually returns for your account — nothing else, including this page, is current by the time you read it.

The five setup steps

1. Create the account in Zoho before you connect it

Add the bank or credit-card account under Banking with the correct account type and currency, and set the opening balance to the closing balance on the day before your feed starts. If you connect first and set the opening balance after, you will spend an afternoon chasing a difference that was never a transaction.

2. Connect, then immediately reconcile one known day

Once transactions start arriving, pick a day you remember — a payroll day, a big vendor payment — and tick it off line by line against the bank statement. You are testing three things: that every line arrived, that none arrived twice, and that debits and credits are on the right side. Finding a sign inversion on day one costs ten minutes. Finding it in month three costs a re-import.

3. Set categorisation rules for the traffic you can predict

Bank charges, interest credits, sweep transfers between your own accounts, and card settlements are high-volume and low-judgement. Rule them once. Leave vendor payments uncategorised on purpose — those need to be matched to a bill, not categorised to an expense head. A vendor payment auto-posted to "Purchases" is a payment that will never link to an invoice, and an unlinked payment is invisible to the 180-day test.

4. Match payments to bills, not to expense heads

This is the step people skip and it is the one that carries tax consequence. In Zoho Books, a bank debit for a vendor payment should be matched to the recorded Bill, so the bill is marked paid on the bank's value date. That link is what tells you, later, which invoices are paid and which are ageing.

5. Close the loop weekly, not monthly

Reconcile weekly and the exceptions are three lines you still remember. Reconcile monthly and they are forty lines from a period you don't. The work is identical; only the recall is different.

A worked example: why the matched payment matters

Take one bill. A design consultancy invoices you on 5 August 2026:

Two numbers now diverge, and both are correct. Your books carry a ₹4,72,000 bill. Your bank feed carries a ₹4,32,000 debit. If that debit is categorised to an expense head instead of matched to the bill, Zoho shows the bill as unpaid. The 180th day falls on 1 February 2027; the period expires in the February 2027 tax period, so an unpaid bill would land in the reversal working for the March 2027 GSTR-3B — carrying ₹72,000 of credit that had in fact been paid months earlier.

Matched properly, the bill closes on the bank's value date and the 180-day clock stops there. That is the entire practical argument for step 4.

One caveat on this example, stated as a caveat rather than an answer. Rule 37 turns on payment of "the amount towards the value of supply along with the tax payable thereon", and CBIC has issued no circular addressing whether income-tax TDS that you deduct and deposit counts towards that amount. Practice differs on it and we do not state a position. What you can do without taking one is evidence it: keep the TDS challan and the Form 16A trail attached to the bill, so that whichever view your advisor takes, the file supports it. There is no authority to cite here, and this page does not supply one.

Note also what the bank feed does not tell you: whether that consultancy filed its GSTR-1 and put the invoice in your GSTR-2B. Paying a vendor and being entitled to the credit are two independent conditions, and the feed only evidences one of them.

Where a clean feed still leaves an ITC problem

A perfectly reconciled bank feed does not make your ITC claim safe. It answers the payment conditions; it is silent on the documentation ones. Three provisions sit outside the feed entirely:

Under Section 16(2)(aa), no GSTR-2B entry means no credit — 2B reconciliation before filing GSTR-3B is a legal precondition, not best practice. GSTR-2B itself is the monthly ITC statement drafted under Rule 60 from your suppliers' GSTR-1, GSTR-5 and GSTR-6 filings. It is static once generated, which is what makes it reproducible for audit — but note that since the Invoice Management System went live it is no longer purely auto-drafted: records you accept, reject or leave untouched in IMS shape what the statement contains, and leaving a record untouched is treated as accepting it.

The consequence of ignoring that half is mechanical. Under Rule 88D, where ITC claimed in GSTR-3B exceeds ITC available in GSTR-2B beyond a threshold, the portal issues a DRC-01C and you must pay with interest or reply in Part B within seven days — or be barred from filing your next GSTR-1 under Rule 59(6). Rule 88D prescribes no figure; it delegates to such amount and percentage as the Council may recommend, and GSTN has never published the operative limit, describing it only as a predefined, configurable threshold. The single figure on record is a recommendation, not a rule: the 50th GST Council, meeting on 11 July 2023, recommended intimation where the difference is more than 20% as well as more than ₹25 lakh — both limbs, cumulatively. Treat that as what it is, a dated recommendation, and ignore the widely repeated "₹1 lakh or 20%" figure, which traces to no rule, no minutes and no advisory. Practically there is no published number to manage to. There is only knowing your own gap before you file.

Three things that break, and the fix

Duplicate transactions after a re-import

Importing an overlapping date range creates duplicates that reconcile to nothing. Before any import, note the last transaction date already in Zoho and start the export from the next day. If duplicates are already in, delete the imported batch rather than the individual lines.

A feed that stopped and nobody noticed

Direct feeds break on password changes, MFA resets and bank-side maintenance. Zoho will usually surface the connection error, but nobody reads a banner. Add one item to the month-end checklist: latest transaction date in each feed is within two days of today. It takes fifteen seconds and catches everything.

Receipts arriving net of deduction

Where your customer is a notified deductor, Section 51 requires deduction at source at 2% (1% CGST + 1% SGST, or 2% IGST) on payments under contracts exceeding ₹2.5 lakh, reported in GSTR-7. So the credit that lands in your feed is short of your invoice by the deducted amount — and the deduction reaches your electronic cash ledger, not your bank. Match the receipt to the invoice and account for the deduction separately; do not write the shortfall off as a discount.

Multiple accounts, one vendor

If you pay the same vendor from an HDFC current account one month and an ICICI one the next, Zoho will not connect the two for you — each feed is its own ledger. The bill is the join. This is another reason to match to the bill rather than categorise to a head: the bill is the only object that survives the account you happened to pay from, and it is the object the 180-day test attaches to.

The first month-close after you connect

Run these four checks once, in this order, and most of the problems above never reach you:

1. Closing balance ties. Zoho's balance for each account equals the bank statement closing balance. If it doesn't, stop — nothing downstream is trustworthy.
2. Zero uncategorised vendor payments. Every debit to a supplier is matched to a bill, not sitting in the uncategorised queue.
3. Ageing report reviewed. Pull unpaid bills sorted by invoice date and look at anything past 120 days. That is your Rule 37 early-warning list, with two months of room to act.
4. 2B compared to your claim. Separately from the bank work, compare your GSTR-2B against the ITC you intend to claim, before you file.

The first three are bookkeeping. The fourth is the one that keeps a Rule 88D intimation off your desk, and no bank feed will do it for you.

What Recoup does with the feed once it's clean

Recoup works with Zoho Books and reconciles bank payments against the books — built against HDFC and Standard Chartered statement formats, and against any bank statement export. On the GST side it reconciles your Zoho Books ITC against your GSTR-2B, names the vendor behind any gap, and tracks the Rule 37 180-day clock per invoice so a reversal never arrives as a surprise. The bank feed gives you the payment dates. What you do with them is the reconciliation.

Related guides