Skip to website
Darius QemzanuChief Financial Officer · Essays & perspective
← All essays

Network economics and avoidable cost5 min read

Closing the loss-making depot would not remove the costs charged to it

An allocated loss supported one story; the costs that would actually disappear supported another. The closure decision needed its own financial comparison.

The depot showed a ₹30 lakh annual loss in the management account. Closing it appeared to remove a weak part of the network. When Nitin and I examined the proposed change, however, the enterprise would lose ₹2.8 crore revenue while avoiding only ₹1.9 crore of the stated costs. On that bounded annual comparison, closure would worsen cash contribution by ₹90 lakh. The reported loss was real within its accounting view; it was simply not a calculation of the decision being proposed.

An allocation explains a report, not automatically a choice

The management account contained ₹2.8 crore revenue, ₹1.4 crore variable service cost, ₹80 lakh direct fixed cost and ₹90 lakh central allocation. Those costs totalled ₹3.1 crore, producing the ₹30 lakh loss. The report was useful for discussing the resources attributed to the depot. It did not establish that all those resources would disappear if the depot closed. The first closure paper had allowed the report's boundary to stand in for the boundary of the decision, which was the enterprise rather than the local column.

The operating sponsor wanted to concentrate activity elsewhere and remove the loss from the network view. I understood the appeal. A persistent negative line can consume management attention and make another use of effort look attractive. But the proposal assumed the depot's ₹2.8 crore revenue would be lost, not transferred intact to another location. Its cost consequences therefore needed to be examined with equal care. We could not keep the convenience of the loss figure while leaving the revenue assumption and continuing obligations in different parts of the conversation.

The responsible owners identified ₹1.4 crore variable expense and ₹50 lakh of direct fixed expense that closure would avoid. The remaining ₹30 lakh of direct fixed commitments would continue, and the central costs represented by the ₹90 lakh allocation would remain in the enterprise. Reassigning that allocation to other depots could change their reported margins without reducing the underlying expense. This is the point at which a closure case can become misleading: a charge leaves one column and is described as a saving even though another part of the business must still carry it.

The stated annual comparison was therefore ₹2.8 crore revenue lost against ₹1.9 crore cost avoided. The ₹90 lakh adverse difference did not include every possible consequence. Additional closure costs, asset-disposal proceeds, financing and tax were outside the bounded illustration and would require separate work. Keeping those exclusions visible was important. I did not want to replace one incomplete claim with another by presenting the avoidable-cost view as a final valuation of every option. It was enough to show why subtracting the allocated loss did not justify the proposed decision.

The alternative needs the same discipline

An argument for retention should be tested as seriously as an argument for closure. It would be easy to conclude from the ₹90 lakh comparison that the depot was healthy or that its future was settled. Neither followed. The service could still have weak demand, an inefficient operating arrangement or costs that management ought to change. The analysis showed that this particular closure proposal did not produce the benefit suggested by the allocated loss. It did not release the team from improving the business or examining other alternatives.

I asked the commercial and operating owners to explain what a service redesign could change and which assumptions would need evidence. If revenue could be retained elsewhere, that should be presented as a supported alternative rather than added casually to the closure case after the first comparison became unattractive. If central resources could eventually be reduced, the timing, cost and responsibility for that reduction needed to be identified. Finance should not reject those possibilities, but neither should it credit their benefit before the enterprise has a credible route to achieving them.

The distinction between a continuing commitment and an avoidable cost can also change over time. An expense that remains in the immediate decision may become adjustable later. That does not make the first account wrong; it makes the decision horizon important. I wanted the annual illustration and its assumptions stated clearly enough that a later review could update them without pretending that the original number had been a timeless truth. A network decision often involves several horizons, and a single loss figure rarely explains all of them.

Our earlier repair appraisal offered a related discipline. Six hundred technically eligible crates could be repaired for ₹5.4 lakh or replaced for ₹15 lakh, but the expected service periods differed: eighteen months of extension versus forty-eight months for new units. The ₹9.6 lakh initial outlay gap was not automatically a lifecycle saving. A simple per-month illustration helped expose the mismatch without replacing a fuller appraisal. The connection is not that repair and depot closure are the same decision. It is that the financial comparison must describe what each alternative actually buys or removes.

Retaining a depot is not the end of the enquiry

Asha retained the depot while asking management to develop a more supportable redesign. That meant the allocated loss remained visible in the management discussion. I considered that preferable to creating an apparent improvement in one report by worsening the enterprise's cash contribution on the stated assumptions. We did not claim that rewriting the paper had generated ₹90 lakh. The analysis prevented us from treating a proposed deterioration as the removal of a loss; it did not itself change the service, win customers or reduce expenditure.

This is sometimes an uncomfortable position for a CFO. Colleagues may want a clear decision that closes the argument, while the evidence supports a narrower conclusion and more work. The response should not be endless analysis. It should be a defined next question, an owner and the evidence needed to choose among real alternatives. In our case, the next work concerned the service and its costs, not a request for another version of the same allocation report. Retention bought the opportunity to examine those choices; it did not make the existing arrangement permanent.

For directors, I would frame the oversight question around the difference between reported performance and the consequence of a proposed action. Both matter. A board needs management accounts to understand the business, and it needs decision-specific comparisons when management recommends changing that business. Directors should be able to ask which revenue remains, which cost disappears, which commitment continues and what is excluded from the paper. Those questions improve the collective decision without requiring the board to manage the depot or dictate the allocation method.

The case stays with me because the intuitive answer was so appealing: close the loss-making location and improve the network. The useful financial account was less comfortable. A smaller enterprise could be worse off if it discarded contribution while retaining the costs it meant to escape. I would bring that caution to another board without assuming that retention is always the right answer. The responsibility is to make the alternatives comparable, preserve their limits and ensure that a cost does not become a saving merely because its name moves to another column.