Learn how to use active ERPat modules through role-based instructions, standard operating procedures, field legends, standards, compliance reminders, and step-by-step workflows. Every guide is synchronized from the owning module and versioned whenever its instructions change.
Showing 7 of 478 synchronized guides.
Diagnosing problems with the ERPat Biotime module: what each failed connection check means, why a connection locks, why an employee shows a conflict, why a punch shows an unexpected day, and a glossary.
Administering the ERPat Biotime module: the seventeen permissions and what each grants, every setting with its default and clamp, the attendance-import controls, the two scheduled jobs, retention windows and the module's security posture.
What the ERPat Biotime module does: mirrors a ZKTeco BioTime or ZKBio TimeCloud attendance server into ERPat, matches every BioTime employee code to a real employee record, and turns the punches into ERPat attendance records for HR to approve.
Routine procedures for the ERPat Biotime module: reading the dashboard, running and monitoring a sync, reviewing employee bindings, resolving a conflict by hand, and handling a partial run.
First-run setup for the ERPat Biotime module: add a BioTime connection, pass the nine-step connection test, run a first sync over a short window, then review and accept employee matches.
Data and screen reference for the ERPat Biotime module: the thirteen mirror tables, nine binding states, punch and verification codes, BT error codes, menu and route map, and the seven integration API endpoints.
The evidence base behind the ERPat Biotime module: which BioTime API routes were verified against a live server, which files were read during design, and what remains documented but untested.