Guide|5 min read

    What a monthly close should really take, and where the days go

    A healthy mid-market close runs about five business days. Many teams take ten or twelve, and the gap is coordination, not accounting. Where the days actually go, and how teams compress them.

    Leo Tsytrinbaum
    Leo Tsytrinbaum

    Ask ten finance leaders how long their monthly close takes and you will get ten different answers, most of them a little defensive. So here is a straight one to anchor against.

    A healthy monthly close for a mid-market company runs about five business days. Many teams are closer to ten or twelve, and the gap is almost never about accounting skill. It is about where the days actually go.

    Where the days actually go

    Very little of a slow close is spent on the accounting itself. The journal entries, the reconciliations, the accruals, those are the part your team is good at and could do in their sleep. The days disappear somewhere less flattering: waiting. Waiting on a number from a department head who has it in a tab. Waiting on the corrected version of a file that came in wrong. Reconciling two spreadsheets that should agree and do not, then finding out why. Rebuilding the same reporting schedule that was rebuilt last month because it lives in a workbook someone overwrote.

    A slow close is rarely an accounting problem. It is a coordination problem wearing an accounting costume.

    Why the gap is expensive beyond the hours

    The obvious cost of a twelve-day close is the twelve days. The real cost is what it does to every decision downstream. If your actuals are not trustworthy until the twelfth business day, then for the first half of every month the company is steering on last month's stale picture. The board deck gets built on numbers that are already two weeks old. The reforecast starts late, so it finishes late, so it lands after the decisions it was supposed to inform. Speed of close is not a vanity metric. It is how fresh your decisions are allowed to be.

    7days

    The typical gap between a slow close and a fast one

    Twelve days versus five. Almost all of it is coordination and version control, not debits and credits.

    How teams actually compress it

    The teams that get to five days rarely do it by working faster. They do it by removing the waiting. The numbers that used to be requested by email arrive through a connection instead, so nobody is chasing a tab. The reporting schedules are built once and refresh on their own, rather than being rebuilt from a workbook each month. There is one version of the actuals that everyone reads from, so the reconcile-two-spreadsheets ritual simply stops happening. None of that is exotic. It is the difference between a close that is a process and a close that is a monthly scramble.

    If your close is closer to twelve days than five, it is worth mapping where your own days go before assuming the answer is "hire more people." Usually it is not, and that mapping is a good first conversation to have.

    Leo Tsytrinbaum
    Leo Tsytrinbaum | Founder, Novaplan

    Previously ran BI teams, shipped AI in production at Fortune-scale, and co-founded an agentic-AI platform from zero. Building the FP&A stack my old teams never had.