Approval workflows for discounts, bookings, refunds and payouts
An approval workflow routes a sales or money decision, such as a discount beyond a limit, a cancellation or a refund, to the people allowed to approve it before it takes effect. In MapBhoomi you write policies per action and project, with conditions and ordered approvers (the requester's manager, a role or a named person), each step any one or everyone, with escalation after a set time. A requester can never approve their own request, and every step is recorded.
Discounts given on a call, refunds paid on a WhatsApp nod and receipts back-dated at month end are how margins disappear. Approval policies make each of them wait for the right person, without slowing down the requests that do not need it.
Where the usual way breaks
- Discounts are agreed verbally and discovered at agreement.
- Refunds are paid before anyone checks the forfeiture.
- Managers approve on WhatsApp and nothing is recorded.
- Everything waits for the owner because nobody else is trusted to approve.
What can need approval
- Holds and hold extensions.
- Bookings with a discount at or above a percentage, below the floor price, or through a partner.
- Quotations with a discount.
- Cancellations, refunds and back-dated receipts.
- Commission payouts, vouchers, vendor payments and purchase orders.
- Unit status changes such as marking a unit sold.
How a request moves
- A change that matches a policy waits; a unit waiting for approval shows as on hold on the public map.
- Approvers get an in-app alert and an email.
- Each step is any one approver or everyone; a step with nobody eligible is skipped, and the owners decide if no step has anyone.
- Escalation after N hours, delegation and expiry are recorded.
- On final approval the change is applied, after checking the unit did not change meanwhile.
Who it is for
- Owners who want to stop approving everything themselves
- Sales heads controlling discounts
- Finance teams approving refunds and payouts
- Companies with a reporting hierarchy
One discount, from request to booking
- Booking asks for 6% off. Sales team: Plot 42 · 6% discount (Policy: 5% and above). Buyer: Plot 42 shows On hold (On the public map).
- Approvers alerted. Management: Approval needed · Plot 42 (In app and by email). Sales team: Cannot approve own request (Waits for the sales head).
- Escalated after 24 hours. Management: Escalated to the director (No answer from step 1).
- Director approves. Management: Approved · 6% discount (Every step on record).
- Booking applied. Sales team: Booking BK/2026-27/00042 (Unit re-checked, then booked). Buyer: Booking form and allotment (At the approved price).
Modules it uses
Can a sales person approve their own discount?
No. The requester can never approve their own request.
Do requests without a policy wait?
No. Only actions that match a policy wait; everything else goes through at once.
Can approvals follow the reporting line?
Yes. An approver can be the requester's manager, a manager several levels up, anyone with a role, or a named member.
Is there a history?
Yes. Every request, approval, rejection, escalation and withdrawal is recorded and cannot be edited.