Case study

From Spreadsheet Chaos to Transparent Property Commission Payouts

Multi-agent sales cases, dual approval, and automatic commission breakdown for Malaysian property agencies

More about this system

Replace opaque spreadsheet math with a clear sales-case workflow: co-agent sharing ratios that must total 100%, dual booking approval, a short path to completion, and an auditable commission breakdown that shows who earned what — and from which completed case.

  • Case lifecycle
  • Dual approval
  • Deterministic commission engine
  • Multi-agent sharing

The business problem

When several agents share a deal, spreadsheets and chat threads cannot answer a simple question: who earned what, from which completed case?

  1. 1Spreadsheet shares

    Co-agent ratios, role tiers, and overrides lived in fragile worksheets that were slow to update.

  2. 2Chat and email proof

    Booking documents and approvals bounced through WhatsApp or email with no single case record.

  3. 3Opaque disputes

    Manual calculation made payout conversations hard to defend when figures did not match expectations.

  4. 4No payout-by-case view

    Finance could not clearly group entitlements by the completed cases that funded each agent.

The LokaTech solution

A structured sales-case workflow with enforced sharing ratios, dual review, and automatic commission on completion.

  • Agents open a case with project, unit, purchasers, and co-agent shares that must total 100%.
  • Booking proof is attached to the case; project head and admin approve before financing continues.
  • On completion, commission lines are generated from project rules, agent shares, and upline overrides.
  • Admin sees inputs, calculation steps, per-agent amounts, and which cases contributed to each payout.

Interactive walkthrough

Follow a fictional booking from case creation to commission payout in about two minutes. Every control updates demo state on this page — nothing is sent to a server.

Step 1/6·Create case

Interactive demo

BookingFinancingCompleted
Viewing as

New sales case

All project, unit, and purchaser data is fictional.

RM 520,000

RM 500,000

More details

Key features

What the demonstrated sales-to-payout loop covers.

  • Multi-agent cases with 100% shares

    Assign three or four participating agents and enforce a live sharing-ratio total of exactly 100%.

  • Dual booking approval

    Project head and admin each review and approve or reject before financing proceeds.

  • Booking → Financing → Completed

    A simplified status path keeps the case moving without spreadsheet hand-offs.

  • Automatic commission on completion

    Project rules, associate shares, and upline roles generate line items without manual spreadsheet entry.

  • Transparent calculation breakdown

    Inputs, step-by-step math, and payee totals stay visible for finance and agents alike.

  • Payout grouped by contributing case

    Administrators see which completed units fund each agent’s payable total.

Business outcome

Qualitative impact supported by the verified workflow — not invented metrics.

  • Shared sales cases can be submitted with clear co-agent ratios and booking proof
  • Project head and admin can approve or reject before financing continues
  • On successful completion, commission submissions are created without manual spreadsheet entry
  • Finance can inspect per-line entitlements and group payouts by contributing case
  • Agents can see commission tied to completed cases instead of opaque worksheet tabs

Original system scope

The production platform covered more than this portfolio walkthrough. Those modules are out of scope for the interactive demo.

  • Full CRM, inventory master, HR, CP58 tax filing, and payment-gateway integrations
  • Claim → finance approval → payment voucher flows beyond the commission breakdown view
  • Request-change loops, holds, revoke/clawback, retrospective tier jobs, and developer-nett recalculation
  • Exact SST/withholding implementation and operational submit locks

Technology and responsibilities

Architectural patterns verified from the original delivery — stated without inventing a public tech stack.

Capability focus: explicit case statuses with dual approvers; a deterministic commission engine that emits line items from project config and case facts; associate percentage split as the sole ME-side path; role-matched upline overrides on share-scaled nett.

Role: Product delivery focused on case lifecycle, dual approvers, and transparent commission line generation.

  • Case lifecycle with booking dual approval before financing and completion
  • Commission as deterministic line-item generation from config + shares + uplines
  • Admin-facing breakdown that groups payable amounts by contributing case

Need transparent commission workflows for your agency?

LokaTech builds operational systems that replace fragile spreadsheets with clear approvals, auditable calculations, and payouts your team can explain.