PRODUCT

Six modules, one chain from clock-in to payday

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.

Core HRAttendancePayrollDormitoryMulti-ledger auditMobile
02 / Attendance

Whatever the floor actually runs, it accepts

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.

A

Multi-segment and overnight shifts

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.

B

Automatic rotation, dual algorithms

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.

C

Exceptions reach the line leader the same day

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.

Exception desk / 2026-10-29 2 open
12 min late · 3 staff Waived per shift rule Shift A, 08:00 start · Workshop 1
Overnight missed punch · 1 staff Correction pending Shift B, 20:00 → 05:00 · Workshop 2
TOIL offset · 5 staff Auto-applied Weekend OT converted to leave balance
Piece-rate hours · not received To verify Daily output for 10-28 not yet imported
Pushed to WeCom the same day
Pay items / PAY-ITEM Every field is editable
Grade paybase rate × attendance factor
Weekday OThours × rate × 1.5
Weekend OThours × rate × 2
Public holidayhours × rate × 3
Piece rate / bonusoutput × unit price + appraisal factor
Net paygross − social insurance − housing fund − tax − deductions
Every figure clicks back to a raw punch
03 / Payroll

Payroll runs on formulas
you can audit, not on a person

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.

04 / The other three

Three more things that surround the shop floor

A factory is not only clock-ins and payday. People records, dormitories and approvals belong in the same dataset.

01

Core HR

Employee records, org structure, contracts and licence-expiry reminders. Hire, transfer and exit on one line, without opening another spreadsheet.

Records · Org · Contracts · Roster
02

Dormitory

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.

Allocation · Utilities · Check-out
03

Mobile

Leave, overtime, missed-punch correction and TOIL are approved inside WeCom or DingTalk. A supervisor travelling off-site can still sign.

WeCom · DingTalk · Approval flows
05 / FAQ

The four questions we are asked before every deal

Can we keep the attendance terminals we already own?

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.

Our shifts are messy — two-shift plus ad-hoc changes. Will the system cope?

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.

Is multi-ledger the same as keeping a second set of books?

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.

How do you roll out an overseas plant? Do you send a team?

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.

Next step

Run one month of your own data through it before you decide

Book a demo +86 755 8964 1030