Somewhere between the roster and the payroll export, fire departments lose money. Not because anyone made a careless mistake, but because the systems handling that handoff were never built for how fire departments actually operate.
Fire department payroll touches more moving parts than almost any other industry. Shift cycles, FLSA work periods, union rules, acting pay, specialty differentials, shift trades, Kelly days. Every one of them has its own codes, its own logic, and its own way of creating errors when the system can't keep up.
The Fair Labor Standards Act gives fire departments access to a special provision under Section 207(k), sometimes called the 7(k) exemption. Instead of calculating overtime based on a standard 40-hour week, departments can establish a work period of anywhere from 7 to 28 days and pay overtime only above the hours threshold for that period. The U.S. Department of Labor’s Fact Sheet #8 provides the federal breakdown of these specific thresholds. On a 27-day FLSA work period, overtime kicks in at 204 hours. On a 14-day period, the threshold is 106 hours. FirefighterOvertime.org has the most thorough public breakdown of how those thresholds work across common work period lengths.
That flexibility exists because the fire service runs on 24-hour shifts, and applying standard overtime math to a firefighter schedule would make virtually every shift an overtime event. The 7(k) exemption is the right tool for the job, but it creates a payroll calculation that operates on completely different logic than whatever system most HR or finance departments are already using.
The complexity builds up from there. A single department may have firefighters on a 24/48 with Kelly days, engineers on a standard rotation, battalion chiefs on a modified schedule, and administrative staff on a 40-hour week. Each group may have a different FLSA work period, different pay rates, different union rules, and different accrual banks. Pay codes that apply to one group do not apply to another. Specialty pay for a certified paramedic is calculated separately from base pay. Acting pay for a firefighter covering a captain's position needs to kick in automatically and stop when the captain returns.
None of that is out of the ordinary. That is a standard day in fire department payroll, and most software handling it was built for a different problem.
When payroll errors happen in fire departments, they tend to cluster around the same failure points.
Acting pay and specialty pay that don't trigger automatically. When a firefighter steps up to cover a vacated captain position, they are owed acting pay for the duration of that assignment. If that assignment lives in a roster system that doesn't talk to the timekeeping system, someone has to manually identify the assignment, determine the correct pay code, and enter it before the payroll export runs. In departments with dozens of daily roster changes, that manual step gets missed. The firefighter gets paid their base rate instead of their acting rate, and catching it requires an audit most payroll admins don't have time to run.
Shift trades that create mismatched time cards. Firefighter A and Firefighter B trade shifts. If the staffing system and the payroll system aren't directly connected, both firefighters may appear to have worked correctly on paper, while their time cards reflect the wrong person working the wrong hours. Depending on pay rate differences, specialty certifications involved, or whether a holiday fell in the swap, the error can ripple through the pay period in ways that take hours to untangle.
FLSA period calculations that don't align with payroll cycles. Texas fire departments, for example, are commonly paid on a 14-day cycle but run FLSA work periods of 21 to 28 days. The FLSA period and the payroll export period don't share a boundary, which means overtime calculations can't be run on a simple export. Someone has to reconcile two different timelines and make sure overtime hours are attributed correctly. When that math is done manually or by a system not designed for it, errors follow.
Pay codes were assigned incorrectly at callout. When a firefighter is hired from the overtime list to fill a vacancy, the roster updates, the staffing list adjusts, and the correct pay code needs to be attached to the hire simultaneously. Whether the hire came from the voluntary or mandatory overtime list often determines the pay code. Whether it was a callback or a holdover carries different coding implications. When those assignments are entered manually, or after the fact, the pay code is often wrong enough to matter.
Conflicting rules that break down over time. This is the failure mode that tends to accelerate in departments running legacy software for years. Every time a new MOU gets negotiated or a department adds an exception for a specific unit, someone adds another rule to the system. Over time, the rules stack up and begin to contradict each other. Pay codes that used to apply correctly stop working. Pflugerville Fire Department ran into exactly this before switching to Stationwise. Years of layered rules in their previous system had reached a point where reliable automation was no longer possible, leaving admins to manually verify and correct time cards every pay period.
The error sources above mostly live on the admin side. But firefighters themselves add another layer.
Firefighters operate in one of the highest-fatigue work environments of any profession. According to research highlighted by the International Association of Fire Chiefs (IAFC), sleep deprivation in the fire service significantly impacts cognitive performance and decision-making. When a software prompt asks them to confirm an overtime assignment or submit a time-off request at 2 am between calls, they take the shortest path available.
It's human behavior under operational conditions, and software that doesn't account for it will produce errors at scale. Building guardrails into the system does what "reminding them to be careful" can't. A time-off request should only be possible on days the firefighter is actually scheduled. Pay code selection should be determined by the staffing action, not left to the person submitting it.
The most visible consequence is back pay. When a firefighter is underpaid, the department owes them the difference, often with interest depending on the union agreement and how long the error went uncorrected. In a department running callouts every shift, underpayments can stack across dozens of employees before anyone catches them. Correcting the records means reopening time cards, adjusting pay codes, and reprocessing payroll retroactively.
Overpayments are a different problem. Recovering overpaid wages from employees is legally complicated and, depending on the union contract, departments may not be able to recoup overpayments beyond a certain window. Some just absorb the cost.
Union grievances are the highest-stakes outcome. When pay errors are systematic or appear to favor certain employees, unions file. Grievance processes pull department leadership, HR, and legal counsel into a process that can run for months, even when the error was genuinely unintentional.
And then there's the cost that doesn't appear in any grievance filing: payroll admin burnout. Eagle Fire Department's payroll admins were spending dozens of hours every pay period keeping everyone accurately paid before they moved to Stationwise. And even after that manual processing, human errors crept in often enough that the data coming out of payroll reports was hard to fully trust. Time is not just a rounding error. It reflects the expertise of those managing department finances. Overloading them with manual corrections creates both retention issues and operational inefficiencies.
The instinct in most departments is to solve payroll errors by adding more manual review. Assign a second person to check the first person's work, build a spreadsheet checklist, and run an audit after every export. Those measures catch some errors but don't prevent them, and they scale poorly as the department grows or schedules get more complex.
The fixes that actually work are structural, and they address the problem before the export runs.
Pay codes need to be assigned automatically based on the staffing action, not as a separate downstream step. When an admin moves a firefighter from the voluntary overtime list onto the roster, the correct pay code should attach instantly. When acting pay triggers, it should calculate from the moment the assignment happens and stop when it ends, without anyone manually entering start and stop times. Removing the manual steps removes the opportunity for error at the moment it's most likely to occur.
The timekeeping system and the staffing system need to share a live connection. Integrated time cards that reflect roster changes in real time eliminate the reconciliation step that creates most downstream errors. Most fire departments are running staffing on one platform, timekeeping on another, and exporting to payroll from a third, with manual hand-offs between each one. That's where the gaps open.
FLSA calculations need to account for the specific work period the department is actually running. Stationwise lets departments configure their FLSA period independently from their payroll export cycle, so the overtime math reflects the actual rule. At McKinney Fire Department, this meant working directly with their payroll provider to finalize FLSA calculations and eliminate hours of administrative overhead that had been building up under their previous system.
An audit trail that logs each roster change, who made it, and when helps keep everyone accountable. The DOL's FLSA record-keeping requirements for fire departments are specific about what needs to be documented and for how long. When a time card discrepancy shows up, payroll admins need to trace exactly what happened, not reconstruct events from memory or emails.
Fire department payroll errors persist because they are treated as operational mistakes rather than design problems. The question departments usually ask after a run of bad pay periods is who made the error. The more productive question is which step in the process requires a human to do something that a system should be doing automatically.
Every manual entry point is a place where an error can happen. Every disconnected system is a gap where information gets lost. Every rule that lives in someone's head rather than in the software walks out the door when that person retires or transfers.
Departments that get payroll right rely on well-connected staffing and timekeeping systems. These systems ensure that the correct pay outcome is easy to achieve. Instead of depending on manual checks, the process is streamlined and efficient.
That's what Stationwise is built to do. The right pay code attaches to the right action automatically, the time card reflects the roster in real time, and the payroll export goes out with confidence that the data is accurate. You can see how it works across the full feature set or book a demo to walk through your department's specific configuration.
