The kinds of request
Staff file everything from Telegram. Seven kinds exist, and they differ in what they change when somebody approves them.
| Kind | What it changes |
|---|---|
| Leave | Marks the day, or one stretch of it, as leave rather than absence |
| Miss scan | Adds the punch that was never made, and recalculates the day |
| Overtime | Makes overtime payable, at the rate chosen on the request — without one, extra hours are recorded and not paid. Its types and rates are the company's own — see Overtime types and rates |
| Expense claim | Goes to payroll with its receipt |
| Salary advance | Goes to payroll, and never leaves a direct message with its amount on it |
| Replacement work | Credits days off to the replacement balance for working a rest day or a holiday, instead of overtime pay — see Replacement work and replacement leave |
| Face photo | Adds a face sample the check-in photo is compared with — filed from the Mini App's settings with the face check camera, and going to the HR role until you configure it. See Face check |
Kinds of leave
A new company starts with six. You can add your own.
| Kind | Paid | Limit |
|---|---|---|
| Annual leave | Yes | The employee's annual balance |
| Sick leave | Yes | You decide |
| Personal leave | Yes | 7 days a year |
| Maternity leave | Half pay | 90 days |
| Unpaid leave | No | No limit |
| Replacement leave | Yes | The employee's replacement balance |
Only annual leave draws on the annual balance, and only replacement leave on the replacement balance. Every other kind has its own yearly limit and leaves the balance alone. Mixing them would produce a balance nobody could explain to the person it belongs to.
Before you start
- Nothing. Every kind works out of the box, and requests go to the manager of the person filing them until you change that — see Deciding who approves what.
Steps
- The employee opens MekongHRM in Telegram and chooses New request.
- They pick the kind, fill in the dates, and press Send it.
- The card goes to whoever approves for them. One approver pressing Approve is enough.
What you should see
The employee is told who it went to. The approver gets a card with two buttons and enough on it to decide without opening anything. Every line starts with a marker — 📝 the kind of request, 👤 who filed it with their staff number and unit, 📅 the days, 🕘 the times, 💬 the note — and the rest depends on the kind:
- Miss scan: the day and how long ago it was, every punch that day should have with the time recorded ("—" where there is none), and the punches the request asks to add. One request covers every punch forgotten that day.
- Leave: the first and last day and how soon it starts, the total with any stretches left out, and what is left of that kind of leave afterwards (kinds with no limit say nothing).
- Overtime: the day, marked when it is a rest day or a holiday; start → end with the hours and the rate, "(+1)" when it runs past midnight; and that day's shift.
- Replacement work: each day with the stretches ticked and their times, and the days it would credit.
- Expense: the day the money was spent, the amount, and whether a receipt photo is attached. The photo itself is opened in the app.
- Salary advance: the amount and, when your company sets a limit, how much has been advanced this month and what is left of the limit, without this request.
Dates carry their weekday, in each approver's own language. The same card is what the overdue reminder repeats and what every copy turns into once somebody decides.
Once it is approved the effect is immediate: a leave request changes the attendance grid straight away, not overnight.
On the web, Requests opens on All requests for somebody who may see every request, and on Waiting for me for everybody else. It has three tabs: Waiting for me, Overdue for somebody with request.override, and All requests. Every tab filters by name or staff number, dates, type, leave type, branch, unit and who a request waits on, sorts by any column header, and pages fifty at a time; a row has the buttons you may press on it — approve or reject what waits on you, step in on or hand on what waits on somebody else. With request.edit (the Owner and HR hold it), a pending request has Change: it opens the on-behalf form filled in with the request, you change what it asks for and say why, and saving cancels the old request and files the change, which goes to its approvers again from the first step; the person is told on Telegram. With request.cancel_approved (the Owner and HR hold it), an approved request has Cancel: with a reason, it undoes what the approval did — leave given back, a missed-punch request's punches no longer counted, replacement days taken back — works the days out again and tells the person on Telegram. A request on a day in a locked period, or an advance or expense a payroll already paid or deducted, cannot be cancelled. All requests lists every request you may see, with the dates each one is about and how much it asks for: days for leave and replacement work, the type, start, hours and rate of overtime, and the amount of an expense or an advance — amounts only for somebody with payroll.view_salary. Leave that leaves stretches out names them on a second line.
If something goes wrong
Nobody is set up to approve this. Ask your HR team to check the approval steps. — nothing in the approval steps produced a person. Use the checker on Approvals to see where the chain runs out.
You cannot approve your own request. — nobody approves their own request, including a manager filing their own leave. It goes to the level above instead.
A request about a closed month is refused. A locked period is not recalculated, so a request that could not change anything is refused rather than accepted and quietly ignored.
Somebody wants to withdraw one. The person who filed it can, while it is still waiting. An approver who wants it gone rejects it, which leaves a reason behind.
Last checked 06/10/2026