All calculators

Guide · Freelance Rates

Milestone Acceptance Delays and Cash Timing

Map delivery, customer acceptance, invoicing and collection as separate dates to see how approval delays change project cash needs.

By PriceAndProfit Editorial Updated 3 min read

On this page
  1. Build the date chain
  2. Test the cash period affected
  3. Locate the stage causing the delay

Completing a deliverable does not always make its related cash available immediately. Under a particular agreement, customer acceptance may precede invoice eligibility, and collection may occur later still. A forecast that uses the delivery date as the receipt date skips these stages. Map each stage explicitly using the entered commercial terms and a supportable estimate of review time.

Build the date chain

Consider a hypothetical $12,000 project with a $3,000 initial payment and a $9,000 final payment. The remaining invoice can be issued after acceptance in this scenario. Delivery occurs on day 20, acceptance is expected seven days later, invoicing takes two more days, and the customer is expected to pay 15 days after invoicing. The modeled final receipt falls on day 44.

Expected receipt day = delivery day + acceptance delay + invoicing delay + expected payment delay
EventBase case daySlower acceptance case day
Deliverable submitted 20 20
Acceptance completed 27 41
Final invoice issued 29 43
Final receipt expected 44 58

In the slower case, acceptance takes 21 days instead of seven. The final receipt moves 14 days later, to day 58, while the project price remains $12,000. This is a timing change, not automatically a revenue concession or a cost overrun. Any additional revision work should be entered as a separate change in hours and cost.

Test the cash period affected

Assume usable opening cash is $5,000 and the $3,000 initial payment arrives before work begins. Project payments of $7,000 leave $1,000 before the final receipt. A separate $2,500 operating payment is due on day 50. In the base case, the day-44 receipt brings cash to $10,000, then the day-50 payment leaves $7,500. In the slower case, the day-50 payment creates a projected $1,500 gap before the day-58 receipt.

The eventual balance after all these events is $7,500 in both cases. That equality does not resolve the temporary gap. Keep the negative forecast balance visible and identify which assumptions would have to change to make the schedule feasible. Do not invent an unagreed right to accelerate billing or impose a delay charge.

Locate the stage causing the delay

Record submission evidence, the responsible reviewer, missing inputs, acceptance status, invoice date, and expected settlement date. A deliverable awaiting a customer's review is different from one returned because work is incomplete. Repeated delays may require a more realistic forecast of the review queue, while actual defects may require additional delivery cost.

Use the agreed process to discuss dates and document updates. A percentage-complete estimate is not a substitute for the specific milestone condition. This worksheet does not decide whether acceptance has legally occurred or whether an invoice is enforceable. It separates operational progress from cash timing so that the forecast does not count a receipt before its modeled prerequisites are met.

Method references: OpenStax: Prepare Financial Budgets. Accessed October 22, 2026. All dollar figures are hypothetical worked examples.

Related calculators & guides