How long should month-end close actually take?

For a single-entity company with one ERP and one chart of accounts, month-end close should land somewhere between 5 and 7 business days. APQC's benchmarking puts the median at 6.4 business days, with top-quartile finance teams closing in about 4.8 days, according to APQC data cited by Coefficient. That's the number most close-software vendors use in their sales decks, and it's a fair target for a clean, single-source business.

It is not a fair target for a company that has acquired three to eight entities in the last 24 months. We've talked to finance leaders at PE-backed roll-ups where close now runs 12 to 18 business days, not because the team got slower, but because every acquisition added a new ERP, a new chart of accounts, and a new set of intercompany relationships that nobody designed to talk to each other. The close didn't get harder. The data got messier, and the software everyone bought to speed up close was never built to clean up mess. It was built to manage a close that's already clean.

What financial close and consolidation software is built to do (and does well)

Tools like FloQast, BlackLine, OneStream, Trintech, Numeric, Abacum, and Wolters Kluwer CCH Tagetik solve a real, well-defined problem: they give a controller a checklist, an audit trail, and a workflow for the tasks that happen inside a close that's already running on consistent, structured data. Task tracking, reconciliation sign-off, intercompany elimination templates, multi-currency translation, flux analysis, and (for the EPM-tier platforms) multi-GAAP and IFRS reporting. Gartner tracks this as its own market category for exactly this reason, and the vendor set it lists is the same set that shows up across every "best financial consolidation software" listicle, per Gartner's financial close and consolidation solutions market.

PwC's framing of consolidation systems is useful here too: the value case for these tools assumes you already have a repeatable way to pull trial balances, apply ownership structures, and run eliminations across a known set of entities, as described in PwC's overview of consolidation systems. That assumption is the whole business model. It's also exactly where the trouble starts for a roll-up.

Where it breaks: the multi-ERP, multi-chart-of-accounts problem

Every piece of consolidation software on the market assumes a mapped, standardized source system feeding it clean trial balances. A company built organically tends to have that, more or less, because one finance team built the chart of accounts and has owned it since inception. A company built through acquisition almost never has that, because each acquired entity arrives with its own ERP (NetSuite here, QuickBooks there, a legacy on-prem system somewhere else), its own chart of accounts, its own revenue recognition quirks, and its own idea of what an "intercompany receivable" even means.

None of the major close platforms normalize that gap for you. What actually happens, in almost every multi-entity roll-up we've seen, is that someone on the finance team builds a shadow process: a spreadsheet (or six) that maps each acquired entity's chart of accounts to the parent company's standard, by hand, every single month. The close software still runs its checklist and its reconciliations, but it's running on top of a manual translation layer that lives outside the tool, usually in one analyst's head and their Excel workbook. That analyst becomes a single point of failure. When they're out sick during close week, the close slips.

This is the gap none of the vendor content addresses, because addressing it honestly means admitting their software is a workflow layer, not a data normalization layer. The feature comparisons between FloQast and BlackLine are arguing over task management UX while the actual bottleneck, getting six different ERPs to speak the same financial language, sits entirely outside the product.

Can close software handle consolidation after an acquisition?

Technically yes, in the sense that you can keep buying modules and consulting hours to force-fit it. Practically, most teams hit a point where the manual mapping work scales faster than the software's ability to absorb it. We tend to see the wall appear somewhere around the fourth or fifth acquired entity, or whenever a newly acquired business runs on an ERP the parent company's integration team has never touched before.

The workaround most teams build is some combination of: a dedicated FP&A hire whose entire job is chart-of-accounts mapping, a growing library of one-off Excel macros that convert each subsidiary's trial balance into the parent format, and a reconciliation process that depends on tribal knowledge about which entity's "other income" line actually means something different from everyone else's. That's not a software problem the next SaaS seat fixes. It's a data architecture problem, and it's the same pattern we've seen play out in adjacent back-office functions, whether that's accounts payable automation hitting its limits at scale or accounts receivable software breaking down once billing gets complex. The software was designed for one clean system. The business has several messy ones.

The compliance stakes: why this isn't just an efficiency problem

A slow close is an annoyance. An unreconciled multi-entity close is a control problem, and for PE-backed companies heading toward a sale, an audit, or an IPO, that distinction matters. The SEC's own guidance allows a newly acquired entity to be excluded from that year's assessment of internal control over financial reporting, but it requires that entity be folded into the control framework afterward, per SEC staff guidance on ICFR assessment and acquired businesses. Most PE-backed finance teams know about the exemption. Far fewer track the deadline to fold it back in, because nobody owns that calendar the way they own the quarterly close calendar.

