How to Update the Details Held in a Mutual Fund Record

Changing a detail in a mutual fund record is really one question: where is that detail kept? Some details sit on an account held with one asset manager. Others sit on a verification record held in a single place that several managers consult. Answer that first, and the number of changes required answers itself.

Start where the trouble starts, before any form is opened. A household decides to update its details. Updating the details sounds like one job. Inside the record it is not one job, and it is not even one place. A record holds a set of separate entries, and the record keeper's word for one of them is a fieldOne separate entry inside a record, such as an address line or an instruction about where money is paid, kept and changed on its own.. Where a holder lives is one field. Where money is paid out is another. Who is recorded as a nominee is a third. The three fields feel like one category because every one of them describes the holder. Different places hold them, different parties keep them, and different reasons put them there.

One case runs from here to the end. Girnar Asset Management Limited, an invented asset manager, runs the Girnar Large Cap Equity Fund, an open ended equity scheme with net assets of Rs 4,200 crore and 120.00 crore units outstanding. Divide the first by the second and one unit is worth Rs 35.00 exactly. The unit value of Rs 35.00 is settled under what an investor record document carries, and is carried across rather than argued again. One household holds three accounts in that scheme, running 2,857.143 units, 1,428.571 units and 857.143 units. Kalyani Bhagat manages the scheme and Sohail Merchant heads operations.

Each entry and what sits inside it, the key the record is anchored on, the verification record itself and the nomination entry are set out separately, and the electronic checking of a person's identity belongs to the digital finance material. The change itself, and what happens to it after it leaves the holder's hands, is what remains. Where a field is kept decides how a change to it is made, and telling that the change reached it is a second question with a second answer. What a change calls for is settled by the Securities and Exchange Board of India (SEBI), read at sebi.gov.in, and by the manager running the scheme. Both change their requirements, so both are read fresh each time.

Which detail is actually being changed?

Almost nobody asks this one. A holder arrives asking how do I change it. The first answerable one is which entry, exactly. How and which are not the same, and getting them the wrong way round is the reason so much effort produces so little movement.

Think about a household that shifts to a new flat two streets away. The milk stops at the old gate until somebody tells the vendor. The school keeps posting to the old address until the office is told separately. The gas agency, the electricity connection and the bank each keep their own book, and telling one of them tells none of the others. Nobody finds that strange. Four different parties keep four different registers, and everyone can see it. The strange thing is that the same household, dealing with one asset manager, will assume that one message updates everything, when the entries inside that one record are also kept in separate places for separate purposes.

The care belongs at the start. Where a holder lives, where money is paid out, who is recorded as a nominee and which phone number is on file are four fields. The four fields have four locations, four kinds of evidence sitting behind them and four different distances that a change will carry. Nobody can answer a request phrased as update my details. The phrase names a category the record does not have, and the first real work on any change is turning it into the name of one field.

The practical move takes about ten seconds and saves the rest. The single entry to be made different is written down, in the smallest words available: the account where redemption money is sent, or the address the scheme posts documents to. If two things need changing, that is two jobs, and treating them as two is not pedantry. Counting two jobs as two is the only way the total at the end comes out right.

Does this detail describe a person or an arrangement?

One line of reasoning does the work, and it needs nobody's list. The named field is examined for what it describes. Does it describe a person, or does it describe an arrangement?

A field stating who a person is generally belongs on the central verification recordThe identification and verification record for a person, kept in one place and looked up by whoever needs it rather than rebuilt by each of them., kept in one place precisely so that everybody who needs the answer reads the same one. A field stating something settled between a holder and one asset manager, for instance where redemption money is to be sent or who stands recorded against the holding, sits on the account. Such a field is called an account level fieldAn entry kept on one account with one asset manager, which therefore exists separately on every other account a person holds., and the name is doing real work: it exists once per account, not once per person.

The rule is already in use elsewhere without being named. A passport says who somebody is. A passport is issued in one place, and the hotel, the airline and the visa office all read the same booklet rather than each writing their own version of that identity. A standing instruction given to one milk vendor about which gate to leave the packet at is not a fact about the household at all; it is an arrangement with that vendor, held in that vendor's book, and the vendor two streets away has never heard of it. Records behave the same way. Identity is looked up. Arrangements are held by whoever the arrangement is with.

