Ask ten finance leaders where AI belongs in the close and you'll get ten different answers, mostly because the question is usually asked at the wrong altitude — "should we use AI in finance" instead of "which specific steps of this specific close are ready to be automated." A Traverse Fractional CFO who has rebuilt close processes around automation, and a Traverse Interim CFO who has spent careers in situations where a wrong number has real consequences, on where that line actually sits.
Automating the Close Without Losing Control
The close tasks worth automating first are the ones with a single correct answer that a person is currently deriving by hand: matching a bank transaction to a ledger entry, flagging a variance that crossed a threshold, routing a routine journal entry through an approval chain. None of that requires judgment — it requires consistency, and consistency is exactly what automation is good at.
The close tasks worth automating are the ones with a single correct answer. The moment a step requires judgment about what a number should be — not just whether it matches — it isn't ready to hand to a model unsupervised.
Done well, this shortens the close calendar meaningfully, and it does it by removing the mechanical work that used to eat the first several days of the month, not by removing the CFO's review of what the numbers mean. The teams that get this right treat automation as freeing up time for analysis, not as a replacement for it.
Where Judgment Still Wins
Most of the situations I get called into don't look like a normal close. They look like a covenant breach, a sudden departure, or a transaction nobody built a process for — and in every one of those, the hard part was never the arithmetic. It was deciding what a number meant, who needed to hear about it first, and how to say it.
- Unusual or one-off transactions. A model trained on routine patterns has nothing to anchor to when the transaction itself is the exception — an impairment, a restructuring charge, a one-time settlement.
- Going-concern and covenant judgment calls. Whether a forecast assumption is defensible enough to put in front of a lender isn't a calculation — it's a judgment about credibility, timing, and relationship, informed by having been in that room before.
- How the number gets communicated. The same variance delivered to a board with context and a plan lands completely differently than the same variance delivered as a flag in a dashboard. That framing is still, and will likely remain, a human job.
The practical split we've landed on: let automation own the parts of the close where the answer is a known fact waiting to be reconciled, and keep a CFO firmly in the parts where the answer is a judgment waiting to be made. Read more on the finance-leadership side of that split in our AI Finance practice.