Let's map your workflow
← Back to Insights Private equity

Why Private Equity Portcos Stay Manual After ERP Go-Live

Private equity teams often expect the ERP to fix finance speed and control. It usually does not. The workflow around it is where the value-creation drag remains.

Yasir Aarafat, CPA · 2026-07-07 · 11 min read

Private equity usually does not have a software problem. It has a workflow problem that the ERP did not remove.

The board wants cleaner numbers sooner. The operating partner wants a faster view of where value is leaking. The portfolio CFO wants fewer late nights in spreadsheets. The implementation partner promised the ERP would simplify all of that. Go-live arrives, the ledger is live, and the close still feels manual.

For PE, that is not just inconvenience. It is value-creation drag. Every extra day in the close delays decisions, hides variance patterns, weakens confidence in the board pack, and leaves the operating team managing the month instead of improving the business.

That is the pattern this article is about.

The ERP records the transaction. It does not redesign the workflow that turns that transaction into a decision-ready number, a defendable board pack, or a control environment the operating team can trust. In PE-backed companies, that workflow is often spread across exports, workbooks, inboxes, Slack threads, and the controller's memory. It is still there after go-live. It just becomes harder to see.

In Short

Who This Is For

This article is for PE operating partners, portfolio CFOs, deal teams, and finance leaders who need faster, cleaner, more repeatable finance output from portfolio companies with a live ERP.

It is especially relevant when the business has already spent on ERP implementation, but the close, reporting, cash view, or board pack still depends on manual assembly.

Why PE Expects More Than ERP Go-Live Delivers

PE cannot afford delay the way a standalone company can. When a portfolio company closes late, the impact is not just annoyance. It delays operating decisions, obscures variance patterns, and slows the next layer of value creation work.

That is why the "ERP will fix it" story falls apart so quickly in portcos. The operating model still needs a workflow that can do five things reliably:

If those five things are not designed, the ERP becomes a newer place to pull data from, not a better operating system for finance. Across several portcos, that means the sponsor pays for implementation and still lacks operating consistency.

The PE Control Layer

The spreadsheets, exports, review steps, exception checks, email approvals, reconciliation routines, and sign-off decisions outside the ERP form the PE finance control layer.

It is not always a bad thing. Some of it is necessary because PE teams need judgment, accountability, and traceability. The problem is not that the layer exists. The problem is when it is invisible, unowned, and dependent on institutional memory.

In a portfolio company, that usually shows up in familiar ways:

That is not a software configuration issue. It is a workflow design issue, and in PE it is part of the value-creation plan.

Where the Time Actually Goes

The delay in a PE-backed company is usually not one dramatic failure point. It is a chain of small manual steps that stack up until the close, reporting cycle, or board pack run becomes a late-night assembly exercise.

The recurring sources of drag are the same:

None of those steps sound strategic. That is exactly why they get left alone.

1. ERP Extraction and Reformatting

Every finance cycle starts with someone pulling data out of the ERP.

In theory, the ERP should be the source of truth. In practice, someone still has to find the right report, export it, reshape it, rename tabs, fix formatting, and send it on to the next person.

That work is low value, but it is also necessary when the process has not been designed properly. It is often the first place PE teams lose control because the export step lives in one person's muscle memory, not in a governed workflow.

You do not want the team rebuilding the same extract every month. You want the extract to be stable, named, scheduled, and visible.

What the workflow should do:

What should stay human:

2. Reconciliation and Tie-Outs

Reconciliation is where PE-backed finance teams often lose the most time. Intercompany balances, bank items, subledger checks, accrual support, and entity tie-outs should not all require fresh judgment every month. But many companies still handle them as if every item were a new problem.

That is not control. It is repeated manual detection.

The better pattern is to let routine matches flow through rules and only surface the exceptions that genuinely need review.

What the workflow should do:

What should stay human:

3. Exception Handling

Exceptions are where the finance team either gains trust or loses it. If exceptions live in email threads, side conversations, and notebook comments, the operating partner sees a process that cannot be trusted. The CFO may know the issue is being worked, but nobody else can tell what is open, who owns it, or when it will close.

PE cannot afford that kind of opacity for long.

What the workflow should do:

What should stay human:

4. Recurring Journals

Recurring journals are a strong support candidate because they are repeatable and controlled. Prepaids, accruals, depreciation support, and other recurring entries usually follow a pattern. If the logic is stable, finance should not be re-entering the same work manually every month.

But PE teams should not automate these blindly. If the underlying business process keeps changing, the journal logic is not stable enough yet.

What the workflow should do:

What should stay human:

5. Reporting and Board Pack Assembly

This is where manual work becomes visible to the board. If the team is still copying numbers into slides, checking versions, and rebuilding charts every month, the board pack is not a reporting product. It is a production line.

