Cash Forecasting for PE-Backed Mid-Market: The Weekly Cycle That Survives a Sponsor Audit

Updated for 2026. The weekly cycle still holds, and the disbursements line now needs an agent-licensing exposure row because vertical SaaS contracts repricing to per-action meters are the surprise cash hit of the year. Pair this guide with the 13-week cash flow operational rhythm and the agent licensing meter field guide. What the sponsor's operating partner actually wants Every PE-backed portco we have advised has the same standing weekly call with the sponsor. The call is sometimes labeled an operating review, sometimes a portfolio update, sometimes simply the Monday-morning check-in; the agenda is consistent regardless of the label. The first artifact the operating partner looks at, usually the only artifact they look at on weeks when nothing material has shifted, is the thirteen-week cash forecast. They read it for under three minutes, they ask three to five specific questions, and the conversation either settles or expands into a longer working session depending on what the forecast reveals about the prior week's actuals and the next quarter's outlook. The pattern across the PE-backed mid-market firms we have audited the cash forecast for is consistent. The forecast is competent. The thirteen weeks are populated. The receipts and disbursements are reasonable. What the operating partner sees, however, is whether the forecast is owned by the controller as an operational artifact or assembled by an FP&A analyst the night before the call. The signals are specific: whether the prior-week variance has a documented explanation tied to a driver, not a category; whether the AR aging tied to the receipts forecast actually matches the AR aging the operating partner pulled from the GL; whether the capex commitments line includes the new equipment purchase the operating partner saw in last week's board materials; whether the debt-service schedule reflects the covenant test the firm is running through next quarter. None of these signals require the operating partner to be hostile or distrustful. They are simply the questions a sophisticated reader of cash forecasts asks, and a forecast that holds up under those questions is a forecast that the firm is actually managing the business against. The cash forecasting practice that survives sponsor scrutiny has four characteristics. It is weekly, refreshed every Monday with the prior week's actuals tied in and the forward thirteen weeks updated. It is operationally driven, with the receipts and disbursements lines tied to the underlying source data, the AR aging, the AP queue, the capex commitments, the debt-service schedule, rather than to monthly trends or budget-derived assumptions. It is variance-disciplined, with every material variance against the prior-week forecast attributed to a driver, owned by a named individual, and reflected in the forward forecast. And it is artifact-complete, with the forecast itself, the supporting tie-outs, and the variance commentary archived in a way the sponsor's quarterly diligence will pull and the firm's own auditors will reference. This guide walks through what each of those characteristics means in practice, the platform options for firms above the spreadsheet threshold, and the failure patterns we surface most often when the sponsor's call has revealed that the forecast is not load-bearing. The four views the forecast actually has to support The thirteen-week cash forecast is the most visible artifact, but it is not the only cash view the sponsor expects. A PE-backed portco running a mature treasury function maintains four interlocking views, each with a different purpose, audience, and refresh cadence. The first is the direct thirteen-week cash forecast, refreshed weekly. This is the operational forecast: receipts and disbursements at a transaction-or-customer level, projected by week, with the running cash balance and the bank-account-level allocation. It is the view the operating partner reads on the Monday call, the view the controller manages working capital against, and the view the treasury team uses to make funding decisions. The receipts side is built from the AR aging and the cash-application history; the disbursements side is built from the AP queue, the payroll schedule, the debt-service calendar, the tax payment schedule, and the capex commitment register. Each line is tied to its source. The second is the indirect cash flow forecast, tied to the budget or the rolling forecast. This is the longer-horizon view: net income forecast plus depreciation plus working-capital movements equals operating cash flow, less capex equals free cash flow, less debt service equals cash to equity. The horizon is twelve to eighteen months at a monthly grain. The view ties to the income statement and balance sheet projections; it informs covenant compliance forecasts, dividend capacity, and capital structure decisions. The sponsor's investment committee reviews this view at the quarterly portfolio update, less frequently than the weekly direct forecast but with more strategic weight. The third is the covenant-headroom view. For firms with debt covenants, leverage ratios, interest-coverage ratios, fixed-charge coverage ratios, the headroom view projects the next four to eight quarters of covenant test results based on the indirect forecast. The view shows the test, the trailing-twelve-month or rolling calculation, the covenant threshold, and the headroom in dollars and percent. Covenant breaches are projected six months in advance so the firm can negotiate amendments rather than request waivers. The covenant view is the sponsor's most important risk view; a portco that surprises the sponsor with a covenant breach has destroyed trust that takes a long time to rebuild. The fourth is the capex commitment view. PE-backed portcos in growth mode often run material capital programs, equipment purchases, facility expansions, IT infrastructure, post-acquisition integration capex. The commitment view tracks every approved capital project: the total approved amount, the cumulative spend to date, the open commitments (purchase orders issued but not yet paid), the forecast spend by week or month for the remaining commitment, and the impact on the cash forecast. The commitment view feeds the disbursements line of the direct forecast and the capex line of the indirect forecast; it also informs capital allocation governance discussions at the board. The four views interlock. A change in the capex commitment view feeds the direct forecast's disbursements and the indirect forecast's capex line, which changes free cash flow and the covenant calculation, which changes the covenant headroom. A material AR slippage in the direct forecast feeds the indirect forecast's working-capital line, which changes operating cash flow, which changes the covenant ratios. The four views are not independent reports; they are projections of the same underlying reality at different horizons and grains. Mid-market firms that maintain them as separate spreadsheets, refreshed by different people on different cadences, end up with internally inconsistent forecasts that the sponsor's diligence will surface. The Monday cycle in detail The weekly cash forecast cycle that we install in PE-backed engagements runs on a Monday-to-Monday rhythm, with each day owning a specific input. The cycle assumes the firm has closed the prior week's books, at least the bank reconciliations, the AR cash application, and the AP posting, by end of day Friday or first thing Monday morning. Firms that cannot meet that threshold should fix the upstream close before adding the cash-forecast cadence. Monday morning, by 9 a.m.: the controller or treasury lead pulls the prior-week actuals. Bank-balance positions, cash receipts by source, cash disbursements by category, AR aging refresh, AP queue refresh, capex commitments status. The actuals are tied to the GL, bank balance ties to the cash GL accounts, AR aging ties to the AR control account, AP queue ties to the AP control account, capex commitments tie to the construction-in-progress and fixed-asset modules. The tie-outs are documented in the working file. Monday morning, by 10 a.m.: the prior-week variance review. The actuals are compared to the prior-week forecast (which projected this week as week one). Material variances, defined as a stated dollar threshold or percentage threshold per line, are attributed to a driver and an owner. Receipts came in below forecast because two enterprise customers delayed payment past the projected date; the forward forecast is adjusted to reflect the new expected payment dates; the AR ownership for those accounts is documented; the next week's receipts line is updated. Disbursements came in above forecast because a vendor accelerated an invoice; the forward forecast is updated; the variance is explained. Monday morning, by 11 a.m.: the forward forecast refresh. Each line of the thirteen-week forecast is refreshed based on the most recent inputs. The receipts line is rebuilt from the AR aging plus expected new bookings; the disbursements line is rebuilt from the AP queue plus the recurring payment schedule plus the capex commitments. The debt-service line pulls from the loan amortization schedules. The tax-payment line pulls from the tax calendar (estimated payments, sales tax remittances, payroll tax deposits). The forecast is internally consistent: the running cash balance ties through, the bank-account allocations tie to the bank-balance forecast, the covenant test (if applicable) is recalculated. Monday afternoon, by 1 p.m.: the operating partner's call. The forecast is presented; the prior-week variance is explained; the forward outlook is discussed; specific risks (large customer payment, vendor negotiation, capex commitment timing) are flagged. The call is conducted with the controller and the CFO together; the operating partner often joins from the sponsor side. The conversation is brief if the forecast holds up and longer if it does not. Monday through Friday: the inputs are maintained continuously. The AR team updates expected payment dates as customer communications arrive; the AP team flags any disbursement-timing changes; the treasury team logs any banking activity that affects the bank-balance projections; the capex team updates the commitment schedule as POs are issued or invoiced. The continuous maintenance means the next Monday's refresh is incremental rather than a full rebuild. The cadence works because the inputs are owned by the operational teams that have the underlying information, and the forecast is the consolidation rather than the source of truth. Firms that try to run the forecast as a single weekly exercise, with FP&A pulling all the inputs in a Monday morning sprint, produce forecasts that are stale in their inputs by the time the call begins. The continuous-maintenance discipline is the difference. The variance discipline that the sponsor reads The variance commentary on a cash forecast is where the sponsor's operating partner forms their judgment about whether the controller is managing the business or reporting on it. The discipline we install has three components. Variance is at the line level, not the aggregate level. Saying that cash receipts came in two hundred thousand dollars below forecast is not commentary; it is observation. Saying that cash receipts came in two hundred thousand dollars below forecast because the seventy-eight-thousand-dollar payment from Customer A was delayed from week one to week three pending dispute resolution, the ninety-five-thousand-dollar payment from Customer B was processed on Friday but did not clear the bank until Monday and is reflected in the new week-one balance, and the remaining variance is timing on smaller accounts, that is commentary. The level of specificity reflects whether the controller is actually working the AR or summarizing reports. Variance is attributed to a driver and an owner. Each material variance has a named owner accountable for the underlying driver (the AR rep working the customer, the AP lead working the vendor, the treasury lead working the bank timing). The owner is documented in the variance log. When the same customer appears in the variance log for three consecutive weeks, the AR strategy is reviewed, the customer is not paying as expected; either the relationship is in distress, the contract terms are not being enforced, or the credit limit needs to be revisited. The variance log becomes the operational signal, not just the explanatory artifact. Variance feeds the forward forecast. A delayed payment is reflected in the forward week's receipts. An accelerated disbursement is reflected in the forward week's disbursements. The forecast is updated with the variance information; the next week's forecast is not a continuation of the old assumptions. Firms that report variances without updating the forward forecast are producing two artifacts that contradict each other; the sponsor will notice and will lose confidence in both. The forecast accuracy itself becomes a tracked KPI. Mid-market PE-backed portcos running mature thirteen-week forecasts typically achieve weekly accuracy of three to five percent on the aggregate cash balance and ten to fifteen percent on the individual receipts and disbursements lines. The KPI trend matters more than the absolute level: a forecast trending toward higher accuracy reflects an improving operational discipline, while a forecast that shows steady or declining accuracy reflects either a destabilizing business or a forecasting practice that has stopped calibrating itself. The platform options Mid-market PE-backed portcos cluster into three platform tiers for cash forecasting, and the right answer depends on the firm's complexity and the sponsor's expectations. Excel-based forecast with structured inputs. Acceptable for firms with one or two operating entities, straightforward banking relationships, and a controller who personally maintains the forecast. The strengths are zero software cost, complete transparency, and full control over the model. The weaknesses are formula fragility (a single broken reference produces wrong numbers that the controller has to find under time pressure), no built-in audit trail (the version control depends on file-naming discipline that breaks down across team members), and no automated tie-out to source systems (the AR aging has to be manually exported and pasted, which produces stale data risk). For PE-backed portcos with active sponsor engagement, the Excel approach works in years one through two of a hold and breaks down after that as complexity accumulates. Trovata. A purpose-built treasury platform with strong bank-connectivity APIs, automated cash positioning, and rule-based forecasting. The strengths are the bank integration (connections to major banks via API, real-time balance updates, automated cash sweeps and reconciliation), the cash forecast modeling environment (rule-based projection of recurring transactions, exception handling for one-time items), and the lighter implementation footprint compared to enterprise treasury management systems. We see Trovata adopted most often in PE-backed portcos in the fifty to three hundred million revenue range with multi-bank relationships and active treasury operations. Implementation typically runs eight to twelve weeks; total cost is in the lower-six-figures range annually for a mid-market firm. Kyriba. Enterprise treasury management system with broad coverage: cash management, payments, FX, debt management, in-house banking, working capital, and compliance modules. Stronger than Trovata for firms with international operations, complex banking structures, or sophisticated treasury needs (FX hedging, intercompany netting, cash pooling). The implementation is longer (sixteen to twenty-four weeks), the cost is higher (upper-six-figures or low-seven-figures annually), and the configuration overhead is meaningful. We see Kyriba adopted in the upper end of mid-market and in PE-backed portcos with complex multi-currency operations. Treasury Intelligence Solutions (TIS). Comparable to Kyriba in scope, with particular strength in payment-process automation and bank-relationship management for firms with many bank accounts and complex payment flows. Common in firms with an international or multi-entity payment surface. Coupa Treasury. Part of the broader Coupa platform, useful for firms already running Coupa for procurement and AP. The integration between AP, payment automation, and treasury is the differentiator; for firms outside the Coupa ecosystem, the standalone value is lower. FloQast Cash Flow. An extension of FloQast's close-management platform into cash forecasting. Useful for firms already running FloQast for the close that want to extend the same workflow into the cash cycle. The platform is newer in this space than the dedicated treasury tools, with less mature features but a tighter integration with the close itself. The decision framework: under one hundred million in revenue with simple banking, run on Excel with disciplined inputs and a defined upgrade trigger (typically the second covenant amendment, the third bank account added, or the first international operation). One hundred to three hundred million with active treasury operations and multi-bank relationships, look at Trovata. Above three hundred million, with international operations or complex treasury, look at Kyriba or TIS. The decision is documented in a one-page memo; the upgrade is planned rather than reactive. The sponsor audit: what they pull and what the response should look like The sponsor's quarterly diligence includes a cash-forecast audit that is more rigorous than most operating partners signal in advance. The audit pulls four artifacts and tests them against each other and against the underlying data. The most recent thirteen-week forecast is pulled with the supporting tie-outs. The receipts line is traced to the AR aging at the same date; the disbursements line is traced to the AP queue and the recurring payment schedule; the bank-balance projection is traced to the actual bank balances and the bank-account-level allocation. Discrepancies between the forecast and the supporting data are flagged for explanation. The trailing-twelve-week forecast accuracy log is pulled. For each of the prior twelve weeks, the forecast (as projected) is compared to the actuals (as reported). The aggregate accuracy KPI and the line-level accuracy are calculated; the variance commentary for each week is reviewed for substance. The log tells the sponsor whether the firm has been forecasting accurately or has been producing forecasts that drift after the fact. The covenant headroom calculation is pulled with the supporting indirect forecast. The covenant test is recalculated from the indirect forecast inputs; the firm's projection is compared to a sponsor-rebuilt version. Material differences are reconciled. The capex commitment register is pulled and traced to board-approved capital. Every commitment is tied to the relevant board approval; new commitments since the prior diligence are reviewed for alignment with the capital allocation framework the firm has agreed. The audit is not adversarial; it is the sponsor's standard diligence to confirm that the forecast they have been reading is the artifact the firm is actually managing against. Firms that maintain the forecast as an operational artifact pass the audit with confirmatory adjustments rather than findings. Firms that produce the forecast for the sponsor and run the business off a different mental model fail the audit and trigger a more invasive sponsor engagement. The patterns we see when the cycle has broken When a PE-backed portco engages us to fix a cash-forecasting practice that the sponsor has flagged, the failure patterns are consistent. The forecast is FP&A's artifact, not the controller's. The receipts line is built from a monthly trend rather than the AR aging; the disbursements line is built from a budget allocation rather than the AP queue; the variance commentary is reconstructed from the GL after the week has closed. The fix is to relocate ownership: the controller owns the forecast, the operational teams own the inputs, and FP&A supports the modeling without owning the output. The thirteen-week forecast is internally inconsistent with the indirect forecast. The direct forecast shows receipts that imply an AR balance the indirect forecast does not reflect; the indirect forecast shows operating cash flow that the direct forecast cannot produce. The fix is the tie-out: the two forecasts are reconciled at the start of every quarter, and the difference is explained in writing. Capex commitments are not in the forecast until the invoice arrives. The firm approves a capital project, issues purchase orders, and only books the cash impact when the vendor invoices. The forecast misses the commitment timing; the disbursement appears as a surprise. The fix is the commitment register, updated at PO issuance, with the forecasted payment timing per the vendor's terms. Covenant headroom is calculated quarterly, not weekly. The firm tests the covenant at each quarter-end and discovers a tight or breached position with no advance warning. The fix is a rolling covenant calculation that runs every week alongside the cash forecast, with the headroom monitored continuously and the covenant amendment process triggered six months before any projected breach. The variance commentary is an output, not an input. The variance is described after the fact; the forward forecast is not updated; the variances repeat across multiple weeks because the forecast does not learn from them. The fix is the discipline described above, variance attributed to driver and owner, forward forecast updated, variance log reviewed for repeat patterns. What we recommend Cash forecasting in a PE-backed portco is not a finance deliverable. It is the operational artifact that the sponsor reads to understand the business and the controller uses to manage working capital. The cycle that survives sponsor scrutiny is built on five practices. Run the Monday cycle every week without exception. Prior-week actuals tied in by 9 a.m., variance reviewed by 10, forward forecast refreshed by 11, sponsor call at 1. The cadence is the discipline; missing weeks signal that the practice is not load-bearing. Build the four interlocking views, direct thirteen-week, indirect twelve-to-eighteen-month, covenant headroom, capex commitments, and tie them to each other. The views are projections of the same reality; inconsistencies among them are the sponsor's first finding. Operate the variance discipline with line-level detail, named drivers, and forward-forecast updates. The variance commentary is the artifact the operating partner reads to judge whether the controller is managing or reporting. Select the platform based on complexity. Excel for simple operations under one hundred million; Trovata for active treasury under three hundred million; Kyriba or TIS for complex or international above that. The decision is documented; the upgrade is planned. Maintain the artifact archive for sponsor diligence. Every weekly forecast, every variance log, every covenant calculation, every capex commitment update, archived in a structured repository that the sponsor's quarterly diligence can pull without a follow-up request. The weekly cash forecasting cycle template included as the artifact for this guide is the version we install in PE-backed engagements when the sponsor has flagged the cash forecast as inadequate or when a new portfolio company is building the practice from inception. Cross-link to the 13-week cash flow operational rhythm for the deeper treatment of the operational mechanics, and to the audit committee reporting post for the broader board-reporting cadence the cash forecast contributes to. The cycle is operational. The discipline is what makes it survive.