finance/accounting/variance-analysis/SKILL.md
Decompose financial variances into drivers with narrative explanations and waterfall analysis. Use when analyzing budget vs. actual, period-over-period changes, revenue or expense variances, or preparing variance commentary for leadership.
npx skillsauth add harsh040506/claude-code-unified-skill-plugin-library variance-analysisInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Important: This skill assists with variance analysis workflows but does not provide financial advice. All analyses should be reviewed by qualified financial professionals before use in reporting.
Techniques for decomposing variances, materiality thresholds, narrative generation, waterfall chart methodology, and budget vs actual vs forecast comparisons.
The most fundamental variance decomposition. Used for revenue, cost of goods, and any metric that can be expressed as Price x Volume.
Formula:
Total Variance = Actual - Budget (or Prior)
Volume Effect = (Actual Volume - Budget Volume) x Budget Price
Price Effect = (Actual Price - Budget Price) x Actual Volume
Mix Effect = Residual (interaction term), or allocated proportionally
Verification: Volume Effect + Price Effect = Total Variance
(when mix is embedded in the price/volume terms)
Three-way decomposition (separating mix):
Volume Effect = (Actual Volume - Budget Volume) x Budget Price x Budget Mix
Price Effect = (Actual Price - Budget Price) x Budget Volume x Actual Mix
Mix Effect = Budget Price x Budget Volume x (Actual Mix - Budget Mix)
Example — Revenue variance:
Used when analyzing blended rates across segments with different unit economics.
Formula:
Rate Effect = Sum of (Actual Volume_i x (Actual Rate_i - Budget Rate_i))
Mix Effect = Sum of (Budget Rate_i x (Actual Volume_i - Expected Volume_i at Budget Mix))
Example — Gross margin variance:
Used for analyzing payroll and people-cost variances.
Total Comp Variance = Actual Compensation - Budget Compensation
Decompose into:
1. Headcount variance = (Actual HC - Budget HC) x Budget Avg Comp
2. Rate variance = (Actual Avg Comp - Budget Avg Comp) x Budget HC
3. Mix variance = Difference due to level/department mix shift
4. Timing variance = Hiring earlier/later than planned (partial-period effect)
5. Attrition impact = Savings from unplanned departures (partially offset by backfill costs)
Used for operating expense analysis when price/volume is not applicable.
Total OpEx Variance = Actual OpEx - Budget OpEx
Decompose by:
1. Headcount-driven costs (salaries, benefits, payroll taxes, recruiting)
2. Volume-driven costs (hosting, transaction fees, commissions, shipping)
3. Discretionary spend (travel, events, professional services, marketing programs)
4. Contractual/fixed costs (rent, insurance, software licenses, subscriptions)
5. One-time / non-recurring (severance, legal settlements, write-offs, project costs)
6. Timing / phasing (spend shifted between periods vs plan)
Materiality thresholds determine which variances require investigation and narrative explanation. Set thresholds based on:
| Comparison Type | Dollar Threshold | Percentage Threshold | Trigger | |----------------|-----------------|---------------------|---------| | Actual vs Budget | Organization-specific | 10% | Either exceeded | | Actual vs Prior Period | Organization-specific | 15% | Either exceeded | | Actual vs Forecast | Organization-specific | 5% | Either exceeded | | Sequential (MoM) | Organization-specific | 20% | Either exceeded |
Set dollar thresholds based on your organization's size. Common practice: 0.5%-1% of revenue for income statement items.
When multiple variances exceed thresholds, prioritize investigation by:
[Line Item]: [Favorable/Unfavorable] variance of $[amount] ([percentage]%)
vs [comparison basis] for [period]
Driver: [Primary driver description]
[2-3 sentences explaining the business reason for the variance, with specific
quantification of contributing factors]
Outlook: [One-time / Expected to continue / Improving / Deteriorating]
Action: [None required / Monitor / Investigate further / Update forecast]
Good variance narratives should be:
A waterfall (or bridge) chart shows how you get from one value to another through a series of positive and negative contributors. Used to visualize variance decomposition.
Starting value: [Base/Budget/Prior period amount]
Drivers: [List of contributing factors with signed amounts]
Ending value: [Actual/Current period amount]
Verification: Starting value + Sum of all drivers = Ending value
When a charting tool is not available, present as a text waterfall:
WATERFALL: Revenue — Q4 Actual vs Q4 Budget
Q4 Budget Revenue $10,000K
|
|--[+] Volume growth (new customers) +$800K
|--[+] Expansion revenue (existing customers) +$400K
|--[-] Price reductions / discounting -$200K
|--[-] Churn / contraction -$350K
|--[+] FX tailwind +$50K
|--[-] Timing (deals slipped to Q1) -$150K
|
Q4 Actual Revenue $10,550K
Net Variance: +$550K (+5.5% favorable)
Complement the waterfall with a reconciliation table:
| Driver | Amount | % of Variance | Cumulative | |--------|--------|---------------|------------| | Volume growth | +$800K | 145% | +$800K | | Expansion revenue | +$400K | 73% | +$1,200K | | Price reductions | -$200K | -36% | +$1,000K | | Churn / contraction | -$350K | -64% | +$650K | | FX tailwind | +$50K | 9% | +$700K | | Timing (deal slippage) | -$150K | -27% | +$550K | | Total variance | +$550K | 100% | |
Note: Percentages can exceed 100% for individual drivers when there are offsetting items.
| Metric | Budget | Forecast | Actual | Bud Var ($) | Bud Var (%) | Fcast Var ($) | Fcast Var (%) | |--------|--------|----------|--------|-------------|-------------|---------------|---------------| | Revenue | $X | $X | $X | $X | X% | $X | X% | | COGS | $X | $X | $X | $X | X% | $X | X% | | Gross Profit | $X | $X | $X | $X | X% | $X | X% |
Track how accurate forecasts are over time to improve planning:
Forecast Accuracy = 1 - |Actual - Forecast| / |Actual|
MAPE (Mean Absolute Percentage Error) = Average of |Actual - Forecast| / |Actual| across periods
| Period | Forecast | Actual | Variance | Accuracy | |--------|----------|--------|----------|----------| | Jan | $X | $X | $X (X%) | XX% | | Feb | $X | $X | $X (X%) | XX% | | ... | ... | ... | ... | ... | | Avg| | | MAPE | XX% |
Track how variances evolve over the year to identify systematic bias:
testing
Performs quality control on single-cell RNA-seq data (.h5ad or .h5 files) using scverse best practices with MAD-based filtering and comprehensive visualizations. Use when users request QC analysis, filtering low-quality cells, assessing data quality, or following scverse/scanpy best practices for single-cell analysis.
tools
Deep learning for single-cell analysis using scvi-tools. This skill should be used when users need (1) data integration and batch correction with scVI/scANVI, (2) ATAC-seq analysis with PeakVI, (3) CITE-seq multi-modal analysis with totalVI, (4) multiome RNA+ATAC analysis with MultiVI, (5) spatial transcriptomics deconvolution with DestVI, (6) label transfer and reference mapping with scANVI/scArches, (7) RNA velocity with veloVI, or (8) any deep learning-based single-cell method. Triggers include mentions of scVI, scANVI, totalVI, PeakVI, MultiVI, DestVI, veloVI, sysVI, scArches, variational autoencoder, VAE, batch correction, data integration, multi-modal, CITE-seq, multiome, reference mapping, latent space.
testing
This skill should be used when scientists need help with research problem selection, project ideation, troubleshooting stuck projects, or strategic scientific decisions. Use this skill when users ask to pitch a new research idea, work through a project problem, evaluate project risks, plan research strategy, navigate decision trees, or get help choosing what scientific problem to work on. Typical requests include "I have an idea for a project", "I'm stuck on my research", "help me evaluate this project", "what should I work on", or "I need strategic advice about my research".
development
Run nf-core bioinformatics pipelines (rnaseq, sarek, atacseq) on sequencing data. Use when analyzing RNA-seq, WGS/WES, or ATAC-seq data—either local FASTQs or public datasets from GEO/SRA. Triggers on nf-core, Nextflow, FASTQ analysis, variant calling, gene expression, differential expression, GEO reanalysis, GSE/GSM/SRR accessions, or samplesheet creation.