The 13-Week Cash Flow: The Operational Rhythm That Prevents Surprises in Mid-Market Finance

The artifact most teams call a 13-week is actually three different things in one spreadsheet In the engagements we have run across PE-backed mid-market finance teams, the 13-week cash flow that gets shown to the sponsor and the lender is, on inspection, an indirect-method extract from the budget reformatted by week, populated with calendarized accruals rather than direct receipts and disbursements, and reviewed only when a quarterly board package is being assembled, which is to say, three things the 13-week is explicitly not supposed to be. A working 13-week is a direct-method projection of cash receipts and cash disbursements, week-by-week, opening cash to closing cash, with the line-of-credit draw or repayment activity shown explicitly, and it is reviewed weekly by treasury or FP&A against the prior week's actuals with variance commentary attached to each material line. The artifact is operational, not analytical, and the discipline is in the cadence rather than the spreadsheet. The pattern across mid-market finance teams is consistent: the team that presents a beautiful 13-week to the lender each quarter and the team that runs the 13-week as an operating rhythm are rarely the same team, and the difference shows up in how often the CFO finds out about a covenant trip from the controller versus from the bank. The structure that survives auditor review and lender scrutiny The 13-week we have refined across deployments has a fixed shape, and the shape matters because the artifact is read across treasury, FP&A, controllership, and frequently the sponsor and the lender, all of whom need to see the same numbers reconcile from week to week without manual stitching. The structure runs as follows. Opening cash by bank account, broken out across operating, payroll, and any restricted or escrow accounts, ties to the prior week's closing cash with a documented rolling reconciliation. Receipts are projected by source, customer collections (typically the largest line, broken out by major customer or segment if concentration warrants), other operating receipts, sale-leaseback or asset disposal proceeds where applicable, and intercompany funding for multi-entity structures. Disbursements run by category, payroll and payroll taxes (with pay-period dates explicit), accounts payable disbursements (separated by vendor concentration or by category for analytical purposes), rent and lease payments under ASC 842, debt service (principal and interest separately, since covenant calculations require both), tax payments (federal, state, sales-and-use), capex, and any non-recurring or transaction-related disbursements that warrant board visibility. Below the operating section sits the financing activity: line-of-credit draws and repayments, term-loan amortization, and any sweep mechanics the credit agreement requires. Closing cash by account ties to opening cash plus net activity, and the artifact closes with covenant headroom calculations, fixed-charge coverage, leverage ratios, minimum liquidity, projected forward by week so the team sees a covenant trip coming twelve weeks out rather than five days out. This structure is what allows a CFO to walk into a lender meeting and answer, in the room, what the cash position looks like at the next covenant test date and what the variance to the credit-agreement-required forecast has been over the last quarter. Without this structure, the answer is "let me get back to you," which is the answer that loses the room. The rolling forecast and the annual budget are different artifacts and serve different decisions The most consistent confusion we encounter when reviewing a finance team's planning stack is the conflation of three artifacts that have distinct purposes, distinct cadences, distinct owners, and distinct levels of precision. The 13-week is one of the three, and it is the one most often left under-resourced because it sits between the more visible annual budget and the more analytically rich rolling forecast. The annual budget is a strategic and contractual document. It anchors compensation plans, board-approved capital allocation, lender-required projections, and the variance commentary that runs the management reporting cycle for the year. It is built bottom-up over six to ten weeks in the fall, locked in December or January, and revised only under defined re-baselining events. The annual budget is a P&L-and-balance-sheet artifact built in the FP&A platform, Workday Adaptive Planning, Anaplan, OneStream, Vena, Pigment, Cube, Mosaic, or Datarails depending on org size and complexity, with cash effect derived rather than directly modeled. The rolling forecast is an analytical document, typically twelve or eighteen months forward, refreshed monthly or quarterly, and used to inform medium-term operating decisions, hiring plans, capacity decisions, capital allocation choices, and reforecasts presented at board meetings. The rolling forecast is also a P&L-and-balance-sheet artifact in the FP&A platform, and the cash effect is again derived through working-capital assumptions rather than directly modeled. Cross-link to /blog/rolling-forecasts-vs-static-budgets-cadence for the cadence discipline. The 13-week is an operational document. It is direct-method, weekly granularity, refreshed every week (not every month, not every quarter), and used to make this-week and next-month decisions about working capital, credit facility utilization, payroll funding, vendor payment timing, and covenant management. The 13-week is most often built and run in Excel for sub-$50M revenue companies, in a treasury management system layer at $50M-$250M, and in an integrated TMS at $250M and above. Confusing the 13-week with the rolling forecast produces a 13-week that gets refreshed quarterly and is structurally incapable of catching the surprises it exists to catch. The same confusion runs in the opposite direction: a team that runs a careful weekly 13-week sometimes fails to build a defensible rolling forecast, because the operating rhythm of the 13-week creates the illusion of forward visibility that does not, in fact, extend beyond the thirteenth week. Cross-link to /blog/cash-forecasting-pe-backed-mid-market for the broader cash forecasting architecture. Ownership: who runs the 13-week depends on org size and structure, and getting it wrong is the most common failure pattern The ownership question is the question that most mid-market finance teams answer wrong, and the answer matters because the 13-week is a cross-functional artifact that pulls data from AR (collections), AP (disbursement timing), payroll (pay-period mechanics), treasury (bank balance reconciliation and credit facility activity), and controllership (period-end accruals, debt service, tax payments). When ownership is ambiguous, the artifact gets built but does not get run, and the cadence collapses within a quarter. In sub-$50M revenue companies, ownership typically sits with the controller or assistant controller, supported by an FP&A analyst if FP&A exists as a function. The model is simple, controllership owns the inputs and the variance review, and the artifact is reviewed weekly with the CFO. There is no treasury function at this scale; the bank-account reconciliation and the line-of-credit activity are owned by the controller's organization. In $50M-$250M revenue companies, ownership shifts. FP&A is now a defined function, treasury may be a defined function or may be a defined responsibility within FP&A or controllership, and the 13-week becomes a shared artifact where treasury (or FP&A acting as treasury) owns the cash mechanics and FP&A owns the customer collection and disbursement assumptions. The variance review is jointly run, and the CFO is the escalation point on exception items. This is the band where ownership ambiguity does the most damage; the answer is to write the ownership down in a one-page operating procedure and to put a single name on the artifact's variance review. At $250M-plus revenue, treasury is its own function with a treasurer, and the 13-week is owned by treasury with FP&A providing collection and disbursement input. The cadence is more formal, the artifact is integrated with the TMS, and the variance review feeds into a monthly treasury report that goes to the audit committee or the board's finance committee. Cross-link to /blog/audit-committee-reporting-clean-meetings for how treasury reporting feeds the AC pre-read. The platform options are not equivalent, and the right answer depends on revenue scale and complexity The platform decision for the 13-week is one of the cleaner sizing decisions in finance ops, because the operational requirements scale with revenue scale and entity complexity in a way that maps cleanly to the available tooling. We see four bands. The first band, sub-$50M revenue, single entity or simple multi-entity, is well-served by Excel. The artifact is direct-method, the data sources are AR aging, AP aging, payroll register, debt schedule, and bank statements, and the integration burden of a treasury platform exceeds the value at this scale. The Excel template should have version control discipline (a single source-of-truth file in SharePoint or Google Drive with a clear naming convention), formula auditing, and a documented input-and-review process. Excel fails not because of its capabilities but because of its review controls; this is a controllership discipline question. The second band, $50M-$250M, multi-entity, possibly multi-currency, is where Trovata, Kyriba, and Coupa Treasury (formerly Coupa Pay / formerly Bellin) begin to make sense. The integration with bank accounts via direct API or BAI2 file feeds eliminates the manual bank-balance reconciliation, the AR and AP integration with NetSuite or Sage Intacct eliminates manual receipts-and-disbursements forecasting, and the platform's variance reporting automates the Monday review cadence. The decision factor is whether the team is spending more than half a day per week on manual data assembly; if so, the platform pays for itself in a quarter. The third band, $250M-plus, complex multi-entity, possibly cross-border, is where an integrated TMS becomes table stakes. Kyriba, GTreasury, FIS Quantum, and the treasury modules of Workday and Oracle are the realistic options. The integration with the ERP (NetSuite, Sage Intacct, Workday, Oracle) is no longer optional, the cash positioning across entities and currencies requires intra-day balance feeds, and the 13-week becomes one output among several from a treasury data layer that also produces FX exposure reports, intercompany netting schedules, and bank fee analysis. The fourth band, pre-IPO and public, adds the disclosure-controls overlay. The 13-week feeds the liquidity disclosure in MD&A, the going-concern analysis the external auditor will review, and the covenant compliance certifications. The platform decision at this band is less about the platform and more about the SOX 404 control narrative wrapped around the platform. Cross-link to /blog/private-company-mda-ipo-readiness for the IPO-readiness implications. The variance review is the entire discipline; the spreadsheet is just the medium The 13-week's value is not the projection itself but the weekly variance review that compares last week's projection to this week's actuals, identifies the material variances, attributes them to drivers, and adjusts the next twelve weeks of the projection accordingly. This is the cadence we run and the cadence we recommend. Monday morning, treasury or FP&A pulls the prior week's actuals, bank statements close on Friday, AR collections are tagged by Sunday, payroll is settled by Monday, and updates the 13-week with the actual week-one column. The system (or the template) compares actuals to the prior week's projection, flags variances exceeding a defined materiality threshold (we typically use $100K or 5% of projected weekly receipts/disbursements, whichever is lower), and produces a variance memo by Monday end-of-day. Tuesday morning, the variance memo is reviewed by the CFO with the controller and, if applicable, the treasurer. Material variances are attributed to drivers, a customer collection slipped, a vendor disbursement was accelerated to capture an early-pay discount, payroll bonus accrual was settled in cash a week earlier than projected, capex closed faster than expected, and the next twelve weeks of the projection are adjusted to reflect both the actuals reality and any forward implications. The adjusted 13-week is the artifact that goes to the lender, the sponsor, and any other external stakeholder. The discipline that breaks this cadence most often is the absence of a defined materiality threshold. Without a threshold, every variance gets discussed, the review takes ninety minutes instead of fifteen, and the cadence is abandoned within a month because the CFO's calendar will not absorb a ninety-minute weekly meeting. With a threshold, the review is exception-based, the meeting runs fifteen to twenty minutes, and the cadence sustains for years. The covenant headroom calculation is the line that separates a 13-week from a glorified weekly cash report The covenant calculation is the line item that, in our experience, distinguishes a 13-week that prevents surprises from a 13-week that merely reports them. A credit agreement typically includes a fixed-charge coverage ratio, a leverage ratio (total funded debt / EBITDA, with definitions specific to the credit agreement), a minimum liquidity covenant, and possibly a maximum capex covenant. Each of these is tested at quarter-end, but the trip is built up over the preceding thirteen weeks, and a 13-week that does not project the covenant calculation forward is structurally incapable of catching the trip in time. The mechanics: each Monday, after the variance review updates the 13-week, the covenant calculation is run for each of the next four quarter-end dates. The inputs are the projected EBITDA (from the rolling forecast, not from the 13-week itself), the projected funded debt (from the 13-week's debt schedule), the projected liquidity (closing cash plus available revolver capacity, both from the 13-week), and the projected fixed charges (debt service, capex, taxes, distributions). The output is the projected covenant ratio at each quarter-end, with a clearly-displayed headroom-to-trip metric. When projected headroom shrinks below a defined threshold, we use 15% of the covenant ratio as a yellow flag and 7.5% as a red flag, the artifact triggers an escalation memo from the CFO to the sponsor and, depending on credit agreement terms, an early conversation with the agent bank. This early conversation is the entire reason the 13-week is run weekly; a covenant trip that the bank learns about three weeks before quarter-end is a renegotiation, while a covenant trip that the bank learns about three days before quarter-end is a default. The teams who run the covenant calculation weekly are also the teams who tend not to trip covenants. The teams who calculate covenants only at quarter-end are over-represented in the covenant-trip population. We have audited both, and the pattern is consistent. The reporting handoffs: who sees the 13-week, in what form, on what cadence The 13-week is consumed by multiple stakeholders, and the form in which each consumes it should differ by audience. Confusing the audiences is the source of most of the criticism the artifact receives, "the lender doesn't read the variance commentary," "the sponsor wants a one-page summary," "the audit committee wants the going-concern angle." Each of these complaints is correct, and each is solved by tailoring the output rather than abandoning the cadence. Treasury and FP&A consume the full 13-week weekly, with the variance memo, the covenant projection, and the next-twelve-week adjustments. This is the operating artifact. The CFO reviews this version with the controller and treasurer each Tuesday morning. The sponsor (PE operating partner or finance partner) consumes a one-page or two-page summary monthly, opening cash, projected closing cash at month thirteen, projected covenant headroom, material variances and drivers, key risks and watches. The cadence is monthly, attached to the monthly operating report, and the form is consistent month over month so the sponsor can read it in two minutes. Cross-link to /blog/investor-reporting-cadence-pe-portfolio for the broader investor reporting cadence. The lender consumes the credit-agreement-required form (typically the agent bank's preferred template) on the credit-agreement-required cadence (typically monthly or quarterly), with covenant compliance certifications attached. This form is often stricter than the team's internal 13-week, different definitions, different roll-forward conventions, different aggregation, and the team that maintains both forms in parallel is the team that does not get caught explaining inconsistencies during a covenant compliance discussion. The audit committee consumes the 13-week's going-concern implications quarterly, in the audit committee pre-read, and the form is the going-concern memo with the 13-week attached as an appendix. The going-concern memo summarizes liquidity adequacy over the next twelve months under the base case and a stress case, references the 13-week's covenant projections, and surfaces any material liquidity risks the audit committee should be aware of. Cross-link to /blog/audit-committee-reporting-clean-meetings for the AC pre-read structure. The board (full board, not the audit committee) consumes the 13-week's monthly summary as part of the monthly board package. The form is one page, the cadence is monthly, and the content is the same as the sponsor summary, opening cash, projected closing cash, covenant headroom, material variances, key risks. Cross-link to /blog/board-reporting-decisions-not-status for the board package structure. What we recommend Run the 13-week weekly as an operating rhythm, not quarterly as a reporting exercise. Pick a single owner, controller in sub-$50M, FP&A or treasury in $50M-$250M, treasurer at $250M-plus, and write the ownership into a one-page operating procedure that defines inputs, materiality thresholds, review cadence, and escalation triggers. Build the 13-week direct-method, not as an indirect extract from the budget. The receipts are real customer collections, the disbursements are real vendor payments and payroll runs, and the working-capital assumptions are visible and defensible. An indirect 13-week looks like a forecast and is incapable of catching the surprises a direct 13-week catches. Project covenant headroom forward weekly, not quarterly. The covenant calculation is the highest-value line on the artifact and is the single most common omission we see in mid-market 13-weeks. Set yellow and red thresholds, and tie the thresholds to defined escalation actions. Tailor the output by audience. Treasury and FP&A get the full artifact, the sponsor gets a one-pager, the lender gets the credit-agreement form, the audit committee gets the going-concern memo, the board gets the monthly summary. Maintaining multiple forms is the cost of running a 13-week that survives external scrutiny; the cost is small relative to the cost of a covenant trip the team did not see coming. Cross-link to /blog/cash-forecasting-pe-backed-mid-market for the broader cash forecasting architecture, /blog/rolling-forecasts-vs-static-budgets-cadence for the budget-vs-forecast cadence, and /blog/mid-market-10-day-close-reference-calendar for how the 13-week interacts with the close calendar.