How to Integrate Workforce Scheduling with Payroll and Time Tracking in 5 Procedures
Workforce scheduling integration with payroll and time tracking takes five procedures, run in this order. Define the scheduled-versus-worked rule, connect scheduling to time capture, pass approved hours to payroll, handle schedule-change rules where they apply, and reconcile every pay period. Federal wage and hour rules run on hours worked, so the schedule is a plan and the approved time record is what payroll runs on.
The order to run these procedures
Run the procedures in order, starting with the scheduled-versus-worked rule, because every later setting needs one source of truth for hours. Connect scheduling to time capture next, so payroll receives approved hours instead of planned ones. Pass those hours to payroll with overtime set on the fixed workweek. Handle schedule-change rules after that, because premiums travel through the approval path and pay-code mapping built in the earlier procedures. Reconcile every pay period. Payroll or finance should own the rule and the reconciliation, while operations or HR owns capture and approvals.
How to define the scheduled-versus-worked rule
Defining the scheduled-versus-worked rule is a one-sentence policy decision that payroll or finance should own. Under federal wage and hour rules, pay follows hours worked, not hours scheduled, and 29 CFR 516.2 requires employers to record each non-exempt employee’s hours worked each workday and total hours each workweek.
What you need first
* Gather each location’s current schedule templates.
* List every role as exempt or non-exempt, because that status drives which records and overtime rules apply.
* Collect existing policies on early arrival, late departure, and unscheduled work.
* Name the person who approves changes to the rule.
1. Write the rule in one sentence, such as “Employees are paid for all hours worked, and the schedule is the plan.”
2. Name the single source of truth for hours worked, and state that payroll reads from it.
3. Carry location, role, and job code from the schedule so the time record is tagged at the point of work.
4. Write the unscheduled-work rule. Work not requested but suffered or permitted is work time when the employer knows or has reason to believe it is being done, and a rule against it is not enough (29 CFR 785.11, 29 CFR 785.13). DOL’s field assistance bulletin on telework describes a reasonable reporting procedure for non-scheduled time with all reported hours paid, even hours not requested, and says a process that discourages accurate reporting is not reasonable diligence. Flag it, manage it, pay it.
5. Write the shorter-or-longer-than-scheduled rule. For fixed-schedule employees, 29 CFR 516.2 lets the schedule be recorded with a note that it was worked, but exact hours are needed in weeks with more or fewer.
6. Leave room for local schedule-change pay. Where a city or state rule requires pay for a late schedule change, that pay sits on top of the hours-worked rule, and the fourth procedure covers it.
What a correct result looks like
A written one-sentence rule, signed off by its owner, names the time record as the source for hours worked. It also covers unscheduled work and shifts that run long or short, so a manager at any location applies it the same way.
How to connect scheduling to time capture and set exception and approval rules
Connecting scheduling to time capture is a setup task for an operations or HR lead who can see every location, and it decides how each published shift becomes a tagged time record.
What you need first
* Pull the employee roster from scheduling, time capture, and payroll.
* List the time-capture method each location uses today.
* List the shift types, locations, and job codes managers schedule against.
* Name each location’s manager and a backup approver.
1. Assign each person one employee ID and use it in scheduling, time capture, and payroll.
2. Choose one time-capture method per location, and tag each shift with a location and job code so punches carry both. If a point-of-sale system also records clock-ins or labor hours, name which system is the source of truth for hours and confirm with each vendor how the systems connect.
3. Define the exception types (missed punch, early or late punch, shift longer than scheduled, unapproved overtime, and meal period worked through) and apply one rule, flag then pay. DOL Fact Sheet #53 Example 13 says nurses who stayed late to chart, with the director’s knowledge, must be paid time-and-one-half for all overtime hours worked even though policy required prior authorization. Discipline is a separate matter.
4. Set rounding once for all locations. 29 CFR 785.48 accepts rounding provided it does not result, over a period of time, in failure to compensate employees for all the time they have actually worked, and DOL Fact Sheet #53 says rounding down every time may violate minimum wage and overtime rules.
5. Record when employees work through a scheduled unpaid meal. Per DOL Fact Sheet #53, an employer that automatically deducts 30 minutes per shift must ensure employees receive the full meal break.
6. Require each location’s manager to approve only that site’s hours before they go to payroll. As a recommended practice, tie the approval deadline to payroll cut-off and name a backup approver.
What a correct result looks like
Every shift carries a location and job code, every exception type has a written flag-then-pay rule, and each location’s hours reach payroll only after that site’s manager approves them.
Asure Time & Attendance is for employers with hourly workforces, especially those with multiple locations. It offers multiple time capture methods, overtime alerts, exception flagging, and manager approval before payroll. Paired with AsureCentral, approved hours flow into payroll with one login and shared data.
How to pass approved hours to payroll with overtime figured on the fixed workweek
Passing approved hours to payroll is a configuration task for a payroll manager, and its main setting is the fixed workweek on which overtime is figured. Under 29 USC 207, federal overtime for covered non-exempt employees is 1.5 times the regular rate for hours over 40 in the workweek, and DOL says the Act does not limit hours in a day.
What you need first
* Confirm the day and hour each location’s workweek starts.
* Export the pay codes from scheduling and the earning types from payroll.
* List each location’s state and any local overtime rule.
1. Set the same fixed workweek in scheduling, time capture, and payroll. Per 29 CFR 778.105, a workweek is a fixed, recurring 168 hours (seven 24-hour periods), need not match the calendar week, and stays fixed unless changed permanently and not to evade overtime.
2. Total each employee’s hours across every location and job. 29 CFR 778.103 says an employer totals all hours worked in the workweek, even across two or more unrelated job assignments, and 29 CFR 778.104 says each workweek stands alone, with no averaging.
3. Figure overtime on the regular rate. Per 29 CFR 778.108, the regular rate includes all remuneration for employment except statutory exclusions, and with two or more non-overtime rates in one workweek it is the weighted average, meaning total earnings divided by total hours at all jobs (29 CFR 778.115). Night-shift differentials and premiums for hazardous or dirty work belong in the regular rate (29 CFR 778.207).
4. Map each pay code (regular, overtime, holiday, differential) to a payroll earning type using each system’s own code or ID, so a renamed label does not misroute hours.
5. Set daily overtime thresholds by each location’s state and confirm each with the state labor agency. As of October 2026, California generally requires 1.5 times the regular rate over eight hours in a workday and for the first eight hours on the seventh consecutive day, with double time over 12 hours in a workday and over eight hours on the seventh day. Colorado’s 2026 COMPS Order poster lists overtime at 1.5 times the regular rate after 40 hours in a week, 12 hours in a day, or 12 consecutive hours. Under 29 USC 207(j), hospital and residential care employers may use a 14-day period by prior agreement, with overtime over eight hours in a day and 80 in 14 days.
6. Release only manager-approved hours to payroll, and have each manager resolve flagged records before cut-off, approving every hour actually worked.
What a correct result looks like
Payroll receives each employee’s approved hours totaled across every location on one fixed workweek, with each pay code mapped and each site’s state overtime rules set.
How to handle schedule-change rules where they apply
Handling schedule-change rules is a task for HR or payroll, and it applies where a city or state predictive scheduling law covers the employer, as in New York City, Oregon, and Chicago. As of October 2026, this procedure sorts those rules into three categories (advance notice, pay for changes, and rest between shifts).
What you need first
* Find the current schedule-publish deadline at each location.
* Identify who can change a published schedule.
* Open the payroll pay-code list.
1. List each location’s city, state, industry, and the employer’s global headcount, then check each against the agency pages linked below, because coverage depends on industry, employer size, and, in Chicago, an earnings cap.
2. Set the schedule-publish deadline to meet each notice window. New York City requires 14 days for covered fast food employers (NYC fast food rules) and 72 hours for covered retail employers (NYC retail rules). Oregon requires 14 calendar days for retail, hospitality, and food services employers with 500 or more employees worldwide (Oregon BOLI). Chicago requires 14 days across seven industries (building services, healthcare, hotels, manufacturing, restaurants, retail, and warehouse services) at employers with 100 or more employees globally, or 250 employees and 30 locations for restaurants, for employees earning up to $33.85 per hour or $64,945.55 per year (Chicago BACP).
3. Create separate pay codes for schedule-change premiums and predictability pay so payroll can carry them. Chicago requires one hour of predictability pay when a schedule changes within 14 days, and New York City fast food employers owe premiums for schedule changes.
4. Check rest between consecutive shifts. New York City fast food employers need written consent plus a premium to schedule fewer than 11 hours between shifts, and Chicago gives covered employees the right to decline work that starts less than 10 hours after the previous day’s shift ends.
5. Record who changed a schedule, when, and why, and route any premium through manager approval into payroll.
What a correct result looks like
Each covered location publishes schedules inside its notice window, premiums post to their own pay codes after manager approval, and a record shows who changed each schedule, when, and why.
For any other state or city rule, check with the state labor agency or employment counsel.
How to reconcile each pay period and keep the records
Reconciling each pay period is a recommended control for a payroll manager or controller, and it checks what time capture approved against what payroll received before payroll is final. Under Anderson v. Mt. Clemens Pottery Co., the employer has the duty to keep proper records, and when they are inaccurate or inadequate, an employee who shows work performed as a matter of just and reasonable inference shifts the burden to the employer.
What you need first
* Confirm that time capture and payroll use the same employee IDs and workweek.
* Set a written variance tolerance, for example no difference in hours for any employee.
* Name an escalation contact for payroll errors and sending failures.
1. Pull approved hours by employee and location from time capture and the hours payroll received, then compare totals by employee and by location so a shortfall at one site is not hidden by an overage at another. Flag each difference.
2. Check that overtime, differential, and schedule-change premium hours carry the right classification and that workweek boundaries match.
3. Trace each difference to its cause, such as an approval not completed, send timing, a pay-code mapping, or an employee ID mismatch, and fix it before payroll is final.
4. Log the period, hours compared, differences, causes, and resolutions, then obtain manager or controller sign-off and release payroll.
5. Keep the records for the full retention periods. 29 CFR 516.5 requires payroll records for at least 3 years, and 29 CFR 516.6 requires basic time and earning records, including daily starting and stopping times, for at least 2 years. Under 29 CFR 516.7, records kept at a central office must be available within 72 hours of notice. The IRS says to keep employment tax records for at least 4 years (IRS Publication 15), and California Labor Code 1174 requires payroll records of hours worked daily for not less than three years. Keep the old system’s records after you change systems.
What a correct result looks like
A signed log for the period lists the hours compared and every difference with its cause and resolution, and the records behind it are stored for the periods above.
Frequently asked questions
Does federal law require a time clock?
The Department of Labor says time clocks are not required (29 CFR 785.48). DOL Fact Sheet #21 adds that employers may use any timekeeping method they choose, as long as the plan is complete and accurate. Name the method and the system that holds the record in your written scheduled-versus-worked rule.
Does the schedule have to include meal and rest breaks?
Federal law does not require lunch or coffee breaks, except reasonable break time to express breast milk, per the DOL breaks page. As of October 2026, DOL’s state table, last revised January 1, 2023, lists 21 jurisdictions with adult private-sector meal period rules, seven of which also require rest periods (California, Colorado, Kentucky, Minnesota, Nevada, Oregon, and Washington), so confirm with the state. California, for example, requires a meal period of at least 30 minutes when work exceeds five hours (waivable by mutual consent when the workday is six hours or less), per the California DLSE.
Is travel between locations paid time?
Travel from one job site to another during the workday is hours worked, per 29 CFR 785.38. Employees who work at more than one location should record departure and arrival times so the travel is tagged to the right location and counted in the workweek total.
What happens if overtime is underpaid?
Under 29 USC 216, an employer that violates the overtime requirement owes the unpaid overtime plus an equal amount as liquidated damages and a reasonable attorney’s fee. Claims may be filed within two years, or three years if the violation was willful (29 USC 255). A court may reduce liquidated damages if the employer shows good faith and reasonable grounds (29 USC 260).
What should you ask a vendor before connecting scheduling, time tracking, payroll, and POS data?
Ask each vendor to confirm in writing which payroll system it connects to and which hours and pay codes pass, whether only approved hours pass, who owns the employee ID list, and which system is the source of truth for hours. For POS or ERP data, ask whether it offers a native connector, an API, or neither, and whether it passes tip data to payroll.
Talk to an expert at Asure
Talk to an expert at Asure about how Asure Time & Attendance and AsureCentral carry approved hours into payroll. AsureWorks is a managed service and PEO alternative with no co-employment. It runs on AsureCentral with Asure specialists doing the work, and you remain the employer of record. See payroll and HR solutions from Asure.
