From Back Foot to Front Foot: How Portfolio Companies Can Combat a Reactive Close

A slow period-end close leaves finance teams producing numbers instead of explaining them. BRG describes what holds up the financial close and how to shorten it.

A slow period-end close leaves operating teams stretched too thin and executive leadership teams in a state of uncertainty for too long—in addition to frustrating accounting. The problem is widespread: nearly half of executives admit they have made a material business decision based on inaccurate, incomplete, or outdated financial data in the past twelve months. A slow close is a common contributor to numbers that arrive late or keep changing—and keep executives in the dark.

We see this pattern wherever a company has grown faster than the processes and systems beneath it: tangled interdependencies across functions, a fragmented data and infrastructure landscape, and tooling that does not relieve manual effort. The result is a reactive close in which finance spends more time producing numbers than interpreting them.

Fixing this starts with understanding where the close breaks down. At BRG, we use a targeted Close Process and Information Technology (IT) Tech Stack Diagnostic to identify the root causes of a reactive close.

The close is the starting point, not the finish line

The close is really the beginning of a period, but most organizations treat it as the end. Every downstream activity sits behind it: variance analysis, forecast updates, board and lender reporting, and—most critically—the operational decisions required to run the business. When the close lands on Day 15 instead of Day 6, the entire cadence shifts with it. Financial planning and analysis (FP&A) has less time to analyze performance, leadership has less time to respond, and the next month is underway before the last one has been explained. Companies find themselves habitually on the back foot, too busy reacting to the last period to shape the current one.

The gap is often wider than management believes. In a recent case, a company that described its close as a ten-day process found itself closer to twenty days once late adjustments and rework were considered. FP&A had just two to three days to report.

For sponsor-owned businesses, a late close also compresses the conversation between management and its owners. Board packages, lender reporting, and value-creation plan updates follow fixed schedules; the longer the close, the more compressed and error-prone reporting is to sponsors.

A reactive close is also expensive. The cost accumulates with overtime, temporary support, repeated rework, and inflated finance headcount to keep pace with entity growth rather than because the work requires it. Decisions made late or using numbers that subsequently change can be harder to quantify but are just as consequential.

What causes a slow close, and how we fix it

The leading practice is a five- to seven-day close; the bottom quartile takes ten or more days. BRG frequently sees issues that delay close across organizations. Here is how we assess and address some of those:

BRG’s diagnostic tests the sequence using facility or functional workshops, task ownership, close calendars, journal timing, reconciliation status, and system data. That evidence shows where work can shift into pre-close, where independent tasks can run in parallel, and where cutoffs, materiality rules, or documented calculations can remove delay.

Identify and remediate where technology is part of the constraint

Once the critical path is understood, the next step involves identifying the root cause of each constraint: process, policy, organization, data, or technology. Not every close problem is a technology problem, and replacing an enterprise resource planning (ERP) system will not fix a poorly designed close. But where fragmented systems, manual interfaces, offline reconciliations, or inconsistent master data sit on the critical path, process improvement alone is typically not enough.

The technology assessment should follow the flow of the close across the system of record, close management and reconciliation, consolidation and intercompany, planning and forecasting, reporting and analytics, and integration and master data. The objective is to distinguish what can be fixed through configuration or process changes now from what truly requires future technology investment.

Even organizations that have updated or replaced their ERP often do so without modernizing what sits around it, adopting a new platform with no defined cloud-based strategy and updated governance. Without a clear IT strategy, technology upgrades can fall short of improving the close or supporting business growth.

The objective is to direct investment at the layer that is binding. A serviceable ERP may need a close-management layer rather than a replacement that comes at a significantly lower cost. Finance and IT together must accelerate the close—uncovering efficiencies, addressing bottlenecks, and reducing fragmentation that prevents the organization from achieving target milestones.

Automate selectively after the process is understood

Artificial intelligence (AI) and automation can reduce manual effort but should not be the starting point. Organizations first must identify whether the underlying activity should exist in its current form. Once the process is simplified and the critical path is clear, automation can be targeted at high-volume, repeatable work such as data extraction, recurring journal entries, reconciliations, and selected accounts payable (AP), accounts receivable (AR), and reporting workflows.

The diagnostic also separates near-term opportunities to implement within the current architecture from longer-term opportunities that depend on broader data, infrastructure, or platform investment. The objective is not to “AI everything” but rather reduce effort and cycle time where doing so changes the close.

What the diagnostic looks like

A multisite healthcare provider engaged BRG to accelerate a close that varied widely between sites. Here’s how we approached the problem:

• Facility-level workshops established “where the time goes.” A single standardized close calendar was rolled out across sites. Intercompany and net revenue—the two largest sources of delay—both were addressed with written policy.
• For net revenue, work was under way to standardize the underlying AR model itself, replacing calculations that differed facility by facility, with the goal of a reliable figure by Day 3.
• A deliberately short list of automation targets followed in AR data extraction, unbilled, and look-back reporting. We focused on the small number of processes that typically account for a disproportionate share of the close delay.
• The diagnostic quantifies effort and cycle time by subprocess to establish which drive the timeline, so policy and remediation work is aimed at the few that matter rather than the whole calendar.

The results were visible within a month: five times as many facilities reported adjusted EBITDA by target Day 7.

When to call BRG

A dysfunctional close may materialize even before it begins to repeatedly miss the target deadline. A diagnostic is warranted when the following warning signs are apparent:

From reactive close to a repeatable management cadence

A targeted Close Process and IT Tech Stack Diagnostic identifies the critical path needed for a shorter, more predictable, and more accurate close that gives management, sponsors, and lenders confidence in the numbers.

Connect with a member of BRG’s Corporate Finance practice to learn more about the diagnostic.