Roster, Attendance and Payroll Don't Match? How to End the Monthly Reconciliation

The roster says Priya worked a night on the 14th. Attendance shows a late check-in. Payroll paid her for a day shift. Somebody in HR spends part of every month working out which of these is right, and the answer is rarely in one place.

This is not a people problem. It is what happens when roster, leave, attendance and payroll are separate systems, each with its own employee list.

In short: Roster, attendance and payroll stop disagreeing when they share one employee record and one shift record. If a published roster creates the shift assignments that drive check-in, attendance and payroll, there is nothing to export and nothing to reconcile. Techseria Roster does this natively on Frappe HRMS and ERPNext.

Where the mismatches come from

• Duplicate employee lists. The roster tool's staff list drifts away from HR.
• Leave keyed twice. Leave approved in one system is imported or retyped in another, and sometimes missed.
• Exports. Hours are exported from the roster, adjusted by hand and imported into payroll.
• Late changes. A swap agreed on the day updates the roster but not the attendance rules or pay.

What a connected flow looks like

1. Leave first. Leave is requested and approved in HR. Approved leave becomes a hard block on the roster, so nobody is rostered on those days.
2. Roster generated from real records. The roster uses the same employee, skill, shift type and holiday records as HR.
3. Publish creates shifts. Publishing creates shift assignments in the HR system.
4. Attendance runs on those shifts. Check-in and automatic attendance, with grace periods and late and early rules, run against the published shifts.
5. Payroll uses attendance. Pay is calculated from the same attendance and shift records.
6. Changes flow through. A rebalance after sick leave updates the shift assignments, so attendance and payroll follow.

How Techseria Roster delivers this

Techseria Roster extends Frappe HRMS and ERPNext through supported extension points and never modifies HRMS core, so platform upgrades stay clean. There is one employee master. Ballot results create HRMS leave allocations and applications. Published rosters create native HRMS Shift Assignments. Roster-calculated overtime, late-entry and early-exit flags on attendance are on the roadmap.

The same platform includes recruitment, onboarding, attendance, payroll, expenses, appraisals and training, plus ERPNext accounting, purchasing and inventory with batch and expiry tracking, so you are not buying separate tools for each.

Questions to ask about any rostering tool

• Does it keep its own employee list, or use your HR record?
• Does approved leave block the roster automatically?
• Does publishing create shift records in your HR system, or just an export?
• Is there one audit trail across roster, HR and finance?

Frequently asked questions

Why do rostered hours not match payroll?

Usually because the roster, attendance and payroll hold separate copies of employees, shifts and leave, with manual exports and re-keying between them. Any change made in one place may not reach the others.

How does a published roster drive payroll in Techseria Roster?

Publishing creates native HRMS Shift Assignments. HRMS check-in and auto attendance run against them, and payroll uses the same shift and attendance records, with no export or re-keying.

Do we need to use Frappe HRMS to use Techseria Roster?

Techseria Roster is built on Frappe HRMS and ERPNext, which are open source and included. For other hospital systems, a REST/RPC API, bulk import and webhooks are available.

Is leave handled in the same system?

Yes. Approved HRMS leave blocks the roster, pending leave is flagged before publishing and leave approved afterwards raises an exception automatically.

Retire the reconciliation spreadsheet

Book a demo and we will show a roster publishing straight into attendance and payroll.