An asset label cannot fund a software programme

A software investment can look smaller when its proposal emphasises the amount expected to be recognised as an asset. That may be relevant to reporting, but it does not reduce the cash the company must commit. Nor does an appropriate accounting treatment establish that the programme will produce the operating benefit described. I ask investment papers to keep three questions separate: what we will pay and when, how the expenditure will be treated under the applicable policy, and what useful change the business expects to obtain. A single return figure can hide a weak answer to any one of them.

Three questions in one approval request

At Mirelva, a reporting-system proposal had a planned cash envelope of ₹2.8 crore. The summary placed considerable emphasis on capitalisation and suggested a limited immediate effect on profit. Its budget contained several kinds of work, including development, exploration, training and support. Those categories required examination on their own terms. A programme title could not determine the accounting treatment of every cost inside it. I asked finance and the external advisers to review the proposed categories and the evidence that would be needed as the work progressed, before the board relied on the expense profile in its decision.

The planning assessment identified ₹1.1 crore of development expenditure that could qualify for asset recognition if the relevant conditions were met. The remaining ₹1.7 crore comprised ₹60 lakh of exploratory work, ₹48 lakh of training and ₹62 lakh of support. These were planning classifications, not permission to book expenditure in advance of the actual work and evidence. I put the complete ₹2.8 crore cash schedule beside them. The company would need to fund the programme regardless of the timing of expense recognition. Directors could then examine reporting and affordability without allowing either to stand in for the other.

This separation does not diminish the importance of accounting judgement. A company should apply its policy consistently and maintain the supporting evidence. It simply prevents a technical conclusion from being used as a commercial recommendation it was never designed to provide. A project may satisfy the relevant recognition conditions and still be a poor use of scarce cash. Another may involve substantial expense and still address an urgent operating weakness. Finance has to explain both dimensions clearly enough for management and directors to weigh them, rather than turn the word 'asset' into a shorthand for desirable investment.

The cash schedule also deserves more attention than a single programme total. A supplier deposit, a milestone payment and a recurring support obligation fall due under different conditions. Some commitments may become difficult to reverse before the business has seen a usable result. I want the approval paper to identify those points and explain what evidence will be available before each one. A staged invoice does not necessarily mean a staged commitment if the contract already obliges the company to pay the whole amount. Commercial and legal colleagues need to establish the actual position before finance describes flexibility that the agreement does not provide.

Capacity released needs a destination

The reporting proposal also included an estimate of staff time released. That can be a valuable benefit, particularly where skilled colleagues spend too much time assembling data instead of examining it. It is not automatically a payroll saving. Our operating review showed that the colleagues concerned would remain employed to handle unresolved client exceptions and improve reporting quality. I therefore removed an unsupported claim of lower employment cost from the return calculation. The work could still be worthwhile, but its benefit needed to be described as additional capacity or better service, with evidence appropriate to that claim.

This distinction can provoke an unhelpful argument between finance and technology. One side may feel that only headcount reduction is being accepted as value; the other may feel that any time estimate is being treated as money saved. Neither position helps a board choose. I want the operating owner to state what the released capacity will be used for, which work will stop and how the result will be observed. A team that can resolve more exceptions within the same staffing may have created real value. The proposal should explain that improvement without adding a payroll reduction that management has no intention of making.

There are also costs of transition that a stable-state calculation can overlook. Colleagues may need training while the old process continues. Data may require correction before it can be used in the new report. A client may need reassurance that a changed output still supports its own work. These activities are not evidence that the investment has failed; they are part of the work required to make it useful. I ask for them to be included in the plan, with ownership and timing. Omitting them can make a sensible programme appear unusually attractive at approval and unexpectedly expensive during delivery.

The quality objective should be specific enough to be examined without inventing a financial equivalent. If management wants fewer unexplained differences between two reports, it should define the differences and how they will be reviewed. If it wants a faster response to client queries, it should identify the current constraint and the evidence of improvement. I do not need every useful outcome converted into a speculative rupee amount. I do need the company to know what it is paying to change and how it will distinguish a functioning system from a programme that has merely completed its scheduled activities.

Stage the commitment around useful evidence

Our board approved a first release of ₹1.2 crore within the overall ₹2.8 crore envelope, with a review before the remaining commitment. The purpose was to examine usable outputs and the revised operating plan before expanding the work. It was not to claim that a smaller first payment had reduced the full cost of the intended programme. The technology team accepted a slower release of funds, and finance accepted responsibility for maintaining the distinction between approved envelope, committed expenditure, cash paid and accounting recognition. Each figure answers a different question during delivery.

A review point is useful only if it can change what happens next. If the remaining scope is already irrevocably contracted, a meeting described as a decision gate may offer little practical choice. If the business cannot define what it expects to learn, the review may become a progress presentation that repeats the original promise. I ask the sponsor to identify the decision that remains open and the evidence that will inform it. That may concern scope, timing, supplier performance or the usefulness of the output. The point is to preserve a real management choice, not to add a ceremonial meeting to the calendar.

For directors, the central task is to understand the commitment and the reason for making it. They should expect the accounting assessment to be supported, the cash schedule to reflect the contract and the operating benefits to have accountable owners. They should also see where management is accepting uncertainty. In our case, a reporting improvement remained worth pursuing after an unsupported payroll saving was removed and the expense profile became less flattering. The stronger decision came from stating those consequences plainly. A software programme earns its place through the work it enables and the obligations the company can sustain, not through the label attached to its expenditure.