From preparing schedules to owning financial challenge

Mandate

Make financial assumptions, product economics and customer dependence intelligible for executive and board decisions

Outcomes

• Corrected an unweighted contribution summary before pricing approval
• Separated production-volume allocation from claimed cash savings
• Added parent-group exposure alongside legal customer accounts

Decisions in context

I lead twelve finance colleagues through two heads and control ₹2.8 crore annual function expense. My enterprise remit covers financial review and controls, not sole authority over the company's commercial or production choices. The role requires me to explain assumptions to the CEO and invited board discussions, including when a finance-approved summary needs correction. The contribution case tested that responsibility directly. I withdrew a persuasive rate and showed the weighted rupee basis before a pricing decision relied on it. My work with operations and commercial teams also separates volume assumptions from expense reductions and legal debtor accounts from common customer exposure. I hold no equity or statutory directorship. Those facts remain explicit when I describe my current authority or discuss how the experience might contribute to another board. The value lies in the decisions I can help examine, not in an implied governance appointment.

Reason for the move

Current role; considering a manufacturing finance mandate and a compatible outside board contribution

Mandate

Connect plant economics with company reporting, budgeting and customer-credit analysis

Outcomes

• Made product-cost boundaries explicit in management reports
• Distinguished individual debtor records from wider customer relationships
• Improved review of volume assumptions before budget approval

Decisions in context

The controller role widened my view from the plant to the company's financial account. I led nine colleagues and managed ₹1.7 crore annual finance expense, coordinating budgets and reviews rather than approving every operating decision. Commercial managers needed customer-level analysis that could support a conversation about terms. Directors needed to understand how those relationships fitted together. I began asking whether separate account codes represented separate economic dependence or merely separate billing entities. The same habit applied to product reporting: a contribution measure needed a clear cost boundary before two lines could be compared. My reports went through the CFO, and I learned to explain the question behind an adjustment without overclaiming what the data proved. Promotion in 2021 gave me responsibility for that final financial challenge and for supporting colleagues when a corrected analysis changed the direction of a proposal.

Reason for the move

Promoted to chief financial officer

Mandate

Explain production costs and planning assumptions to plant and finance leadership

Outcomes

• Connected costing reviews with production-planning discussions
• Separated observed output from future-volume assumptions
• Clarified the variable-cost basis used in product comparisons

Decisions in context

Joining the manufacturer put me inside the operating discussions that had previously arrived as client schedules. Six colleagues supported plant costing and accounts, with ₹84 lakh annual function expense. I worked with supervisors to understand how product configuration, material use and production sequence affected the financial view. Their practical explanations often revealed a reason for variation that a summary report concealed. I also saw how a planned production number could be repeated until it appeared to be an achieved result. My task was to preserve that distinction and explain the financial sensitivity. Engineering and quality determined product suitability; finance did not approve a crate's technical design through a cost calculation. The role prepared me for enterprise control by connecting the assumptions in a report with the colleagues and decisions that produced them, while respecting the authority of each discipline.

Reason for the move

Promoted to enterprise financial control

Mandate

Review client cost schedules and document their assumptions before management discussion

Outcomes

• Required production bases to accompany unit-cost schedules
• Reviewed totals against their underlying periods and categories
• Escalated unclear client assumptions to the engagement manager

Decisions in context

I supervised five colleagues preparing industrial cost schedules, with ₹29 lakh annual team expense and no authority over client spending. The work taught me that checking a calculation and understanding its economic meaning were related but different tasks. A fixed expense could be divided correctly by a production figure that had not been explained. Two margin rates could be accurate individually while answering different questions about cost. I asked colleagues to retain the assumptions supplied by clients and refer unresolved points to the engagement manager. I did not present our schedules as independent technical assurance or use them to make decisions reserved for the client's management. Moving into a plant-finance position let me test those questions closer to production and take responsibility for the recurring management account, rather than support it from outside through periodic assignments.

Reason for the move

Joined a manufacturing client-sector business for direct plant-finance responsibility

Mandate

Prepare reconciled account schedules with traceable periods and source records

Outcomes

• Reconciled schedules to the underlying account records
• Flagged mixed periods before comparisons were circulated
• Learned to distinguish preparation work from approval authority

Decisions in context

I joined after my commerce degree and worked in a four-person preparation group without direct reports or spending authority. Much of the work involved tracing a total to the records behind it and checking whether the comparison used the same period. That could seem less visible than the management conclusion, but I saw how an unexplained total encouraged confident interpretations it could not support. I learned to ask a specific question and show the record that prompted it, rather than call a client figure wrong without understanding its purpose. The supervisor reviewed my work before it reached an engagement manager. That sequence taught me the difference between preparing evidence and approving an account for use. Promotion brought responsibility for other colleagues' schedules and made me more attentive to how a review could miss a misleading summary even when individual numbers reconciled.

Reason for the move

Promoted to supervise cost-account preparation