Implementation guide
Generate Narrative from Raw Numbers
Detailed training workflow for Generate Narrative from Raw Numbers in Finance & Accounts.
Implementation guide
Detailed training workflow for Generate Narrative from Raw Numbers in Finance & Accounts.
Guided walkthrough
Problem: Variance reports show 'what' happened (e.g., +20% spend), but not 'why' it happened. Inject Raw Variance Input your Actuals vs. Budget spreadsheet into the Lab. Contextual Cross-ref AI links the overspend to specific hire dates or vendor price hikes from the Vault.
Advanced implementation notes
Automated Financial Commentary Engine Multi-Dimensional Variance Decomposition AI breaks each variance into its drivers: Volume variance (we sold more/fewer units), Price variance (unit price changed), Mix variance (product mix shifted), and FX variance (currency moved). This isolates whether the variance is operational or market-driven. Causal Attribution AI cross-references financial data with operational events: new hires (HR system), vendor price changes (procurement system), one-time purchases (PO system), and seasonal patterns (historical data).
Generates specific causal narratives: 'Marketing spend was $150K over budget due to unplanned Q3 product launch campaign approved on [date].' Materiality Filtering Not every variance deserves commentary. AI applies materiality thresholds: absolute ($50K+) and relative (>10% of line item budget). Below-threshold variances get a single-line note; above-threshold variances get full commentary with root cause and corrective action. Trend Projection AI doesn't just explain the past — it projects the impact: 'If current spend rate continues, Marketing will end
the year $600K over budget. Recommended actions: (1) Defer $200K campaign to Q1, (2) Negotiate vendor rate reduction, (3) Request budget reallocation from underspent IT line.' Stakeholder-Specific Output AI generates three versions of the same variance report: (1) Executive Summary for the CFO (3 bullets), (2) Detailed Commentary for Finance Partners (paragraph per variance), (3) Action-Oriented brief for Department Heads (what to do about it). Include a 'Forecast to Complete' with every variance report — the question isn't just 'why are we over?' but
'where will we land at year-end?' Track variance trends, not just point-in-time — AI should flag when a line item has been adverse for 3+ consecutive months, indicating a structural budget problem. Distinguish controllable from uncontrollable variances — FX movements and mandated regulatory costs are uncontrollable; travel and discretionary hiring are controllable. Don't write variance commentary as 'Costs were higher than expected' — that's describing the number, not explaining it. AI should always answer 'because...' Don't present 50 line-item
variances — executives can absorb 5-7 key messages. AI should aggregate and summarize below-materiality variances. Don't skip favorable variances — an unusually favorable variance often indicates timing (costs shifted to a future period) or under-investment (we didn't spend on something we should have). The 'Rolling Forecast' Evolution Replace the annual budget with a rolling 12-month forecast updated monthly. AI re-forecasts each line item using: actual run-rates, known commitments (signed contracts, approved headcount), and leading indicators. This
eliminates the annual 'budget season' marathon and gives leadership always-current projections instead of comparing against a 12-month-old assumption.