Payroll compliance review: checking each pay run against wage-and-hour rules

Payroll verification involves comparing pay runs line by line against applicable wage-and-hour regulations. Reviewers evaluate the hours and pay rates recorded for each specific pay code and state jurisdiction, flagging any discrepancies for further investigation. Labrynth outlines three main strategies on its payroll platform: standard calculation software, periodic internal audits, and external validation of payroll outputs.

Payroll compliance centers on paying workers their statutory compensation on time while maintaining verifiable employment records. Applicable legal frameworks combine federal statutes with state and municipal mandates. This domain focuses specifically on wage calculations, including minimum wage standards, overtime eligibility, exemption classifications, tracked hours, mandatory break periods, and final paychecks, while excluding payroll tax administration.

Labrynth develops automated payroll solutions alongside technical resources, making its technology one option examined in this review. Company details reflect information published on Labrynth's active payroll platform as of October 27, 2026, while statutory references draw directly from Department of Labor and eCFR documentation accessed on the same date.

The federal floor

Under the Fair Labor Standards Act (FLSA), federal standards cover minimum wage and overtime as well as recordkeeping and youth employment. The U.S. Department of Labor's FLSA page, read on October 27, 2026, gives the federal minimum wage as $7.25 per hour, effective July 24, 2009. It also says overtime at not less than one and one-half times the regular rate of pay is required after 40 hours of work in a workweek.

Per that page, a workweek is any fixed and regularly recurring period of 168 hours, seven consecutive 24-hour periods. Department of Labor Fact Sheet #23 (revised October 2019) adds that averaging hours over two or more weeks is not permitted, so a two-week pay period has to be split back into separate workweeks before overtime can be tested. Where an employee is covered by both state and federal minimum wage laws, the FLSA page says the employee is entitled to the higher one.

The regular rate decides the overtime math

Overtime is one and one-half times the regular rate, which can differ from the hourly wage on the offer letter. Fact Sheet #56A from the Department of Labor (December 2019) gives the formula for the regular rate: total compensation in the workweek, except statutory exclusions, divided by total hours worked in that workweek. An agreement between employer and employee cannot change the result, because the fact sheet says the figure rests on actual facts.

Under the same fact sheet, a bonus stays out of that figure only when both its payment and its amount are at the employer's sole discretion at or near the end of the period, and no earlier contract, agreement or promise leads employees to expect such payments regularly. A bonus promised in advance fails that test and is counted in. Calling a payment discretionary doesn't make it so; the fact sheet says the label and the reason do not settle the question.

Fact Sheet #23 covers mixed work. When an employee does two or more kinds of work at different straight-time pay in one workweek, the regular rate for that week is the weighted average of the pay for each. Using only one of them is wrong for that week, unless the section 7(g)(2) method described in the same fact sheet applies.

Exempt or non-exempt, and the salary threshold today

Minimum wage and overtime rules apply to non-exempt employees. Exemption depends on duties and on salary, and it covers executive and administrative roles and professional ones. Fact Sheet #17A from the Department of Labor (revised September 2019) says job titles do not determine exempt status; duties and salary must meet every requirement of the regulations in 29 CFR Part 541.

Executive exemption illustrates how specific the duties tests are. Per the fact sheet, the employee's primary duty must be managing the enterprise or a department, the employee must regularly direct two or more other full-time employees or their equivalent, and the employee must be able to hire or fire, or have hiring and firing recommendations given particular weight. If one test fails, the employee is not exempt and the overtime rules apply.

On salary, the U.S. Department of Labor's earnings thresholds page, opened on October 27, 2026, lists a standard salary level of $684 per week, equal to $35,568 a year. It lists $107,432 per year as total annual compensation for highly compensated employees, which must include at least $684 per week on a salary or fee basis, and $27.63 per hour for computer employees paid hourly. The page shows no effective date.

A Wage and Hour Division technical amendment dated May 15, 2026 (Federal Register document 2026-09839) explains the background: federal courts vacated the Department's 2024 rule that would have raised these levels, and the amendment restores the 2019 text. The amendment also notes that the 2019 salary level itself was not challenged. Because the levels have moved before, a review should read the Department's page on the day it runs, not a figure printed in an article, this one included.

Per the FLSA page, the Department's guidance on employee versus independent contractor classification, last addressed by a January 2024 rule, will be updated, so that question belongs with counsel.

Where state law is stricter

The Department of Labor's chart of state minimum wage laws, marked updated July 1, 2026, supplies the state figures below, except for meal periods and paydays, which have companion pages dated January 1, 2023.

