How-to eMandate SIP schedule delete mandate Coin Console stock SIP

How to fix the error when deleting a Zerodha schedule or mandate

From WebNotes, a public knowledge base. Last updated 21 June 2026. Reading time ~9 min. Level: Beginner.

Key facts

Exact error	Error deleting schedule: Error processing delete mandate request
Main cause	A previous instalment is still in processing status and not yet credited to your account
Second cause	Active or paused SIPs are still linked to the mandate; unlink them first
Timing rule	You cannot modify or delete a SIP linked to a mandate within 2 days of the next instalment
Schedule-cancel notice	Cancel a Console schedule at least 3 working days before the next credit date (4 for SBI)
Cost	Free; no charge to cancel a schedule or an eMandate

Procedure

Read the exact error and identify the causeIf the message is ‘Error deleting schedule: Error processing delete mandate request’, a previous instalment is still in processing status and the debited amount has not yet been credited to your Zerodha account. Wait for that credit to land, then retry the deletion.
Check for a pending or in-process instalmentOn Coin or Console, open the SIP or schedule and check its last instalment status. If a debit was triggered recently and shows as processing, the system blocks deletion until the credit completes, which can take one to two working days.
Unlink every active and paused SIP from the mandateOn Coin web, click your profile, then Mandates, then Edit, then Unlink. Select ‘None’ from the Mandates dropdown, click Modify, then Confirm. A mandate cannot be deleted while any active or paused SIP is still linked to it.
Delete the mandate after unlinkingOn Coin web, click Edit on the now-unlinked mandate, click Delete mandate, then Confirm. The mandate is removed once no SIP depends on it and no instalment is in process.
Cancel a Console schedule with the right noticeTo stop auto-debit without deleting the full eMandate, cancel the schedule at console.zerodha.com/funds/mandates at least 3 working days before the next credit date, 4 working days for SBI accounts. The eMandate stays usable for future schedules.
Cancel the full eMandate if you no longer need itAt console.zerodha.com/funds/mandates, choose to cancel the eMandate. It shows ‘Pending Cancellation’ while under process and takes up to 5 working days to be deleted at the bank and NPCI level.
Raise a ticket if the error persistsIf the error continues after the in-process credit has landed and all SIPs are unlinked, raise a support ticket on Zerodha. Persistent delete-mandate errors are resolved at the back end by the support team.

The error you hit when deleting a scheduled SIP or eMandate on Zerodha reads “Error deleting schedule: Error processing delete mandate request,” and it is almost always a dependency problem, not a fault. The deletion is blocked because a previous instalment is still in processing status, or because an active or paused SIP is still linked to the mandate you are trying to remove. Clear the dependency and the deletion goes through.

This guide covers the two causes in order: an in-process instalment whose debited amount has not yet been credited to your Zerodha account, and a mandate that still carries linked SIPs. It then walks the Coin and Console flow to unlink, delete a schedule, and cancel a full eMandate , with the timing rules that decide whether the next debit still goes out.

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 numbered infobox at the top of this guide gives the full sequence. The H3 sections below expand the two dependency causes and the platform-specific clicks that catch people out.

1. Read the exact error and identify the cause

The wording tells you which dependency is blocking the deletion. “Error deleting schedule: Error processing delete mandate request” points at an in-process instalment: a debit was triggered, the money left your bank, and it has not yet been credited to your Zerodha account. The depository and NPCI rails treat the instalment as live until that credit lands, so the system will not let you delete the schedule mid-cycle. A different message about unlinking SIPs points at the second cause, a mandate that still carries linked SIPs.

2. Check for a pending or in-process instalment

Open the SIP or schedule on Coin or Console and read its last instalment status. If a debit was triggered in the last day or two and shows as processing, that is the block. The credit usually completes within one to two working days for NACH and UPI AutoPay mandates. Wait for it, then retry the deletion. There is no way to force the deletion ahead of the credit, because the instalment is already in flight on the payment rail.

3. Unlink every active and paused SIP from the mandate

A mandate is a parent; the SIPs that draw on it are children. Zerodha will not delete the parent while a child still depends on it, which is why a delete-mandate request fails even when no instalment is in process. On Coin web, click your profile, then Mandates, then Edit, then Unlink. Select “None” from the Mandates dropdown so the SIP no longer points at this mandate, click Modify, then Confirm. Repeat for every active and paused SIP that lists this mandate. A single SIP cannot be linked to multiple mandates, but multiple SIPs can share one mandate, so check each one.

4. Delete the mandate after unlinking

With no SIP depending on it and no instalment in process, the mandate will delete. On Coin web, click Edit on the mandate, click Delete mandate, then Confirm. The mandate is removed from your active list. If you still see the error at this point, recheck that every SIP shows “None” as its mandate and that no instalment landed in the last two days.

5. Cancel a Console schedule with the right notice

If your goal is to stop the auto-debit but keep the eMandate for future use, cancel only the schedule, not the whole mandate. Go to console.zerodha.com/funds/mandates and cancel the schedule at least 3 working days before the next account-credit date, or 4 working days for an SBI bank account. The eMandate itself stays active and you can attach a fresh schedule to it later without creating a new mandate, which avoids the multi-day re-registration of a brand new eMandate.

