Malaysian housing developers sell under a statutory sale and purchase agreement prescribed by law — Schedule G for landed property and Schedule H for strata units. Payments are not negotiated; they follow a stage schedule set out in the agreement, and each stage is claimable once the appointed architect or engineer certifies it. The compliance burden is low if the certificate, the claim and the buyer's financier all read from the same record, and high if they do not.
The claim chain
- Work reaches a defined stage on site.
- The appointed architect or engineer certifies that the stage is complete.
- The developer issues a progress claim to the purchaser, referencing the certificate and the stage in the schedule.
- Payment follows from the purchaser or their end-financier within the period the agreement allows.
- Late payment attracts interest at the rate the agreement provides.
The stages themselves — work below ground, structural framework, walls with door and window frames, roofing and internal services, internal and external finishes, external works such as drains and roads, and vacant possession — appear in the Third Schedule of the statutory agreement, each with its own percentage. Take the percentages from the executed agreement for your project. The schedule is the contract, and a summary from anywhere else is a summary.
Where developers lose time
Certificates that arrive after the claim is drafted. The certificate is the authority for the claim. Producing the claim first and chasing the certificate afterwards guarantees rework whenever the certified stage differs from the assumed one.
End-financier packs assembled by hand. Most purchasers are financed, and the financier releases against the claim and the certificate. A pack assembled from three different systems takes days per unit at exactly the moment volume is highest — every unit in the project hits the same stage at roughly the same time.
No reconciliation between claimed and received. With hundreds of units claiming the same stage in the same fortnight, the only way to know who has paid is a claim-level ledger. Without it, a handful of unpaid claims per stage survive to handover.
Vacant possession and what follows
Delivery of vacant possession triggers the defect liability period, during which the purchaser can notify defects for rectification, and a portion of the purchase price is held by the stakeholder and released in tranches as that period runs. Two obligations follow for the developer: track every notified defect to rectification with dates, and track the stakeholder sums so the releases are claimed when due. Neither is difficult; both are commonly run on spreadsheets and commonly incomplete. The rectification discipline is the same as snag lists and defect liability.
The delivery clock is a financial control
The statutory agreement fixes the delivery period from the date of the agreement, and late delivery attracts liquidated ascertained damages calculated as the agreement provides. That converts programme slippage directly into a quantified liability per unit, which is why the delivery date should sit in the same system as the units and be visible to management monthly rather than annually. See what a construction delay costs.
What good automation looks like
- Stages configured once per project from the executed schedule.
- Certificate recorded against the stage, with the document attached.
- Claims generated for every affected unit in one action, with the correct percentage and reference.
- Financier packs produced from the same records.
- A claim ledger per unit: claimed, due, received, outstanding, with interest computed where applicable.
That is the whole system. Done this way, a stage claim across 300 units is an afternoon; done manually it is a fortnight.
What to do next
Take your most recent certified stage and count how many hours passed between certification and the last claim issued. If it is more than a day, the delay is in assembling documents rather than in the work — see stage certification driving claims.