That is a PE problem because it slows decision-making across the portfolio. The board pack should be drafted from final numbers, not rebuilt from scratch after the close is done.

What the workflow should do:

What should stay human:

The PE Readiness Test

Before PE-backed finance work should be supported, it has to pass a basic test. Can a new controller see the source, follow the handoffs, understand the exceptions, and find the approval trail without chasing three people?

If the answer is no, the process is still living in memory instead of system. That is when automation makes the mess faster.

What PE Should Build First

The best first candidate is not the loudest pain point. It is the recurring workflow that is both important and stable enough to govern.

Typical first candidates in a PE-backed company include:

The first build should be narrow. Do not try to redesign the whole finance function in one move. Start where ownership is clear and the process can be measured.

The goal is to remove repetitive assembly work from the critical path, not to remove finance judgment from the process. In PE terms, that means more reliable visibility, faster decisions, and less operational leakage between the close and the board.

What Should Stay Human

Some parts of PE finance should remain human even after the workflow is better designed.

The role of workflow design is not to make the finance team invisible. It is to make the right parts of their work visible and repeatable.

If the process depends on judgment, the judgment should stay with a named person. If the process is repetitive, the repetition should not keep consuming high-value finance time.

How an Operating Partner Should Read the Workflow

If you are an operating partner, the question is not whether the portfolio company has an ERP. It almost certainly does.

The useful questions are more specific:

Those questions tell you whether the company has a managed finance workflow or a fragile one. That matters because the PE value creation plan depends on repeatability. If the finance layer is fragile, the operating partner is managing symptoms, not improving the system. The portfolio does not just lose time. It loses comparability, confidence, and the ability to move faster on the next decision.

Build, Defer, or Inspect Next

Once the workflow is visible, the decision becomes explicit.

Build when the workflow repeats, source data is accessible, ownership is clear, exceptions are understood, and human approvals can be preserved without adding friction.

Defer when source data is disputed, ownership is unclear, exception logic changes every period, or the process is still being redesigned.

Inspect next when the selected workflow is not the real bottleneck. Sometimes the board pack is slow because the forecast input is late. Sometimes the reconciliation is messy because the source data upstream is already broken. When that happens, the right move is to inspect the upstream workflow before building anything downstream.

This is the part PE teams usually skip. They start with the most visible pain instead of the most governable workflow. That leads to bad automation and weak control.

What It Looks Like When You Get It Right

The controller stops rebuilding the same pack every month. Exceptions show up in a queue instead of an inbox. The operating partner sees the issue before the month is closed, not after. The board pack is drafted from final numbers instead of assembled by hand at the end of the cycle.

The finance team is still doing judgment work. They are just not spending their time on manual assembly.

That is what better workflow design should produce in a PE-backed company: faster output, clearer control, less dependence on institutional memory, and a cleaner operating rhythm across the portfolio.

FAQs

Why do PE-backed companies stay manual after ERP go-live?

Because ERP go-live usually solves the wrong problem. The ledger changes; the handoffs do not. Most of the drag sits in ownership gaps, exception handling, and pack assembly.

Is the ERP the wrong system for PE-backed finance?

Usually no. The ERP is still the system of record. The mistake is treating it like the system of decision. PE needs a clean path from source data to sign-off, and that path usually lives outside the ERP.

What breaks first when the process is weak?

Usually the same three things: the close slips by a day or two, exception ownership gets fuzzy, and the board pack ends up relying on one person who knows where everything is hidden.

Where should PE start automating?

Start with the workflow that is already stable enough to survive a handoff. If the source is disputed or the exception logic changes every month, automation just hardens the confusion.

What should stay human?

Anything that changes the numbers or the story. Material judgment, policy calls, and final sign-off should stay with named people. Automation should move files, route tasks, and surface exceptions, not replace accountability.

What should an operating partner ask before funding another finance tool?

Where does the workflow break today, who owns the fix, and what evidence will prove it is better next month, not just prettier this month?

Close

The first step is not choosing another tool. It is choosing the workflow that needs to be seen.

For PE-backed companies, that usually means mapping the control layer between the ERP and the board pack, then deciding what is stable enough to support and what still needs inspection.

That is the work that creates faster numbers, clearer control, and less monthly churn across the portfolio.

If your portfolio company has a live ERP but finance still closes through exports, spreadsheets, emails, and review loops, start with one workflow.

A Finance Workflow Diagnostic maps the manual control layer for the workflows that matter most to the close, reporting, or board-pack process. It typically runs 2-3 weeks and produces a workflow map, control-gap analysis, automation suitability assessment, and a prioritised improvement plan before any commitment to a larger build.

Start a Finance Workflow Diagnostic

↑