6. Cancel the full eMandate if you no longer need it

To remove the bank authorisation entirely, cancel the eMandate at console.zerodha.com/funds/mandates. A mandate under process shows the “Pending Cancellation” status, and the cancellation takes up to 5 working days to complete at the bank and NPCI level, because the destruction of the mandate is a NACH or UPI AutoPay instruction, not a Zerodha-only setting.

The timing rule that decides whether the next debit still goes out

The deletion logic and the debit logic run on separate clocks, and that is the trap. You cannot modify or delete a SIP linked to a mandate within two days of its next instalment date. If you cancel a Console schedule after the upcoming debit is already confirmed, the funds are still debited and added to your Zerodha account, and only the debits after that one are cancelled. So the practical rule is: act early in the cycle. A deletion attempted close to the debit date either gets refused outright, inside the two-day window, or goes through but still lets one more debit run, because that debit was already locked in.

Stock SIP versus mutual-fund SIP

The dependency model is the same whether you are deleting a stock SIP set up on Kite or a mutual-fund SIP on Coin. Both refuse deletion while an instalment is in process, and both expect a linked mandate to have no dependent SIP before the mandate itself is removed. The difference is only where you click: a stock-SIP schedule is managed from the Kite SIP section, while a mutual-fund SIP and its mandate are managed from Coin and Console. If you run both off the same eMandate, unlink the stock SIP and the mutual-fund SIP before trying to delete the shared mandate.

What can go wrong

Deleting during an in-process instalment: the “Error processing delete mandate request” message means a debit is mid-flight. Wait for the credit to land in one to two working days, then retry.
Forgetting a linked SIP: the mandate will not delete while any active or paused SIP points at it. Set every SIP’s mandate to “None” first.
Cancelling too close to the debit: within two days of the next instalment the deletion is refused, and a confirmed debit still runs even after you cancel. Act earlier in the cycle.
Expecting an instant eMandate cancellation: a full eMandate cancellation shows “Pending Cancellation” and takes up to 5 working days at the bank and NPCI level.
Cancelling the mandate when you only meant to pause: if you may want to auto-debit again, cancel only the schedule; the eMandate stays reusable and saves a fresh registration.

External references

References

Zerodha support, “Error deleting schedule: Error processing delete mandate request” (as of 21 June 2026).
Zerodha support, How to rename, modify, or delete a mandate on Coin web, and the unlink-then-delete sequence (as of 21 June 2026).
Zerodha support, eMandate cancellation, schedule-cancel notice of 3 working days, 4 for SBI, and the up-to-5-working-day deletion (as of 21 June 2026).
NPCI, National Automated Clearing House and UPI AutoPay operating framework for recurring debit mandates.

Frequently asked questions

Why does Zerodha say 'Error deleting schedule: Error processing delete mandate request'?

A previous instalment is still in processing status and the debited amount has not yet been credited to your Zerodha account. The system blocks the deletion until that credit completes. Wait one to two working days for it to land, then retry.

Why can't I delete my mandate on Coin?

A mandate cannot be deleted while any active or paused SIP is still linked to it. First unlink every SIP by setting the mandate to ‘None’ on each SIP, then delete the mandate. A single SIP cannot be linked to multiple mandates.

How long before the next instalment can I delete a SIP?

You cannot modify or delete a SIP linked to a mandate within 2 days of its next instalment date. Make the change earlier in the cycle. For a Console schedule, cancel at least 3 working days before the next credit date, 4 for SBI.

Should I cancel the schedule or the whole eMandate?

Cancel only the schedule if you may want to auto-debit again later; the eMandate stays active and reusable. Cancel the full eMandate only if you want to remove the bank authorisation entirely. The full eMandate cancellation takes up to 5 working days.

If I cancel after a debit is confirmed, does the money still get taken?

Yes. If you cancel a schedule after the upcoming debit is confirmed, the funds are still debited and added to your Zerodha account, but all future debits for that schedule are cancelled. Cancel before the confirmation cut-off to stop the next debit.

Does deleting a stock-SIP schedule differ from a mutual-fund SIP?

The dependency logic is the same: an in-process instalment or a linked mandate blocks deletion. A stock SIP on Kite and a mutual-fund SIP on Coin both refuse deletion while an instalment is processing or a mandate link remains.

Reviewed and published by

WebNotes Editorial Team

The WebNotes Editorial Team covers Indian capital markets, payments infrastructure and retail investor procedures. Every article is fact-checked against primary sources, principally SEBI circulars and master directions, NPCI specifications and the official support documentation published by the intermediary in question. Drafts go through a second-pair-of-eyes review and a separate compliance read before publication, and revisions are tracked against the SEBI and NPCI rule changes referenced in the methodology section.

Last reviewed: 21 June 2026
Conflicts of interest: WebNotes is independent. No relationship with any broker, registrar or bank named in this article.