Core HR
Employee records, org structure, contracts and licence-expiry reminders. Hire, transfer and exit on one line, without opening another spreadsheet.
Not six features bolted together. One set of master data moving through six stages: onboarding, rostering and clock-in, exception slips, formula payroll, report output, mobile approval. No system switch, no Excel relay in between.
We don't ask the shop floor to change how it works — the system learns the shifts. That is the single biggest difference from generic time-and-attendance software.
One shift can be split into several segments, each flagged separately as normal time, weekday overtime, weekend overtime or holiday overtime. A shift crossing midnight is settled once, not cut into two days and stitched back by hand.
The most likely shift is inferred from punch data, so rotating rosters stop needing manual re-entry. Shop floor and office run separate calculation logics side by side in one system.
Late arrivals, missed punches and overtime breaches are judged by rule and pushed to the supervisor's phone for approval — so HR isn't chasing slips at month end.
Punches, leave, overtime and piece rates flow straight into payroll — no manual patching. Formulas are configured by HR, with no code and no vendor ticket.
Differences are visible per person: if someone is a cent out, you can see which punch caused it.
Payslips, bank payment files and tax filing — three outputs from one run.
Country rules built in: Vietnam regional minimum wage, Thai public holidays, Bangladeshi overtime caps.
A factory is not only clock-ins and payday. People records, dormitories and approvals belong in the same dataset.
Employee records, org structure, contracts and licence-expiry reminders. Hire, transfer and exit on one line, without opening another spreadsheet.
Bed allocation, check-in and check-out, utility cost sharing. The dorm list and the attendance list come from the same source, so they cannot disagree.
Leave, overtime, missed-punch correction and TOIL are approved inside WeCom or DingTalk. A supervisor travelling off-site can still sign.
Yes. ZKTeco, Hanvon and other mainstream protocols connect directly, so existing devices keep working — connect first, then decide whether hardware needs replacing. Historical punch data can be imported without disrupting the current month's payroll.
Yes. Multi-segment shifts, overnight shifts and automatic rotation are standard capabilities, not custom development. During implementation we configure your actual shift table, then run a month of historical data for you to verify before signing off.
No. The raw punch data is stored once and never rewritten; multi-ledger produces reports on different reporting bases from that same data. Every basis switch is logged — when, and by whom — so when an auditor traces a figure the trail is clearer than a spreadsheet would ever give.
We have local implementation partners in Vietnam, Thailand and Cambodia. Our Shenzhen team configures rules and reports remotely while the partner handles on-site training. The system supports eight interface languages and country-specific payroll rules, and headquarters and plants share one set of master data.