A developer's payment schedule should be translated into the buyer's cash and loan calendar before booking. The percentage due at each stage matters less than whether the household knows the trigger, notice, funding source and deadline. Ask the lawyer and lender to explain the actual project's documents.

How do you build the calendar?

For an illustrative new-launch purchase, make a row for each contract milestone with the amount, expected or known date, source document, cash portion, CPF portion if eligible, loan portion and person who confirms it. This purchase is fictional; do not use a generic schedule as the legal terms of a named project. URA's property-buying guide explains the transaction stages, while its housing-developer guidance gives official context for development sales. Ask for the current sale agreement and payment schedule before completing the worksheet.

CPF's home-ownership guidance explains conditions for using eligible savings. IRAS's BSD guide helps calculate the acquisition duty separately. Do not place an assumed CPF amount into a payment row before eligibility and limits are checked. Keep legal fees, insurance and move-in spending visible outside the property-price percentages.

What if a milestone arrives sooner or later?

Run two scenarios around the estimated timetable. A fictional buyer may need to pay rent on an existing home while progressive purchase payments begin; a delay might extend that overlap. Ask the lender about loan validity and disbursement conditions and the lawyer about contractual notices. Our construction-progress guide shows how to log developer updates without relying on rumours. The mortgage pre-approval guide helps test financing before a booking decision.

Do not call an estimated date a promise. Record what is contractual, what the developer forecasts and what the household assumes for planning. If a notice arrives, match it to the correct milestone row, confirm the payable amount and request an explanation of any mismatch. A spreadsheet can organise questions; it cannot replace qualified contract advice.

Which documents should be saved?

Keep the signed schedule, payment notices, lender statements, CPF correspondence, receipts and lawyer's explanations with dates. Set reminders before deadlines but wait for formal notice where required. If the household's income or borrowing changes, revisit every future row before making another commitment. The new-versus-resale cost guide helps compare the different timing of cash needs. You can send NewLaunchGuru a payment-calendar question for editorial guidance. We do not calculate personalised financing or promise a lender match.

Ask the lender to show how interest or payment obligations behave during progressive disbursement for the specific loan offered. If the buyer is still renting, place rent and progressive payments in the same monthly cash calendar. A project delay can alter the overlap, so test a longer scenario without claiming that delay is likely. If a payment notice differs from the spreadsheet, trust neither automatically: compare the formal contract, ask the lawyer to explain the notice and have the lender confirm funding in time. Record the final answer and date.

A household that uses several bank accounts should also note which account will hold each cash amount in advance, leaving enough time for any permitted transfer and verification.

Ask who sends the formal notice and which channel the buyer must monitor for it.

Common questions

Is every milestone date known at booking?

Distinguish contractual triggers from estimates and ask how formal notice is given.

Can CPF be assumed for every payment?

Check eligible use and limits for the actual buyer and property.

Should BSD be hidden inside the loan calculation?

Show it as a separate acquisition cost using IRAS's current rules.

Sources

Something changed or worth adding?

Send a correction or suggestion