variance-analysis

Solid

Use 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.

AI & Automation 476 stars 127 forks Updated yesterday NOASSERTION

Install

View on GitHub

Quality Score: 83/100

Stars 20%
89
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

<!-- Generated from `.claude/skills/_available/finance/variance-analysis/SKILL.md` by `scripts/generate-agents-skills.py`. Do not edit. --> ## When to use Use when a finance or leadership user needs an evidence-backed explanation of actuals against an approved budget or forecast for a named period, category, or total. Confirm the comparison period and basis before calculating. Do not use this skill to post or reclassify ledger entries, change a budget or forecast, approve corrective action, or provide audit sign-off. Not for close-status tracking, tax advice, or a financial decision made on behalf of a human owner. ## Inputs and source discipline 1. Capture the period, comparison basis, metric definition, actual source, budget/forecast source, source dates, date checked, and explicit `as-of` date. Record unit, currency, sign convention, and time window for every input; never invent a missing date or denominator. 2. Prefer reconciled ledger or close-package actuals, then an approved budget or forecast, then dated operational reports, then dated context in meeting notes. A narrative explanation is not evidence of a number. Preserve source hierarchy and contradictory inputs. 3. Validate that actual and comparison values measure the same category, period, unit, currency, accounting basis, and aggregation. Convert only with a cited rate or rule and date; otherwise mark the comparison not comparable rather than forcing a result. ## Method 1. Work read-only ...

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

AI & Automation Listed

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).

0 Updated 1 weeks ago
alihusains
AI & Automation Listed

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'.

15 Updated 2 days ago
alebgl77
AI & Automation Listed

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).

0 Updated 1 weeks ago
alihusains