How Working Capital Cycles Affect a Startup's Funding Requirement and Why They Are Missing from Most Financial Models

A company closes a Seed round of £1.5 million. The financial model shows eighteen months of runway. The model is correct — if the revenue is collected when it is recognised and the costs are paid when they are incurred. The company's actual billing terms are sixty days: enterprise customers pay sixty days after invoice. The company's actual vendor terms are thirty days: software subscriptions, payroll, and infrastructure are paid within thirty days. The company closes three enterprise contracts in month two and invoices for £90,000. The cash arrives in month four, not month two. Meanwhile, the company pays its month two and month three costs of £60,000 each in month two and month three. By month three, the cash balance is £180,000 lower than the financial model projected, because £90,000 of expected revenue collection is sixty days behind the model's assumption.

The model showed eighteen months of runway. The actual runway is approximately fourteen months. The company is not performing below plan. Its revenue, gross margin, and headcount are all on track. The cash shortfall is structural — it is the result of a working capital cycle that the financial model did not account for.

WHAT A WORKING CAPITAL CYCLE IS

Working capital is the difference between current assets and current liabilities. The working capital cycle is the timing pattern by which a business converts its operational costs into cash and then converts that cash into revenue and back again. For a startup, the most material components of the working capital cycle are accounts receivable (revenue earned but not yet collected), accounts payable (costs incurred but not yet paid), and deferred revenue (cash collected for service not yet delivered).

A company with a negative working capital cycle — where cash is collected before costs are paid — has a structural cash generation advantage that improves with scale. A company with a positive working capital cycle — where costs are paid before cash is collected — has a structural cash consumption requirement that grows with revenue.

For most B2B software companies with enterprise customers on sixty to ninety day payment terms, the working capital cycle is positive: the company pays salaries, infrastructure costs, and software subscriptions monthly while waiting sixty to ninety days for customer payments. As revenue scales, this timing gap creates an increasing working capital requirement that must be funded from the capital raise.

THE STRUCTURAL REQUIREMENT

A financial model that does not model the working capital cycle treats revenue as cash received in the period of recognition and treats costs as cash paid in the period of accrual. This assumption is accurate for a company with immediate payment collection and immediate cost payment. It is inaccurate for any company with payment terms, which means it is inaccurate for the majority of B2B startups that sell to enterprise customers.

The correct structural requirement is a cash flow model that separates the timing of cash collection from the timing of revenue recognition, and the timing of cash payment from the timing of cost accrual. Accounts receivable is the vehicle for the former: when a customer is invoiced in month two and pays in month four, months two and three carry an accounts receivable balance that represents cash that has been earned but not yet collected. Accounts payable is the vehicle for the latter: when a vendor invoice is received in month three and paid in month four, month three carries an accounts payable balance that represents costs that have been incurred but not yet paid.

The cash flow model must project these working capital movements monthly and incorporate them into the cash flow statement as working capital adjustments in the operating activities section. The indirect method cash flow statement begins with net income and adjusts for the change in accounts receivable (an increase is a use of cash), the change in accounts payable (an increase is a source of cash), and the change in deferred revenue (an increase is a source of cash). A financial model that omits these adjustments produces a cash flow statement that is equal to the income statement adjusted for non-cash items, which is not the same as actual cash flow for a business with meaningful working capital movements.

The funding requirement is directly affected. A company that projects £300,000 of monthly revenue growing to £600,000 over twelve months, with sixty day enterprise payment terms, has a working capital requirement that grows from approximately £150,000 to £300,000 over the same period. That growth in working capital requirement must be funded from the capital raise. If the raise amount was calculated on the assumption that revenue is collected in the month of recognition, the working capital build is unfunded and will consume cash that the model showed available for operational purposes.

WHAT THE INVESTOR EVALUATES

A Series A investor reviewing a financial model for a B2B company that sells to enterprise customers will check three things related to working capital. The first is whether the cash flow statement differs materially from the income statement in the same period. If the two statements show similar cash figures month by month, the investor will check whether the model includes accounts receivable and accounts payable adjustments. If it does not, the model is treating revenue as cash received and costs as cash paid, which is incorrect for this business.

