Same system. Different sectors.
A twenty-person firm, a government-linked group and a direct selling company do not run HR the same way. Kiplework is one product, set up three ways.
One approval. Two outcomes.
Every HR system records an approval. Kiplework also moves the money. That single difference is what changes for each type of company below.
Your people act in the app
Leave, claims, clock-in, payslips. One phone app, no forms, no email chains.
Your rules decide the route
Thresholds, approvers and tiers are set once by HR. The system enforces them every time.
Approval becomes payment
Approved claims land in the staff member's Kiplepay wallet, drawn from a prefund balance you control.
Payroll closes the loop
Claims, overtime, attendance and bonuses flow into the month's run. One ledger, one bank file.
HR for the company where the boss still signs the claims.
In a small firm, the owner or one admin person is HR, Finance and Payroll on the same afternoon. Kiplework takes the keying, the chasing and the month-end panic off that one desk.
Before
Claims in a WhatsApp group, receipts in a drawer, a payroll spreadsheet only one person understands.
With Kiplework
Claims submitted with the receipt photo, approved by rule, paid to the wallet. Payroll runs from the same data.
What it costs
RM6 per user per month at the early bird rate. Every launch module included, so a ten-person firm pays for ten people, not for tiers.
Typical setup
A starting configuration. Change anything later from Settings.
Governance first. Speed second. You get both.
In a government-linked company, every ringgit needs an approver, a record and a reason. Kiplework keeps the control where procurement expects it, and still gets people paid faster than a bank transfer batch.
For the audit committee
Who approved what, when, and against which threshold. Exportable to Excel or PDF for any period.
For Finance
One prefund balance, visible at all times, with a low-balance alert. No cash leaves without an approval behind it.
For staff
The same process they know, minus the waiting. A Tier 2 claim approved on Tuesday is in the wallet on Tuesday.
Typical setup
A starting configuration for a group with several departments.
Group and subsidiary structure for holding companies is on the roadmap. Ask us about timing if you run more than one entity.
Seven hundred outlets. One payroll run. Zero petty cash tins.
A retail chain is a few thousand people who are never in the same building. They clock in at a mall in Kuching and a high street in Ipoh, work weekend shifts, and pay for a taxi to cover another outlet. Kiplework runs their HR from the phone in their apron pocket, and pays them back before the shift ends.
HR Director
"How do I onboard 3,000 people without 3,000 forms?"
Bulk import by Excel, one-time identity check in the app, and each staff member sets up their own profile and notification preferences.
Finance
"Whose cash, and where is it?"
One prefund balance you top up, visible at all times, with a low-balance alert. Every ringgit out traces to an approval and a payroll line.
Store Operations
"Can area managers approve from the road?"
Yes. Leave and claims are approved from the phone, and a manager sees every pending request across their outlets in one list.
Store staff
"When do I get my money back?"
When the claim is approved. It lands in the wallet, spendable at any DuitNow QR merchant or moved to a bank account.
Typical setup
A starting configuration for a chain with hundreds of outlets.
Kiplework records shifts and calculates overtime from clock times. It does not build rosters. If you use a scheduling tool, talk to us about connecting it.
Your team is everywhere. Their HR should be too.
Direct selling companies and field-heavy businesses run on people who are rarely at a desk: branch staff, trainers, area managers, drivers. Kiplework puts HR on the phone they already carry and pays their expenses where they are.
Branch and event staff
Attendance by location or QR, overtime from clock times, shift patterns for weekend events.
Area managers
Approve claims and leave from the road. See who is holding what. Nothing waits for a trip back to HQ.
Head office HR
One payroll run for every branch, with attendance and claims already in it. Bonus runs by grade or fixed amount.
Typical setup
A starting configuration for a multi-branch team.
Kiplework is built for your staff. If you also pay independent distributors or agents, talk to us about that separately.
Already have an HR system? Keep it. Add the pay layer.
Large groups rarely replace a core HR system in one move, and we do not ask you to. Start with what your existing system cannot do: pay approved claims to a wallet the same day, and run it for your outlet staff first. Your HR system of record stays where it is.
Not sure which one is you?
Register your interest and tell us your company size and type. We will suggest a starting setup before you ever log in.