It's day 11 of the month. Your CFO asks when actuals are landing. Answer: "tomorrow, Friday." The CEO has the board meeting Monday and needs numbers before. You say it can't be done. You leave the cubicle at 11PM, again.
Closing in 12 days is not about team talent. It's about how many bottlenecks you're tolerating. Each day is made of specific problems — manual accruals, intercompany by email, FX revaluation by hand — that every company carries without seeing them.
The difference between closing in 5, 8, or 12 days is not budget or headcount. It's operational discipline. This module shows you exactly where the days are lost and how to recover them without hiring anyone.
By the end of this module you'll have it down. Let's go.
Your close takes 11 days. Your team says "we need to hire 2 more people to close in 7." Is that really the problem?
In plain language
Before the mechanics, the four basic questions.
Why do this at all?
Because the rest of finance work depends on numbers closing on time. FP&A can't analyze what's not closed. Treasury can't project cash with pending accruals. The board can't decide with 12-day-old numbers. Close speed is the oxygen of everything else.
Who uses it?
The controller leads with their accounting team. The CFO coordinates. FP&A consumes (analyzes), Treasury (projects), the board (decides). In large companies, the close director is a dedicated role. In mid-market, it's explicit controller responsibility.
When does it show up?
Every month. Every close. Additionally: at quarter-end with extra adjustments, at year-end with external audit, in any M&A or due diligence event where someone external is going to read your numbers fast.
What if we skip it (or do it slow)?
The whole financial chain delays. FP&A explains variances with old data. Treasury projects with non-closed numbers. The board decides with delayed vision. More expensive: when audit arrives, problems that weren't seen during the year all surface together. The slow close is the symptom; costs are downstream.
Days aren't lost by chance — they're lost in specific places
Andina S.A. closes in 11 days on average. Its controller swears the team "is too small." When you audit the close by process, you find: late pre-cutoff (1 day lost), AP accruals built manually each month (1.5 days), intercompany reconciliation by email between subsidiaries (2 days), FX revaluation by hand (1 day), audit prep mixed with the close (1.5 days). Sum: 7 extra days over the 5 a clean close would take.
None of those bottlenecks are invisible. All are in plain sight of the controller every month. What's missing isn't the diagnosis — it's the decision to eliminate them one at a time instead of tolerating them.
The visual below lets you play with the bottlenecks: turn each on and off, and watch the close shrink or stretch in real time. It's exactly the conversation you'd have with your own team if you decide to fix it.
Bottlenecks, live
Each bottleneck adds a specific number of days. It's not general estimation — these are the actual days each problem costs.
Turn one off. Watch the close curve shrink. Turn off the next. Another reduction. This is what happens when a mature controller enters a slow close: identifies causes, prioritizes by days saved, attacks them in order.
Interactive visual
Why do you close in 5, 8, or 12 days?
The extra days are not mystery. Each bottleneck adds specific days. Toggle one at a time and watch the close shrink.
10.0days
Typical close
Active bottlenecks
What you are seeing
There is no magic. Each day is bought by removing one specific cause. The company that closes in 5 days does not have a team twice the size of the one that closes in 10 — it has half the bottlenecks. Close speed is a proxy for operational maturity, not team capacity.
Close speed is a proxy for the operational maturity of the accounting function, not team capacity. Companies closing in 5 days don't have teams twice as big — they have half the bottlenecks.
Practical next step: next time your close takes 10+ days, don't ask for more headcount. Pull this list, measure how many minutes the team loses on each one, and prioritize eliminating the 3 most expensive. The close drops to 7-8 days without hiring anyone.
The mechanics: how to build a fast close
- Explicit pre-cutoff on the last business day. Sales, AP, AR confirm before 5PM day 0. Exceptions are formally approved, not assumed.
- Rule-based auto-accruals. PO + receipt triggers automatic accrual. The controller only approves exceptions (typically <5% of volume), doesn't build the accruals.
- Intercompany with single locked matrix. One source of truth per subsidiary pair. Mismatches show in dashboard before consolidating, not after.
- Bank rec by API + auto-match. Direct bank connector, automatic match by reference. Only unmatched items go to a human queue.
- Automated FX revaluation. ERP runs the rev-eval with locked month-end rates. Controller reviews exceptions, doesn't recalculate manually.
- Audit-prep parallel, not inside. The close ends day 5 (or 7). Auditor preparation starts day 6. Different work-streams with different people if the team allows.
- Post-mortem after every close. Day +1 after the close: 30 minutes to identify what was late and why. The next close improvement comes from there, not from an external consultant.
- The common fear: "if we close fast, we'll have errors." Actually, slow closes produce MORE errors than fast ones. The tired team on day 11 makes more errors than the team already resting on day 6.
- Speed comes from processes, not shortcuts. Shortcuts produce errors. Automation produces speed without errors — because it eliminates the human step that was the bottleneck.
- The right test: errors detected in external audit. If your fast close produces more material adjustments than your slow close, there's a problem. If it produces the same or fewer, the speed was pure gain.
- Practical rule: companies that close in 5-7 days AND have few audit adjustments are in better shape than those closing in 12 days AND with few adjustments. Both are "correct," but only one is efficient.
Adversarial check
Adversarial check
1.Your CEO sees you close in 12 days and says "good CFOs close in 3." Before defending yourself, what do you ask?
2.Your team closes in 11 days but produces reports with several post-close adjustments every month. What's the first change?
3.What's the most important difference between a 5-day close and a 12-day close at similar companies?
Exit checklist
Suggested re-review: 90 days after implementing the first improvement; 12 months later as a complete close audit.
Optional
Go deeper
Sources and books to dig into the original material