Rental and property management in Bali

What should be agreed with a manager first?

Not commission size. Start with a map of authority: who speaks with tenant, who approves price or discount, who holds keys and access, who receives money, what can be ordered without approval, how costs are supported and who sends report. Only then do figures and timeframes have meaning.

The short answer

Build one operating brief: asset and period, role of each party, communication channel, decision calendar, independent-spend limit, payment flow, required primary records, access list, incident path and handover rules when manager changes. Anything not in the brief remains an open question, not a silent expectation.

1. Name services one by one before selling ‘full management’

Separate tenant search, communication, check-in, calendar, payment receipt, cleaning, maintenance, emergency calls, reporting and asset handover. Every line needs executor, decision right, trigger, result record and responsibility boundary.

This matters more than an attractive package name. One person may do several tasks, but owner should see where their mandate ends and who receives the question next.

2. Money, reporting and data access are not the same thing

A report without primary records is a retelling. A payment without a clear connection to agreement, period and asset is not a usable financial picture. Access to a booking account or bank alert does not itself say who may decide on refund, discount or expense.

The operating brief should list every flow separately: who sees receipt, who matches it to agreement, who holds support, who approves expense and where owner receives a copy. Then history does not disappear when a person changes.

3. Rental model, permissions and tax are checked separately

OSS describes risk-based business licensing and distinct categories including accommodation and accommodation-management services. That does not mean a general service name determines requirements for a selected asset or operating model. This needs precise activity classification and directed review.

DJP’s rental-income rule governs income from renting land and/or buildings and shows that contractual payments and related lines cannot be reduced to one casual word, ‘rent’. There is no need to guess treatment or rate here: the brief should state who verifies applicability, records and handling of specific payments.

4. An incident needs a route before it occurs

Do not stop at an ‘emergency number’. Agree separately: who receives first message, when owner is needed, who may grant contractor access, where photo or report is recorded, who confirms completion and what is told to tenant. These questions often matter more than the speed of first reply.

Do not promise repair outcome or dates nobody controls. You can describe a route in advance: message — initial record — mandate decision or escalation — completion support — owner and tenant update.

5. Management handover is a verifiable pack, not ‘we will brief the new person’

When manager changes, assemble active agreements, current tenants, contacts, calendar, open works, keys, digital access, latest reports and unresolved questions. Every item needs holder and transfer confirmation, not only a promise to send a file later.

A new manager should not inherit unsupported promises. Separate old period and new mandate by date, record pack and clear address for questions relating to the past.

Decision steps

1. Map the mandate

   Assign every service to executor, decision right, trigger and result.

2. Agree records

   For payments, works and messages, define source, holder and owner copy.

3. Build access list

   List physical keys, accounts, calendars, contacts and authority to grant access separately.

4. Set incident route

   Set first contact, escalation, decision limit, record and completion confirmation.

5. Review operating model

   Before launch, separately verify legal, licensing and tax applicability for the actual model.

What to check

Sources

Next reading

In this section