A list of fields and their locations goes quietly out of date. Asking what a field describes keeps working long after the list has stopped. Where a particular field actually sits in a particular arrangement is a matter for the asset manager and for the rules SEBI sets at sebi.gov.in. The reasoning gives the right expectation to walk in with, and something to check against once the place a change has to be made is named.

How far does one change actually travel?

Give the idea a name so it can be argued about. The reachHow far a single change carries: which accounts and which parties end up holding the new value once the change has been made. of a change is how far it carries once it has been made. A change to a field kept on an account reaches that account and stops there. The account is the only place the field exists. A change to a field kept on the central verification record becomes visible to any asset manager consulting it. None of them was keeping a copy in the first place. Each was reading the one record.

Now put the two side by side and notice what is missing. The work of making the change feels the same either way. The same effort of remembering, filling, submitting and waiting produces one result in the first case and many in the second. Nothing in the effort itself signals which of the two is under way, so the reach has to be worked out from where the field is kept, before the first form is opened rather than after the confirmationA message saying that a request arrived and what was done with it. It reports on the request, not on the current state of any record. arrives.

Knowing which side of that line a field sits on converts a vague worry into a number. Once the side is known, the job is known to be one thing or several, and it is known in advance. Everything that follows is arithmetic on top of that one determination.

What happens when the same information sits in two places?

Everything so far assumes a field is kept in one place. Some information is not. A single value can sit in two places at once, held by different parties who each need it for a different reason, and neither of them is doing anything wrong by keeping it. Two books holding one value is the one way a change is completely correct and still lands nowhere.

A household example makes the pattern familiar the moment it is pointed at. A phone number is with the school office because the school needs to call about a child. The same number is with the tuition class because the class needs to call about a missed session. Telling the school is a complete, correct and successful act, and the tuition class still has the old number that evening. Nobody failed. There were simply two books, and only one of them was written in.

Records do this too. Imagine an address kept centrally as part of the description of who a person is, and the same address kept on each account because the asset manager posts documents from its own book. The address in that example shows information able to sit in two books. Where any particular entry actually sits is a matter for the manager and for the rules SEBI sets at sebi.gov.in. Change it centrally and the central record now holds the new value. The three accounts hold what they always held. Here is the case where every step was right and no account moved: the request was correct, the change was made, the confirmation was issued, and each account carried on exactly as before.

The reason it is so hard to catch is that the paperwork behaves perfectly. A confirmation reports on the place it came from. A confirmation has no way of speaking about a book it was never looking at, and it does not pretend to. So the only tell is in the wording: what the confirmation actually names is what it covers, and everything it does not name stands untouched until somebody looks. Reading the wording that way is not suspicion. Plain reading takes the document for what it says rather than for what it was hoped to settle.

Why is one change harder to make than another?

Anybody who has made two different changes knows that one of them went through quietly and the other asked for a great deal. The difference is not arbitrary and it is not about how much the manager likes the holder. The difference follows from the job the field is doing.

The starting point is why anything is asked for at all. A record cannot see who is standing in front of it. A record has only what arrives, so something has to tie the request to the person the record is about, and something has to show that the new value is real rather than merely typed. The purpose behind both is durable and worth understanding. The particulars are not: what counts as showing either of those things, in what form, and with what going alongside it, belong to SEBI, read at sebi.gov.in, and to each asset manager's own published route.

Two things then make one change heavier than another. The first is reach. A change to something describing who a person is becomes visible to any manager consulting that record, so it is treated in proportion to how far it carries. The second is what the field controls. A wrong value in a field that decides where money leaves to sends money somewhere. A wrong value in a field that decides where a document is posted sends paper somewhere. The two are not the same animal. The weight of what is asked tracks what would happen if the change were wrong. A money field and a postal field are never treated as the same job, however alike updating my details makes them feel.

The skill that survives every revision of every requirement is small and unglamorous. The instructions printed on the manager's own route are read afresh rather than last time's steps repeated. The name on whatever is produced has to read the same as the name standing on the record. A name written differently in two different decades is one of the commonest reasons a perfectly honest request stops, and a mismatch like that is a record keeping artefact rather than anybody's carelessness. One field per request keeps a query about one of them from holding up the other. And whatever acknowledgement comes back is worth keeping. The acknowledgement is what dates the request.