The second is whether the use of proceeds accounts for the working capital build. A raise amount that funds headcount and marketing without explicitly allocating capital to the working capital requirement may be insufficient for the operational plan it describes. The investor will check whether the capital is sufficient to fund both the operational plan and the working capital cycle through the projected milestone.

The third is whether the accounts receivable days in the model are consistent with the company's actual payment terms. A model that assumes thirty day collection from enterprise customers when the actual contract terms are sixty days will show a cash position that is consistently more favourable than the actual position, and the deviation will widen as revenue scales.

COMMON STRUCTURAL PROBLEMS

The most common structural problem is the income-statement proxy cash flow. Many early-stage financial models use the income statement as the basis for the cash flow statement without incorporating working capital adjustments. The model shows operating cash flow equal to net income plus depreciation and amortisation. For a company with stable, small working capital movements, this approximation is close enough for planning purposes. For a company with sixty to ninety day payment terms from enterprise customers and growing revenue, the approximation becomes materially wrong within three to six months of the model being built, because the working capital build is not captured.

The second structural problem is omitting the working capital requirement from the use of proceeds. A use of proceeds statement that allocates the raise across headcount, marketing, and product development without a working capital line item has not captured the full funding requirement. If the business is growing revenue with sixty day payment terms, the working capital requirement grows proportionally and must be funded. A company that discovers mid-raise that its working capital requirement was not included in the use of proceeds is either underraising or misrepresenting the sufficiency of the raise amount to fund the described plan.

The third structural problem is inconsistent payment term assumptions. A financial model that assumes thirty day collection on enterprise contracts because that is the invoice date, rather than the actual contractual payment terms of sixty or ninety days, is modelling the working capital cycle incorrectly from the first period. The accounts receivable balance builds more slowly in the model than in reality, the cash balance appears higher, and the runway appears longer. The gap between the model and the actuals compounds with each month of trading.

HOW THE FFI STANDARD DEFINES THE REQUIREMENT

The FFI Standard addresses working capital modeling in Book 2, Performance Modeling and Forecasting. At Level 2 Investor Readiness compliance, the Standard requires the financial model's cash flow statement to incorporate accounts receivable and accounts payable working capital adjustments that reflect the company's actual payment terms with customers and vendors. The cash flow statement must not be derived from the income statement without these adjustments for any company with payment terms materially different from zero. The working capital requirement must be identified in the use of proceeds as a distinct allocation where it constitutes more than five percent of the total raise amount. Full criteria at ffistandard.org/glossary/working-capital/.

THE LAYER ENGAGEMENT

Working capital modeling is incorporated into the Foundation layer engagement as a component of the three statement model build, and into the Raise layer engagement as a component of the investor-grade financial model. Both engagements build the cash flow statement from the correct methodology — using the indirect method with accounts receivable, accounts payable, and deferred revenue working capital adjustments — so that the projected cash position reflects actual timing of cash collection and payment rather than revenue recognition timing.

For companies that have an existing financial model without working capital adjustments, the Blueprint Diagnostic at theoakworth.com/portal/blueprint/ identifies the specific gap and quantifies the effect on the projected cash position and runway. For companies approaching a Series A raise, the diagnostic confirms whether the raise amount adequately funds the working capital requirement through the projected milestone or whether the amount requires adjustment before the investor process opens.

RELATED INSIGHTS
- The Assumption Layer in a Startup Financial Model Is Not a Tab. It Is a Governance Document.
- The Headcount Model Most Startup Financial Models Either Miss or Build Incorrectly
- Why a Startup Valuation Without a Documented Methodology Does Not Survive Series A Diligence
- Cap Table Errors That Surface During Legal Due Diligence and the Infrastructure Required to Resolve Them
- How a KPI Framework Connects the Annual Operating Plan to Board-Level Financial Governance

Tool: Blueprint Diagnostic