Project cash flow: plan milestone revenue around team costs
Project cash flow becomes more reliable with a deposit, objective milestones, acceptance rules and a plan that places payroll on real payment dates.
A project can be profitable and still run short of money halfway through. The client may pay at kickoff, design approval and final delivery, while payroll, contractors, software and materials continue every week or month. Project cash flow is therefore about more than the contract total. It is about the distance between discrete receipts and continuous costs.
This is different from general irregular-income planning. The revenue may already be contracted. The uncertainty sits in the conditions: when may you invoice, who accepts a stage and how much must you spend before that point? A useful project cash flow forecast exposes those dependencies before delivery starts.
This article provides general business-finance education, not legal, tax or financing advice. Review contracts and tax consequences for your situation.
Design project cash flow first
Do not split the price into three equal invoices by habit. Match each payment to the cost and risk of its stage. A deposit can cover reserved capacity, initial purchases and mobilisation. A middle payment can follow a verifiable deliverable. The final payment should support proper completion, yet not force your business to finance nearly the whole engagement.
The Dutch Chamber of Commerce, KVK, recommends agreeing payment arrangements in the quotation and terms. It identifies partial advance payment and staged invoices for long projects as ways to receive cash sooner. Translate that into project cash flow: every stage needs an amount, invoice trigger, payment term and conservative receipt date.
For large direct costs, test whether the deposit actually covers them. A percentage that sounds standard can be inadequate when licences, materials or specialists are payable immediately.
Make milestones objectively billable
"Halfway" is not a useful invoice trigger. Define the result, reviewer, review period and what happens when feedback is late. State how many revision rounds or changes are included.
Project cash flow becomes fragile when approval is entirely subjective. Work may be ready while billing is blocked by a busy decision-maker or new wishes. Use observable acceptance criteria: agreed files delivered, test completed, stage report approved or installation demonstrably finished.
Separate acceptance from scope change. A new request should not automatically postpone payment for correctly delivered work. Record additional work with its price, schedule effect and, where appropriate, a separate milestone. This keeps project cash flow tied to decisions both sides can verify.
Forecast the receipt date, not milestone day
A milestone on 10 September is not cash on 10 September. Invoicing, the agreed payment term and the client's accounts-payable process still follow. Put both expected invoice date and realistic receipt date in the project cash flow plan.
KVK defines a liquidity budget as expected receipts and expenses used to see whether bills can be paid on time. Its example notes that current revenue may arrive after thirty or forty-five days while suppliers and rent are due earlier.
Use at least three states: contractually planned, billable and received. Only the last state is available cash. The others still belong in the forecast, provided their uncertainty remains visible.
Treat payroll as the continuous stream
Payroll does not wait for design acceptance. Schedule gross pay, employer costs, holiday allowance, applicable pension costs and contractor payment dates. Include non-billable time for project management, meetings, quality control and remediation.
Then build a weekly project cash flow view: opening balance, reliable receipts, payroll and contractors, other project costs and closing balance. A monthly total can hide a shortage around payday. Weekly timing is often more useful between milestones.
Do not automatically treat an early payment as profit distribution or purchasing room. It may need to carry six weeks of team capacity. Give each receipt a job first: direct costs, payroll, tax, buffer and only then uncommitted margin.
Size the bridge between milestones
The necessary project buffer is not simply one month of revenue. Find the largest cumulative shortfall between reliable receipts. Add the costs certain to leave during that interval and subtract only receipts you can reasonably expect. Then allow for delayed acceptance or payment.
Suppose a team works four weeks after the first instalment before stage two becomes billable, followed by a fourteen-day payment term. Project cash flow may need to carry six or seven weeks of costs, not four. A delivery delay plus an internal client delay widens the gap again.
Keep this project buffer separate from tax reserves and the company's general emergency buffer. The project buffer handles a foreseeable timing gap; the emergency reserve handles events outside the normal delivery path.
Stress-test two different delays
Build two scenarios beside the base case. In the first, acceptance moves two weeks. In the second, the milestone is approved on time but the client pays late. Keep payroll, rent and critical suppliers on their real dates in both cases.
The result creates a decision boundary. Can another contractor start? Can a non-critical purchase wait? Should you negotiate a larger deposit or smaller stages before signing? Project cash flow adds value when it changes such decisions before a shortage.
Add a delivery-risk scenario as well. Missing a milestone is different from late payment: you may face remediation cost and a delayed invoice together. Assign that combined risk an owner and response.
Review delivery and money together
A weekly project review needs three lines: what was delivered, what became billable and what was received? Add remaining work, committed costs and upcoming payroll dates. This prevents project management from watching only schedule while finance watches only invoices.
Give one person ownership of the live project cash flow, but share signals with delivery and sales. Sales needs to understand which payment structure is workable. Delivery needs to know which evidence releases a payment. Finance needs a realistic receipt date.
For every change request, record whether it changes only scope or also milestone timing, invoicing and resources. Several small additions can consume another payroll cycle without increasing the project price at the same speed.
Use a simple commitment signal
Green means cash received and highly reliable instalments cover obligations through the next gate. Amber means the plan depends on timely acceptance, so non-critical commitments wait and the milestone is monitored closely. Red means even the base case does not cover payroll or critical suppliers.
This signal is not an accounting standard. It is a decision rule that prevents a large contract value from being mistaken for cash available today. Update it after invoices, receipts, scope changes and shifted delivery dates.
Project cash flow cannot guarantee perfect delivery or prompt payment. It can reveal early which agreement, buffer or choice the team needs to pass the next milestone without panic.
Combine project cash flow across the portfolio
An agency or contractor rarely runs one engagement at a time. Each job can show healthy project cash flow while the company still becomes tight when three teams reach payday before two clients pay. Place active projects on one timeline and inspect their combined lowest balance, not only the margin on each contract.
Do not let a new deposit silently finance an old delivery. Money can share one bank account, but project cash flow should preserve the purpose of every receipt. If project B can start only by using project A's final instalment, that is a deliberate financing decision, not free capacity.
Mark correlated receipts too. Three milestones from one client are not independent when the same procurement team or approver controls them. One internal delay may move all three parts of project cash flow.
Read profit is not cash for the broader distinction between results and liquidity. Project work makes it concrete: revenue may be recognised while the milestone remains unpaid.
Close project cash flow at every milestone
After receipt, check more than the invoice amount. Compare planned and actual hours, outside costs, revision rounds and elapsed time. Then update the remaining project cash flow. A first stage that used extra capacity reduces later room even when the client paid exactly on time.
Record the reason for every material variance. Was scope unclear, estimation weak, acceptance slow or execution inefficient? A contract issue changes future terms; a delivery issue changes planning, staffing or quality gates.
Release apparent surplus only after recalculating the next milestone and all remaining obligations. This turns project cash flow into a rolling forecast instead of a spreadsheet created once during the proposal.
Agree an escalation path
Before starting, decide who acts when evidence is not reviewed, an invoice is not processed or a change threatens the milestone. Give each step a date. A friendly reminder, scheduled call and formal follow-up under the contract are more effective than improvising when payroll approaches.
The escalation path protects the relationship. The client knows what documentation is required and who may accept it. Your team knows when work continues and when new effort pauses. Project cash flow becomes a shared delivery condition rather than a surprise dispute.
Finally, compare original project cash flow with every actual receipt and expense after completion. Use the largest timing variance to improve the next deposit, stage size or buffer. Each engagement can strengthen the payment architecture of the next one.
Keep the version of project cash flow that supported each major commitment. Later, you can see not only that the balance changed, but which information was available when the choice was made. That discipline makes project cash flow a learning system without treating every variance as a mistake in hindsight.
Project cash flow then remains a practical control as the company grows, and the project cash flow review stays tied to evidence rather than optimism.