Skip to content

Variance Analysis

Overview

Variance analysis in treasury refers to the systematic comparison of forecasted cash flows against actual results to understand prediction accuracy and identify drivers of deviation. This enables treasury teams to validate their forecasting processes, take corrective actions when predictions miss, and build confidence in their cash management decisions.

For treasury teams, variance analysis answers the fundamental question: "Can I trust my forecast?" It provides the data needed to explain forecast reliability to stakeholders, configure forecasting models appropriately, and identify anomalies that require investigation.

For detailed ICP context and terminology, see fundamentals.md

Top Jobs & Desired Outcomes

Full history: jobs.md

1. Investigate variances between forecast and actuals to create accountability ✓

Desired Outcomes: - Minimize the time to identify root causes of forecast variances - Minimize the time required to identify which categories are causing variances - Reduce manual effort to drill down from summary to transaction level - Increase the ability to make informed model configuration decisions - Provide data-backed feedback to business teams when their forecast inputs don't match actuals - Increase ability to show forecast improvement to management

Sources: ON x5, Personio x3, Sonder, Volvo Cars (Confirmed) - "The most critical part of reporting"

2. Confirm treasury-initiated payments went through daily ⚡

Desired Outcomes: - Minimize the time to identify delayed or failed payments - Reduce the risk of missing critical payment failures - Increase confidence that funded accounts have correct balances

Source: ON (Emerging)

Key Pain Points

Full history: pain-points.md

  • Data validation consumes time before analysis can start - Hours of prep work before the actual analysis (Source: Personio)
  • Customer inflows variance is a "black box" - Many factors impact collections; hard to explain (Source: Personio)
  • No formal variance analysis process exists - Teams are building this capability from scratch (Source: ON)
  • Manual payment verification required - Need to manually check if treasury-initiated payments went through (Source: ON)
  • AP data gaps - Incomplete data limits variance analysis completeness (Source: ON)
  • Holiday schedules across countries affect timing unpredictably - Have to Google to explain zero collections (Source: Sonder)
  • Understanding the "why" requires manual investigation - Cross-team outreach needed (Source: Sonder)

Key Opportunities

  • Dedicated variance analysis section - Not just a sub-function of forecasting
  • Configurable variance thresholds - Alert when variance exceeds meaningful levels (e.g., 20%)
  • Flexible time frame selection - Weekly, bi-weekly, custom periods
  • Anomaly detection - Flag unusually large variances automatically

Open Questions

  • [ ] What variance thresholds are meaningful across different company sizes?
  • [ ] How to differentiate timing variances from true forecast misses?

Last updated: 2026-02-17 | Sources: 17 transcripts (view all)