How-to · Zoho & banking

Connecting Zoho Books to Standard Chartered Bank. The setup, and the approval step most guides skip

The short answer

Connecting Standard Chartered to Zoho Books needs a one-time token from your bank relationship manager — not Zoho support — entered against your Straight2Bank Group ID by an organisation admin you designate as Integration Administrator. Payments initiated in Zoho Books are then approved separately, inside the Straight2Bank portal, using a physical Vasco token — a step entirely outside Zoho Books that most first-time setups don't expect.

Standard Chartered is one of the banks Zoho names for direct integration in India — but the connection runs through a second system entirely, Straight2Bank, with its own Group ID, its own administrator role, and a hardware-token approval step that has nothing to do with your Zoho Books login. Get the roles right and the rest is mechanical. Get them wrong and a correctly-initiated payment just sits unapproved.

Two systems, one setup

Standard Chartered doesn't connect to Zoho Books the way a retail-style direct feed does. The integration runs through Straight2Bank, Standard Chartered's own corporate-banking portal — a separate login, a separate Group ID, and a separate approval step for every payment Zoho Books initiates. Per Zoho's own setup documentation, the two systems stay distinct for the life of the integration: Zoho Books is where you initiate a payment, Straight2Bank is where it's authorised.

Before you start: new relationship or existing one?

Steps and eligibility below are as per Zoho's help page, as of 2 October 2026 — Zoho can change its own screens and figures without notice. Zoho's own help page splits the onboarding path in two, and which one applies changes what you need on day one:

SituationPathWhat happens
No existing Standard Chartered relationshipSettings > Online Payments > Vendor Payments > Set up Now > Request for a New AccountFill in organisation and contact details, accept the Terms, and a bank executive contacts you to open the account. Zoho's documentation notes annual turnover must exceed ₹2.5 crore for a new account request made this way.
Already a Standard Chartered corporate customerSettings > Online Payments > Vendor Payments > Set up Now, enter org/contact details, agree to the Terms, SaveBank executives issue a one-time token to authenticate the connection — no new account opening involved.

Either path lands you in the same place: a connection sitting in Pending status until it's authenticated.

The one-time token — and who actually issues it

This is the first place first-time setups stall. Zoho's documentation says the one-time token is provided by the bank's executives ("Enter the token provided by RM") — so if authentication is stuck, start with your Standard Chartered RM, not a Zoho support ticket. Zoho lists [email protected] for integration queries on the Zoho Books side.

To authenticate, you need three things together on the integration screen: the Straight2Bank Group ID (your bank registration ID), the token from your RM, and an organisation admin designated as Integration Administrator. Once validated, status moves from Pending to Active.

The Integration Administrator is the one role that can change anything

Zoho's documentation is specific about this split, and it's worth setting deliberately rather than letting it default to whoever happened to run the setup:

SettingPurpose
Integration AdministratorMust be an admin of the organisation. The one user who can edit any of the settings below; all other users can only view them.
Straight2Bank Group IDThe registration ID the integration authenticates against
Allowed Payment AccountsWhich Standard Chartered accounts can be used to initiate payments from Zoho Books
Payment InitiatorsWhich users are permitted to start a payment — a separate group from the Administrator alone
Bank Statement AccountsWhich accounts feed bank-statement reconciliation

In practice, treat the Integration Administrator the way you'd treat any other single point of failure: name a real person, document who it is outside Zoho Books too, and don't let it sit with whoever was logged in during setup by accident. Zoho's documentation doesn't describe how the role is reassigned if that person leaves, so settle succession before you need it.

Adding a vendor's bank account

Before you can pay a vendor through Standard Chartered, Zoho Books needs their account details on file: Purchases > Vendors, select the vendor, open the More dropdown, and Add Bank Account. Enter the account exactly as the vendor's own bank states it — it's far cheaper to catch a typo here than at the Straight2Bank approval step below.

Making a payment: domestic, international, bulk

Once a bill exists against a vendor with a bank account on file, Pay via Standard Chartered appears on it. Per Zoho's documentation:

  • Domestic — choose Transaction Type (IMPS / RTGS / NEFT, or an internal Book Transfer), confirm the amount, source and destination account, and Proceed.
  • International — the same screen, but Zoho Books recognises a foreign-currency payment and picks TT (Telegraphic Transfer) for you; you additionally pick a Purpose of Payment and should check the quoted exchange rate before confirming.
  • Bulk — from Purchases > Bills, filter Unpaid Bills, select several, Pay via Standard Chartered, pick one From Account for the whole batch, then review each vendor's total and set Transaction Type per vendor where it differs, before Initiate Payment.

