Jakarta, UTC+7Open to remote roles and projects

Work/ 03

Deposit Refunds

@Rukita

Most deposit refunds started arriving on time once each step had to be done before the next could start.

ROLE
Product Manager
SCOPE
Refund SOP, process rules, ops and tenant enforcement
WORKED WITH
Finance, Ops, CS, Engineering, Data, UI/UX
YEAR
2025 to 2026

Problem

A deposit refund passed through several teams, and it broke at the handoffs. Tenants didn't know they had to add a bank account to get their refund, and the app never told them. Ops was supposed to inspect the room before the refund moved, but nothing checked that it happened. When a payment got stuck, Finance couldn't see which step had failed, so they chased CS, and CS chased the tenant. Only 14% of refunds went out within the deadline.

Why this approach

The refund flow already existed. It failed between teams, not inside any one of them. Instead of rebuilding it, I closed the gaps: each person had to do their part at the moment it was due, and the system checked before moving on.

What I did

I rewrote the refund SOP with Finance, Ops and CS, so each division knew its steps and its share of the deadline.

In the ops app, I added the deposit bank account as a required check at checkout, and made room inspection a gate before the refund could move. In the tenant app, a reminder asks for the bank account every session until it's filled in.

Before a payout goes out, the system now checks that the bank account and inspection are done. Payments carry a status, so a stuck refund shows an error instead of failing quietly.

With the data team, I improved the Finance dashboard so it shows which step each refund is waiting on. The changes took about two weeks.

What I built

before

  1. Tenant checks out
  2. Room inspection
  3. Payment stuck, no alertonly 14% on time
  4. Finance chases CS, CS chases tenantmissing bank account, round and round
  5. Resolved late

after

  1. Tenant checks in
  2. App asks for the bank account until it's added92% on time
  3. Tenant checks out
  4. Inspection unlocks the refund
  5. System checks the bank account and inspection
  6. Payout goes out on time, every step visible to Finance

The call I made

I enforced the process at both ends. Reminding tenants alone would have left the ops gap open, so tenants got the reminder that kept coming back, and ops got the bank account check as a required checkout task.

What could break, and how I tested it

Refunds stalling without anyone noticing.

Each payment now has a status, and the dashboard shows where it's waiting.

Ops skipping the inspection.

The refund can't move until it's done.

Before rollout, I tested the new flow with Finance.

Result

Refunds paid within the deadline (10 working days for coliving, 20 for apartments) went from 14% in Q3 to Q4 2025 to 92% in Q1 to Q2 2026.

Complaints about deposit refunds fell by about 37% in Q1 to Q2 2026, and incomplete bank information fell by about 60% between Q4 2025 and Q2 2026.

What I'd change

Give every team its own clock.

The refund deadline was split across divisions, so one late team made the whole refund late, and teams needed a daily nudge to finish their part. Next time I'd agree each division's share of the deadline with its lead at the start, and show each team its own queue and due dates. Then the late step is visible without anyone chasing.

Point at the step, not the person.

When a refund stalled, the conversation drifted toward who was at fault. I'd set the dashboard and follow-ups around which step was stuck and why, so teams fix the process instead of defending themselves.

Building something complex, got a messy workflow or an AI idea?

let's talk!
© Mega SetiawatiBuilt with a little magicSide work: Offscreen