Force Majeure in Indonesian Property Contracts: 2026 Climate Clauses Buyers Miss

What Reza did the next week — consult a notary in Bekasi, re-read PPJB article 11 (titled "Keadaan Memaksa" or Forced Circumstance), and learned that his contract — like 70% of Bekasi cluster PPJBs in 2024–2025 — used generic language giving developers a wide exit. Bekasi flooding is an annual high-probability event. But his contract's force majeure clause mentioned "natural disasters" without distinguishing routine flooding from extreme events.

Cases like this aren't isolated. During the March 2026 flood, reports from buyer-association complaint channels indicate at least seven Jabodetabek-area clusters had developers send force majeure notifications to buyers. All seven ended without penalties — even though several buyers had already paid down payments above Rp 200 million and rented temporary housing for months awaiting handover.

What Force Majeure Means under Indonesian Law

Indonesian Civil Code (KUHPerdata) Articles 1244–1245 define force majeure (overmacht) as a circumstance preventing the debtor (here: developer) from fulfilling obligations due to events that are unforeseen, unavoidable, and beyond control. All three elements must apply together — not just one.

Often missed by buyers: "unforeseen" has limits. February–March flooding in North and East Bekasi is recurring at least since 2007. BPBD Bekasi records 18 of the last 19 years saw significant flooding somewhere in Bekasi. Claiming "unforeseen" for annual flooding stands on weak legal ground — if buyers are willing to dispute it.

What kept those seven cases favorable to developers: the PPJB clause was drafted broader than the Civil Code. Many Bekasi developer drafts add "bad weather" or "extreme natural conditions" as standard force majeure items without quantification. Buyers signing without slowly reading agree — by contract — that even routine flooding counts.

What Changed in 2026 — 3 Post-March-Flood Drafting Patterns

PPAT consultants regularly handling Bekasi cluster PPJBs report three revision patterns appearing in developer drafts since April 2026:

Pattern 1 — "Natural disaster with intensity above 10-year average"

A progressive change. Force majeure only applies if the event exceeds the 10-year historical baseline. For Bekasi flooding: developers can only claim if the flood is genuinely extreme (e.g., water height >1.5 m across >40% of the cluster, duration >5 days). Annual routine flooding doesn't qualify. This clause is more buyer-protective — make sure your PPJB uses this version.

Pattern 2 — "Including but not limited to floods, earthquakes, riots, pandemics"

The back-door pattern. The phrase "not limited to" makes almost anything claimable as force majeure later. Buyers agreeing to this effectively grant the developer unilateral veto over schedule compliance. If found in a PPJB draft, ask for removal or tightening.

Pattern 3 — "Either party may declare force majeure with written evidence from competent authority"

The most buyer-protective pattern. Developers must obtain official letters from BMKG, BPBD, or the relevant ministry confirming the event qualifies as force majeure. Without that letter, the claim is invalid. Several mid-to-large Bekasi developers adopted this version since Q2 2026.

Documentation Buyers Must Save from PPJB Signing

When buyers want to contest a developer's force majeure claim, the burden of proof sits with both parties. The developer must prove the event meets force majeure criteria. The buyer must prove the impact suffered and the developer's effort considered inadequate.

1. Complete PPJB copy (all articles + appendices). Save the original + scanned PDF, cloud backup.
2. Full payment receipts (DP, installments, additional charges). Transfer slips + developer receipts + tax evidence (PPN, BPHTB).
3. Monthly construction progress photos. Serious buyers visit the site monthly, time-stamped photos of progress. Can't visit? Ask the developer to send monthly progress photos (most developers have this system — just request).
4. Keep developer correspondence in writing. Email, WhatsApp, formal letter — don't rely on verbal meetings alone. If there is a meeting, send a summary via email or WhatsApp afterward and request confirmation.
5. Developer's letters about delay + reason + revised timeline. Every delay must come with a formal letter. Don't accept "the sales person says it's 2 months delayed."
6. Evidence of delay impact on the buyer. If you have to rent extra accommodation or hotel, save receipts. If you miss key moments like a child's school year, document it.

Full pre-signing checklist in key PPJB clauses for buyer protection and developer delivery delay penalties.

