Purpose of the Role

This role exists to stop unbudgeted or inefficient spend before it happens, not to report on it after. The person controls first, then validates. Every cost or expense above the defined threshold gets checked against the approved budget before it is committed.

If it doesn't fit, it doesn't go through without a documented reason and a sign-off. The same person also runs management accounting for both entities — tracking actuals against budget by cost center, spotting inefficiencies, and pushing HODs toward corrective action instead of just flagging a number in a report.

Core Mandate: Control Before Validation

The process this role owns has two stages, and the order matters.

Control

Before any cost or expense commitment — PO, contract, hire, capex, opex line — is finalized, it is checked against the approved budget for that cost center and period. If it's within budget, it moves. If it's not, it's held, and the HOD either justifies the exception or resubmits within budget.

Nothing above the defined threshold gets committed without this check.

Validate

Once spend is approved and moving, the role continues to check whether it was the right spend, not just an approved one. This is where inefficiencies get caught — a cost that fits inside the budget line but shouldn't have been incurred at all, or should have been structured differently.

Key Responsibilities

- Design and own the budget control workflow across Ishan Technologies and Saksham AI — approval thresholds, sign-off chains, escalation path to CFO for exceptions.
- Check every cost/expense commitment above the defined threshold against the approved budget before it is released for payment or contracting.
- Track actuals against budget by cost center and HOD, monthly at minimum, and flag variances as they emerge rather than at quarter close.
- Identify inefficiencies in spend — duplicate vendors, avoidable overruns, mis-costed projects,



recurring exceptions — and ask HODs the right questions to find the root cause.
- For every inefficiency or variance identified, propose a specific corrective action, agree it with the HOD, and track it to closure.
- Build and maintain a corrective action log: what was found, what was proposed, who owns the fix, and by when.
- Run monthly or fortnightly budget reviews with each HOD, focused on their cost centre specifically.
- Report to the CFO on budget health, open exceptions, and corrective action status — not just variance numbers, but what's being done about them.
- Manage and develop the small analyst team supporting this function across both entities.

Corrective Action Process

Minimum structure the role is expected to run:

- Identify — variance or inefficiency flagged through the monthly review or the pre-commitment check.
- Diagnose — sit with the HOD to establish the actual cause, not the stated one.
- Propose — a specific corrective action with an owner and a deadline, not a general recommendation.
- Track — corrective action logged and reviewed at the next cycle until closed.
- Escalate — anything not closed within two review cycles goes to the CFO with the HOD's explanation attached.

Stakeholder Interaction

Works directly with every HOD across Ishan Technologies and Saksham AI, specifically on their cost center's budget adherence and spend efficiency. This isn't a finance-to-business handoff — the role sits with HODs, walks through their numbers, and holds them to the corrective actions they've agreed to.





Reports outcomes and open items to the CFO on a regular cadence.

OKRs and Metrics

Objective

Key Results

How It's Measured

Every rupee committed is checked before it's spent

100% of commitments above threshold checked against budget before release; zero unapproved overruns without CFO sign-off

Pre-commitment compliance rate; count of unauthorized overruns per quarter

Inefficiencies get caught and fixed, not just reported

Inefficiencies identified per quarter; corrective action agreed within 2 weeks of identification; corrective actions closed within the quarter raised

Number identified vs. number closed; average days from identification to agreed action; % closed on time

HODs manage their budgets instead of working around them

Monthly review held with 100% of HODs; variance explanation received within 5 working days; recurring variance (same cause, 2+ consecutive months) reduced

Review completion rate; average response time; recurring-variance count trend

Spend discipline shows up in the numbers

Validated cost savings/avoidance (₹); reduction in cost centres exceeding budget by more than X%

Quarterly savings tracker; count of cost centres over threshold

Note: exact targets (thresholds, ₹ values, time limits) to be set once a baseline quarter of data is available from both entities. The structure above is ready to run as soon as that's in place.

Qualifications and Experience

- CA / CMA or equivalent, 8–12 years in management accounting, FP&A;, or budget control, with at least 3 years in a role that had direct authority over spend approval, not just reporting on it.
- Experience working across multiple cost centers or business units, ideally in a multi-location or multi-entity setup.
- Comfortable holding a line with HODs — this role needs someone who can say no to a spend request and explain why, without turning it into a fight.
- Working knowledge of ERP-based budget and PO workflows.

📌 Senior Manager Budget Control & Management Accounting (Surat)
🏢 Ishan Netsol Private
📍 Surat