A calendar built around a constraint that's disappearing
The monthly close, the quarterly forecast, the annual plan: finance's operating rhythm exists because reconciling ledgers, consolidating entities, and building forecasts used to require a sequence of manual steps that only a person could execute, one after another. The calendar is a monument to that sequencing constraint, not a deliberate choice about how often the business needs to understand itself.
Once reconciliation, consolidation, and first-draft forecasting can run continuously rather than in a monthly batch, the calendar becomes a choice again instead of a constraint. Most finance leaders haven't yet asked what they'd choose if they were designing the cadence from scratch.
Where autonomy actually helps first
The highest-value place to start isn't the most visible part of the close, it's the most mechanical: transaction matching, intercompany reconciliation, and variance flagging, the steps where the judgment required is low and the volume is high. These are also the steps most responsible for why the close still takes days instead of hours.
Forecasting is the harder and more valuable frontier. An autonomous system can maintain a continuously updated baseline forecast from live operational data, freeing the FP&A team from rebuilding the model every cycle and letting them spend that time on the scenarios and judgment calls that actually change a decision.
The finance calendar is a monument to a sequencing constraint that's disappearing, not a deliberate choice about how often the business needs to understand itself.
Tahmid Islam, Chief Financial Officer
What doesn't change, and shouldn't
Judgment calls on materiality, estimates, and anything that touches external reporting still need a named, accountable person, and that shouldn't change regardless of how capable the underlying tools become. The finance function's credibility rests on that accountability being real, not automated away in the name of speed.
The mistake to avoid is autonomy for its own sake: automating a judgment call because the technology makes it possible, rather than because the judgment was mechanical to begin with. The discipline is in knowing exactly where that line sits, and holding it, even as more of the work around it moves faster.
What this means for the team
A finance function that automates its transactional work well doesn't need fewer people so much as it needs a different mix: fewer people reconciling and consolidating, more people interpreting what a continuously updated forecast is actually saying about the business and translating that into a decision the leadership team can act on.
That shift needs to be planned deliberately, with a real path for the people whose current role is heavy on the transactional work, rather than left to attrition and hoping the team reshapes itself. Finance leaders who plan this transition get a stronger function on the other side. The ones who don't lose the people they most needed to keep.