Holders reach for the wrong party constantly, so one more part of the map is worth having. The entries live in a register kept by the asset manager and by the party that keeps that register for it. A distributor may have helped open the account, may explain the route and may carry a request, and none of that is the same as altering what the record holds. The same goes for a refreshBringing a verification record up to date so that what it holds still describes the person. Whether, when and how that is done is set by the rules. of a verification record: it is done where that record is kept, not wherever an account happened to be opened.

What does a change deliberately leave alone?

The mistake here runs in the opposite direction from every other mistake so far. Having worried that a change does too little, a holder then expects it to do far too much. A change works forward. A change does not travel backwards through everything the record has already produced.

The household version is obvious once said aloud. A household shifts house and gets the address corrected on every document that matters. The letters already delivered to the old flat do not un-deliver themselves. A certificate issued three years ago still prints the address the household lived at three years ago, and no office reissues it because the household moved. Nobody thinks of that as an error in the certificate.

A record behaves the same way. A report drawn last year still says what the record held when it was drawn. No earlier report is drawn again because an entry moved later, and none should be. The whole value of that report is that it describes a particular moment accurately. The record is right about today and the earlier document is right about its own day, and neither of those two facts is a fault in the other.

The mistaken picture underneath is a record as a single sheet somebody corrects in ink, the correction making the old version disappear. A record is not a sheet. A record is a running position that carries one value up to a point and another value after it. Two practical things follow from holding that picture. Effort spent chasing reissues of old documents is wasted. There is nothing wrong with those documents. And an old document is evidence about its own date rather than a claim about today. Anybody assessing it will read it that way too.

How is a change known to have actually landed?

One distinction leans on nobody's procedure and cannot go out of date. Two documents look like they answer the same question and do not.

A confirmation reports on a request. A confirmation says something arrived and something was done with it. Such a document is genuinely worth having and worth keeping. The confirmation is what dates the asking. A confirmation cannot report what any book holds now, and it never claimed to. A read backAsking for the current value standing in one named entry, in one named place, and being told what it is. is the other document. A read back gives the value standing in that one entry, in that one place, today.

The same distinction is already familiar from parcels. A message saying a shipment has been booked is evidence about a booking. Ringing the person at the other end and asking whether the parcel is in their hands is evidence about the parcel. Nobody sensible treats the first as the second when something matters. Yet a confirmation about a record gets treated as proof of the record's contents constantly. The confirmation arrives looking so much like the end of the task.

A confirmation stands as evidence about a request. The entry read back stands as evidence about the record itself, and only the second answers the question actually asked. The check that follows is short. The value in that field is asked for on each account that carries it, named one at a time, and what was said and when is noted. The read back costs one question, and it is the only thing standing between a change believed in and a change that is actually there.

What do three accounts do to a single change?

Then comes the arithmetic that actually decides how much work the change involves. An account level field exists once on each account. Not once per person, not once per manager. Once per account. So a household holding three accounts is holding three copies of that field, and changing it means doing the same thing three times.

Three floors of one building, each with its own electricity connection, is the everyday version. Every connection has its own consumer record, and correcting the name on one of them does not correct the other two, however obviously they belong to the same household. Nobody announced that as a rule. The repetition falls out of the fact that there are three connections.

The repetition is not a policy anybody chose and not a manager being difficult. The count drops straight out of where the entry is kept, and the number of accounts therefore matters more than the procedure for changing any one of them. The count comes first. How many accounts stand in a holder's name with one manager, and what value each one shows in a named entry, is a listing the manager, together with whoever keeps its register, can put together one line per account. A holder is entitled to ask for that listing before starting, and it turns a vague job into a finite list.

The count is also what makes partial progress so dangerous. Doing two of three feels like being nearly finished, and the two confirmations in hand both say so, truthfully. Nothing in the holder's possession mentions the third. So the household below is counted out in full rather than left to assumption.

How many changes does this household's job actually take?

