A PE-backed monthly close should be predictable, not heroic. Flash by WD3. Preliminary P&L by WD5. Variance commentary and MBR pack by WD8. Board file uploaded WD10. The 13-week cash flow refreshes every Monday, independent of the close. Miss the cadence twice in a row and you lose sponsor trust, which is the currency you cannot rebuild in one quarter.
The monthly finance cadence at a PE-backed portfolio company is the operating rhythm your sponsor uses to decide whether they trust the numbers. Get it wrong in year one and you spend year two on a short leash. Get it right and you get room to run. This is what a working WD1 to WD10 cadence looks like, who owns each step, what the output is, and the mistakes that break it.
Why the cadence matters more than the close
Sponsors do not actually need audited financials on WD5. They need reliable financials on the same day every month, delivered in the same format, with variance commentary that reads like it was written by someone who runs the business. Predictability beats speed. A slow, reliable close on WD8 beats a fast, sloppy close on WD4 that gets restated on WD11.
The mid-market PE playbook has hardened around a common cadence in the last five years. AlixPartners noted in its 2025 CFO Excellence report that portfolio companies that hit a consistent monthly reporting cadence in year one see a 22 percent lift in sponsor-rated CFO effectiveness by year two. The point is not the number. The point is that sponsors reward the boring virtue of “same day, same format, same quality.”
The WD1 to WD10 cadence
Working days, not calendar days. If month-end is a Sunday, WD1 is Monday.
| Day | Task | Owner | Output | Purpose |
|---|---|---|---|---|
| WD1 | Cash cut-off, credit card sweep, subledger tie-out kickoff | Controller / AP lead | Confirmed cash balance, credit card feeds pulled | Cash is the one number sponsors will call about first |
| WD2 | AR aging, AP accruals, unbilled revenue estimate, inventory position | Controller | Working trial balance draft 1 | Get the balance sheet close to right before touching the P&L |
| WD3 | Revenue flash to CFO and sponsor operating partner | FP&A lead | One-page revenue flash: actual vs budget vs prior year, by unit | Sponsor wants a directional read within 3 days. Do not skip this. |
| WD4 | Payroll cut-off, benefit accruals, bonus accrual review, prepaid amortization | Controller | Payroll ledger reconciled | Labor is usually the second-largest line. Miss it and the P&L moves. |
| WD5 | Preliminary P&L to CFO. Draft variance commentary starts. | Controller + FP&A | Preliminary consolidated P&L | Locks the numbers so commentary can be written against fixed data |
| WD6 | Variance analysis: revenue by segment, COGS by driver, opex by department | FP&A lead | Variance workbook with commentary | Explains WHY the numbers moved, not just that they did |
| WD7 | Balance sheet review, cash flow statement, DSO / DPO / inventory days | Controller | Full financial package draft | Working capital is where sponsors find hidden risk |
| WD8 | MBR pack finalized. CFO sign-off. Send to sponsor operating team. | CFO | MBR PDF + Excel financial package | Sponsor reads before the MBR call |
| WD9 | MBR call with sponsor. Deep-dive on 1 or 2 topics agreed in advance. | CFO + CEO | Meeting notes + follow-ups | Not a re-read of the deck. Working conversation. |
| WD10 | Board file upload, covenant compliance certificate (if applicable), forecast refresh queued | CFO / Controller | Uploaded package + signed compliance cert | Closes the loop. Trigger for next month’s forecast. |
Where the 13-week cash flow fits
The 13-week cash flow does not live inside the monthly close. It is a weekly artifact, refreshed every Monday, independent of WD1 to WD10. That separation matters. If you tie the 13-week to the monthly close, you get one data point per month. If you refresh it weekly, you catch collection slippage in week 2 instead of week 6.
Two touchpoints with the monthly cadence: on WD1 you reconcile the prior week’s 13-week actual against the closed cash balance, and on WD8 the MBR includes the updated 13-week view for the next quarter. See the companion piece on building an operational 13-week cash flow for a PE-backed company for the mechanics.
What belongs in the MBR
The Monthly Business Review pack is the finance team’s deliverable but the CEO’s meeting. It should be tight. A 45-page pack that gets read for 6 minutes is worse than an 18-page pack that gets read cover to cover.
What I run:
- Cover page: month, headline number (revenue and EBITDA vs budget and prior year), one sentence on the story of the month
- P&L: current month and YTD, actual vs budget vs prior year, three columns per side
- Revenue detail: by segment, by customer type, unit economics if the business has them
- Gross margin bridge: budget to actual, walk the drivers (mix, price, volume, input cost)
- Labor: hours, rate, overtime, productivity metric if applicable
- Opex by department: with variance commentary written by the department, not FP&A
- Working capital: DSO, DPO, inventory days, AR aging bucket
- 13-week cash flow: current view, changes from last month, decisions needed
- KPI dashboard: 6 to 10 operating metrics with red / yellow / green
- Forecast: current year forecast vs budget, key assumption changes
- Risks and asks: 3 to 5 items the sponsor should know about, with what you need
That is it. If the pack is longer, it is because someone is padding. See the companion post on the PE-backed CFO board reporting package for the deeper structure.
Variance commentary: what actually gets read
The sponsor operating partner reads variance commentary looking for two things: does the CFO know what happened, and does the CFO know what to do about it. Everything else is filler.
Good commentary sounds like: “Q3 revenue missed by $412K, driven by two customer delays in the industrial segment. Both orders shipped in the first week of October and are captured in Q4 flash. Segment margin held at 34.1 percent, in line with plan. No structural issue.”
Bad commentary sounds like: “Revenue was below expectations due to timing. We continue to monitor the situation.”
Every material variance needs three components: what moved, why it moved, and what you are doing about it. If you cannot answer the third question, say so plainly. Sponsors respect “I do not know yet, I will have an answer by Friday.” They do not respect “we continue to monitor.”
Common failure modes in year one
1. Sliding the calendar
You committed WD8 for the MBR pack. In month 3 you slide to WD10 because payroll took an extra day. In month 4 you slide to WD11 because a customer disputed an invoice. By month 6 the sponsor no longer knows when to expect the pack, and every month starts with an email asking “when will we see numbers.” You lost the cadence.
2. Flash that does not match final
WD3 flash says revenue is $8.2M. WD8 final says $7.6M. The sponsor now trusts neither number. If your flash is going to be materially wrong, make it a range with an accuracy band, or push it to WD4. Better to commit to a number you can hold than a number you have to walk back.
3. Commentary written by finance, not the business
Ops variance commentary written by an FP&A analyst who has not walked the plant floor reads like it. The best cadences have finance owning the numbers and department heads owning their own variance commentary. Finance edits, does not author.
4. No forcing function for the forecast refresh
The monthly close closes the month. It should also trigger the forecast refresh for the current year. If your cadence ends at WD10 with the board file, the forecast gets stale. Add “forecast refresh queued” as an explicit WD10 output.
5. The MBR call becomes a re-read of the deck
If the operating partner reads the pack cold in the meeting, you have already lost. The MBR pack has to land 24 hours in advance so the call is a working session on the 1 or 2 topics that actually matter this month. That is the whole point of sending it early.
The 90-day proof point
Three consecutive months of on-cadence delivery is the threshold. After month 3 on time, you have earned the right to ask for headcount, defend a strategic investment, or push back on a sponsor request. Before month 3, you do not. This is not sponsor politics, it is basic credibility math. See the first 90 days as a portfolio company CFO for the earlier setup.
Push back on this.
Every operator’s situation is a little different. If you run this differently, disagree with the methodology, or think we got something wrong, tell us. We publish the best counter-approaches on our Reader Contributions page, credited or anonymous, your call. Email hello@thepragmaticcfo.com.
FAQ
What if my ERP cannot close by WD5?
Then WD5 is not preliminary P&L, it is preliminary revenue and preliminary labor. Do not fake the close date. Sponsors would rather see the cadence honestly extend to WD10 than see a “close” that keeps getting reversed.
Does the sponsor really read all of it?
Operating partners read the cover page, the revenue detail, the working capital slide, and the risks and asks page. Deal team reads the whole thing. Portfolio company CEOs read cover page and forecast. Design the pack knowing that.
Do I need to hit WD5 flash if we already give the sponsor a weekly revenue update?
Yes. Weekly revenue and monthly flash are different. Flash includes preliminary margin. Weekly revenue does not.
How much of this can AI actually help with?
Variance commentary drafting, MBR narrative first drafts, and 13-week cash flow scenario runs. Not the numbers themselves. See the AI-assisted CFO weekly cadence for what actually works.
What is the single most common reason the cadence breaks?
The CFO tries to compress WD5 to WD3 without adding the infrastructure to support it. Speed without accuracy destroys trust faster than the slower cadence would have.
Sources
- AlixPartners, “CFO Excellence in PE Portfolio Companies,” 2025 report
- AICPA and CIMA, “Finance Function Benchmarking Survey,” 2025
- AFP (Association for Financial Professionals), “FP&A Board Reporting Practices,” 2025
- Bain & Company, “Global Private Equity Report,” 2026
Written by The Pragmatic CFO. 15+ years running FP&A and finance operations across PE-backed portfolio companies.
The Pragmatic CFO 