Contract and payments when buying in Bali

How do you avoid turning an agreement into a file opened only when something goes wrong?

Read it as a decision route. For every amount, date and promise, there should be an answer: which asset it concerns, who is obliged, what evidences performance, where the money goes and how a change is recorded.

The short answer

Before the first transfer, map seven links: asset ↔ description; party ↔ obligation; price ↔ inclusions; payment ↔ trigger; trigger ↔ evidence; money ↔ payee and record; change ↔ pre-agreed action. A gap in one link should not be covered with ‘this is how it is usually done.’

Evidence scope

Checked on

2026-10-15

Geography

Indonesia and Bali; a particular transaction requires review of its own records and circumstances.

Established

• The national framework distinguishes land rights and registration.
• PPAT material concerns deeds used for registration changes.
• Regulation covers specified rights-transfer events and related agreements.

Not established

• Validity, completeness or fairness of a particular agreement.
• Reliability of a party, account, payment request, asset or timeline.
• Tax outcome or a safe transfer procedure for a particular transaction.

1. Start with one version of the asset

A project name, an attractive render and a number in a message can describe the same asset in different ways. Before the agreement, assemble one working card: address and parcel or an unambiguous location reference, type and number, plan, area and its measurement basis, finishes and furniture, common areas, parking and infrastructure where it affects the decision. The point is not page count; it is whether the promise can be compared with what will be handed over.

If part of the description is not yet fixed, that is not a reason to pretend it does not exist. Mark what may change, who may initiate a change, how the buyer will be told and what action is available before the next payment. This makes the agreement work with reality rather than a brochure.

2. Map the roles before mapping the money

One transaction may involve a brand, land holder, developer, contracting party, agent, contractor, payee and registration professional. Matching names on social media or a signboard explain nothing. You need a simple map: who signs the obligation, who must deliver the result, who receives each amount and which record connects each role to the asset.

Indonesia's framework treats land rights and their registration as distinct matters; the PPAT material describes deeds used for changes in registration data. That does not turn this page into a registration manual or confirm a particular chain. It is, however, a good reason not to compress a promise to sell, the underlying right and registration into the single word ‘documents.’

3. Turn the payment schedule into a table of questions

Every payment line needs more than a number and date. Add eight columns: amount and currency; what the amount includes; the trigger; evidence for that trigger; payee; account details and the basis for using them; record after transfer; and what happens if evidence is absent or disputed. Even where the answer is still ‘to be confirmed,’ the gap becomes visible before money leaves.

Do not substitute a calendar for a trigger. ‘Second payment on 1 June’ and ‘second payment after a specific verifiable result’ are different constructions. Whether the first works in a particular agreement is for qualified review. The second at least makes the parties name the result, the evidence and the route if they disagree.

4. Evidence has to be usable for reconciliation

‘We were told it is confirmed’ does not answer what was actually confirmed. For a key condition, agree a minimum record set: the source document or its reference details, date, issuer or signatory, connection to the asset and a way to reconcile it with the prior version. A site photo, a manager's email and a bank message can all help, but they answer different questions.

After a transfer, keep more than the bank confirmation. Link it to the invoice or payment request, schedule version, agreement clause and the payee's confirmation. This is not a legal formula; it is a way not to lose the payment's meaning two months later when the message thread contains dozens of files.

5. Write the change route while things are calm

The most expensive questions rarely arise in the first agreement draft. They arrive when timing, area, layout, specification, bank account or performing party changes. Review not only whether a change is possible, but its procedure: who notifies, in what form, the response time, which records are replaced, whether a new schedule is needed and what happens before agreement is reached.

A simple stress test is especially useful: if one fact changes tomorrow, can a person who was not in the negotiations see from the records which actions stop, which need confirmation and where the decision is captured? If the answer is ‘ask in the chat,’ the process has not yet been described.

6. Handover, delay and exit are separate moments

The word ‘handover’ often hides several different events: the asset is ready for inspection, the buyer receives access, a record is signed, keys are delivered, defects are addressed, documents are completed or use begins. It is useful to separate these events in the agreement and schedule. Then the final payment is not tied to a word the parties understand differently.

Read delay and termination separately as well. Do not look for reassuring language. Look for a definition of the event, the notice route, records that capture each party's position and the next step. The actual consequences depend on the agreement and applicable law; the point here is to make them a review subject rather than an assumption.

Decision steps

1. Assemble the asset version

   Put the description, plan, number, inclusions and every decision-changing feature in one file.

2. Separate the roles

   Name the contracting party, performer, payee and records connecting each to the asset separately.

3. Test every payment line

   For each amount, find the trigger, evidence, payee, account details, receipt and action if there is a dispute.

4. Run a change stress test

   Pick one likely change—timing, specification or account—and trace how it moves through the records.

5. Request review of the actual version before signing

   Submit the current agreement, appendices, schedule and role map—not a marketing deck—for review.

What to check

FAQ

Sources

Next reading