Every planning organization has this meeting. It has different names: the BVA review, the alignment sync, the pre-close huddle. The agenda is always the same. Two teams open two files, discover their numbers don't match, and spend an hour figuring out why.

The meeting feels like work. It produces a reconciled number, action items, sometimes a decision. But look at what actually happened: the organization spent senior people's time restoring an agreement that its own systems broke.

Now count how often it happens. Twice a month for BVA. Weekly during forecast season. Ad hoc every time leadership asks a question that spans two functions. At most enterprises, reconciliation isn't a meeting. It's a standing tax on the planning calendar.

Where the mismatch comes from

The numbers don't diverge because someone made an error. They diverge because the process guarantees it.

A typical BVA cycle looks like this. Data gets extracted from the ERP, the HRIS, the CRM, and the data warehouse. Someone consolidates it in Excel, organizes it into templates, and distributes it to budget owners. Budget owners respond with questions, corrections, and context, over email. The FP&A team incorporates the feedback and redistributes. Repeat until close.

Every step in that chain has a timestamp, and no two timestamps match. The version the budget owner is annotating is already older than the actuals in the warehouse. The consolidated file is a snapshot of a moving system. By the time everyone agrees on the number, the number has changed.

One finance team we work with described their prior state exactly this way: dozens of hours per cycle, twice each month, spent on extraction, manual consolidation, template distribution, and the email loops needed to clarify discrepancies. And even after all that effort, the data stayed too aggregated for the analysis anyone actually wanted to run.

The part nobody prices in

The hours are the visible cost. The invisible cost is what the reconciliation loop does to analytical depth.

When assembling the view consumes the capacity, interrogating the view doesn't happen. Variance gets explained at the department level because PO-level detail would take another week to compile. Questions from budget owners get answered next cycle. The FP&A team, which was hired to analyze, spends its time formatting.

There's also a trust cost. When stakeholders regularly discover that their numbers disagree, they stop trusting any distributed number. They build shadow files. Shadow files diverge further. The reconciliation burden grows to cover the shadow files. This loop is self-reinforcing, and process discipline alone doesn't break it, because the root cause is that everyone is working from copies.

What it looks like without copies

The structural fix is to remove the copies. When actuals feed a unified planning environment automatically, and budget owners work inside that environment rather than on distributed extracts, there is nothing to reconcile. Everyone reads the same live number, scoped by permissions to their role. Review, commentary, and analysis happen in the system, against data that is current by definition.

Artlist, a creative technology company running a complex B2B and B2C multi-product business, moved its BVA process onto Fintastic and cut time spent on the cycle by 70%. The deeper change was qualitative: analysis now runs down to PO-level granularity, budget owners self-serve against live data, and the twice-monthly consolidation ritual simply no longer exists. As their FP&A manager put it, BVA went from a report someone prepares to a view that is always available.

That is the general pattern. The reconciliation meeting doesn't get shorter. It gets deleted, because the condition it existed to fix, divergent copies of the truth, is no longer produced.

A question for your next planning cycle

Tally the hours your organization will spend this quarter restoring agreement between numbers your own systems let drift apart. Include the meetings, the email loops, the shadow-file maintenance, and the analyst time spent consolidating instead of analyzing.

Then ask whether that's a process to optimize or a structure to replace.

This is one of the questions on the table at our fall dinner series, where we're hosting planning leaders from finance, revenue, workforce, and operations in Boston, New York, Dallas, and San Francisco this September. One table with peers comparing notes on where planning actually hurts.

Request your seat now