AI Variance Analysis for FP&A Teams — deFacto Analysis

How the Analysis agent works in deFacto

An FP&A analyst types a variance question — for example, “Why is Q3 revenue below budget?” — and the Analysis agent begins by planning the extract: identifying which dimensions, members, and time periods are relevant, and asking the analyst to confirm before running anything. This plan-then-confirm step prevents the agent from pulling the wrong scope and wasting time on a bad extract.

Once the analyst confirms, the agent resolves all dimension labels by verifying they exist in the model. It will not proceed with a member name that does not exist — it asks for clarification rather than approximating. After verification, it stages the five-dataset variance pack as structured files: actuals values, budget values, actuals comments, audit values, and audit comments. The analyst can opt out of any dataset, but by default all five are included.

The agent then runs the requested analysis — variance, descriptive statistics, member ranking, correlation, trend, or custom Python — and returns a report card with a plain-language summary and suggested follow-up questions. The full source data sits alongside the summary, so finance can verify every number before presenting in a review.

Five datasets give variance a full context, not just numbers

Every variance analysis with the Analysis agent stages five datasets unless the analyst explicitly opts out: actuals values, budget values, actuals comments, audit values, and audit comments. This matters because a number alone does not explain a variance — the comment attached to it does, and the audit trail shows who changed it and when. A CFO who sees a $2M unfavorable revenue variance and then immediately sees the associated comment (“Q3 contract delayed to Q4, field confirmed Aug 8”) can close the meeting in five minutes instead of forty. Without the comment and audit data, the analysis is incomplete.

The workflow is plan-confirm-resolve-analyze-summarize

The Analysis agent does not run a query and return a result — it runs a structured workflow. Plan: identify scope and confirm with the analyst. Resolve: verify every dimension label against the model before extracting. Stage: pull the five-dataset pack as structured files. Analyze: run variance, descriptive statistics, ranking, correlation, trend analysis, or custom analysis depending on the request. Summarize: return a report card with a plain-language narrative and follow-up options. Each step is transparent — the analyst can see what the agent is doing and why.

Structured analysis tools replace ad hoc scripts

The agent runs a defined set of structured analyses — variance for budget vs actual differences, descriptive statistics for distribution and spread, ranking for top and bottom contributors, correlation for relationships between metrics, and trend analysis for period-over-period direction. For custom analytical questions that fall outside these categories, the agent can run Python-based analysis as well. This means the analysis is repeatable: the same request returns the same methodology the next quarter, which matters when the CFO asks the same question at every close.

Dimension verification means no invented members

The agent verifies every dimension label against the model before any extract runs. If a member does not exist, the agent says so and asks for clarification — it does not proceed with an approximate match.

This is a meaningful shift from how most FP&A variance analysis actually happens. In a typical spreadsheet workflow, a finance analyst builds a pivot table or VLOOKUP against exported data, selects a cost center or product line by typing or filtering, and the formula runs whether or not the selection is accurate. A typo, a renamed member, or a misremembered hierarchy level produces a result — it just happens to be the wrong one. The error may not surface until someone in the review room asks a follow-up question.

The Analysis agent cannot do that. It checks the model first. If the cost center doesn’t exist as named, it stops and asks. The result is that every output is guaranteed to reflect the actual members in the plan — not an approximation, not a renamed dimension from last quarter, not a deleted entity that Excel cached. For finance teams running variance analysis that will be presented to a CFO or audit committee, that guarantee is worth more than speed.

Mid-market analytics lead: deFacto 4.55 vs Vena 4.30, Planful 4.05

In the mid-market peer table, deFacto scores 4.55 on analytics, compared to Vena at 4.30 and Planful at 4.05 (industry survey of planning platforms, July 2025). The Analysis agent is the primary driver of that analytics score — a structured, five-dataset variance capability with source citation and audit trail is materially different from dashboard-level analytics that surface charts without the underlying context.

Where variance analysis fits in the deFacto model

The Analysis agent is one of many options in our conversational agents. Conversational AI answers general planning questions. The Analysis agent goes deeper: it plans a structured extract, verifies members, stages datasets, and runs statistical analysis. dF Anomaly is a separate tool — it detects drift and writes companion scenarios. Do not collapse these into one “analysis” capability; they are distinct tools with distinct outputs.

See also: AI planning software hub · Compare analysis platforms · Compare reporting platforms · Compare to Vena · Compare to Planful