The 15-Day Close Playbook

Every finance team I have worked with has a version of the same story. The close used to take 25 days. Someone was asked to compress it. A few tasks got moved earlier. It came down to 22, then 20, and then it stalled. The remaining days felt immovable, the bottlenecks felt structural, and the process settled into a rhythm that nobody was happy with but everyone had learned to tolerate.

Getting from 20-plus days to 15 is a different kind of problem. It is not about working faster. It is about redesigning how the close flows, who owns each piece, and where the real dependencies sit (as opposed to where the team assumes they sit). I have led this redesign, and the playbook that follows reflects what actually worked and what looked good on paper but failed in practice.

What the Close Calendar Actually Looks Like

A 15-day close is not 15 days of equal effort. It is three distinct phases, each with a different operational character, and the structure matters more than the individual tasks.

Days 1 through 5: the hard close. This is where the transactional accounting lands. Sub-ledger reconciliations, bank reconciliations, accounts payable close, revenue cut-off, and the first pass at accruals. The goal of this phase is to get the general ledger to a point where the core financial statements can be drafted. Everything in this phase runs on a task-level calendar with specific owners and deadlines measured in hours, not days.

Days 6 through 10: the analytical close. This is where the numbers get turned into information. Intercompany eliminations finalize, management reporting gets built, the variance analysis against budget and forecast takes shape, and the FP&A team starts constructing the narrative. The analytical close is where most organizations lose time, because the dependencies between controllership and FP&A are poorly defined and the handoff points are ambiguous.

Days 11 through 15: the review and reporting close. The CFO reviews the management pack, the board reporting gets assembled, the final adjustments post (ideally minimal), and the close is formally signed off. This phase should be clean. If it is not, the problem is almost always upstream in Phase 1 or Phase 2.

The mistake I see most often is trying to compress the calendar by squeezing all three phases uniformly. That does not work. The hard close has a natural floor determined by transaction volume and system capability. The real compression opportunity is in the analytical close, where process redesign and clearer ownership can eliminate two to four days that are currently consumed by ambiguity rather than actual work.

Task Ownership and the Dependency Map

A close calendar without clear task ownership is a list of aspirations. Every task needs three things defined before the close cycle starts: who owns the task, what their input dependency is (which upstream task must complete before they can begin), and what their output is consumed by (which downstream task is waiting for them).

This sounds basic. In practice, most close calendars I have inherited define the “what” and the “when” but leave the dependency chain implicit. People know their own tasks. They do not know who is waiting on them, and they do not know what to escalate when an upstream dependency is late. That ambiguity is where close calendars slip, one task at a time, until the CFO is asking why Day 10 tasks are still incomplete on Day 14.

When I redesign a close process, I start by mapping every task to its predecessor and successor. The output is a directed graph, not a flat list, and it makes the critical path visible. The critical path is the longest chain of dependent tasks through the close, and compressing the close means compressing that chain. Tasks that are not on the critical path can absorb a day of delay without affecting the overall timeline. Tasks that are on the critical path cannot absorb any delay at all.

In most organizations, the critical path runs through revenue recognition, intercompany, and the consolidation journal. Everything else can flex. Those three cannot.

The Three Bottlenecks That Always Appear

I have never led a close redesign where these three bottlenecks did not surface. They are structural to how multi-entity businesses operate, and the solutions are process-level, not effort-level.

Intercompany Reconciliation

Intercompany is the single largest source of close delays in any business with more than two entities. The problem is not the reconciliation itself. The problem is that entities book intercompany transactions at different times, with different descriptions, and sometimes with different amounts (because of FX timing, markup calculations, or simple data entry disagreement). The reconciliation then becomes a detective exercise, and it sits on the critical path because the consolidation journal cannot post until intercompany is clean.

The fix is not to reconcile faster. It is to eliminate the reconciliation gap at the source. That means standardized booking protocols (both entities book the same transaction, in the same period, using the same reference), automated matching where the ERP supports it, and a defined escalation window. If intercompany does not balance by Day 4, the entities have 24 hours to resolve the difference. After that, the controllership team posts a forced balance entry and the investigation happens after the close, not during it.

That forced-balance decision is the hardest call in the close process because it goes against every instinct a CA has about accuracy. But the trade-off is real: a close that is precise to the rupee and lands on Day 22 is less useful to the business than a close that is materially correct and lands on Day 15. The investigation still happens. It just happens outside the critical path.

Accruals

Accruals are the second bottleneck, and the problem is information asymmetry. The controllership team needs to accrue for expenses that the business has incurred but not yet invoiced. That requires information from procurement, from legal, from operations, from anyone who has committed spend that has not yet flowed through the AP system. Chasing that information during the close window is slow and unreliable.

The process fix is to move accrual data collection before the close starts. In the last week of the month, every cost center owner submits a standard accrual template covering known commitments above a defined threshold. The controllership team books standing accruals for recurring items (rent, utilities, standard contracts) and uses the templates for the variable items. This front-loading cuts accrual processing from three days to one.

The threshold matters. Accruing every invoice below a materiality floor is effort without value. I set the accrual threshold at a level where a missed item would not change the management reporting narrative. For most mid-market businesses, that is somewhere between 50,000 and 200,000 rupees depending on the overall cost base. Below that threshold, the controllership team uses a trend-based estimate and moves on.

Revenue Cut-Off

Revenue cut-off is the third bottleneck and the most consequential, because revenue errors do not just affect the current period. They affect the variance analysis, the forecast accuracy measurement, and the credibility of the finance function with the commercial team.

