DEV Community

Val Morgan
Val Morgan

Posted on

Planned vs. Worked vs. Paid: Integrating Hospital Scheduling with Timekeeping and Payroll

Most hospital scheduling projects get judged on the roster screen. In my experience they succeed or fail on a much less visible piece: the pipe between the schedule, the time clock and payroll. If that pipe leaks, nurses get paid wrong, and nothing kills adoption faster than a short paycheck.

I have built or repaired this integration a handful of times. Here is what I would tell an engineer starting on it.

Three systems, three different truths

The scheduling system knows what was planned: who should work which shift, on which unit, in which role. The timekeeping system knows what happened: punches, meal breaks, missed punches, edits by managers. Payroll knows what is owed: base rate, differentials, overtime, premiums. Your integration exists to reconcile those three, and they disagree constantly.

A nurse scheduled 07:00 to 19:30 on 4 West punches in at 06:52, gets floated to the ED at 11:00, misses a meal break, and stays until 20:10 to finish handoff. Payroll needs to know about the float (different cost center, maybe a float premium), the missed meal (a penalty in some states), and the 40 minutes of overtime. If your data model only stores "shift worked: yes", you lose all of that.

Model segments, not shifts

What has worked for me is storing worked time as segments: start, end, unit or cost center, job code, and a reference back to the scheduled shift. One shift can produce several segments. Pay rules then run over segments, not over a single shift record.

{
  "employee_id": "E10442",
  "scheduled_shift_id": "S-2026-11-18-4W-D",
  "segments": [
    {"start": "06:52", "end": "11:00", "cost_center": "4W", "job_code": "RN"},
    {"start": "11:00", "end": "20:10", "cost_center": "ED", "job_code": "RN", "float": true}
  ],
  "flags": ["missed_meal"]
}
Enter fullscreen mode Exit fullscreen mode

Practical integration notes

  • Use the vendor's export or API, but plan for files. Many payroll systems still prefer a fixed-format file dropped to SFTP on a cutoff schedule. Build the file generator as a well-tested module, not a script someone runs by hand.
  • Make edits auditable. Managers will correct punches after the fact. Every edit needs who, when and why, and payroll exports should be reproducible for a past period.
  • Respect the pay period cutoff. Late corrections after cutoff go into the next period as adjustments, not as silent rewrites.
  • Match employee IDs early. HR, scheduling and payroll often use different identifiers. A mapping table with ownership and validation will save you weeks.
  • Test with ugly weeks. Daylight saving changeover, a holiday, an agency nurse, a shift crossing midnight.

Choose tools with integration in mind

When teams evaluate scheduling vendors, I push them to ask for API docs and a sample payroll export during the sales process, not after signing. If you want a quick view of the main options first, here is a roundup of staff scheduling platforms built for hospitals.

The roster is the part people see. The payroll file is the part they remember.

Top comments (0)