How to Prepare a Mutual Fund Service Request Properly
Preparing a mutual fund service request means settling four things before anything is written: what change is being asked for, whose folio it affects, what proof the register will want, and which channel will carry it. A request missing one of those is rarely refused outright. The request is parked, and the waiting is what the mistake actually costs.
Three things sit underneath that answer. The first is that a service requestAn instruction asking the party that keeps a scheme's records to change something it holds, or to send something it holds. is an instruction to record keeping, and that acceptance and completion are two separate events rather than one. The second is that every channel a request can travel along converges on the same register at the end. The third is that a request reaches a folioThe account number under which one holder's units in a scheme are recorded, together with the details attached to that account. rather than the pooled scheme itself. The order of preparation is doing all of the work.
One case runs through this guide from end to end. Girnar Asset Management Limited operates the Girnar Large Cap Equity Fund, an open ended equity scheme with net assets of Rs 4,200 crore held across 3,80,000 folios. The first figure divided by the second gives an average folio in the Girnar Large Cap Equity Fund of about Rs 1,10,526/-. Kalyani Bhagat manages the scheme's portfolio and Sohail Merchant heads operations at Girnar Asset Management.
The form to use, the documents to attach, the period allowed and the cut off that applies are settled elsewhere. Requirements of that kind are set by the Securities and Exchange Board of India (SEBI) and by the scheme's own stated documents, and they move. A list printed anywhere else would not become dated on the day it changed. The list would become wrong, and a reader following it would prepare the wrong thing with complete confidence. The sequence holds instead, and the sequence does not move. So does the handful of habits that make it work: reading the form's own instructions, matching the name on the proof to the name on the folio, keeping whatever is handed back when the request goes over, and knowing which single change is being asked for.
What has to be settled before anything at all is written?
Four things, and all four before a pen touches anything. The change itself, from what to what. The folio it sits on, and everybody else standing on that folio. The proof the register will want before it agrees to change what it holds. And the route that will carry the request to that register. Settle those four and the writing takes minutes. Everything the writing needs is already decided.
The order matters more than the list. A household that starts with the form works backwards: it discovers halfway down that it does not know which folio the change belongs to, guesses, and finds out weeks later that it guessed wrong. A household that starts with the four questions never opens the form until the form has nothing left to ask. The sequence is not a courtesy to whoever processes the request; it is the difference between a request that moves and a request that waits for a question nobody has asked yet.
Seven steps follow. The first four are the settling. The fifth is handing it over. The sixth is the one almost nobody performs, and it is the step the whole sequence turns on. The seventh is recognising when what is in hand is no longer a request at all.
Most service requests that stall are stopped by which of these three?
Step one: can the change be said in a single sentence?
Say it out loud before anything is written on anything: the change itself, from what, to what. If that sentence will not come out whole, the request is not ready to be written, and no amount of neat handwriting on the correct paperwork will rescue it. Most requests that stall are not incorrect, they are ambiguous, and an instruction that can be read two ways will be read the slower way.
The same thing happens at a counter anywhere else. A note handed over at a bank saying please change my address leaves the person reading it to ask which address, changed to what, and on which account, and each of those questions is a round trip. A note saying change the address on this account from the old flat to the new flat, with both written out, leaves nothing to ask. The second note is not more polite or better presented than the first. The second note is closed, and a closed instruction can be acted on the moment it is read.
The test is mechanical and takes about ten seconds. The sentence is read back, hunting for anything a stranger could interpret in more than one way: a folio not named, a change with no from and no to, a person not identified. Girnar Asset Management, like the party that keeps the records for any scheme, reads the instruction cold, with no memory of a telephone call and no view of what was meant. The person who reads the instruction knows nothing about the household. The instruction is written for that person.
Step two: whose folio is it, and who has to be part of the request?
The folio is named first, then everybody standing on it. One household commonly holds several folios across several asset managers, opened at different times for different reasons, and a request naming the wrong one is a request against a record that does not contain the thing being changed. A request naming the wrong folio describes a change the receiving record has no trace of. Nobody can complete such a request, however willing.
Then comes the part that catches people, and it catches them repeatedly. A jointly held folio has more than one person on it, and who has to be part of the request is a property of how the folio is held rather than of who noticed the problem. A joint holdingA folio recorded in the names of more than one person, so the record itself names each of them. is not a folio belonging to one person with a spare name attached. The record names both, so the instruction has to come from both, and it does not matter in the slightest which of the two opened the statement and spotted the stale bank detail.
Picture a household running on one salary. The bank account is in one name, the folio was opened in two, and the person who handles the paperwork is whoever is free on a Saturday. The arrangement is completely normal and works fine for years, right up to the point where a change is needed and one holder is travelling. The request goes in with one signature, waits, and comes back untouched. Nothing unreasonable happened. The register simply cannot act on an instruction that half of the record has not given.
A jointly held folio needs a change of bank detail. One holder is travelling and cannot be reached this week. Whose request is it?
Step three: what proof will the register want, and who decides that?
The proof is settled before the writing, not after a trip back to fetch it. The party that keeps the folio records will want evidence before it changes what it holds, and the evidence has a name: the proof of recordThe evidence a register asks to see before it will change a detail it holds, so that the change can be traced to the person entitled to make it.. Finding out what it is takes one question asked in advance. Finding out afterwards costs the whole round trip, and the round trip is the part that hurts.
SEBI and the scheme's own stated documents set what any particular change requires, and a list written down elsewhere would be wrong rather than merely dated on the day it moved. That is not caution for its own sake. A reader who follows a stale list prepares confidently, hands over the wrong thing, and only discovers the error at the point where discovering it is most expensive. Knowing where the current answer lives is worth more than holding a copy of it.
The answer lives in three places, and all three are close at hand. The scheme's own stated documents, published by Girnar Asset Management for the Girnar Large Cap Equity Fund, say what that scheme requires. sebi.gov.in carries what SEBI requires of every scheme. And the third place is a person: a distributor, or an investor service centre, either of whom handles requests of this kind constantly and will usually answer in a sentence. The Association of Mutual Funds in India (AMFI) at amfiindia.com publishes industry level material as well, though nothing there makes a rule. The durable skill is not knowing the list; it is knowing that the list exists somewhere current, and asking before rather than after.
Two habits survive every revision of every requirement, so they are worth more than any list. The first habit is reading the form's own instructions, printed on the form precisely because they change with it. The second habit is matching the name on the proof to the name on the folio, character for character. A mismatch there is the quietest and commonest reason a request goes back untouched. A folio opened years ago in a maiden name and a proof carrying a married name describe two different people as far as a register is concerned, and no goodwill anywhere in the chain can bridge that.
The list of documents this particular change requires: where does it come from?
Step four: which channel should carry it, and what does that channel do?
Choose the route, and choose it knowing what a route actually does. A request can be handed to a distributor. Another can be taken to an investor service centre. A third can go to the counter of the registrar and transfer agent, the party that keeps the folio records. A fourth can travel by an electronic route with no counter and no person in it. And where units are held in dematerialised form there is a depository participant in the picture as well, with the National Securities Depository Limited (NSDL) and Central Depository Services Limited (CDSL) sitting behind that arrangement.
One fact makes the choice honest rather than anxious. Every one of those routes ends at the same register, so the question is which of them will report fastest that something is missing, not which of them can do more. None of them can do more. A distributor cannot change a record and neither can a service centre; they carry the request to the party that keeps the record, and that party makes the change. Since no route unlocks anything the others cannot reach, most of the worry comes out of the choice.
The routes genuinely differ in one thing: feedback. A person who looks at a request while the holder is standing there can say in one breath that a signature is missing. A route with nobody in it accepts whatever is put into it and reports later, or leaves the holder to find out. Neither is better in the abstract, and how long any of them takes is set elsewhere. Where there is doubt about whether a request is complete, the route with a person at the front of it answers that question soonest.
Does choosing a different channel let a service request do something it otherwise could not?
A distributor agrees to get the bank detail on a folio changed, and does so willingly. What has the distributor actually done?
Step five: what is kept once the request has been handed over?
Whatever is handed back, with the date on it and the route that took it. The thing handed back is the acknowledgementWhatever is handed back when a request is received: a counterfoil, a stamped copy, a reference number or a message confirming receipt., and it may be a stamped copy, a counterfoil, a reference number or a message. Its form varies by route. Leaving with something in hand, rather than a memory of having passed a paper across a counter, is what matters.
The acknowledgement amounts to a time stampA record of when something was received, used to fix the moment a request entered the process. on the moment the request entered the process. The acknowledgement fixes when the request was made, and the date of asking is the only thing that will matter if the request later stalls. The acknowledgement proves nothing at all about whether the register has accepted it. Those two facts sit right next to each other and almost everybody collapses them into one. A stamp on a piece of paper says a person or a system received something. The stamp does not say the something was in order, it does not say anybody has looked at it, and it certainly does not say the folio now reads differently.
The acknowledgement is only ever needed on an occasion of some irritation already, so it belongs somewhere it can be found without hunting. A note of the date and the route, kept with the statement for that folio, costs nothing and is the entire insurance policy.
The request has been handed over and the acknowledgement is in hand, dated. Is the request finished?
Step six: how is it known that the request is actually finished?
Ask what completionThe point at which the register holds the change that was asked for, rather than merely holding the request for it. looks like for this particular change, and then go and check for exactly that. Checking is the step almost nobody performs, and the whole sequence exists for it. Confirming that something was submitted is not confirming that anything happened.
Completion has a different shape for every kind of change. Asking about it therefore beats assuming it. For a change of bank detail it is the new bank showing against the folio. For a change of address it is correspondence arriving at the new one. For a nomination it is the new name visible on the record. For an instruction that executes on a schedule it is the next instalment going through against the updated detail rather than the old one. In every case there is something specific to look at, and in every case it lives in the record rather than in a file of paperwork.
So, while their attention is still on it, the question goes to whoever took the request at the moment it is handed over: what will be seen, and where, when this is done. Anybody who handles requests routinely will answer that in one sentence, and the answer converts a vague hope into a specific check the household can perform for itself. A household that asks that one question at hand over turns an open ended wait into a closed loop, and it costs nothing but the asking.
What does completion look like for a change of bank detail on a folio in the Girnar Large Cap Equity Fund?
Step seven: when has it stopped being a request?
When a completed request has produced nothing, or has produced the wrong thing, and repeating it changes nothing. At that point what the household holds is no longer a request. The thing in hand is a grievanceA complaint that something already asked for was not done, which travels a different route from the original request., and the difference is not a matter of tone. The route from there is a different one, and sending the same request through the same channel a third time is a loop with no exit in it.
The sequence stops at that boundary. Where a grievance goes, what has to happen before it can be raised, how long anything is allowed to take and what escalation exists beyond the first step are all set by SEBI, and sebi.gov.in is where the current position lives. The sequence gives the recognition instead: noticing that one process has been crossed out of and another entered, rather than repeating a request patiently for months because nobody said it had stopped working.
Much of the preparation pays off here. A household that kept the acknowledgement can say precisely when it asked. A household that settled who was on the folio knows the request was properly made. A household that asked what completion looked like knows for certain that completion did not occur, rather than suspecting it. All three of those come out of steps one to six, and all three are what a grievance route will want at its front door.
A request was properly made, the acknowledgement is in hand, three months have passed and the record still reads the way it always did. What does the household have now?
How does the whole sequence run on one household's folio?
Take one folio in the Girnar Large Cap Equity Fund, held jointly by a household running on a single salary. The Girnar Large Cap Equity Fund has net assets of Rs 4,200 crore spread across 3,80,000 folios, so the average folio carries Rs 4,200 crore divided by 3,80,000. The division gives Rs 1,10,526.32 taken to the nearest paisa, and about Rs 1,10,526/- in round terms. At the scheme's value per unit of Rs 35.00, worked as Rs 4,200 crore divided by 120.00 crore units, that folio holds about 3,157.895 units. The change needed is a small one: the salary account has moved to a different bank and the folio still carries the old one.
The sequence contains no document name, no form number and no period, so watch how far this household gets without one. Step one, said out loud before anything is written: change the bank account on this folio from the bank currently on the record to the new one. Step two, the folio is one of three the household holds and only one of the three is with Girnar Asset Management Limited, so that one is named. The folio is held jointly, so both holders are part of the request rather than the one who happened to open the statement. Step three, what proof the register wants is settled by asking: the scheme's own documents say it, sebi.gov.in says what SEBI requires, and the distributor who has looked after these folios for years answers it in two minutes because he handles these weekly.
Step four, the household hands it to that distributor. The distributor cannot change any record at all, and the household chose that route because a distributor will telephone the same afternoon if something is short. Step five, the acknowledgement comes back and is kept, with the date on it. Step six, and this is where the sequence earns its keep, the household asks what completion will look like, is told it will show as the new bank detail against the folio, and goes and checks for exactly that rather than filing the acknowledgement and assuming. Step seven does not arise: the change completed.
| Step | What the household actually did | How it knew the step was done |
|---|---|---|
| One | Said the change in one sentence: this folio, from the bank on the record, to the new bank | The sentence came out whole, with nothing left to ask |
| Two | Named the one folio of three that sits with Girnar Asset Management Limited, and brought both holders in | The record is a joint holding, so both names appear on the instruction |
| Three | Asked the distributor, and checked the scheme's own stated documents, before writing anything | Nothing came back later asking for something that had not been brought |
| Four | Chose the distributor as the route, knowing the request still ends at the same register | The route was chosen for feedback speed, not for what it could approve |
| Five | Kept the acknowledgement, with the date on it and the route noted beside it | The household can say precisely when it asked, if that is ever needed |
| Six | Asked what completion would look like, then looked for the new bank detail against the folio | The record itself now reads differently, which is the only proof that counts |
| Seven | Did not arise | Completion was confirmed, so nothing crossed into a grievance |
One thing shows why any of it mattered, and it needs no period at all. Had the request stalled at step five, with the acknowledgement filed and nobody checking, the folio would have gone on carrying the old bank quietly. Months later a redemption from that folio would have been paid against the account the record still showed, and the household would have experienced that as the redemption going wrong. The failure would have been dated to the day of the redemption and would actually have belonged to a request nobody ever confirmed. That is the whole argument for step six, and it holds without any period being named at all.
| The one computed figure in this guide | The arithmetic | Result |
|---|---|---|
| The average folio | Net assets of Rs 4,200 crore divided by 3,80,000 folios | Rs 1,10,526.32 |
| Rounded for reading | The same figure taken to the nearest rupee | Rs 1,10,526/- |
| The check, backwards | Rs 1,10,526/- across 3,80,000 folios | Rs 4,199.988 crore |
| Which is short by | The rounding dropped from each folio, gathered back up | Rs 1,20,000/- |
| In units | Rs 1,10,526.32 divided by a value per unit of Rs 35.00 | 3,157.895 units |
The average folio is a division, not a measurement, and the backwards check shows exactly what the rounding costs: about thirty two paise a folio. Those paise gather into Rs 1,20,000/- across 3,80,000 folios and come to nothing at all for a single household. The arithmetic can be redone from the figures rather than trusted.
Would this request survive being handed over?
The default below is the household's request on the Girnar Large Cap Equity Fund folio exactly as the worked run describes it, with all six items settled. Change any one of them and watch where the sequence stops. The rail finds the first step that is short and stops there. A real request stops in exactly the same way.
This is the household's request on the Girnar Large Cap Equity Fund folio exactly as the worked run above describes it: the change said in one sentence, both holders on it, the proof settled in advance, the channel chosen, the acknowledgement kept, and completion confirmed against the record. Nothing is parked, and step seven never arises.
Educational illustration. Held constant throughout: the folio is a joint holding, so both holders are always required, and the change asked for is a bank detail on that folio. SEBI and the scheme's own stated documents set what any particular change requires, so this calculator settles no period, no form and no document requirement, and it cannot establish whether a real request is complete. The folio figure of Rs 1,10,526.32 is computed here in whole paise from net assets of Rs 4,200 crore and 3,80,000 folios.
Who runs this sequence on a working day, and what do they get from it?
Three people reach for it and none of them is doing it out of interest. Sohail Merchant, who heads operations at Girnar Asset Management, looks at the volume of requests that come back short and knows that almost none of them were wrong. The requests were open, or they were missing a holder, or they arrived without something nobody had asked for in advance. Only the person who wrote the instruction knows what was meant, so an operations desk cannot fix ambiguity from its own side.
A distributor uses the sequence as a checklist before accepting anything. Reading the change back in one sentence, asking how the folio is held and confirming what the register will want takes about two minutes at the counter and removes the round trip entirely. Two minutes at the counter is the whole value of a route with a person in it, and a household that is unsure should prefer the channel that answers questions over the one that merely accepts.
The household is the only party that pays for the delay, so the household gets the largest share. A household cannot make anybody process faster and has no view of what is happening inside the register. The household can control whether the request that went in was complete, and whether anybody checked that the record actually changed. Both of those are entirely within reach of anyone with ten minutes and this sequence, and both are what almost nobody does.
The error that gets made, and what it costs
The preparation stage gets skipped for two opposite reasons and both end in the same parked request. The first household assumes the distributor will handle everything, so nothing is settled in advance: the folio is not identified, the second holder is not present, no proof is gathered. When the request comes back short, that household experiences it as the distributor failing them, when what actually happened is that a request nobody could complete was handed over.
The second household assumes the opposite, that nobody will help and everything has to be done alone. So the request goes in through whichever route was nearest with whatever paperwork seemed sensible, and it comes back short for exactly the same reason: what the register needed was never established. Neither household did anything unreasonable. Nobody publishes what the register wants in a form a person reads on a Sunday afternoon, so neither household was ever told.
The cost is identical in both cases, and it is not measured in days. The cost is that the next thing depending on that record cannot happen, and that the household does not find out until that next thing is what it is trying to do.
The correction is a habit rather than a rule. Completion is settled before anything starts, and whoever is nearest the register is asked what the register will want, whether that is a distributor, an investor service centre or the register itself. A household that does that once tends to do it every time, and it is the cheapest habit anywhere in this subject.
Who sets what a request must carry, and where is that written down?
SEBI sets what evidence a change of record requires, the periods within which a request has to be processed, what a scheme has to disclose about its service arrangements, and the route a complaint takes when a request has failed. Every one of those is a live rule that is revised. The current position is read at sebi.gov.in, alongside the scheme's own stated documents published by Girnar Asset Management, on the day it is actually needed.
The same applies to the boundary between what a distributor may do and what counts as advice. SEBI draws that line and attaches conditions to it. The structural fact sits apart from the conduct rule: a distributor carries a request and cannot change a record. Who holds the register settles that, not any rule about conduct.
AMFI at amfiindia.com publishes industry level material about the distribution framework and about investor service, and AMFI publishes that material rather than making any rule. Where units are held in dematerialised form, NSDL at nsdl.co.in and CDSL at cdslindia.com sit behind the depository arrangement.
Of the seven steps, which is the one almost nobody performs, and the one this whole sequence exists for?
References
| Source | Document | Where |
|---|---|---|
| Securities and Exchange Board of India | The requirements governing what evidence a change to a folio record needs, the periods within which a service request is processed, and the complaint route available when a request has not been completed | sebi.gov.in |
| Association of Mutual Funds in India | Industry level material on the distribution framework and on investor service arrangements | amfiindia.com |
| National Securities Depository Limited | One of the two depositories behind units held in dematerialised form | nsdl.co.in |
| Central Depository Services Limited | The second of the two depositories behind units held in dematerialised form | cdslindia.com |
Girnar Asset Management Limited, the Girnar Large Cap Equity Fund, Kalyani Bhagat, Sohail Merchant, the household in the worked run, and its figures of Rs 4,200 crore in net assets, 3,80,000 folios, 120.00 crore units and a value per unit of Rs 35.00 are invented.
Educational material. Not advice on any investment, tax, budget or market position.