Negotiating Force Majeure Clauses Before Signing

Buyers have the most leverage before paying the DP. After DP, leverage drops because money is committed. Before PPJB signing:

1. Ask for specific force majeure definitions with quantitative thresholds

Instead of "natural disaster," request the wording: "flooding with water height >1 m lasting >72 hours, earthquake above 5 SR, riots with regional government emergency declaration." Explicit numbers make arbitrary claims harder.

2. Request a "best effort" clause regardless of force majeure

The developer remains obligated to take reasonable mitigation steps (relocating work, parallel processes, etc.) even during force majeure. Without this clause, the developer can sit still and claim the entire delay duration as force majeure.

3. Request buyer cancellation right if force majeure lasts >180 days

Without an exit clause, buyers can be stuck in a PPJB with no end. Fair standard clause: if force majeure lasts more than 6 months, buyers have the right to cancel and receive a 100% refund with no deduction.

4. Separate partial from total force majeure

Flooding that submerges access roads for 5 days ≠ flooding that destroys building structures. A good PPJB distinguishes the two. Partial force majeure: a reasonable timeline extension is 7–14 days, not 6 months.

If You've Already Signed and the Developer Invokes Force Majeure

The steps are layered. Don't blow up at the site office immediately — that shrinks negotiation space.

1. Request a formal letter from the developer. Force majeure claims must be in writing with event details, duration, project impact, and revised timeline. Reject verbal claims.
2. Check whether the event genuinely meets PPJB criteria. 30 cm of flooding for 12 hours may not meet a PPJB threshold (if the threshold is 1 m). If the clause is generic, evaluate proportionality — does it make sense that the project is delayed 7 months because of 3 days of flooding?
3. Consult an independent notary/PPAT. Not a notary who's also a developer partner. Consultation fee Rp 750k – 1.5 million for PPJB review + advice. Cheap relative to the dispute value.
4. Send a formal objection letter. Not via WhatsApp — registered mail to the developer's address (listed in the PPJB). Copy the Developer Association (REI or APERSI), Housing Department, and legal counsel if applicable. This letter becomes formal evidence if escalating to arbitration or court.
5. Consider mediation before litigation. District court in Bekasi has long queues and high costs. BANI (Indonesian National Board of Arbitration) or OJK (if mortgage financing is involved) can be faster routes. Many PPJBs have mandatory arbitration clauses for disputes — check the "Dispute Resolution" article.
6. Escalate to mass media only as a last step. This works but permanently damages the relationship. Think carefully because buyers still need developer cooperation for title transfer, akad, and after-sales.

For systematic escalation after handover when there are defects, see developer warranty claims for new home defects.

What's Not Force Majeure but Often Claimed

• Material shortages or price increases. That's the developer's business risk, not force majeure. This clause is often inserted but its legal standing is weak.
• Main contractor bankruptcy. That's the developer's problem with its contractor, not force majeure against the buyer.
• Local government permit delays. If there is a real regulatory change requiring a new permit (e.g., PBG replacing IMB), it's limited force majeure. Mere bureaucratic slowness isn't.
• Small demonstrations or unrest near the site. Unless there's an official emergency declaration from government, this usually doesn't qualify as force majeure.
• "Bad weather" without disaster status. Three days of heavy rain isn't force majeure — that's normal Indonesian rainy season. If claimed, ask for BMKG data declaring the event extreme.

Signals of a Buyer-Friendly Developer Clause

Before signing, watch for these signals:

• Developer willing to share PPJB draft before booking fee — not requiring payment to see the draft
• Force majeure clause carries specific quantitative thresholds
• Includes "best effort" clause and buyer cancellation right tied to prolonged force majeure
• The assigned notary is willing to explain clauses to the buyer, no rush
• Developer has a track record of on-time delivery in prior projects — verify against new home warranty periods + handover reputation

Kingspoint itself uses a PPJB with quantitative thresholds for force majeure (flooding >1 m for >72 hours) and a 180-day buyer cancellation clause. Not to brag — this is the standard that should be the reference for Bekasi buyers in 2026. If other developers have looser clauses, buyers are right to ask for tightening.