4) Technical and professional questions (UK-focused)
This is where you separate yourself from candidates who can “talk finance” from those who can control it. UK employers will test your grip on IFRS vs UK GAAP, audit interaction, revenue/cost recognition, and systems. They also care about how you build a narrative from numbers—especially for boards and non-finance leaders.
Q: How do you ensure balance sheet integrity month to month?
Why they ask it: A Controller is judged on balance sheet discipline, not just P&L commentary.
Answer framework: RCR (Reconcile → Challenge movements → Resolve root cause).
Example answer: “I run a balance sheet review pack with reconciliations, aging, and movement analysis for every material account. I expect clear support for accruals, prepayments, payroll liabilities, VAT, and fixed assets, and I challenge unusual movements with the owner before close sign-off. Where we see recurring recon breaks, I fix the process—often upstream in AP, billing, or payroll—so the balance sheet doesn’t become a dumping ground.”
Common mistake: Treating reconciliations as a tick-box exercise rather than a control system.
Q: Talk me through your approach to revenue recognition under IFRS 15 (or UK GAAP equivalent).
Why they ask it: They need to know you won’t create a revenue time-bomb.
Answer framework: 5-step IFRS 15 walkthrough (identify contract → performance obligations → price → allocate → recognize).
Example answer: “I start by mapping the contract and identifying performance obligations—especially where there are implementation services, support, or variable consideration. Then I assess whether revenue is recognized over time or at a point in time, and what evidence supports that. I make sure the accounting aligns with billing and operational delivery so we don’t end up with unexplained contract assets or deferred revenue swings. If it’s complex, I document the position early and align with auditors before year-end.”
Common mistake: Giving a textbook definition without showing how you operationalize it in systems and close.
Q: How do you decide between IFRS and UK GAAP (FRS 102) treatments in practice?
Why they ask it: UK entities vary—group reporting, statutory accounts, and policy choices matter.
Answer framework: Context → Standard → Policy → Disclosure → Audit trail.
Example answer: “First I clarify the reporting basis: statutory under FRS 102 versus group consolidation under IFRS. Then I identify the policy areas that drive differences—leases, financial instruments, revenue, and share-based payments are common ones. I document the policy choice, ensure consistent application, and build disclosures early so year-end isn’t a scramble. The key is a clear audit trail: memos, calculations, and approvals.”
Common mistake: Assuming every UK company reports under IFRS, or ignoring statutory vs group requirements.
Q: What’s your approach to VAT control and reporting in the UK?
Why they ask it: VAT errors create cash risk and HMRC pain.
Answer framework: Process map (data sources → coding rules → reconciliations → review → submission).
Example answer: “I focus on correct VAT coding at source, because cleanup at quarter-end is expensive. I reconcile VAT control accounts to returns, review exceptions like partial exemption, reverse charge, and import VAT where relevant, and I sanity-check trends against revenue and spend. I also make sure documentation is retained and that any manual adjustments are clearly supported and approved.”
Common mistake: Treating VAT as ‘just a tax team thing’ instead of a core control area.
Q: Which ERPs and reporting tools have you used, and what did you improve in them?
Why they ask it: They want a Finance Controller who can modernize reporting, not live in spreadsheets forever.
Answer framework: Tool → Use case → Improvement → Outcome.
Example answer: “I’ve worked with NetSuite and SAP, plus Power BI for management reporting. In NetSuite I improved the chart of accounts mapping and automated recurring journals to reduce manual posting. In Power BI I built a margin bridge dashboard tied to the GL and sales data, which cut the time to produce weekly trading updates from half a day to under an hour. Excel is still essential, but I try to make it the last mile—not the whole pipeline.”
Common mistake: Listing tools like a CV keyword dump with no business outcome.
Q: How do you build a management accounts pack that leaders actually use?
Why they ask it: They’re testing whether you can turn numbers into decisions.
Answer framework: Audience-first pack design (Decisions → KPIs → Drivers → Risks → Actions).
Example answer: “I start with what decisions the leadership team makes monthly—hiring, pricing, spend controls, cash planning. Then I build a pack that leads with KPIs and driver bridges: revenue volume vs price, gross margin by product, overhead run-rate, and cash conversion. I keep commentary tight: what changed, why, what we’re doing next. If a page doesn’t trigger a decision or a question, it doesn’t belong in the pack.”
Common mistake: Producing a 60-page pack that’s accurate but unread.
Q: How do you handle audit requests and keep the year-end on track?
Why they ask it: UK employers want a calm, organized audit lead.
Answer framework: PBC discipline (Plan → Prepared-by-client file → Ownership → Timelines).
Example answer: “I agree the audit timeline early, build a PBC folder with clear naming conventions, and assign owners for each schedule. I front-load high-risk areas—revenue, provisions, impairment, leases—so we don’t argue in the final week. I also keep a running issues log with decisions and evidence, so nothing gets lost in email threads. The goal is fewer surprises, fewer late nights, and a clean sign-off.”
Common mistake: Treating audit as a last-minute document chase.
Q: Tell me about a time you improved working capital (cash, AR, AP, inventory).
Why they ask it: Controllers in the UK are often expected to be cash-first, especially in mid-market firms.
Answer framework: Diagnose → Interventions → Governance → Result.
Example answer: “Our DSO was creeping up because invoicing lagged delivery and disputes sat unresolved. I mapped the order-to-cash process, introduced weekly AR calls with Sales Ops, and created a dispute aging dashboard with owners. We tightened credit terms for repeat offenders and improved invoice accuracy at source. Over two quarters, DSO improved by 8 days and cash forecasting became materially more reliable.”
Common mistake: Claiming ‘I chased debt’ without showing process fixes and cross-team governance.
Q: What would you do if the ERP is down during close week and you still need management accounts?
Why they ask it: They’re testing resilience and control under pressure.
Answer framework: Contingency plan (Stabilize → Snapshot → Manual controls → Reconcile later).
Example answer: “First I’d confirm scope and ETA with IT and freeze any non-essential posting to protect data integrity. If possible, I’d take a data snapshot from the last successful extract and use controlled manual workarounds for critical items—cash, payroll, major accruals—clearly flagged as estimates. I’d communicate early to leadership what will be provisional and what the risk is. Once systems are back, I’d reconcile the manual estimates to actual postings and document the incident for audit trail and future contingency planning.”
Common mistake: Promising ‘business as usual’ without acknowledging control risk and reconciliation needs.
Q: How do you assess materiality and decide what to fix now vs later?
Why they ask it: They want judgment, not perfectionism.
Answer framework: AMR (Amount → Momentum → Risk): size, recurrence, and compliance/audit risk.
Example answer: “I look at the quantitative impact, whether it’s recurring, and the risk profile—tax, statutory reporting, covenants, or audit scrutiny. A small one-off miscode might wait; a small recurring cut-off issue becomes big fast and needs a process fix. I also consider stakeholder impact: if it distorts a KPI leaders use, it’s effectively material even if it’s below audit thresholds.”
Common mistake: Either obsessing over immaterial noise or ignoring issues until year-end.