California adds daily overtime. The chart quotes Labor Code section 510: work over eight hours in a workday, over 40 in a workweek, or in the first eight on a seventh consecutive workday is paid at one and one-half times the regular rate. Work over 12 hours in a day, or over eight on a seventh day, is paid at no less than twice the regular rate. A long day can therefore be overtime in California even when the week stays under 40, which the federal weekly test would not flag. The chart adds that exceptions apply to employees on an alternative workweek and for commuting time.

As of that July 2026 update, the Department of Labor chart lists a California basic minimum rate of $16.90 an hour. Alaska shows premium pay after a daily threshold of eight and a weekly one of 40, with a basic minimum of $14.00, and notes that the daily and weekly premium requirement does not apply to employers of fewer than 4 employees. Alabama has no minimum wage law of its own, so the federal $7.25 applies there.

On meal periods, the Department's meal period page says Colorado requires a half hour when a shift runs past five straight hours, for the industries its wage order covers. Illinois requires at least 20 minutes, starting no later than five hours in, for employees who work seven and one-half continuous hours or longer. The page counts 21 states or jurisdictions with meal period rules; seven of them also set rest periods (California, Colorado, Kentucky, Minnesota, Nevada, Oregon and Washington). Because that page is dated 2023, confirm any rule with the labor department of the state concerned before acting on it.

On final pay, the Department's Last Paycheck page says federal law does not require an employer to hand a former employee the final paycheck immediately, and that some states may require immediate payment. It gives no list. Pay frequency is a state matter too: the Department's State Payday Requirements page shows which frequencies each state allows. For a broader comparison across states, the Red Tape 50 ranking from the Red Tape Index, a series powered by the same company, ranks all 50 states on nine dimensions that include labor. It is a general ranking, not a table of wage rules.

Hours worked: what counts

Hours are the first input to every overtime test. Fact Sheet #22 from the Department of Labor (revised July 2008) says the workweek ordinarily includes all time during which an employee is necessarily required to be on the employer's premises or on duty at a prescribed workplace.

Fact Sheet #22 separates an employee engaged to wait, which is work time, from an employee waiting to be engaged, which is not. Attendance at meetings and training programs need not be counted only if four criteria are all met: it is outside normal hours, it is voluntary, it is not job related, and no other work is performed at the same time.

Short rest periods, usually 20 minutes or less, are customarily paid and must be counted as hours worked. Bona fide meal periods, which the fact sheet puts at typically 30 minutes or more, generally need not be paid, but the employee must be completely relieved from duty. An employee required to perform any duties while eating is not relieved. Where state law requires meal or rest periods, a check also needs the state's remedy for a missed break, and the Department's meal period page does not list remedies.

Rounding, punches and unpaid time

Under 29 CFR 785.11, work not requested but suffered or permitted is work time. Fact Sheet #22 gives the case of an employee who keeps working after a shift to finish a task or correct errors, and says the reason is immaterial.

Rounding sits in 29 CFR 785.48(b), in the eCFR version current as of October 23, 2026. Recording start and stop times to the nearest five minutes, or to a tenth or quarter of an hour, is accepted for enforcement only if it does not, over a period of time, leave employees short on the time they actually worked.

Because that wording looks at a pattern over time, one day's punches will not show it; a comparison of punches with paid time across many pay lines will.

Inputs of a pay-line check

Each check sets what was paid against what the rule requires for one person, in one week, in one state. The inputs follow the records the FLSA already requires.

• Hours worked per day and per workweek, taken from time records and not from scheduled hours.
• The regular rate, rebuilt from every pay code in that workweek that the rule counts.
• The rule itself, chosen by work location and employee classification.
• The state or locality where the work was done, which can differ from the employee's home address or the employer's registered state.
• The pay code on each line, because a code that excludes a payment from the rate has to be right before it can be trusted.
• Deductions and additions, which the recordkeeping rules require employers to track beside gross pay.

Department of Labor Fact Sheet #21 (revised July 2008) lists what the FLSA requires an employer to keep for each non-exempt worker. It includes the hours worked each day and each workweek. It includes the basis of pay and the regular hourly rate. Earnings are recorded as straight-time and as overtime, alongside additions to and deductions from wages and the date of payment. The fact sheet adds that the Act requires no particular form for these records, but that the information must be accurate.

How a finding should read