Initiating a payment in Zoho Books only moves it to In Progress. Nothing has actually left the account yet — that happens in Straight2Bank.

Approving in Straight2Bank: the step most first-time setups don't expect

This is the second place setups stall, because it looks like the payment should be done and it isn't yet. A payment initiated in Zoho Books has to be separately logged into and authorised inside the Straight2Bank portal itself — Zoho's documentation routes approval through the bank's portal, not through Zoho Books. The flow is:

  1. Log into Straight2Bank with your Group ID and User ID.
  2. Enter the digital one-time password generated by your physical Vasco token device.
  3. Go to Transaction Statistics, open the relevant batch under Batches, select the transaction, click Authorize Batch, then Save to authorise.
  4. The screen displays a Challenge value. Key that value into the Vasco device.
  5. The device returns a one-time code — enter it into the Response field and Submit.
  6. Send to Bank to actually process it.

Status moves to Processed only after that round trip. If your Payment Initiator and your Straight2Bank approver are different people — common, since Zoho's own Payment Initiators setting and Straight2Bank's own user/approval rights are configured independently — build the handoff into your week rather than assuming "initiated in Zoho Books" means "paid."

Virtual account numbers, for the receiving side

The setup above is for paying vendors. Standard Chartered's virtual account numbers solve the opposite problem — matching an incoming customer payment to the right customer. Per Zoho's documentation: enable Virtual Account Number on the Standard Chartered side first, then in Zoho Books go to Settings > Templates, edit your default invoice template, open Footer > Add Your Bank Details, enter the bank name, account number and IFSC, append the bank's four-digit virtual-account prefix to the account number field, then use Insert Placeholder > Virtual Account Number Suffix so the invoice you send each customer carries that customer's unique number. The bank feed then carries that number, so Zoho Books can propose the Best Match for you.

Once it's connected: feeds and reconciliation

Standard Chartered bank feeds refresh automatically once active. Transactions land under Banking > [your Standard Chartered account] > Uncategorised Transactions, where Zoho Books proposes a Best Match against existing bills and invoices — confirm with Match rather than letting a vendor payment default to an expense category. The same discipline our HDFC/ICICI/Axis/SBI bank-feed guide covers applies here: a vendor debit matched to its bill, rather than categorised away, is what gives you an evidenced payment date. That date is Rule 37's payment test — a reversal there is proportionate to whatever remains unpaid 180 days from the invoice date (Section 16(2), second proviso; Rule 37(1)), not the full credit, and is accounted for in the GSTR-3B for the tax period immediately following the one in which the 180 days lapse. An Uncategorised Transaction that never gets matched can't evidence anything.

What Zoho's own documentation doesn't say: closing or replacing the account mid-year

Zoho documents how to remove the integration itself — Settings > Online Payments > Vendor Payments > Standard Chartered > Delete, giving a reason, and confirming — but its published documentation does not state what happens to historical data already generated under the integration: whether previously-issued virtual account numbers on past invoices keep resolving, whether vendor bank-account records added for Standard Chartered payments carry over if you reconnect under a replacement account, or whether past Processed-status payment history remains visible after deletion. If you're closing or switching a Standard Chartered relationship, the safer assumption until Zoho documents otherwise is to export your payment and reconciliation history first, and treat any virtual account numbers already printed on sent invoices as something a customer could still try to pay against after the integration is gone — worth confirming with Zoho support and your Standard Chartered RM before you delete, not after.

How Recoup fits in

Recoup doesn't set up Straight2Bank or approve Vasco-token payments — that's the mechanics above, and it stays inside Zoho Books and the bank's own portal. What Recoup does is sit downstream of a connected feed: reconciling Standard Chartered payments in Zoho Books against the vendor bills they settle, and those bills against your GSTR-2B — so a payment that cleared in Straight2Bank but was never matched doesn't leave a paid bill showing as unpaid in your 180-day ageing.

Connected doesn't mean reconciled

Recoup reconciles your Zoho Books transactions — Standard Chartered included — against vendor bills, and those bills against GSTR-2B, and ages every open payable against its invoice date before it becomes a Rule 37 problem.

Book a demo →

Related guides