How to Prepare a Cash Flow Forecast for an Etimad Tender

2026-11-05 · 5 min read

Why a tender-specific cash flow forecast matters

When you bid on a government tender through Etimad, the evaluation is not just about price and technical capability. The entity needs confidence that you can fund the project until it pays you. A cash flow forecast for an Etimad tender is the document that shows this — not your annual budget, and not your profit projection, but a month-by-month view of cash in and cash out for that specific contract.

Most SMEs that struggle after winning a tender do not fail because the contract was unprofitable. They fail because the cash timing did not work: guarantees were deposited early, suppliers demanded payment before the first milestone was accepted, and the government payment arrived later than expected. A tender-specific forecast exposes those gaps before you commit.

Step 1: Map the payment milestones from the tender documents

Start with the contract itself. Read the payment terms in the tender documents and the draft contract. You are looking for:

• The milestone or delivery schedule — what must be completed before you can invoice.
• The acceptance process — who signs off, and how long that typically takes.
• The invoicing process — what documents the entity requires with each invoice.
• The stated payment period — and, separately, what actually happens in practice with that entity.

Build a table with one row per milestone and columns for the planned completion date, the invoice date, the expected acceptance lag and the expected payment date. Be conservative on the lag. If you have supplied this entity before, use your actual history; if not, ask around and check the official Etimad terms. A forecast built on optimistic payment timing is worse than no forecast, because it gives false comfort.

Step 2: Add the guarantee and retention deductions

This is the part most first-time bidders underestimate. A tender usually involves more than one guarantee, and each one affects cash at a different point.

• Bid bond: deposited or arranged before submission, returned after award or rejection. It ties up cash or bank credit for weeks.
• Performance guarantee: usually required on award, and stays in place for the contract duration plus the warranty period.
• Advance payment guarantee: if you receive an advance, the entity will normally require a guarantee for the same amount.
• Retention: deducted from each interim payment, typically a percentage, and released after completion and the defect liability period.

Put each of these in the forecast on the date it actually hits your bank account, not the date it is mentioned in the contract. For a worked view of bid bond mechanics, see our guide on how to issue a bid bond for an Etimad tender.

Step 3: Schedule supplier and subcontractor payments

Now map the cost side. For each major supplier or subcontractor, list:

• The payment terms you have agreed — advance, on delivery, or on credit.
• The lead time from order to delivery.
• Whether they will accept payment after your first milestone receipt.

A common mistake is to assume suppliers will wait for the government. Most will not, especially on a first order. If you need supplier credit to make the project work, negotiate it before you bid, and put the agreed terms in the forecast. The gap between when you pay suppliers and when the entity pays you is the core working capital requirement of the tender. Our article on how much working capital an Etimad tender needs explores how to size that gap.

Step 4: Build the monthly cash flow

With milestones, guarantees, retention and supplier payments mapped, you can build the forecast. Use a simple monthly grid:

The closing cash line is the number that matters. It tells you the lowest point your bank balance will reach during the contract. If that low point is below your safety buffer, you have a funding requirement — and you need to address it before you submit the bid, not after.

Step 5: Stress-test the forecast

A single forecast is a guess. Three scenarios are a plan. Run the model with:

• Base case: your expected milestone dates and payment lags.
• Delayed payment case: add one to two months to each government receipt.
• Cost overrun case: increase supplier costs and add a month to the schedule.

If the business survives the delayed payment case without breaching its buffer, the tender is financeable. If it only survives the base case, the bid is fragile. This stress test is also exactly what a bank or financing partner will want to see when you approach them for working capital. Our guide on what banks look for when financing Saudi companies explains the questions they will ask.

Common mistakes to avoid

• Treating the contract value as cash received in month one.
• Forgetting that retention is deducted from every interim payment, not just at the end.
• Leaving guarantee deposits out because they are returned later — they still tie up cash now.
• Assuming suppliers will accept the same payment terms as the government entity.
• Using a single optimistic scenario and calling it a forecast.

How Aamalak helps

Building this forecast by hand in a spreadsheet is possible, but keeping it current as milestones slip and supplier terms change is where most teams lose control. Aamalak brings your bank accounts and statements into one view so you can see actual cash movements against the forecast, and its tender financial readiness view helps you check whether your balance sheet and cash position can support a specific Etimad opportunity before you bid. You can also connect bank statements and Odoo through Aamalak's integrations to keep actuals flowing into the same view.

Conclusion

A cash flow forecast for an Etimad tender is not a formality. It is the document that proves — to yourself and to anyone funding you — that you can carry the project until the government pays. Map the milestones, include every guarantee and retention deduction, schedule supplier payments honestly, and stress-test the result. If you want to see how Aamalak can support that process, book a demo.