A flag that reads "possible overtime error" gives the reviewer nothing to act on. Labrynth's page says each finding shows the affected payroll input, the applicable requirement and the reasoning behind the flag, for expert validation. For wage-and-hour work, the Department of Labor sheets above indicate what that looks like: the hours behind the line, the regular rate and the pay codes that entered it, and the rule with its source and date, such as California Labor Code section 510 for a daily overtime question.

Review decisions and resolution history are kept as well, per the page, so a flag dismissed because a schedule exception was missing from the data keeps its reason.

Payroll software, audits and a review layer compared

All three rows restate how Labrynth's own payroll page describes them, and the third row describes Labrynth's own product. The page does not describe checks inside payroll systems. No payroll vendor's documentation and no audit firm's engagement terms were reviewed for this guide.

Where Labrynth fits

Labrynth's page describes a read-only review of payroll against wage-and-hour requirements, offered as payroll compliance software for wage-and-hour review and auditing. It flags potential issues at the employee and pay-line level and produces explainable findings. The existing payroll platform stays the system of record. Corrections happen inside the organization's own workflow, not in the review itself.

From connecting payroll data and defining the regulatory scope, through validators and exception review, the page leads to findings that are resolved in the existing payroll workflow. Calculable rules are checked by calculation, and requirements that depend on complex conditions or cross-references are handled by regulatory reasoning. Each finding shows the affected input together with the applicable requirement and the reasoning behind the flag.

Scope is set per deployment, and the page says coverage is not assumed for every rule or jurisdiction, and it describes the service as expert-guided, not only self-serve. Payroll tax work is outside it, from calculation to filing. Prevailing wage and certified payroll are not claimed as supported functions. The page also says the service does not replace external auditors or legal counsel, or the organization's own judgment. This guide is general information and not legal advice; it supports licensed professionals in the same way.

A payroll compliance checklist for the first review

Gather these items before anyone starts comparing pay lines, whether that person works inside the company or outside it.

• Every state and locality where employees work, and the headcount in each.
• The workweek definition used for each employee group, since overtime is tested per workweek.
• The classification list, with each employee's exempt or non-exempt status, the salary of each exempt employee and the duties basis for the exemption.
• Time records at punch level, not only the totals that reached payroll.
• The pay code table, marking which codes count toward the regular rate and why.
• Rounding and timekeeping policies, plus break policies for states that require meal or rest periods.
• Deduction and addition records for the period under review.
• Separation records with the date of final payment, for any state with a final pay rule.
• The person who decides each kind of finding, named in advance.

Labrynth's page invites teams to show their payroll environment and jurisdictions along with their current compliance process, and a team can ask for a demo on the payroll page with this list in hand.

Frequently asked questions

Can an employer decline to pay overtime that was not approved in advance?

No. Department of Labor Fact Sheet #23 (revised October 2019) says an announcement that no overtime will be permitted, or that it will not be paid unless authorized in advance, does not impair the employee's right to pay for overtime hours actually worked. The fact sheet adds that the overtime requirement cannot be waived by agreement, and that an agreement counting only 8 hours a day or 40 a week as working time also fails.

Is a fixed salary enough when the regular week runs past 40 hours?

Not by itself. Department of Labor Fact Sheet #23 (revised October 2019) says a fixed salary for a regular workweek longer than 40 hours does not discharge the FLSA obligations. Its example is a $405 weekly salary for a 45-hour week: the regular rate is $405 divided by 45, or $9.00, and the employee is due an extra half of that rate for each of the 5 overtime hours, $22.50 in total.

Are on-call time and travel time hours worked?

Sometimes. Fact Sheet #22 (revised July 2008) says an employee required to remain on call on the employer's premises is working, while one on call at home or reachable by message is not working in most cases. Ordinary home-to-work travel is not work time, but travel from job site to job site during the workday is. A special one-day assignment in another city counts as work time, less the normal commute.

Do the salary levels apply to every exempt employee?

No. The Department of Labor's earnings thresholds page says the levels do not apply to certain types of employees, including doctors and lawyers as well as teachers and outside sales employees. The page also lists separate levels for Puerto Rico, Guam, the U.S. Virgin Islands, the Northern Mariana Islands and American Samoa, so a workforce in those places needs the matching figure.

What payroll records must be kept, and for how long?

Fact Sheet #21 (revised July 2008) says payroll records must be preserved for at least three years, and the records on which wage computations are based, such as time cards and piece work tickets, for two years. They must be open to inspection by Wage and Hour Division representatives. The fact sheet covers the federal rule only, so a multi-state employer should check each state's retention rule.