The cut-off problem is straightforward: the finance team needs to determine which revenue belongs in the current period and which belongs in the next. In a SaaS business, this means confirming contract start dates, verifying delivery milestones, and checking that the recognition schedule aligns with the performance obligations under Ind AS 115 (which I covered in detail in this earlier article). In a services business, it means confirming percentage of completion and getting sign-off from delivery teams.

The process fix is the same pattern: move the data collection upstream. The commercial team submits a revenue recognition checklist by Day 2 covering all deals that closed in the final week of the month, with contract start dates, deliverables, and any non-standard terms. The controllership team processes the checklist against the recognition policy, and exceptions go to a defined approver (typically the Finance Controller) by Day 3. Clean cases get recognized. Exception cases get parked in deferred revenue until the next cycle, and the commercial team knows this in advance so there are no surprises.

FP&A vs. Controllership: Who Does What During the Close

The biggest process improvement I made in the close redesign was not a task-level change. It was clarifying where controllership ends and FP&A begins.

Controllership owns the hard close. They are responsible for the accuracy of the general ledger, the completeness of the reconciliations, and the integrity of the trial balance. Their deliverable is a closed ledger that FP&A can rely on without re-checking. When FP&A has to re-verify controllership output, that is a process failure, not a diligence virtue.

FP&A owns the analytical close. They take the closed ledger and build the management view: the variance analysis, the bridge from budget to actuals, the forward-looking implications, and the narrative that accompanies the numbers. Their deliverable is the management pack that the CFO reviews, and that pack should reflect finance judgement, not just financial data. I covered what good variance commentary looks like in the variance analysis article, and the principles apply directly here.

The handoff between these two functions is the most important moment in the close calendar. I define it as a specific event: the “ledger release.” At a defined time on a defined day (in my calendar, 6 PM on Day 5), controllership declares the ledger closed. FP&A begins their work against that snapshot. If controllership needs to post adjustments after the ledger release, they follow a defined protocol: the adjustment is logged, the FP&A team is notified, and the management reporting reflects the adjustment with a clear audit trail.

Without this handoff discipline, what happens is a gradual bleed. Controllership posts a late adjustment on Day 7. FP&A discovers the variance analysis they built on Day 6 is now wrong. They rework it. Another adjustment comes through on Day 9. The management pack, which should have been drafted by Day 8, is still being revised on Day 12. The close technically finishes on Day 15 because the ledger closed on time. But the management reporting (the part that actually informs decisions) is rushed and incomplete.

The ledger release ceremony is a forcing function. It puts a deadline on controllership that is visible to the entire finance team, and it gives FP&A a stable foundation to work from. It is the single most impactful process change in the playbook.

Communication Cadence During the Close

A 15-day close requires more structured communication than a 20-day close, not less. When the calendar is compressed, a one-day delay has proportionally more impact, and the team needs to know about it immediately rather than discovering it at the end-of-week status update.

I run three communication touchpoints during the close.

Daily stand-up, Days 1 through 5. Fifteen minutes, every morning, controllership team only. Each owner reports: what they completed yesterday, what they are working on today, and what is blocked. The purpose is not status reporting. It is early escalation. A task owner who says “I’m waiting on the Singapore entity to confirm the intercompany balance” on Day 2 triggers an intervention. The same information surfacing on Day 5 triggers a crisis.

Midpoint review, Day 5 or 6. Thirty minutes, controllership and FP&A leads. This is the ledger release checkpoint. Controllership confirms which reconciliations are complete, which are outstanding, and whether the ledger release will happen on schedule. FP&A confirms their analytical plan for the next five days and flags any data gaps.

Pre-submission review, Day 12. One hour, full finance leadership. The management pack is reviewed in draft. The CFO sees the numbers and the narrative before the formal submission. This is where the last round of questions gets resolved, not on Day 15 when the pack is supposed to be final.

The cadence looks simple, and it is. The discipline is in actually running it every month without exception. The close months where something goes wrong are almost always the months where someone decided the stand-up was not needed because “this month is straightforward.”

What Good Looks Like

A well-run 15-day close has a specific feeling to it. By Day 5, the ledger is closed and controllership is wrapping up reconciliation exceptions rather than still processing transactions. By Day 10, FP&A has a draft management pack with variance commentary that answers the CFO’s likely questions before they are asked. By Day 15, the formal close is a formality because every number has already been reviewed and the narrative has been pressure-tested.

The team is not working late. The process is predictable enough that people can plan their month around the close window rather than being consumed by it. Escalations happen on Day 2 and Day 3, not Day 12 and Day 13. The controllership-to-FP&A handoff is clean, and the FP&A team spends their time on analysis rather than data verification.

And critically, the close process improves each month. The post-close retrospective (which takes 30 minutes on Day 16) captures what went well and what slipped, and those lessons feed into the next month’s close calendar. The teams I have led track two metrics across cycles: days to close, and the number of post-ledger-release adjustments. The first measures speed. The second measures quality. Both should trend down over time.

The 15-day close is not the goal. The goal is a close process that gives the business timely, accurate financial information with enough lead time for the management team to act on it. Fifteen days is the point at which that becomes consistently achievable for most mid-market organizations. Below 15 days, the marginal compression starts requiring system investments and automation that may or may not justify the cost. Above 15 days, the finance function is delivering information too late to shape the current month’s decisions.

If you are working on compressing your close, redesigning the ownership model, or figuring out where the time is actually going, I would love to hear how it is going. Let’s connect.