How We Used Cortex Code to Turn Finance Variance Analysis into a Live, Intelligent Workflow

How We Used Cortex Code to Turn Finance Variance Analysis into a Live, Intelligent Workflow

Skip to content

Blog / Product and Technology / How We Used Cortex Code to Turn Finance Variance Analysis into a Live, Intelligent Workflow

MAY 28, 2026 / 9 min read Product and Technology How We Used Cortex Code to Turn Finance Variance Analysis into a Live, Intelligent Workflow

Brad Floering +2

FP&A Should Spend Close on Analysis — Not Spreadsheet Assembly

Every FP&A team knows the pattern. Close begins, actuals start moving, and before anyone can explain what changed in the business, someone has to rebuild the workbook.

That was our reality. Each month, our team spent hours stitching together department-level P&Ls, aligning mappings, refreshing actuals, formatting outputs and chasing one more cut of the same budget vs. actual analysis. In a normal close, that meant three to four hours lost before the real work of analysis began. When a mapping or linking issue surfaced, that could stretch to five or six.

And that is the core problem: FP&A teams are hired to explain performance, pressure-test the plan and help leaders make decisions. But too often, a meaningful share of the job is spent on logistics: pulling actuals from the ERP, aligning charts of accounts, mapping to the budget model, reconciling timing and reclasses, and rebuilding the same workbook every close.

Our previous budget vs. actual process reflected exactly that. During close, Corporate FP&A consolidated department-level P&Ls into a single Excel workbook with variances across every line item. That workbook was distributed to the broader FP&A organization, and each team manually added commentary and formatting for the departments they supported. It worked, but it was fragile, repetitive and slow.

The bigger issue wasn’t the workbook; it was the workflow

Manual effort was only part of the challenge.

Actuals flowed from Workday on a two-hour refresh cycle, so journal entries posted by accounting were invisible until the next scheduled update. The workbook could not be finalized until accounting had completed posting for the period. And every organizational change — for example, a new cost center, a new hierarchy, a restructuring — created manual rework across formulas, mappings and layouts.

In other words, the process was not just time-consuming; it delayed finance’s ability to see what was happening and act on it. Instead of helping the business understand emerging variances in real time, FP&A was stuck assembling the infrastructure required to begin the conversation.

That was the opening for Snowflake Cortex Code, or CoCo.

Why we turned to CoCo

The question for us was not whether we could build a better budget vs. actual workflow in Snowflake. The question was whether CoCo could help us build it fast enough, directly enough, and simply enough for finance to own.

That is what made CoCo compelling in this use case. Because it runs natively in Snowflake, it had context on the data model, cost center and ledger mappings, and forecast tables and journal lines already powering the workflow. We were not starting from a blank page in a disconnected tool. We were building directly where the data, logic and governance controls already lived.

That context changed the build process. Instead of spending weeks onboarding data into a separate development environment, analysts could describe the variance view they wanted in plain English, and CoCo could help wire it to the right Snowflake objects. That dramatically compressed the distance between idea and working application.

From static workbook to live finance application

A live dashboard is only as good as the structure underneath it, so we first established a clean hierarchy in Snowflake across four nodes: leader, BvA section, headcount and cost center. That gave users a full drill-down view of the P&L from the consolidated level all the way down to an individual cost center, without manual pivoting or workbook gymnastics.

From there, CoCo accelerated the build. With it, we created a budget vs. actual dashboard in Streamlit that replaced the static Excel workbook entirely. The pipeline runs continuously, pulling actuals directly into Snowflake without manual intervention. No one has to trigger a refresh, rebuild a tab or redistribute a file.

The impact during close is immediate. As accounting posts entries, the dashboard reflects them. That removes the two-hour refresh lag as a blocker and changes how FP&A operates. Teams no longer have to wait for a workbook to be assembled and distributed. They can open the dashboard during close, review variances as they emerge, and investigate major discrepancies before the formal review cycle even begins.

Built in weeks, not months

One of the clearest proofs of value was speed.

We had a prototype within two weeks and a fully functional app live within a month. Stakeholder feedback turned into code changes the same afternoon instead of waiting for the next sprint. Before CoCo, a project like this likely would have required dedicated BI support and could have taken up to three months to deliver a working version.

That matters because the benefit was not just a better end product. CoCo changed the economics of getting there. Instead of sitting in a technical backlog, finance could move from business problem to working solution while the need was still immediate.

More than a dashboard: a better way to work

The old Excel model locked users into a fixed view. The new application does not.

Users can toggle across forecast versions and time periods, adjusting the view to the scenario most relevant to their analysis instead of waiting for a new published cut. Adding a new cost center or department no longer requires a manual rebuild. As the business grows, the dashboard grows with it. New business units, reporting dimensions and organizational changes are reflected automatically through the underlying hierarchy and source data.

That is important, but the bigger shift is that the workflow now supports the way FP&A actually works. Users can move from the consolidated P&L down to the cost center level to isolate the precise driver of a variance. The app is not just faster than the workbook. It is better aligned to the questions finance actually needs to answer.

Where CoCo starts to change the job

This is where the use case becomes more compelling than simple dashboard modernization.

Selected expense categories already…