Staff Leave & Claims: Approval That's No Longer a Guess in WhatsApp

A car workshop on the edge of town, three mechanics. One texts the owner the night before: "Boss, I'm off tomorrow, taking my kid to the clinic." The owner types "ok" and moves on. The next morning the mechanic who was supposed to open the morning shift isn't there, and the other two end up covering a car that was promised by noon. The leave was genuinely approved — it just existed inside one message buried under a hundred others, seen by nobody but the owner.

A dental clinic with one receptionist who often fuels up her own car to drop lab samples off. She sends a photo of the receipt in the clinic's WhatsApp group and gets paid in cash that same day. A month later she sends the same receipt photo again, thinking it was never settled — and the owner, who can't remember which receipts were already paid, pays it a second time.

A salon with five staff. Around Hari Raya, three of them separately ask for leave the same week — one messages the owner directly, one asks in person, one tells a senior staff member who she assumes will pass it on. On what was meant to be the busiest morning, the owner only realises three of the five aren't coming in, and clients who booked a week earlier have to be moved to another day.

Why this keeps happening

First, a leave request or a claim usually lives as a conversation, not a record. A WhatsApp message, a phone call, or something said in passing can't be checked back tomorrow, let alone next year when payroll or an audit needs proof.

Second, there's no single balance to check against. The owner doesn't remember how many annual leave days each staff member has already used, so every approval is a guess — approve now, worry later about whether they'd already run out.

Third, approval and notification are two separate steps that are easy to drop. The owner types "ok" to one staff member, but whoever else has to cover the shift finds out only on the day itself.

Fourth, proof of claims and payment status scatters everywhere. A receipt in a chat thread, a cash payment recorded nowhere — there's no single place anyone can trust to say what's already been settled.

What owners try instead

Most common: a text or a call straight to the owner. Fast, but it depends entirely on one person's memory — and it breaks the moment more than one person (the owner and a manager, say) can approve leave, because neither can see what the other already approved.

One step up is a logbook or spreadsheet staff fill in themselves after they're back. The trouble is the record gets written AFTER the fact, not before — so it's a history, not an approval, and it does nothing to stop two key staff taking the same week off without anyone noticing early enough.

For claims, many owners just pay cash out of petty cash the moment a receipt shows up, with no mark on the receipt itself to say it's been paid — the exact cause of the double payment in the dental clinic story above.

How staff leave and claims should work

First principle: every request is filed by the staff member themselves, in one place. Once an owner switches on the "Enable HR / Staff module" toggle under Settings, a "Staff Portal" menu appears for every staff login. From there they apply for leave and submit claims on their own — no texting the owner and hoping it's remembered.

Second principle: leave types match how Malaysian workplaces actually run, not one generic "leave" box. TempahKu supports eight types — annual, sick (MC), unpaid, emergency, maternity, paternity, compassionate, and marriage leave. Maternity and paternity are counted as consecutive calendar-day blocks, matching the statutory requirement, rather than working days only — and the system only shows maternity leave to female staff and paternity leave to male staff.

Third principle: the day count is automatic, not guessed. Staff pick a start and end date, and the system counts actual working days — weekly rest days and business closures don't get counted against the leave taken. There's a half-day option for the leave types that aren't calendar blocks, and the system blocks a request that overlaps leave the same staff member already has pending or approved.

Fourth principle: the leave balance is visible before approval, not after. The owner sets the entitlement for each leave type (the defaults are 8 annual days and 14 sick days a year, for instance) under "Leave Entitlement", and the system deducts against it automatically as leave gets approved through the year. A request that would exceed the balance is flagged immediately — staff can switch to unpaid leave instead if they need to.

Fifth principle: approval and notification become one step instead of two. Staff requests land straight in the "Leave Requests" panel on the owner's HR dashboard, with one-tap Approve or Reject buttons — and the owner gets an instant Telegram alert the moment a new request comes in. As soon as a decision is made, the staff member who applied gets their own Telegram notification about it, so nobody has to ask "did it get approved yet?" (Owners and managers can log their own leave for record-keeping too — it's auto-approved, since nobody should have to approve their own boss's time off.)

Sixth principle: expense claims run the same way, with one extra step. Staff submit a claim under a category — Travel, Meals, Supplies, or Other — attach a photo of the receipt, and the owner approves it in the "Expense Claims" panel. What matters is that "approved" and "actually paid" are two separate states: the owner only taps Reimburse once the money has genuinely gone out, so no claim ever gets paid twice because nobody remembered whether it was already settled.

When it helps most

It matters most for businesses with three or more staff, especially once more than one person (an owner and a manager, say) can approve leave, or where shift coverage depends on knowing early who won't be in tomorrow.

It's also worth it for businesses that give real leave entitlements — not just "take a day off if something comes up" — because a visible balance is what makes that entitlement mean something, instead of a verbal promise nobody is tracking.

If your business has one or two staff working right beside you every day, and leave gets asked for and approved in a single conversation you genuinely remember, the HR module is probably more steps than you need right now. The toggle switches off just as easily as it switches on, so there's no cost to trying it and turning it back off if it doesn't suit your size.

In short

Leave and claims drifting through WhatsApp isn't anyone's fault — there just isn't anywhere else to put them. The problem isn't that an owner can't be trusted, it's that memory isn't a record, and one "ok" typed to one person never reaches everyone else who needed to know.

TempahKu puts staff leave requests and expense claims in one Staff Portal that staff reach themselves: eight leave types, an automatically-tracked balance, one-tap approval with automatic Telegram alerts, and a "paid" status kept separate from "approved" for claims. All of it starts with one toggle in Settings that the owner switches on when they're ready.