variance-analysis
SolidUse when explaining a dated actual-versus-budget or actual-versus-forecast variance for a comparable finance period. Not for tracking close checklist completion; use close-status.
Install
Quality Score: 83/100
Skill Content
Details
- Author
- davekilleen
- Repository
- davekilleen/Dex
- Created
- 7 months ago
- Last Updated
- yesterday
- Language
- Python
- License
- NOASSERTION
Integrates with
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
finance-month-end-variance-analysis
Runs month-end variance analysis in the only order that works: reconciliation first, explanation second, so that anything failing to tie out is reported as the finding rather than explained as a variance. Decomposes explained movement into price, volume, mix, timing, FX and one-off effects and refuses to produce commentary when the ledger, sub-ledger or prior-period figures were not supplied. Use at month-end or quarter-end close, when a P&L or cost line moved unexpectedly, when preparing the close pack, or when a reviewer asks why a number changed. Trigger on 'month-end', 'variance analysis', 'why did this line move', 'close pack', 'flux analysis', 'reconciliation', 'period-over-period'. Not for forward-looking budget narrative and forecast implications (use finance-budget-vs-actual-commentary) or for assessing individual expense claims (use finance-expense-policy-triage).
variance-analysis
Explains budget-vs-actual or period-over-period variances: sets a materiality threshold first, builds the variance table in dollars and percent, decomposes drivers (price, volume, mix, timing, one-offs), draws a bridge waterfall, and writes the so-what per material line with forecast impact. Use when the user says 'why are we over budget', 'explain the miss vs plan', 'build the monthly flux commentary', or 'what drove the revenue variance'.
finance-budget-vs-actual-commentary
Turns a reconciled budget-versus-actual position into cost-centre commentary that a budget holder can act on: driver-based explanation, an explicit full-year implication for every variance, a named owner and action, and a hard refusal to write narrative for figures that were never supplied or were not reconciled first. Use when preparing budget-holder commentary, a monthly business review, a cost-centre pack, a forecast update, or when a budget owner asks what their overspend means for the year. Trigger on 'budget vs actual', 'BVA', 'cost centre commentary', 'forecast update', 'why are we over budget', 'management commentary', 'run rate'. Not for the reconciliation and period-over-period flux that must precede it (use finance-month-end-variance-analysis) or for judging whether a specific claim is policy-compliant (use finance-expense-policy-triage).