.svg)
Latest estimate (LE) for PE portcos: the half-yearly forecast cycle (2026)
The LE is the formal half-yearly revised forecast the portco CFO delivers to the Private Equity (PE) board. What it is, when to deliver LE1 and LE2, how to build the bridge to budget, how it ties into your LBO model and covenants, and which tool makes this feasible.
.png)
Latest Estimate (LE): formal half-yearly revised forecast for Private Equity (PE) portfolio companies (portcos). LE1 in July, LE2 in October. Bridge to budget, covenant tracking, LBO alignment. Multi-level: per entity and consolidated.
Latest estimate (LE) for PE portcos: the half-yearly forecast cycle (2026)
What the LE is, when it’s delivered, how to build it and how to present it to the PE board.
TL;DR
The latest estimate (LE) is the formal half-yearly revised forecast the PE-portco CFO delivers to the PE board — not a replacement for the budget, but an honest locked update of where you’re landing. LE1 in July (after H1 close), LE2 in October (after Q3 close, plus first view on next year). Built from actuals year-to-date plus revised view for the rest of the year, with a bridge analysis between budget and LE per cause (volume, price, cost, timing, FX). Explicitly mirrored against covenant requirements, LBO model and value creation plan. Multi-level: per OpCo and consolidated at HoldCo level. Finstack supports LE as a forecast type from EUR 39/month per entity.
What is a latest estimate and why is it standard for PE portcos?
A latest estimate (LE) is a formal, locked half-yearly forecast the portco CFO delivers to the PE board. The LE has two parts: actuals year-to-date (the realized figures through the LE moment) plus revised view for the rest of the year (what you now expect to realize in the remaining months, based on current assumptions). Together they form the current best estimate of where you’ll land full-year. The LE is frozen at the LE moment and stands as the reference until the next LE.
For PE portfolio companies the LE is standard, while in the broader SME segment it’s less common. The reason is structural: PE investors have a hold period of typically 4-7 years with an established value creation plan and an expected exit thesis. Half-yearly they want to verify whether the plan is on track, whether covenants stay in view, and whether the LBO model set up at acquisition remains tenable. The rolling forecast (internal, continuous) and the budget (annual anchor) are not enough for this investor discipline — a formal half-yearly update is required that’s board-presentable.
The LE discipline lives or dies by the bridge analysis and proactive risk communication. An LE that simply presents figures without explaining why they deviate from budget — and without an action plan on the deviations — fails its purpose. The PE board wants to see that the portco CFO understands the drivers, recognizes the risks and formulates targeted counter-measures. For broader context on forecasting in SMEs and PE portcos — including the four forecast types (budget, rolling forecast, latest estimate and 13-week cashflow) — see our article on forecasting for SME CFOs.
LE vs budget vs rolling forecast: three forecast types that work together
For PE portfolio companies three forecast types live side by side: the budget (set before year start), the rolling forecast (internal continuous), and the latest estimate (formal half-yearly to the board). Each has its own role and they undermine each other when used interchangeably.
The practical mechanic: the budget is set in December and remains as the anchor for bonus linkage and covenant reference. The rolling forecast lives alongside and is updated monthly by the portco CFO and finance team for operational steering — no external distribution. The LE is built twice per year by freezing the rolling forecast at the LE moment, adding a formal review layer (drivers, risks, action plans) and delivering it as a board pack to the PE board.
The relationship between LE and rolling forecast: the LE is not a new forecast built separately from the rolling forecast — that would be duplicate work and create inconsistency. The LE is the rolling forecast at a specific moment, with an extra external-communication layer on top. For the operational forecast cycle itself: see the complete guide on rolling forecast for SME CFOs. For holding the budget as anchor: see the guide on setting up a budget for SME CFOs. For PE portcos running multi-level (HoldCo, MidCo, OpCo): each forecast type runs per level plus consolidated.
The LE cycle for PE portcos: LE1 (July) and LE2 (October)
The standard LE cycle for a PE portco has two LE moments, both tied to a quarter close. Per LE moment a 3-4-week process runs of actual close, rolling-forecast update, LE build and board-pack delivery. The timing below assumes calendar-year portcos; for broken fiscal years the rhythm shifts accordingly.
Mid-year update after H1 close
Trigger: H1 close end of June. The portco CFO has 3-4 weeks to build the LE: actuals H1 from the ERP, revised view H2 based on the current rolling forecast, bridge analysis vs budget, covenant update, LBO-model mirror, value creation plan update. Delivery end of July or early August to the PE board.
Focus: full-year landing. The PE board wants to know where you expect to land on revenue, EBITDA, cash and debt — and what the top-3 risks for H2 are.
Q3 update plus first budget view for next year
Trigger: Q3 close end of September. Turnaround 3-4 weeks: actuals YTD plus revised view Q4, bridge analysis, covenant tracking, plus — what distinguishes LE2 from LE1 — a first view on next year’s budget. Delivery end of October or early November.
Focus: full-year landing with more certainty (3 quarters of actuals) plus strategic input for next year’s budget. The PE board uses LE2 to approve next year’s budget by end of December.
Some PE funds request an additional LE3 in March (full-year close confirmation, to support the audit) or work with quarterly LEs for portcos under covenant pressure. For portcos in a VCP trajectory where the value creation plan requires formal milestone tracking, a quarterly LE is not uncommon. Align the exact cadence with the investor-relations team at the fund manager.
Practical tip for the portco CFO: build your internal monthly cycle so that LE1 and LE2 are incremental extra work on top of the standard rolling forecast, not a separate exercise. That saves 5-10 days of work in peak months. For the operational cycle: see the rolling forecast guide.
Bridge analysis: how do you explain the difference between budget and LE to the PE board?
The bridge analysis is the heart of a good LE presentation. A PE board does not accept an LE that simply says “EBITDA comes in at €X instead of budget €Y” — it wants to see the causes, structured, with magnitude per cause. A good bridge analysis explains the gap per causal category, not per line item.
The standard bridge categories for a PE portco are:
- Volume: higher or lower volume vs budget — per business line or segment.
- Price: realized price vs budgeted price (including discount-mix effects).
- Variable cost: unit cost vs budget — raw materials, external purchasing.
- Fixed cost: Opex vs budget — staff, rent, marketing, IT.
- Timing: deals shifting from H1 to H2 or vice versa, without full-year impact.
- FX: currency effects for portcos with foreign operations.
- One-off: incidental income or expense (restructuring, M&A costs, settlements).
The bridge presentation follows a fixed structure: budget EBITDA → per category the delta with magnitude and explanation → LE EBITDA. Visually typically a waterfall chart. Per category at minimum a one-line explanation (what is the cause?) and an action plan (what are we doing about the cause in H2 or next year?). A board pack without an action plan on the top-3 causes fails its purpose — the PE board wants to see that you not only know what is happening, but also what you’re doing about it.
For PE portcos with multi-level: do the bridge first consolidated, then per significant entity. Not per cost center — that level of detail belongs in the appendix. The PE board wants the top-down causal logic, not the line-by-line analysis. For multi-entity context: see forecasting per entity and cost center. A practical heuristic: pick at most 5-7 bridge categories; more makes the analysis unreadable for the board. Keep detail per category in the appendix for follow-up questions.
LE and LBO-model alignment: covenants, debt ratio, value creation plan
What distinguishes the LE for PE portcos from an SME LE is the explicit mirror against three reference frames set up at acquisition: the LBO model (financing structure and exit thesis), the covenants (bank requirements during the hold period), and the value creation plan (operational value-creation roadmap).
LBO model. The LBO model is the financial model that underpinned the business case at acquisition — purchase price, financing (senior debt, mezz, equity), expected returns. Per LE: mirror actual H1 + LE H2 against LBO assumptions per business line. Question: are we on track for the exit thesis or do we need to correct? An LE that omits this mirror misses the highest-impact part of its purpose.
Covenants. PE portcos typically have a set of bank covenants linked to the senior-debt financing: leverage ratio (debt/EBITDA, typically <5x at start, <3x toward exit), interest cover (EBITDA/interest), DSCR (Debt Service Coverage Ratio), minimum cash. Per LE: actual H1 vs covenant, LE full-year vs covenant, headroom (% of the requirement). With shrinking headroom (<15-20% toward year-end) it becomes a red flag in the board pack. For cashflow discipline around covenants: see the 13-week cashflow guide.
Value creation plan (VCP). The VCP is the operational roadmap for value creation during the hold period — typically organized around 4-6 levers: organic growth, M&A, pricing optimization, operational efficiency, working capital, and exit readiness. Per LE: per VCP lever a progress update (target, actual, gap, action). That keeps the PE board sharp on strategic execution, not just on the financial outcomes.
The combination of these three mirror frames is what makes an LE board-presentable for a PE context. An LE that presents the figures without LBO mirror, covenant tracking and VCP progress is an SME LE, not a PE LE. For scenario work around bank covenant discussions: see scenario planning for SME CFOs.
LE per entity and per cost center in a PE-portco group
PE portcos are rarely single-entity. The typical structure is a HoldCo (acquisition vehicle holding the senior debt) above a MidCo (legal structuring) above one or more OpCos (the operating companies). For a platform deal multiple OpCos can sit under the same HoldCo. The LE must reflect that structure: built per OpCo, consolidated at HoldCo level, with the financing costs and intercompany relations explicitly included.
The practical setup for multi-entity PE portcos:
1. LE per OpCo, bottom-up. Each OpCo builds its own LE with its own drivers, its own assumptions, its own bridge analysis vs budget. The OpCo CFO or OpCo controller owns it — the holding CFO consolidates but does not invent figures per OpCo. Drivers per OpCo often differ fundamentally: a Dutch manufacturing OpCo has different drivers than a German sales OpCo within the same platform deal.
2. Consolidation at HoldCo level with intercompany elimination. At HoldCo level the tool adds the OpCo LEs, eliminates intercompany transactions (management fees, IC loans, dividends), and adds HoldCo-level items (interest on senior debt, mezz coupon, fund-level costs). The result is the consolidated LE that goes to the PE board.
3. Per cost center where it adds value. For PE portcos in sectors with a strong cost-center structure (healthcare, retail, professional services) forecasting at cost-center level is crucial — budget overruns become visible early. For PE portcos with a cleaner operating model (a SaaS platform, a product company) forecasting per entity is sufficient. For multi-entity forecasting in detail: see forecasting per entity and cost center.
Finstack supports this setup natively: unlimited forecasts per entity, scenarios per forecast, automatic intercompany elimination during consolidation, and a consolidated view with toggles for sub-grouping (per acquisition year, per geography, per business line). For platform deals where M&A and bolt-ons are common: entities can be added, restructured or removed without breaking historical reporting.
What does your tool need to do for the LE cycle of a PE portco?
The LE cycle lives or dies by the tool. If every LE means copying a spreadsheet, manually filling it from the ERP and consolidating per OpCo, the LE is a 4-week project that dominates the portco CFO’s schedule. With good tooling the LE build is incremental on the rolling forecast and the marginal time is 1-2 weeks. Five tool requirements make the difference.
1. LE as a first-class forecast type alongside budget and rolling forecast. Finstack supports budget, rolling forecast, latest estimate and 13-week cashflow as separate forecast types, per entity and per cost center. An LE is a frozen snapshot of the rolling forecast at the LE moment, with versioning so LE1 and LE2 sit side by side for historical comparison.
2. Automatic bridge reporting between budget and LE. For the bridge analysis: per line item the variance against budget, automatically categorized where possible (volume, price, cost, FX). The portco CFO adds the causal explanation; the tool delivers the figures and the categorization.
3. Multi-entity consolidation with intercompany elimination. For the HoldCo-MidCo-OpCo structure: automatic consolidation per LE moment, intercompany elimination between entities (management fees, IC loans, dividends), and consolidated view at HoldCo level. Indispensable for platform deals with multiple OpCos.
4. Automatic actuals feed from your ERP per entity. For the YTD actuals that form the base of every LE. Finstack natively connects with Exact, AFAS, Twinfield, Odoo, Pennylane, Xero, QuickBooks and MS Dynamics 365 BC. Per entity and at transaction level — no manual trial-balance imports.
5. Spreadsheet flexibility for LBO model and VCP tracking. The LBO model and VCP typically live in Excel or Google Sheets — often in a complex model designed by the PE fund manager. With Finstack’s 2-way Excel and Google Sheets sync, both stay in their existing spreadsheet environment, while actuals and LE figures are fed automatically. No manual retyping, no version conflict between reporting tool and investor model.
Plus — for fractional CFOs and interim CFOs serving multiple PE portcos: a tool that works portfolio-wide, with switching between client environments and consistent reporting format. Our guide for fractional CFOs covers this requirement further.
Build the LE-pack template once properly — bridge waterfall, covenant tracker, LBO mirror, VCP progress — and reuse it every LE cycle. The marginal time for LE1 and LE2 drops to 1-2 weeks instead of 4. Start with the 14-day free Finstack trial to experience LE as a forecast type.
Explore Finstack.
Free trial for 14 days.
Access to all features. No credit card required.
.png)
Three common mistakes with the LE for PE portcos
The LE cycle is a combination of internal discipline (rolling forecast as base) and external communication (bridge, covenants, LBO mirror) to the PE board. Three patterns recur in PE-portco practice that structurally undermine the value of the LE.
Presenting the LE as a new forecast instead of as an update
The portco CFO builds a completely new forecast for the LE instead of freezing the rolling forecast at the LE moment. Result: duplicate work, inconsistency between the internal steering forecast and the external board LE, and the portco CFO is tied up for 3-4 weeks during a busy close period. What works: keep the rolling forecast continuously up to date; at the LE moment freeze the rolling forecast and add the review layer (bridge, covenants, LBO, VCP). Typically saves 60% of LE turnaround time.
Figures without bridge analysis and without action plan
The LE presentation shows the difference between budget and LE without explaining why and without an action plan on the deviations. The PE board gets figures but no logic, and cannot judge whether the portco CFO understands the drivers and recognizes risks. What works: bridge per cause (volume, price, cost, timing, FX), per cause an action plan, top-3 risks explicitly addressed. Rather 5 causes with clear explanation than 15 line items without a coherent connection.
Covenants and LBO mirror missing
The LE presents P&L, cashflow and balance sheet without explicit mirror against covenant requirements and LBO assumptions. The PE board has to derive it themselves — and they don’t, so the LE misses its purpose. What works: covenant tracker with headroom percentage in every LE pack (leverage, interest cover, DSCR, minimum cash), plus an LBO mirror table that shows how LE relates to the exit thesis. Not a separate analysis on separate request — standard fixed component of every LE.
Frequently asked questions
Can't find your question? Please let us know
What is a latest estimate (LE) for a PE portco?
An LE is a formal half-yearly revised forecast the portco CFO delivers to the PE board. LE1 in July (view on full year), LE2 in October (plus first view on next year). Locked snapshot — not a replacement for the budget, but an honest update. Standard for PE because the board needs to verify each half-year whether the VCP is on track.
What is the difference between LE and rolling forecast?
Rolling forecast: continuous internal best-current estimate that moves monthly — for operational steering by portco CFO and MT. LE: formal half-yearly snapshot that’s locked and goes to the PE board, with bridge analysis vs budget. Rolling forecast = internal steering tool. LE = external board deliverable. Rolling forecast feeds the LE.
When do I deliver LE1 and LE2?
Standard PE cycle: LE1 within 3-4 weeks after H1 close (end of July/early August), view on full-year landing. LE2 within 3-4 weeks after Q3 close (end of October/early November), full-year plus first indication for next year. Some funds request LE3 in March for close confirmation, or quarterly LEs under covenant pressure or VCP-tracking requirements.
How do I present an LE to the PE board?
Three pillars are standard. (1) Headline figures: revenue, EBITDA, cash, debt — actual H1, LE2H, LE full-year vs budget. (2) Bridge analysis: difference per cause (volume, price, cost, timing, FX), not per line item. (3) Drivers and risks: top-3 assumptions and downside. PE board wants the logic, not just figures. For groups: consolidated at level 1, per entity as appendix.
How do I use the LE for covenant tracking?
Each LE compares explicitly against relevant covenants: leverage (debt/EBITDA), interest cover (EBITDA/interest), DSCR, minimum cash. Per metric: actual H1, LE full-year, covenant requirement, headroom (% of requirement). With shrinking headroom (<15% toward year-end): warning signal in the board pack and proactive lender communication. Covenant tracking should be part of LE discipline.
How does the LE tie into the LBO model and value creation plan?
The LE is mirrored against the LBO model (set up at acquisition) and the value creation plan (VCP, steered during the hold period). Per LE: mirror actual H1 + LE2H against LBO assumptions and VCP targets, identify top-3 deviations, give an action plan. LBO model is your reference point for the exit thesis; LE shows whether the thesis is on track.
Which tool fits best for the LE cycle of a PE portco?
Finstack for PE portcos with 1-30 entities: budget, rolling forecast, LE and 13-week cashflow as separate forecast types, per entity and per cost center. ERP connections with Exact, AFAS, Twinfield, Odoo, Pennylane, Xero, QuickBooks and MS Dynamics 365 BC. Bridge reporting budget vs LE. Multi-level for HoldCo-MidCo-OpCo. Plus 2-way Excel/Sheets sync for LBO model and VCP. From EUR 39/month per entity, 14-day free trial.
CFO turned Founder - Finstack
Sources and provenance
- finstack.io — Reporting & insights — LE, bridge reporting and covenant tracking
- finstack.io — Spreadsheet sync — 2-way Excel and Google Sheets integration for LBO model and VCP
- finstack.io — Consolidation — HoldCo-MidCo-OpCo consolidation and multi-level
- finstack.io — Integrations — native ERP connections for actuals feed
- Finstack Help Center — Sources & connections — ERP connections and sync frequency (3 hours)
- finstack.io — Pricing — from EUR 39/month per entity
Last reviewed: June 23, 2026 · Next review: September 2026
Consolidated reporting and forecasting.
