Duplicate staff lists
The roster tool's employee list drifts away from HR.
Techseria Roster is not bolted on to HR. It uses Frappe HRMS records directly: one employee, one leave record, one shift record and one attendance record, from planning to payslip.
Every standalone roster tool creates a second employee list, a second leave record and a monthly export.
The roster tool's employee list drifts away from HR.
Shared by roster, leave, attendance and payroll.
Leave approved in one system is imported or re-entered in the other.
Approved HRMS leave blocks rostering automatically.
Hours exported from the roster are checked against attendance every month.
Publishing creates native Shift Assignments.
Attendance and payroll run on the same records.
The roster tool's employee list drifts away from HR.
Leave approved in one system is imported or re-entered in the other.
Hours exported from the roster are checked against attendance every month.
Shared by roster, leave, attendance and payroll.
Approved HRMS leave blocks rostering automatically.
Publishing creates native Shift Assignments.
Attendance and payroll run on the same records.
Each step hands over to the next through HRMS records.
Winners get an HRMS Leave Allocation and a Leave Application to their approver.
Approved leave is a hard block on the roster.
The engine uses Employee, Skill Map, Shift Type and Holiday List records.
Publishing creates native Shift Assignments.
HRMS check-in and auto attendance run against the published shifts.
Shift and attendance records feed HRMS payroll with no exports or re-keying.
Leave approved after publishing raises an exception, then a rebalance updates Shift Assignments.
Extends HRMS through supported extension points and never modifies HRMS core.
The single staff master, extended upgrade-safely with job site and mobile check-in settings.
Drives skill-based slot matching.
Shift timings feed templates and the engine, with grace-period and overtime settings.
Approved leave blocks, pending leave is flagged, late-approved leave raises an exception and ballot outcomes create leave.
Created on publish and kept in sync after rebalancing, with guards against accidental deletion.
HRMS check-in and auto attendance run against published shifts. Roster-calculated overtime, late-entry and early-exit flags are on the roadmap.
Every HRMS and ERPNext feature stays available and unchanged under the roster.
Recruitment, onboarding, transfers, promotions and exit.
Biometric or app check-in, auto attendance and shift management.
Policies, accrual, encashment, compensatory leave and holiday lists.
Salary structures, tax, benefits, gratuity, salary slips and bank remittance.
Appraisal cycles, KRAs, goals, feedback and training programmes.
Accounting, purchasing, inventory with batch and expiry tracking, assets and projects.
Book a demo and we will show a roster publishing straight into attendance and payroll.