Finance Manager Interview Questions

I treat the budget process as a planning exercise, not an administrative one. I start six to eight weeks before the new period by reviewing the prior year: actuals versus budget by line, variance analysis, and any structural cost changes such as headcount shifts or new contracts. I then hold planning sessions with each budget owner to understand their priorities for the coming year and translate those into financial line items. I use a bottom-up build with a top-down sense check: the sum of departmental plans gets compared to revenue assumptions and margin targets, and I work through any gaps collaboratively before the budget is finalised. Once approved, I hold monthly variance reviews with each budget holder, focusing on the three to five lines that are driving the most material variance. I never let a variance sit unexplained for more than one month.

Accuracy starts with process design: clear cut-off rules, defined ownership for each balance sheet and P&L line, and a close calendar that everyone follows. I maintain a month-end close checklist that specifies what needs to be done, by whom, and by when, and I track completion daily in the final week of close. For complex areas like accruals or provisions, I maintain assumptions logs so that every estimate has a written rationale that can be reviewed and challenged. I run a pre-close review two days before the close deadline to catch any open items early. On the timeliness side, I work backwards from the reporting deadline to set internal milestones. I also invest in process improvement: every quarter I identify one manual step in the close process and work to automate or eliminate it.

I adapt the communication format to the audience. For the executive team I prepare a short narrative pack: three to five key messages, supported by the most relevant charts, with the detailed schedules as appendices. The goal is to answer the question "so what?" before it is asked. For operational managers I focus on the numbers that are within their control: their cost lines, their headcount, their variances. I remove lines that are corporate allocations or costs they cannot influence. For board reporting I follow a structured format: results versus budget, results versus prior year, key drivers, and the updated full-year outlook. I always frame financial data in business terms: "marketing spend is 15% over budget because we brought forward the campaign launch" lands better than "line 47 is adverse by £120k."

During a quarterly review at my previous company I noticed that our largest customer, which represented 28% of annual revenue, had reduced their order volume by 35% over three months. This had not triggered any sales-team alert because each individual order reduction was within normal fluctuation. When I aggregated the quarterly trend, the signal was clear. I raised it immediately with the CEO and the sales director. We pulled the full account history, ran a cash flow stress test assuming the relationship ended within six months, and identified that we would breach a debt covenant if revenue fell by more than 20%. We used that analysis to accelerate conversations with the customer, restructured the account pricing, retained the customer, and built an early warning dashboard for any customer representing more than 10% of revenue.

Midway through a financial year I had to inform the board that we were tracking to miss our EBITDA target by approximately 18% due to a combination of unexpected cost overruns in one department and a delay in a product launch. I prepared by completing a full root cause analysis and modelling three scenarios: do nothing, take immediate cost actions, and a hybrid. I presented the situation clearly without softening the numbers, explained the drivers without assigning blame, and recommended the hybrid scenario with a specific action plan and timeline. I had already pre-briefed the CFO so that the board had context before the meeting. The board approved the plan and we closed the year at 11% below target, which was an improvement on the trajectory at the time of the presentation.

When I joined my previous company, the monthly close took 14 days and the management accounts were often contested because different teams were working from different data extracts. I mapped the close process end to end in my first month and identified three root causes: manual journal preparation in Excel with no review step, two separate data pulls from the ERP that sometimes diverged, and no standardised pack template. I introduced a single ERP extract, a journal review sign-off step, and a locked pack template. Close time reduced from 14 days to 7 over three months and the number of restatements dropped from an average of three per month to zero. The management team responded to the faster reporting by making faster decisions.

I build models from the bottom up, starting with the key business drivers rather than prior-year actuals. For a revenue forecast, that means understanding the sales pipeline, conversion rates, average deal size, and retention rates, not just extrapolating a trend line. I keep models simple enough that any assumption can be changed and the impact flows through automatically, and I build in a clearly labelled assumptions tab so that anyone reviewing the model can see the logic without reverse-engineering formulas. I run three scenarios for any material decision: base, downside, and upside. The downside scenario uses a plausible worst case, not a mild miss. I also document what would have to be true for each scenario to occur.

I maintain a rolling 13-week cash flow forecast updated weekly. The 13-week horizon is long enough to give early warning of a liquidity shortfall but granular enough to be action-able. I distinguish between committed cash flows (contracted payables and receivables) and forecast cash flows (based on pipeline and operational plans). I review the variance between forecast and actual weekly and investigate any material differences before they compound. I maintain a minimum cash buffer agreed with the board, and I monitor covenant compliance monthly, not just at reporting periods. On the working capital side, I work closely with the accounts receivable team to track debtor days and follow up on overdue balances.

I start with the strategic rationale before looking at the numbers: does this investment align with where the business is trying to go? For the financial evaluation I use NPV as the primary metric, with IRR as a supporting calculation. I am sceptical of IRR in isolation because it can be manipulated by the shape of the cash flows. I build the model using conservative assumptions for benefits (I apply a 20-30% haircut to management estimates) and full-cost assumptions for costs (including implementation, change management, and opportunity cost). I also run a sensitivity analysis on the two or three assumptions the return is most dependent on, and I consider non-financial risks: execution risk, dependency risk, and reversibility.