How to schedule an eMandate transfer on Zerodha
An eMandate on Zerodha lets you schedule automatic recurring fund transfers from your bank account, so money moves on a fixed date without you approving each transaction. This guide covers three related tasks: scheduling a fund transfer to your trading account through Zerodha Console , scheduling that transfer to arrive in time for a stock SIP on Kite , and scheduling a mutual fund SIP on Coin that debits straight from your bank. It assumes you have already registered a mandate; if you have not, start with the UPI eMandate setup guide or the netbanking eMandate setup guide .
Scheduling is where most eMandate confusion starts. The mandate is the standing authorisation your bank grants once. The schedule is the recurring instruction that tells Zerodha when to pull funds and how much. A single mandate can carry more than one schedule, and the timing rules differ depending on whether you are funding a trading-account stock SIP or a Coin mutual fund SIP.
Conflict-of-interest disclosure. This guide is published by the WebNotes Editorial Team for informational purposes and is written independently. WebNotes operates a Zerodha account-opening referral programme, disclosed on the pages that carry the referral link; this guide does not carry it and earns no referral commission from the procedure described here.
Step-by-step procedure
The procedure infobox near the top of this page lists the scheduling steps in order. The sections below expand each step for the Console fund-transfer route, then cover the stock-SIP timing rule and the Coin mutual fund SIP direct-debit route separately, because the two flows differ in where the money is drawn from.
1. Log in to Zerodha Console
Open console.zerodha.com . Enter your client ID and password, then complete two-factor authentication with TOTP or SMS OTP. Mandate and schedule management lives on Console. You cannot create or edit a schedule from Kite, and the mobile Kite app hands off to Console for these actions.
2. Open the Mandates page
Click Funds in the Console navigation and select Mandates, or go straight to console.zerodha.com/funds/mandates . The page lists each registered mandate with its bank account, reference number, and status, along with any transfer schedules already attached.
3. Select or create a mandate
If you already hold an active mandate on the account you want to debit, select it. If not, click Create a new mandate, choose the bank account, and authenticate on your bank’s mandate-approval gateway using a debit card or netbanking. A Console fund-transfer eMandate authenticates through debit card or netbanking; UPI AutoPay is the separate Coin route covered later. A netbanking or debit-card mandate can take up to 5 days for the bank to activate, so create it well before the first date you need to schedule.
4. Start a new transfer schedule
On the active mandate, choose the option to add or create a schedule. The schedule is the layer that turns a one-time authorisation into recurring transfers. Because multiple schedules can sit under one mandate, you can, for example, run a monthly transfer for a stock SIP and a separate weekly top-up from the same mandate, as long as the combined debits stay within your bank’s mandate ceiling.
5. Name the schedule and set the transfer date
Give the schedule a name you will recognise later, such as the fund or the purpose. Then set the fund-transfer date. This is the single most important field for anyone funding a stock SIP: set the transfer date 2 to 3 days before the SIP date, not on the SIP date itself. The reason is covered in the stock-SIP section below.
6. Set the frequency and amount
Select the frequency, which is monthly for most SIPs, and enter the transfer amount. The amount cannot exceed the ceiling on the underlying mandate. If you need to move more than the ceiling, either raise a fresh mandate with a higher ceiling or split the transfers. For the current per-mandate and per-day caps, and the difference between the UPI AutoPay and eNACH figures, see the Zerodha eMandate limit page rather than assuming a single number, because Zerodha’s own pages state different limits for the two mandate types.
7. Create the schedule
Click Create schedule. The schedule saves against the mandate and runs automatically on each scheduled date. No further approval is needed from you for individual debits; the one-time bank authentication at mandate registration covers every debit under the mandate.
8. Confirm the schedule and note the debit timing
Check that the schedule appears with the correct name, date, frequency, and amount. Keep in mind the actual debit lands one working day before the scheduled date, and you receive an SMS and email a day before that debit. Keep enough balance in the bank account by then. A failed debit for insufficient funds can attract a bank penalty and, for a SIP, a missed instalment.
Scheduling for a stock SIP on Kite
A stock SIP on Kite buys shares or ETFs from the money sitting in your trading account. The SIP does not pull from your bank directly; it spends the trading-account balance. So funding a stock SIP is a two-part job: an eMandate schedule tops up the trading account, and the stock SIP then invests that balance.
This is why the transfer date matters. Zerodha advises scheduling the eMandate a few days ahead of the SIP date because bank confirmation of the transfer can be delayed. Its own worked example: for a SIP on the 5th of the month, schedule the eMandate for the 2nd or 3rd. That buffer gives the transfer time to complete and settle before the stock SIP runs, so the SIP does not skip for want of funds.
Because the account is debited one working day before the scheduled date, a transfer scheduled for the 3rd is debited on the 2nd working day, and you are alerted the day before. Plan the buffer around working days, not calendar days, so a weekend or bank holiday between the transfer and the SIP does not eat into the lead time. If a stock SIP does miss for insufficient funds, the failed SIP debit guide walks through recovery.
Scheduling a mutual fund SIP on Coin (direct debit)
A mutual fund SIP on Zerodha Coin works differently. The mandate here is a payment mechanism that automatically pays for your SIPs straight from your bank account. The instalment is debited directly from the bank under the mandate, not from your existing Coin or trading balance, so you do not need to pre-fund the account the way you do for a stock SIP.
Coin offers two mandate types for this: UPI AutoPay and bank eNACH. When you register a SIP on Coin, you attach it to a mandate. Two rules govern the pairing:
- A single SIP cannot be linked to more than one mandate, but multiple SIPs can be linked to a single mandate. One eNACH or UPI AutoPay mandate can therefore drive an entire fund portfolio, as long as the total instalments stay within the mandate ceiling.
- You cannot link a mandate when the SIP due date falls on the T+2 day. If you are setting up a SIP and the earliest due date is only two days out, pick a later date or fund the first instalment manually, then let the mandate take over from the next cycle.
Only primary and secondary savings accounts can carry a Coin SIP mandate. Current accounts cannot create mandates at all. For the concept behind auto-debited instalments, see the eMandate and NACH for SIPs explainer and the SIP overview.
UPI AutoPay versus eNACH: which to schedule
The two mandate types behave differently at registration and activation, which affects how early you must schedule.
| Feature | UPI AutoPay | Netbanking or debit-card eNACH |
|---|---|---|
| Where it is set up | Coin, for mutual fund SIPs | Console (Funds > Mandates) and Coin |
| Authentication | UPI PIN in your UPI app | Debit card or netbanking on the bank gateway |
| Activation time | Almost immediate | Up to 5 days for the bank to activate |
| Verification step | A Rs 1 debit that is credited back in T+4 working days | No separate token debit |
| Eligible accounts | Primary and secondary savings accounts | Primary and secondary savings accounts |
The activation gap is the practical difference for scheduling. A UPI AutoPay mandate is usable almost at once, so you can schedule a Coin SIP for a near date. A bank eNACH mandate can take up to 5 days, and the Coin route notes bank mandates can take up to 72 working hours to activate, so the first scheduled debit must sit far enough out to clear activation first. When a UPI AutoPay mandate is created, a Rs 1 verification amount is debited and credited back within T+4 working days; this is a token check, not a charge.
How the debit and notifications work
Once a schedule is live, the sequence on each cycle is fixed:
- Zerodha and your bank send an SMS and email one day before the debit.
- The bank debits your account one working day before the scheduled transfer date.
- The funds land in your trading account, or the SIP instalment is applied, on the scheduled date.
For a stock SIP, step 3 is the account top-up, and the SIP then invests from that balance. For a Coin mutual fund SIP, the debit is the instalment itself. Either way, keep the balance ready by the debit day, not the scheduled day.
Charges on a scheduled transfer
There are no charges at Zerodha for eMandate registration or for transferring funds using an eMandate. The cost you can incur is a bank-side penalty if a scheduled debit fails for insufficient funds. The specifics, including the penalties some banks levy per failed instance, are set out on the Zerodha eMandate charges page. To avoid them, fund the account before the one-working-day-prior debit date.
Editing or stopping a schedule
A schedule can be cancelled without deleting the mandate, which leaves the mandate available for future schedules. Deleting the mandate itself is a separate action. Both are covered in the cancel eMandate guide . If you hit an error while removing an in-process schedule, the delete schedule mandate error guide covers that specific case. Cancel a schedule at least 3 working days before the next credit date, and 4 working days for SBI accounts, so the change takes effect before the next debit.
Frequently asked questions
When should I schedule an eMandate transfer for a stock SIP on the 5th?
Does a Coin mutual fund SIP need money already in my Zerodha account?
Can one eMandate cover more than one SIP?
Why can I not schedule a mandate for a SIP due in two days?
How soon does a scheduled eMandate become active?
Can I schedule an eMandate from a current account?
How much can a single scheduled transfer be?
See also
- How to set up a UPI eMandate on Zerodha
- How to set up a net-banking eMandate on Zerodha
- How to cancel an eMandate on Zerodha
- Zerodha eMandate troubleshooting
- Zerodha eMandate limit
- Zerodha eMandate charges
- Zerodha eMandate overview
- How to set up a UPI AutoPay SIP on Coin
- How to create a stock SIP on Kite
- How to fix a failed SIP debit
- Delete schedule mandate error on Zerodha
- eMandate and NACH for SIPs
- Systematic investment plan (SIP)
- Zerodha Console
- Kite by Zerodha
- How to add funds to Zerodha via UPI
- How to add funds to Zerodha via net banking
- NPCI
- Reserve Bank of India
- Zerodha
External references
- Zerodha Support: Set up an eMandate
- Zerodha Support: Mandate for a scheduled SIP
- Zerodha Support: SIP mandate on Coin
- Zerodha Support: UPI AutoPay on Coin
- NPCI: UPI AutoPay
- NPCI: National Automated Clearing House (NACH)
References
- Zerodha Support, “How to set up an eMandate,” support.zerodha.com.
- Zerodha Support, “How do I set up a mandate for a scheduled SIP?” support.zerodha.com.
- Zerodha Support, “SIP mandate on Coin,” support.zerodha.com.
- Zerodha Support, “UPI AutoPay on Coin,” support.zerodha.com.
- NPCI , “UPI AutoPay product overview,” npci.org.in.
- Reserve Bank of India , “Framework for processing of e-mandates for recurring transactions,” RBI/2019-20/133, January 2020.