A cash flow forecast shows how much money will come in and go out of your real estate business, week by week and month by month, so you can see a shortage before it happens. For developers, the key is to connect three streams: customer installments coming in, construction and land costs going out, and loan or partner funding in between.
This guide shows a simple, practical way to build one, what to include, how to test scenarios and how an ERP keeps it up to date. It pairs well with project budget vs actual costing for developers.
Why cash flow is the real risk for developers
Profit and cash are not the same thing. A project can be profitable on paper and still run out of money in the middle of construction.
Here is why.
- Costs come early. Land is bought upfront. Piling, structure and approvals need money long before most flats are paid for.
- Income is spread out. Customers pay in installments over months or years.
- Payments can be late. Collections rarely match the schedule exactly.
- Costs can rise. Material prices and variations change the plan.
- Many projects share one pool. Money from one project often props up another, which hides risk.
- Loans have fixed dates. Interest and repayments do not wait for sales.
A forecast turns these into numbers you can plan with.
Two views you need
1. Short-term: 13 weeks, updated weekly. This shows the next three months in detail. It answers: can we pay the contractors, salaries and suppliers this month? It is your operating tool.
2. Medium-term: 12 to 36 months, updated monthly. This shows the project life. It answers: when will we need funding, how big is the gap, and when will sales cover it? It is your planning tool.
Use both. The short view stops surprises. The long view guides decisions.
What goes in: cash coming in
1. Booking money and down payments. Based on expected sales per month. Use your sales plan, but be careful with optimism.
2. Installments from sold units. Take the payment schedules of every customer. This is the most reliable inflow, because it is contractual. See flat and apartment sales software and land and plot sales software.
3. Collection adjustment. Not every installment arrives on time. Apply a realistic collection rate and delay, based on your own history by project and customer group. If you do not know your history, find out from your due lists before you build the model.
4. Handover payments. Larger amounts due at handover or registration, tied to the construction milestone.
5. Bank loans and drawdowns. When the money is available, and under what conditions.
6. Partner or investor funding. Capital injections, landowner arrangements or joint venture contributions, with dates.
7. Other income. Rent, parking, utility recoveries and sale of unsold or commercial space.
What goes in: cash going out
1. Land and acquisition payments. Installments to landowners, registration, legal and brokerage.
2. Approvals and design. Fees and consultants.
3. Construction. Contractor running bills, retention releases, materials, labor and site overhead. Use your project plan and committed orders. See contractor management systems and construction ERP software in Bangladesh.
4. Payroll and office overhead. Salaries, rent, utilities and admin. See HR and payroll solutions.
5. Sales and marketing. Advertising, events and agent commission, often tied to sales.
6. Loan interest and repayment. Fixed dates and amounts.
7. Taxes and VAT. Payments on their due dates. Ask your accountant for the schedule.
8. Utility and handover costs. Connection fees, lift commissioning and common area works near the end of the project.
9. Contingency. A planned buffer.
Step by step: build the forecast
Step 1: Start from your opening cash. Real bank and cash balance today, by company and by project if you separate them.
Step 2: List inflows by month. Start with signed installment schedules. Add expected new sales separately, and mark them as lower confidence.
Step 3: Apply collection reality. For each month, reduce expected collections by your typical shortfall and delay.
Step 4: List outflows by month. Start with committed costs, then planned costs, then overhead.
Step 5: Calculate the net cash flow for each month: inflows minus outflows.
Step 6: Calculate the closing cash. Opening cash plus net flow, month after month.
Step 7: Set a minimum cash level. For example, one to two months of fixed costs. Any month where closing cash falls below that is a warning.
Step 8: Find the funding gap. The lowest point of the cumulative curve is the maximum funding you will need.
Step 9: Test scenarios. See the next section.
Step 10: Update. Weekly for the short view, monthly for the long view.
A worked example (illustration only)
The numbers below are invented to show the method. Do not copy them.
A developer has one project. All figures are in BDT lakh. The minimum cash level is 50.
| Month 1 | Month 2 | Month 3 | Month 4 | Month 5 | Month 6 | |
|---|---|---|---|---|---|---|
| Opening cash | 200 | 150 | 40 | -35 | 20 | 95 |
| Scheduled installments | 180 | 180 | 190 | 190 | 200 | 200 |
| Collection rate applied | 85% | 85% | 85% | 85% | 85% | 85% |
| Expected collections | 153 | 153 | 162 | 162 | 170 | 170 |
| New sales receipts | 40 | 30 | 20 | 20 | 20 | 20 |
| Total inflow | 193 | 183 | 182 | 182 | 190 | 190 |
| Construction and material | 160 | 190 | 170 | 90 | 85 | 80 |
| Land installment | 50 | 50 | 0 | 0 | 0 | 0 |
| Payroll and overhead | 20 | 20 | 20 | 20 | 20 | 20 |
| Loan interest | 13 | 13 | 13 | 13 | 10 | 10 |
| Total outflow | 243 | 273 | 203 | 123 | 115 | 110 |
| Net cash flow | -50 | -90 | -21 | 59 | 75 | 80 |
| Closing cash | 150 | 60 | 39 | 98 | 95 | 175 |
(The opening cash for later months uses each previous closing cash. The table is a simplified illustration. Check the arithmetic in your own model.)
What the picture shows: closing cash falls below the minimum of 50 in month 3, and the cumulative position is tight. The developer has time to act before month 3: arrange a short-term facility, slow part of the finishing spend, push for collections of overdue installments, or time a new launch earlier.
Notice also what the 85 percent collection rate does. If collection were 100 percent, the shortage would not appear. If collection were 75 percent, it would be much worse. That single assumption deserves the most attention.
Scenarios you should always run
Base case. Your best estimate.
Downside case. Collections 10 to 15 percent lower, sales slower, costs 5 to 10 percent higher.
Upside case. Faster sales and collections. Useful for planning a new launch.
Stress test. One big thing goes wrong: a contractor delay, a loan drawdown is late, or a major buyer cancels.
For each case, record the lowest cash point, the month it happens and the funding needed. Decisions get easier when you see all three side by side.
Actions when the forecast shows a gap
If the forecast shows a shortage, you have options, ordered from least to most painful:
- Speed up collections. Follow up overdue installments, offer small rebates for early payment, and fix the reminder process.
- Adjust timing of costs. Re-phase non-critical finishing, negotiate supplier terms and align contractor bills with measured progress.
- Release more sales. Push unsold units or run an offer, with care for pricing.
- Arrange bridge funding. Talk to your bank or partners early, not at the last minute.
- Delay a new project launch. Stop one project from draining another.
- Reduce scope or specification on future phases, if appropriate.
The earlier you see the gap, the more options you have.
The data you need from your systems
A good forecast depends on clean source data.
- Customer installment schedules, with due, paid and overdue amounts. See real estate ERP guide.
- Collection history by project and customer.
- Committed costs from purchase and work orders.
- Contractor bills and retention.
- Loan schedules.
- Payroll and overhead budgets.
- Bank balances, reconciled. See finance and accounting for real estate ERP.
If these live in different files, the forecast will always be late. When they live in one ERP, the forecast can update from live data. See key modules of real estate ERP.
What to ask your ERP vendor
- Can the system produce a month-by-month expected collection from customer schedules?
- Can I apply a collection rate or a delay assumption?
- Can I see committed costs by month from approved orders?
- Can I add loans, partner funding and tax dates?
- Can I run base, downside and upside cases?
- Can I see cash by project and for the whole company?
If the answer is no, plan to export to a spreadsheet, and ask what that export looks like.
Mistakes to avoid
Assuming 100 percent collection on time. Use your real history.
Counting uncontracted sales as sure income. Keep them separate.
Forgetting tax and loan dates.
Mixing project cash without tracking. Know which project funds which.
Updating once a quarter. Update weekly for the short view.
Hiding the downside. A forecast that only shows good news is not a forecast.
No minimum cash rule.
How PinBuild+ helps
PinBuild+ holds customer installment schedules, collections, purchase and contractor commitments and accounts in one place, which are the building blocks of a forecast. [Add: confirm whether you offer a cash flow forecast report, what it includes, how collection assumptions are set and whether scenarios are supported. If forecasting is done by export to Excel, say so honestly. Add a screenshot and one client example.]
To see how it fits, request a real estate ERP demo and bring a sample installment schedule and a month of costs.
Quick checklist
- Opening cash from reconciled balances
- Installment schedules by customer
- Collection rate and delay from real history
- New sales shown separately and with caution
- Committed and planned costs by month
- Land, loan, tax and payroll dates
- Minimum cash level
- Base, downside and upside cases
- Short-term weekly view and long-term monthly view
- Actions ready for a gap
FAQs
What is a cash flow forecast for a developer? It is a projection of money in and out by period, so you can see shortages and funding needs in advance.
How far ahead should I forecast? Thirteen weeks in detail, and 12 to 36 months at a high level.
What is the most important assumption? The collection rate and delay on installments.
Should I forecast by project or for the whole company? Both. Project forecasts show each project, and the company forecast shows the total pool.
How often should I update it? Weekly for the short view, monthly for the long view.
Can ERP do this automatically? It can supply live data for it. Ask your vendor what the system reports and what needs a spreadsheet.
