Cut-Off Processing: From an Order to Allotted Units
Between an instruction and a unit balance sits a run of work. A point of acceptance takes the application and stamps it. The money travels its own route. Once the day has closed, the scheme computes one value per unit. Applications considered against that value are divided into units, and a record keeper writes the result against a holder's account. Which day's value applies turns on when both arrivals landed.
A holder gives an instruction. Something comes back saying it had been received. Days later a unit count appears, and it is not the number the holder had worked out. Nothing went wrong, and nobody made a mistake, but the holder has no picture at all of what happened in between. The interval between the receipt and the unit count holds the whole answer.
Girnar Asset Management Limited, an invented fund house, runs the Girnar Large Cap Equity Fund, an open ended equity scheme with net assetsWhat a scheme holds after subtracting what it owes, which is the amount the unit count is divided into. of Rs 4,200 crore and 120.00 crore units in issue. The first figure divided by the second gives one unit worth Rs 35.00 exactly. Kalyani Bhagat manages the portfolio. Sohail Merchant heads operations.
Three things are covered separately: what a unit is, how one value per unit is computed out of a scheme's books once a day, and what a cut-off is as an idea. The machinery on either side of that line has not been settled anywhere, and nearly every question a holder actually asks turns out to live there.
What is cut-off processing, if the cut-off itself was settled earlier?
The cut-off is a line. Cut-off processingEverything a scheme does after an instruction lands and before a number of units stands against a holder in its records. is the run of work that happens on either side of that line, and knowing the first says almost nothing about the second. A queue at a government counter works the same way. The shutter coming down says nothing about the clerk's handling of the form afterwards, who checks it, what happens if a column is blank, or when a name appears on a list. The shutter is one fact. The processing is everything else.
Laid out in order, the run has five stages, and the reason it feels opaque is structural rather than anybody's fault. An application lands somewhere and gets stamped. Separately, the payment sets off. Once the day has shut, the scheme works out one value per unit from what it held and owed. The division is carried out and units are entered. The holder record is updated and a confirmationThe line a holder finally gets to read on a statement, after units have been entered to their name. follows. Out of those five stages a holder is present for the opening one and the closing one, and all three that settle the answer happen somewhere nobody outside the scheme can look.
What does a time stamp actually establish?
An application is handed in at a point of acceptanceAny counter, desk or electronic channel through which a scheme agrees to take an application in., and it is stamped. The time stampA mark showing when something was handed in. The mark proves the handing in and settles nothing that comes after. is the single artefact of this whole run that a holder ever physically holds. Being the one thing a holder can hold is exactly why the stamp gets over-read.
A courier receipt behaves the same way. The receipt proves the parcel entered the network at a particular counter. The receipt does not itself promise a delivery date, and it certainly does not create the delivery schedule. The schedule exists separately, is written by somebody else, and can change without a single word on the receipt changing. The stamp proves that a landing took place. The rule that converts a landing into a claim on one particular day's computed value is an entirely separate object, written by the Securities and Exchange Board of India (SEBI) and changed more than once. Anyone reading the stamp as though it were that rule has mistaken a record for a rule, and the two have different authors.
An application has come back stamped and acknowledged. Does that decide the day whose computed value attaches?
Which of the two arrivals can a holder never watch?
Two things have to reach the scheme, not one. The application is the first. The money is the second, and the two arrivalsTwo things that must both get to a scheme, the paperwork and the payment, moving on separate routes at separate speeds. travel by completely different routes. The instruction may go through a distributor, an electronic channel or a counter. The money moves through the banking system on its own rails, with its own checks, its own reasons for stopping and its own record of having got there.
Consider a wedding invitation posted and the gift couriered separately. Both are addressed to the same household. The two leave on the same morning. The two do not arrive on the same morning, and the one that can be tracked is rarely the one that matters. The instruction can be watched going while the payment offers no window at all. The landing that cannot be seen is very often the one that settles the result. The unseen landing is the single most common reason a unit count surprises somebody.
The instruction has been handed over and has gone. Which of the two arrivals is now happening out of sight?
Suppose a scheme let an application take a computed value while that application's payment was still in transit. Who would be paying for that?
Why must a line separate one day's value from the next?
One half of this subject stays true no matter what any rule says next year, and it is the half worth slowing down for. A value per unit for a given day is assembled out of that day's facts. The holdings, priced at that day's close. The obligations, standing at that day's close. The second subtracted from the first gives net assets. Divided by the units in issue, that gives one figure for that day. StrikingWorking out what one unit is worth for a given day, once that day has shut and from that day's figures alone. that figure is a closing act, and it can only use what was true at the close.
Now put the question the other way round. If a figure computed out of one day's facts were allowed to absorb money that turned up afterwards, what would the figure mean? The figure would be describing a pool that did not exist. Somebody would hold units against money the scheme did not have. The reason a line has to exist somewhere is arithmetic and does not move. Where that line falls is a rule, is SEBI's to write, and has been revised. The arithmetic and the rule age at completely different rates, and holding the two apart is most of the discipline of this subject.
What would it cost if a computed value took in something that landed afterwards?
An assertion that value would move is worth much less than a figure, so pricing it out is worth the trouble. No scheme admits an application ahead of its money. The arithmetic below runs on that impossible assumption, to show exactly what the line prevents.
Start from the value itself. Rs 4,200 crore of net assets shared among 120.00 crore units in issue comes to Rs 35.00 a unit exactly. An application of Rs 1,00,000/- divided by Rs 35.00 gives 20,000 over 7. The quotient is 2,857.142857 and does not stop there, so it is carried to three decimals and rounded up to 2,857.143 units. Note which way that rounding went. The direction comes back in a moment.
Now imagine, purely to watch something break, that those 2,857.143 units were entered while the Rs 1,00,000/- was still somewhere in transit. While that holds, the units in issue read 1,20,00,02,857.143. Nothing was put into the pool, so net assets read Rs 4,200 crore as before. Divide again: Rs 42,00,00,00,000/- over 1,20,00,02,857.143 units gives Rs 34.99991667 a unit.
| Line | The arithmetic, worked rather than quoted | Result |
|---|---|---|
| Start | Net assets of Rs 4,200 crore shared among the 120.00 crore units in issue | Rs 35.00 a unit |
| One | Rs 1,00,000/- divided by Rs 35.00, carried unrounded | 2,857.142857 units |
| Two | Carried to three decimals, rounded up | 2,857.143 units |
| Check | Backwards: 2,857.143 units at Rs 35.00, against the Rs 1,00,000/- paid | Rs 1,00,000.005 |
| Three | Units in issue, if those units were written before the money landed | 1,20,00,02,857.143 |
| Four | Rs 4,200 crore, unchanged, over that unit count | Rs 34.99991667 |
| Five | Rs 35.00 less Rs 34.99991667, the fall on every single unit | Rs 0.00008333 |
| Six | That fall as a proportion of Rs 35.00 | 0.00023809 per cent |
| Seven | Rs 4,200 crore times 2,857.143 over 1,20,00,02,857.143 | Rs 99,999.77 |
| Check | 120.00 crore units at Rs 34.99991667, the paying holders' claim | Rs 41,99,99,00,000.23 |
| Check | Rs 41,99,99,00,000.23 plus Rs 99,999.77, the pool that never changed | Rs 42,00,00,00,000.00 |
The residues are where sloppy arithmetic hides. Read them before the headline. Line two rounded upwards, from 2,857.142857 and continuing, to 2,857.143. The backwards check then multiplies those units by Rs 35.00 and lands on Rs 1,00,000.005. Rs 1,00,000.005 is half a paisa more than the money paid, and it sits exactly halfway between two paise. Stating it to the paisa means silently choosing a rounding rule. The remainder makes that a real check rather than a restatement. Line four rounded upwards too, from a figure continuing past the eighth decimal, and line seven rounded upwards from Rs 99,999.766905 and continuing. The final check row is exact. Nothing was created and nothing was destroyed, so the two claims sum back to Rs 42,00,00,00,000/-.
Measured on one unit the damage cannot be seen at all, measured across the whole scheme it is precise, and it comes out at almost exactly the Rs 1,00,000/- that never landed. On a single unit it reads Rs 0.00008333, or 0.00023809 per cent of Rs 35.00, and it would vanish in the rounding on any statement anybody will ever be handed. Summed instead, those 2,857.143 units carry a claim of Rs 99,999.77 on a pool nothing was paid into. Everybody who had already paid is holding Rs 99,999.77 less than a moment before. The pool stayed the size it was, so one figure serves twice.
One warning about a pattern that looks like proof and is not. The drop of 0.00023809 per cent on each unit is precisely the newcomer's share of the pool, 2,857.143 units over 1,20,00,02,857.143. The two figures are not independent routes agreeing. The two figures are one identity written twice: the fall in the value per unit divided by the old value is one minus the ratio of the old unit count to the new one. Simple rearrangement turns that into the new units over the new total, and the identity holds exactly at the unrounded 20,000 over 7. Saying it is a check would be self flattery. The genuine backwards check is the multiplication in the check row, and it produces a residue of half a paisa rather than a tidy agreement. A residue is the only kind of confirmation that could have failed.
The fall works out at Rs 0.00008333 on a unit worth Rs 35.00. Is that small enough to ignore?
Let an application in ahead of its payment, and watch where the value goes
Educational illustration. The outcome a scheme has to prevent is drawn large below, so the reason becomes obvious. Nothing was paid in, so net assets stay pinned at Rs 4,200 crore the whole way across.
Let an application of Rs 1,00,000/- attach to a computed value while its payment is still in transit, and one unit slips from Rs 35.00 to Rs 34.99991667, a drop of Rs 0.00008333 apiece that no statement would ever print, while Rs 99,999.77 of claim on a pool of unchanged size crosses from the people who paid to the one who has not.
Units are carried in whole thousandths and money in whole paise, and the sum let in runs from Rs 1,00,000/- up to Rs 500 crore. The control starts at the worked example above, figure for figure. The magnification factor is stated on the figure and is always an exact power of ten.
When the units are finally written against a holder's account, who decides how many of them the holder gets?
Who chooses the number of units an application receives?
Nobody. The answer is that blunt, and it surprises people. Once the day has closed, the scheme values what it held, subtracts what it owed and divides by the units in issue. The three steps produce one figure. Every application considered against that figure is then divided by it, and the quotient is the unit count. AllotmentEntering a number of units to somebody's name once the sum has been worked out. is a sum done against a figure that was settled before the application arrived, rather than a bargain struck or an opinion formed about any one holder.
The everyday version is a wedding caterer weighing out sweets. The rate for the day was fixed before anyone queued. Whether the customer hands over Rs 500/- or Rs 50,000/-, nobody at the counter decides how much comes back; the scale does, at the rate already set. The convention for the last fraction is all that is left, and it is the only place a choice is made at all. On the Girnar Large Cap Equity Fund the Rs 1,00,000/- application divides to 2,857.142857 and continuing. The scheme's stated convention carries it to three decimals, so the confirmation reads 2,857.143 rather than an endless figure. The rounding convention is the scheme's own, printed in its documents, and is that scheme's practice rather than anybody's rule.
Where in this run does the registrar and transfer agent sit?
Three different records exist inside a scheme and they hold three different things. The portfolio is one record, and Kalyani Bhagat, who manages the Girnar Large Cap Equity Fund, works entirely inside it. The scheme's own books are the second, and it is out of those that one value per unit is computed at the close. The registerThe list a scheme keeps of who stands behind how many units, one account at a time. is the third, and it is the only one of the three that has ever heard of the holder.
The register is maintained by the registrar and transfer agentThe outfit that looks after who holds what in a scheme and posts each purchase or exit to that list.. The agent posts the units to a folioThe account in a scheme's records against which one holder's units are held., carries the running balance, and puts out the confirmation that reaches the holder in the end. Kalyani Bhagat's work stops at the portfolio and never touches a holder's balance at all, so a question about missing units goes to a record keeper and not to a fund manager. Sohail Merchant, who heads operations at Girnar Asset Management, sits between the two, which is a job about instructions and records rather than about holdings.
The units have still not appeared against a holder's account. Whose record actually holds the answer to that question?
What can be rechecked on a confirmation, and what cannot?
A confirmation carries four things that can be tested with a pencil, and one thing that cannot be tested at all. The amount is the money sent. The value per unit is stated. The date that value belongs to is stated. The unit count is stated to three decimals. The third multiplied by the fourth should land within the rounding convention of the first, and on this scheme that check reads 2,857.143 times Rs 35.00 is Rs 1,00,000.005 against the Rs 1,00,000/- paid, a remainder of half a paisa produced by rounding the units upwards.
Whether the right day's value attached in the first place cannot be tested at all. The gap is not a defect in the document; it follows from the nature of the document. A confirmation records what happened. The confirmation does not carry the conditions under which what happened was correct, and those conditions turn on when each of the two arrivals landed relative to a line whose position SEBI sets. A holder who knows exactly which question the document cannot answer knows exactly where to take it instead. Naming the unchecked thing is therefore far more useful than pretending the confirmation settles it.
On the confirmation sit an amount, a value per unit, the day it belongs to and a unit count. Which one of these is beyond what the document can settle?
Where does this run break, and does it break in only one place?
The run breaks in three places, and they are three genuinely different problems. An incomplete application never gets past acceptance, so there is nothing downstream to look for. A transfer of money that fails stops the second arrival, so the instruction is sitting there complete and the funds are not. An account reference that fails to match leaves the units with nowhere to go, so a number has been produced and there is no name to put it under. Three break points, three remedies, and a holder who reports only that their units have not appeared has handed the record keeper none of the three.
A parcel that has not arrived at a household works the same way. The parcel was never handed over. The parcel was handed over and is stuck somewhere. The parcel arrived and was left at the wrong door. Saying only that the parcel is missing describes all three equally, and each has a different person to call. The same discipline pays here: name the last stage for which evidence exists, and hand over that evidence. How long each of the three takes is bound up with the conditions SEBI sets.
Why does a stated deadline go wrong faster than the arithmetic?
Because the two halves of this subject age at completely different rates. Why a line has to exist is arithmetic, and the arithmetic worked above will read exactly the same in ten years. Where the line falls is a rule. The rule is SEBI's to write, it applies differently by the kind of scheme and the kind of instruction, there is a separate condition about the money having reached the scheme, and every one of those has been revised. A deadline written down would not become dated when the conditions next change; it would become wrong, and a confidently wrong sentence about a deadline is far more damaging than a blank with an address beside it.
The blank points somewhere. SEBI publishes the version in force at sebi.gov.in, and each scheme sets out the governing version in its own documents. Knowing the shape of the run, knowing that two arrivals matter rather than one, and knowing exactly which question belongs to which document is worth far more than a number that quietly expired.
Who reaches for this run on a working day, and what do they do with it?
Sohail Merchant, who heads operations at Girnar Asset Management Limited, reads the run backwards. When an application has not become a unit balance, his first move is not to look at the value per unit at all, but to establish which of the three checkpoints the item last cleared. The checkpoint an item last cleared routes the whole enquiry. Everything after it is somebody else's desk.
Somebody servicing holders uses the run as a script. The useful question to a holder is never whether their units have appeared. The holder already knows that. The useful question is which artefact they are holding: an acknowledgement only, a confirmation of the money having left, or a statement line. Each of the three answers points at a different stage, and asking for the artefact rather than the complaint turns a vague problem into a located one.
A household reading its own confirmation gets the smallest and most durable use of it. Recompute the unit count from the amount and the value per unit, and if the two tie within the rounding convention, the arithmetic is not the issue and no amount of staring at it will help. Which day's value attached is all that remains, and it goes to the scheme's documents and to SEBI at sebi.gov.in.
None of the three can settle from this material whether the value that attached was the correct one. The arithmetic on a confirmation is fully checkable and the attachment behind it is not, and a working process treats those as two separate enquiries rather than one.
The error that gets made, and what it costs
Here is the mistake, and it is not a careless one. The stamp comes back. The acknowledgement carries a scheme name, an amount and a reference, so it looks exactly like a confirmation. So the transaction feels finished, and the money is treated as a formality that will catch up. The reading is completely reasonable, given that an acknowledgement is the only artefact the holder has. The reading is also wrong: a scheme has to receive two things and so far it has received one.
For the holder the cost is a wrong expectation and then a search in the wrong place. Worked against the value they had in mind, the unit count refuses to tie. So they go hunting for a slip in the scheme's sums that was never made, and the search is long and entirely unproductive.
For anyone designing or explaining the process the cost is much larger, and the worked instance above prices it. Run a scheme on that basis and value leaves the pool at every transaction without exception, in the precise sum of whatever payment was still in transit. On one application of Rs 1,00,000/- that came to Rs 99,999.77, invisible at Rs 0.00008333 a unit and exact in the total, and it would happen again on the next one and the one after.
The fix is a definition rather than any extra vigilance. Count the run finished only once both things have got there and a unit balance stands in the holder record, and read an acknowledgement as proof of one landing rather than of a completed transaction. The separate question of which day's value ought to have attached goes to the conditions at sebi.gov.in and to the scheme's own documents, never to the acknowledgement, which was never in a position to answer it.
Who sets these conditions?
Every condition that decides which day's computed value attaches to an application is set by SEBI, and the version in force is published by SEBI at sebi.gov.in. The published version covers the deadline itself, how it differs by the kind of scheme and the kind of instruction, and the separate condition on what counts as the money having reached the scheme. Each one has been revised more than once, so the version in force on the day it is needed is the one that governs.
The scheme's own offer documents restate the position that applies to that scheme, so a holder with a specific application in hand has two places to look: SEBI and the scheme's own documents. Industry level practice and the shared vocabulary used to group schemes sit with the Association of Mutual Funds in India (AMFI) at amfiindia.com. AMFI publishes and explains rather than making any rule. Where units are held in a demat account, the depository record is kept by the National Securities Depository Limited (NSDL) at nsdl.co.in or Central Depository Services (India) Limited (CDSL) at cdslindia.com.
One last question. Where the line actually falls: why is that left to SEBI?
Where these conditions are published
| Body | What it settles | Site |
|---|---|---|
| Securities and Exchange Board of India | Every condition governing which day's computed value attaches to an application, what counts as the money having reached a scheme, and the obligations around acceptance, allotment and confirmation. | sebi.gov.in |
| Association of Mutual Funds in India | Industry level practice around acceptance and record keeping, and the shared classification vocabulary, published rather than made into a rule | amfiindia.com |
| National Securities Depository Limited | The depository record where units sit in a demat account rather than in a statement of account | nsdl.co.in |
| Central Depository Services (India) Limited | The second depository record for units held in a demat account | cdslindia.com |
Girnar Asset Management Limited, the Girnar Large Cap Equity Fund, Kalyani Bhagat and Sohail Merchant are invented.
Educational material. Not advice on any investment, tax, budget or market position.
