Forecast project cash using certification and payment stages

Illustrative example: a contractor plans a ₹30 lakh application. At the forecast update, the client has certified ₹24 lakh. Both amounts are for this application after prior-period reconciliation, not cumulative contract totals. Assume a contractually authorised ₹1.2 lakh retention, no receipt yet allocated and no other deductions in this simplified example. Taxes, statutory withholding and recovery treatment are excluded and must be added under the actual project rules.

Assume, for the teaching scenario, that finance expects the ₹22.8 lakh on 25 November based on the actual certificate and payment process. That date is a forecast assumption, not a contractual promise established by this article. The ₹6 lakh difference should carry its own resolution scenario and expected timing. It should not remain hidden inside the same November receipt.

If later evidence supports a different certification or payment date, update the forecast and retain the reason. Changing the date without explaining the stage movement makes forecast performance difficult to assess.

If finance receives ₹10 lakh against this expected net receipt before the next update, the remaining forecast is ₹12.8 lakh, subject to any revised adjustments. Keep the ₹10 lakh in actual receipts and remove it from future receipts. Leaving the full ₹22.8 lakh in the forecast would count the same cash twice.

Use a bill or claim identity that links the application, its revisions, certificate, invoice where applicable and receipts. Capture the relevant dates, amounts, outstanding differences and responsible owner. A returned application should preserve its relationship to the resubmission so the forecast does not count both.

Autodesk’s payment-application documentation illustrates distinct application and later approval/payment states. In the project forecast, “paid” should be reconciled by finance to actual receipt evidence and allocation; a status selection alone is not sufficient.

For milestone contracts, establish the evidence needed to claim the milestone and the forecast date for that evidence. General physical completion may not establish payment eligibility. For item-rate work, use checked measurements and the cumulative claim history. The RA bill guide explains that quantity bridge.

Retention withheld today may be released only when the applicable conditions are satisfied. Keep the balance, release trigger, supporting evidence, responsible owner and forecast date together. Do not schedule release simply because the construction activity is nearly complete.

Advance recoveries affect the cash received from later bills and need a cumulative balance. Material recoveries or disputed deductions may change the expected net receipt. Show their status and basis, with commercial approval and finance treatment as required.

The same discipline applies to guarantees or other instruments whose release affects cash or borrowing arrangements. Include only the effects supported by the project’s facts and finance policy, rather than treating every released document as a cash inflow.

Supplier and subcontractor cash outflows depend on payment terms, acceptance, certification, invoices and authorised decisions. Payroll and other recurring payments have their own timing. Finance should verify these obligations against current records and applicable requirements.

Cost incurred and cash paid are different views. A received item may be recognised in cost before payment, while an advance can consume cash before the related work is performed. Use the cost-to-complete forecast to understand the remaining economic exposure, then translate expected obligations into dated cash flows.

Autodesk’s budget/contract reference distinguishes cost and forecast measures. Do not assume a cost-to-complete column is already a payment calendar.

For a separate timing scenario, assume the original ₹22.8 lakh remains wholly unpaid at the start of November. Opening unrestricted project cash is ₹10 lakh and planned November payments are ₹28 lakh. With the full receipt expected on 25 November, the base closing balance is:

₹10 lakh + ₹22.8 lakh − ₹28 lakh = ₹4.8 lakh

That positive month-end figure can conceal an earlier shortage. Suppose ₹18 lakh of the payments fall due before the 25 November receipt, with the remaining ₹10 lakh afterward and no other movements. The balance falls to minus ₹8 lakh before recovering to ₹14.8 lakh on receipt and closing at ₹4.8 lakh. Use weekly or dated cash movements where payment concentration matters; a monthly total cannot reveal that interim funding need.

If that receipt moves to December while November payments remain unchanged, the arithmetic position becomes minus ₹18 lakh. That represents a funding gap to review, not an instruction to delay payments or a conclusion about available credit. Finance needs to assess the business’s actual funds, facilities, obligations and permitted actions.

Use explicit scenarios rather than applying an arbitrary confidence percentage to every bill. A base scenario can use the most supportable dates; a delayed-certification or delayed-payment scenario can show the exposure. Identify the event that would move an amount from one scenario to another.

Compare prior expected receipts with actual receipts, separating amount and timing differences. Causes may include incomplete evidence, lower certification, a disputed deduction, an incorrect payment assumption or a receipt allocated to another bill.

Review outflow differences too. A favourable cash balance caused by unrecorded overdue obligations is not an operational improvement. Keep restricted cash and project/entity boundaries clear so one project’s apparent surplus does not imply unrestricted availability elsewhere.

Commercial owns application and certification assumptions. Project controls supplies realistic completion and evidence dates. Finance owns cash allocation, payment assumptions and the consolidated view. Assign an owner to each material uncertainty rather than allowing a formula to imply certainty.

A useful cash forecast shows why money is expected, what has to happen first and how a timing change affects the balance. Its value comes from making uncertainty actionable before the payment date arrives.

1. Link open applications to certificates, invoices and allocated receipts.
2. Separate uncertified value, retention and recoveries from expected net receipts.
3. Validate payment obligations and timing with finance.
4. Model the effect of delayed certification or payment on the cash balance.
5. Review forecast differences by cause and update the next cycle’s assumptions.