The receipt is not the whole financial story

A defined subscription cohort paid ₹12 crore for twelve months of continuing research service beginning 1 January 2022. In the March review, the cash receipt appeared beside a commercial account that treated the full amount as the quarter's achievement. The sales result was real, but the accounting question was when the promised service had been delivered. The cohort's reviewed policy treated performance as occurring evenly across the twelve-month term. Amounts in this case exclude GST.

The commercial team wanted the receipt to support an ambitious quarter-end earnings story. I understood the attraction: the customers had paid, the collection risk for that amount had reduced, and the team had done difficult selling work. I asked the controller and qualified advisers to keep those facts separate from recognition. For this cohort, three months of service supported ₹3 crore revenue through March, while ₹9 crore remained a contract liability for the service ahead. Other contract types required their own assessment.

I supported that presentation and asked the operating plan to show the continuing delivery obligation. The decision did not return ₹9 crore to customers or imply that the cash was held in a separate restricted bank account. It meant that the earnings account should not move ahead of performance simply because billing and collection had occurred earlier. Rohan accepted the lower recognised amount in the quarter's discussion while preserving the commercial team's contribution in its proper measure.

The practical cost was a less impressive immediate earnings story and more work explaining the relationship among sales, cash and service. I would have established those measures before the campaign began, so the team did not encounter the distinction only after celebrating collection. Finance should not use accounting language to diminish a genuine sale. It should prevent that achievement from being asked to prove a different event that has not yet happened.

In 2023 a data supplier offered a three-year licence for ₹9 crore, compared with ₹3.6 crore for a single year. The annualised comparison made the longer agreement appear ₹60 lakh cheaper per year. Research leadership was still reconsidering the scope of the product that used the data, and the contract did not provide the cancellation flexibility the initial business paper assumed. The question was whether the discount justified committing before the future need was clear.

Procurement colleagues preferred the three-year agreement because the lower annualised price was certain on the offered terms. Anita argued that the research direction might change substantially after the next cycle. I asked for the alternatives to show their actual obligations rather than compare only annual averages. The shorter agreement cost ₹3.6 crore for the first year; the longer one committed ₹9 crore across three. The remaining ₹5.4 crore was not a saving under the shorter choice, because future data needs and prices were still unknown.

I recommended the one-year licence and accepted its ₹60 lakh first-year premium against the longer offer's ₹3 crore annualised amount. Rohan approved the recommendation with a review before the next renewal. We did not claim that research would certainly change direction or that the supplier's longer contract was unreasonable. It was an appropriate offer for a customer able to support that commitment, and we could not yet do so.

The consequence was higher near-term cost in exchange for a shorter obligation, not free flexibility. The research team also had to use the review period to clarify its needs rather than postpone the same uncertainty indefinitely. My correction for the next procurement was to involve finance before the annualised saving became the headline. Once that number had been repeated, the discussion sounded like finance opposing a discount when the real disagreement concerned how much future need the company was prepared to purchase.

A research line generated ₹7.2 crore annual revenue in the FY 2024 review. Its report included ₹4.9 crore avoidable costs and ₹3.5 crore allocated central costs, showing a ₹1.2 crore loss. A proposal to close the line described that loss as a financial improvement available to the company. The problem was that the ₹3.5 crore central cost would remain over the decision period; allocating it elsewhere would not make it disappear.

I initially found the reported loss persuasive. Anita challenged whether the proposed saving described any actual reduction in resources. We rebuilt the comparison around the costs that closure could change. The line contributed ₹2.3 crore toward continuing central costs before those allocations. That did not prove it was strategically valuable or the best use of research capacity, but it did mean that closure could remove contribution while leaving the common expense behind.

We recommended a six-month continuation with a specific commercial and research review instead of immediate closure. The CEO accepted the recommendation. Over that subsequent six-month period, the line produced ₹3.4 crore revenue against ₹2.5 crore avoidable costs, a ₹90 lakh contribution before common costs. This was not ₹90 lakh net profit, and the shorter period could not simply be compared with the earlier annual result as evidence of improvement. The result informed the next decision rather than settling the line's future permanently.

Keeping the line also consumed people and attention that could have served another proposal. That opportunity cost belonged in the review even though it was not an invoice we could eliminate. My lesson was to begin with the actual choices: close, continue, change scope or redeploy capacity. A reporting allocation can help describe the enterprise, but it should not silently become a claim about cash released or resources avoided when management chooses a different course.

The FY 2026–27 planning discussion included a US$1 million data purchase. At an assumed ₹84 per dollar, the rupee amount was ₹8.4 crore before taxes and fees. A sensitivity at ₹94 produced ₹9.4 crore, a ₹1 crore difference for the same dollar amount. These were deliberately stated planning assumptions, not current exchange quotations or predictions of where the currency would trade. The initial budget summary had made the lower figure look like a settled cost.

Research colleagues wanted to preserve product scope and argued that a sensitivity should not automatically reduce investment. Treasury colleagues wanted the exposure visible before the company made customer and supplier commitments on different assumptions. I agreed with both concerns. I asked the paper to separate the research choice, the contractual currency exposure and the range of rupee outcomes. Any hedging or payment arrangement required the proper treasury, legal and qualified advisory review; I did not treat a spreadsheet sensitivity as a completed risk-management action.

Rohan accepted a budget discussion that retained both scenarios and required a fresh assessment before the supplier commitment. We did not claim to have avoided ₹1 crore loss or saved the difference. The higher amount was not an expense already incurred, and the lower amount was not a binding supplier price in rupees. The useful change was that the decision-maker could see how the same research plan depended on a financial assumption that the research team did not control.

The cost was a less simple approval discussion and additional coordination before commitment. I would now show the currency basis beside the first rupee figure, including exclusions and the date or status of the assumption. A CFO should not let a convenient conversion acquire more certainty as it travels through successive presentations. The purpose of the sensitivity was to improve the choice, not to turn finance into a forecaster of exchange rates.

In 2025 a management dashboard showed ₹24 crore as annualised recurring demand for a selected sales portfolio. The figure included ₹3.6 crore of one-off commissioned studies. Those studies were valid commercial wins, but no corresponding repeat purchase had been contracted. I had previously accepted the broad dashboard label because it made the portfolio easier to summarise. The planning discussion revealed that colleagues were interpreting it as evidence of a more durable revenue base than the contracts supported.

Sales colleagues objected that removing the studies would make their achievement look smaller. They had won substantial work, and some customers might return. I agreed that the business should recognise that contribution. I asked the team to distinguish the value of the won project from the evidence that it would recur. The revised recurring component was ₹20.4 crore, with ₹3.6 crore shown separately as one-off commissioned work. The total remained ₹24 crore within the management measure.

This was a correction to a planning dashboard, not cancellation of contracts, a cash outflow or a restatement of statutory revenue. Finance and the appropriate people owners reviewed future performance definitions without retrospectively treating valid project sales as misconduct. Rohan supported showing both categories and asked any assumed repeat demand to carry its own basis in the next forecast. We did not set the probability of repetition to zero; we stopped describing an uncontracted possibility as though it had the same standing as the recurring component.

The consequence was a less flattering recurring-demand headline and a more honest starting point for planning capacity. My own error belonged in the explanation. A useful commercial measure should not require the sales team to guess which meaning finance will give it later. I would now define the measure, its exclusions and the decision it is meant to support before using it in incentives or budgets. Precision should preserve real achievement while preventing that achievement from proving a future purchase it cannot establish.