Count it out on the household. The scheme first: net assets of Rs 4,200 crore divided by 120.00 crore units gives Rs 35.00 for one unit, exactly, and that division is where every rupee figure below comes from. The three accounts carry 2,857.143 units, 1,428.571 units and 857.143 units. Added, they come to 5,142.857 units.

Multiplying those balances by Rs 35.00 turns up something small and honest, shown here rather than hidden behind the word about.

The residues are there because a unit balance is carried to three decimals. Account one's balance is a division rounded up at that third decimal and account two's is a division rounded down. One residue is therefore positive and the other is three times as large the other way. The total repays attention: Rs 1,79,999.995 sits exactly halfway between Rs 1,79,999.99 and Rs 1,80,000.00, so it cannot be written to the paisa without quietly picking a rounding rule and calling the result a fact. No rounding rule is picked here. The figure therefore reads about Rs 1,80,000/-, and every rupee figure attached to this household carries the same word.

Change one: where money is paid out

The household wants redemption money sent to a different bank account. The bank instruction sets out something agreed between a holder and one manager, so it sits on the account, and there are three accounts. Three changes. Suppose two of them are done and the third is not. An ordinary week interrupting the job produces exactly that.

Two of three sounds like two thirds finished. By count it is: 66.7 per cent of the accounts. By value it is not. The accounts are different sizes. The two changed accounts carry 2,857.143 plus 1,428.571. Set against 5,142.857, those 4,285.714 units are 83.3 per cent. Left standing on the old instruction are 857.143 units: 16.7 per cent of this household's units in the scheme, about Rs 30,000/- set against about Rs 1,80,000/-. Both shares are struck on that base and on nothing wider: one household, one scheme, invented figures.

Change two: something describing who the person is

Now the household wants to change something that states who the person is. A field of that kind sits on the central verification record, so it is changed once, in one place, and any manager consulting that record sees the new value. One change. Three changes for the first job, one for the second, and what separates them is not effort, urgency or importance; it is only where each field is kept.

And now the trap, on the same household

Say a postal address sits in two books at once: centrally, as part of the description of a person, and again on every account, as the place documents go out to. Change it centrally and that is one correct change, properly made, properly confirmed. The three accounts still carry the old address. For this household the whole job counts four: one made centrally and three made on accounts. Doing the central one alone is 25 per cent of the job, and the holder finishes that quarter holding a document that truthfully says a change was made.

The rest of it belongs elsewhere: what has to be shown for any of those four changes, what any of them takes in elapsed time, and whether anything about an account is held still while one is being worked. All three questions are settled by SEBI, read at sebi.gov.in, and by each manager's own published route.

What is there to do when a change never lands?

Sometimes a change is asked for properly and the record still does not carry it. There is a route for that. The route has a shape, set out below. Every particular of it belongs to the regulator and the manager, and the particulars are exactly the part that moves.

The shape is simple. The route opens with whoever holds the entry, meaning the manager and the party keeping its register. Nowhere else can the entry actually be altered. Going anywhere else first is the commonest wasted week. From there it climbs, and that climb is an escalationA route that moves a complaint from the party first asked to a party standing above them, one stage at a time.: what those stages are, who each one goes to, what any of them may be asked to do and every interval hanging off any of it belong to SEBI, read at sebi.gov.in, and to whatever each asset manager publishes.

One part of it never moves: what a holder carries in at the start. The entry by name, the book it sits in, what was asked and the day it was asked, and the value standing there today are what any route works from, and not one of the four is hostage to a procedure that moves. Notice that the fourth one is the read back rather than the confirmation. A route that begins with what the record currently holds is arguing about a fact, and one that begins with a confirmation is arguing about a request.

Nothing about arriving here is a failure of attention. A field kept once per account is not a thing anybody mentions to a holder, a confirmation that describes one book is doing its job correctly, and a request that stopped for a reason nobody explained is a record keeping outcome rather than a personal one. The route exists precisely because these things happen in the ordinary course, and using it is the normal thing to do rather than an escalation of temper.

Girnar Asset Management Limited, the Girnar Large Cap Equity Fund, the Girnar Broad Market Index Fund, Kalyani Bhagat and Sohail Merchant are invented.
Educational material. Not advice on any investment, tax, budget or market position.