PCAOB defines a material weakness as a deficiency, or combination of deficiencies, creating a reasonable possibility that a material misstatement won't be prevented or detected on a timely basis, under PCAOB Auditing Standard 5, Appendix A. An intercompany elimination process that depends on one analyst's personal spreadsheet, applied inconsistently across entities with different charts of accounts, is close to a textbook example of that definition. Baker Tilly's recent analysis of public-company material weaknesses shows a meaningful share tied directly to post-acquisition control gaps, not fraud or complex accounting judgment calls, just unintegrated acquired entities, as tracked in Baker Tilly's trend data on material weaknesses. If your company is PE-backed and heading toward any kind of liquidity event, this stops being an internal efficiency conversation and becomes a diligence finding waiting to happen.

Should you build, buy more software, or augment what you have?

We tell clients to run three checks before deciding, the same framework we use across the finance-ops stack, whether that's close, AP, AR, or procurement automation hitting the same scale ceiling.

• Count your source systems, not your entities. Three entities on one ERP is a very different problem from three entities on three ERPs. If every acquired business runs on the same system, buying a better consolidation module is probably the right call. If they don't, no amount of SaaS spend fixes the mapping layer.

• Measure the manual hours, not the close length. A 10-day close that's 10 days of software-assisted work is fine. A 10-day close that's 3 days of software and 7 days of one person reconciling spreadsheets by hand is a staffing risk dressed up as a software problem.

• Check who owns the mapping logic. If the chart-of-accounts translation lives in someone's head or a personal file, that's not a process. It's a liability. The fix isn't a better interface for the checklist; it's getting that mapping logic into a system that survives the person leaving.

If the honest answer to all three is that your source data is the mess, not your workflow tooling, the right move is usually a thin custom layer sitting between your ERPs and whatever close software you already have, not a swap to a different vendor with the same single-source assumption baked in.

What a custom close and consolidation layer actually looks like

In practice, this isn't a rebuild of your close software. It's a normalization and reconciliation layer that does three things a SaaS seat can't: it maps each entity's chart of accounts to your standard automatically instead of by hand, it runs automated intercompany matching across entities with agents that flag mismatches by confidence level instead of forcing a human to eyeball every line, and it keeps a clean audit trail of every mapping decision so your auditors (and your buyer, if there's an exit on the horizon) can see exactly how a subsidiary's trial balance became a consolidated number.

This is close to the same shape of problem Genta AI Solutions worked through with C&G Energy Services, an electric infrastructure company whose billing process was leaking over $1M a year because the data flowing from field logs into invoicing wasn't standardized across the business. The fix wasn't a smarter AI model bolted onto the existing system. It was breaking the process into discrete projects and automating the data flow end to end, recovering roughly $800K a year, most of it through process automation and integration work rather than anything exotic in the AI itself. The full numbers are in the C&G Energy Services case study. The lesson transfers directly to multi-entity close: the diagnosis of where the data actually breaks matters more than whichever model or platform gets layered on top of it afterward.

A build like this also gives finance leaders a cleaner story when they take the spend request to the board or the PE sponsor. If you're trying to put a number on that case, the same discipline used to track ROI on any AI-adjacent spend applies here, which is worth reading alongside how to measure AI ROI and spot fake productivity before you commit budget to either another SaaS seat or a custom build.

If you're working through this decision, this is exactly what our Discovery phase at Genta AI Solutions maps out before anyone writes a line of code, and we're happy to compare notes. For teams further along who already know they need a custom data and automation layer rather than another license, the starting point is usually our AI automations work.

Frequently asked questions

How long should month-end close actually take?

APQC's benchmark puts the median close at 6.4 business days, with top-quartile teams closing in about 4.8 days. That's a fair target for a single-entity company with one clean source system. Multi-entity roll-ups with several ERPs commonly run 12 to 18 days, and the gap is almost always manual chart-of-accounts mapping, not weaker close software.

Can FloQast, BlackLine, or OneStream handle consolidation across newly acquired entities with different ERPs?

They manage the workflow, sign-off, and reconciliation tasks around consolidation well, but none of them normalize data from mismatched charts of accounts automatically. Most teams end up building a manual spreadsheet mapping process outside the software to translate each acquired entity's data before the platform can use it.

What's the difference between financial close software and financial consolidation software?

Close software (FloQast, task-tracking tools) manages the checklist, sign-offs, and audit trail for closing the books each period. Consolidation software (OneStream, CCH Tagetik) adds the mechanics of combining multiple entities into one set of financials, including eliminations and currency translation. Many platforms now bundle both, but the underlying capabilities are distinct.

Should a PE-backed company build custom close automation instead of buying another SaaS seat?

Only once you've confirmed the problem is messy source data across multiple ERPs, not weak workflow tooling. If every entity shares one ERP, better consolidation software is usually the right call. If each acquisition brought its own system and chart of accounts, a custom data normalization layer typically solves what another license can't.

Does a messy multi-entity close create SEC or audit risk?

Yes, once it passes a certain point. The SEC allows excluding newly acquired entities from that year's internal control assessment but requires them to be folded in afterward. PCAOB defines material weakness as a control gap that creates a reasonable possibility of an undetected material misstatement, and Baker Tilly's data shows a meaningful share of recent material weaknesses trace back to unintegrated post-acquisition controls.