A payroll dispute is easiest to mishandle when everyone starts with a conclusion. The worker says, “I am owed overtime.” Payroll says, “The system calculated correctly.” Sales says, “The commission has not vested yet.” Legal says, “Which state are we talking about?” All four statements can be partly true while the file is still missing the facts needed to decide the issue.

For a U.S. federal wage question, the Fair Labor Standards Act is often the first checkpoint, not the complete answer. Covered nonexempt employees generally must receive overtime after 40 hours in a fixed workweek, and overtime is based on the regular rate rather than automatically on the stated hourly rate. State and local rules, contracts, collective bargaining agreements and commission statutes can change the result. The checklist below is designed to organize the file before anyone escalates it.

Step 1: identify the legal employer and the place where the work was performed

Start with names and geography, not pay math. Write down the entity shown on the wage statement, the entity that directed the work, the worker’s actual work locations, and whether the person worked remotely across state or national borders.

This matters because wage rules are highly jurisdiction-sensitive. A remote employee living in one state while reporting to a manager in another may trigger different questions than a worker who occasionally travels. Do not assume the company’s headquarters decides every rule.

Step 2: lock the workweek before calculating overtime

Federal overtime generally runs on a fixed, recurring 168-hour workweek. A two-week payroll cycle is not permission to average a 46-hour week with a 34-hour week.

Ask payroll to identify the official workweek start and end. Then rebuild the disputed weeks one at a time. If the workweek itself changed during the period, document when and why. A moving workweek used to suppress overtime is very different from a longstanding administrative schedule.

Step 3: determine whether the worker is covered and nonexempt

Do not stop at “salary,” “manager,” “professional,” or another label. If an exemption is being asserted, identify the exact exemption and the facts supporting each element.

This is where many files become more complex. Some exemptions turn on duties and compensation tests; other special rules apply to certain occupations or industries. The correct question is not “Are salaried people exempt?” but “Which legal exemption is claimed, and does this person actually satisfy it for the period in dispute?”

Step 4: reconstruct hours from more than the timesheet

A time record is evidence, not always the whole story. Compare schedules, badge records, system logins, call records, ticketing activity, chat timestamps, travel assignments and manager instructions.

Under federal rules, work that an employer suffers or permits may be compensable even when a policy says overtime requires advance approval. That does not make every message sent after dinner payable time. It means the investigation should separate genuine work from incidental activity and ask whether the employer knew or should have known it was occurring.

Step 5: build the regular-rate worksheet

Create a one-week table with every payment component: base wages, shift differentials, production incentives, nondiscretionary bonuses, commissions, premiums and reimbursements.

The FLSA regular rate generally includes remuneration for employment unless a statutory exclusion applies. That is why “hourly rate × 1.5” can be wrong when a worker also earns incentive pay. For each component, write either “included,” “excluded,” or “needs legal confirmation,” and cite the rule or source used.

Step 6: isolate commission rules from overtime rules

Commission disputes often hide two separate problems. First, when did the worker earn the commission under the plan? Second, how does that commission affect overtime or wage payment obligations?

Preserve the exact plan version in force during the sale. Capture definitions for booking, shipment, customer payment, cancellation, clawback, territory changes, termination and split credit. A current CRM screenshot is not a substitute for the plan that governed the disputed month.

Step 7: check whether a commission exemption is actually being used

Some commissioned employees of retail or service establishments may qualify for the federal Section 7(i) overtime exemption, but only if the statutory conditions are met. The employer needs reliable hours and earnings records to support that analysis.

If the business cannot identify the exemption, the representative period, or the data supporting the test, do not let “commission-based role” become shorthand for “no overtime.” Treat the exemption as an evidence question.

Step 8: separate timing errors from amount errors

A correct amount paid late and an incorrect amount paid on time are different problems. Build a small chronology: date work occurred, date commission was earned, date payroll closed, date payment was due under the governing rule, and date payment actually occurred.

This also helps identify whether the disagreement is caused by a late customer payment, a disputed sale, a payroll cutoff, a clawback, or a legal wage-payment deadline.

Step 9: quantify the dispute in three columns

Before a demand is made, calculate:

  • the amount everyone agrees was earned;
  • the amount genuinely disputed;
  • any additional amount that depends on a legal classification or penalty question.

This prevents a file from becoming emotionally larger than the underlying accounting dispute. It also makes negotiation easier because the employer can pay the undisputed portion without pretending the rest has been resolved.

Step 10: preserve the communication record and watch for retaliation issues

Keep emails, payroll tickets, internal complaints and responses. If a worker raises wage concerns, managers should avoid careless comments about loyalty, attitude or future scheduling.

Federal law protects employees from retaliation for asserting certain wage rights, and state rules can be broader. Even when the underlying wage calculation is debatable, a retaliatory response can create a separate problem.

Step 11: choose the escalation path only after the evidence file is complete

Options may include an internal payroll correction, a written demand, a Wage and Hour Division complaint, a state labor-agency process, contractual grievance or arbitration, or a private legal claim.

The right path depends on the amount, limitation period, need for speed, evidence quality, relationship, retaliation risk, collective agreement and local procedure. A federal agency complaint is not a universal substitute for private counsel, and private litigation is not automatically the best first move for a small, well-documented payroll error.

Step 12: write the unresolved questions on one page

A strong file ends the checklist with what is still unknown. Examples:

  • Which state’s commission-payment rule applies?
  • Does a claimed exemption cover these actual duties?
  • Is a bonus discretionary for regular-rate purposes?
  • Are travel hours compensable?
  • Did the worker perform off-the-clock work with management knowledge?
  • Did a commission become earned before termination?

This one-page “unknowns” list is often more useful than another ten-page memo because it tells the next reviewer exactly what could change the answer.

A practical handoff packet

Before the issue leaves payroll or HR, the handoff should contain the worker profile, governing locations, workweek definition, disputed-period time records, pay records, commission plan, incentive rules, relevant communications, the regular-rate worksheet, and a chronology of payments.

Do not send a folder of 300 screenshots without an index. Name the records, date them, and state which question each document answers. A clean evidence packet reduces legal cost and makes an agency, lawyer or internal reviewer far less likely to repeat basic fact-gathering.

The boundary that should stay in the file

This checklist is a triage framework, not a legal conclusion. Federal FLSA rules are only one layer, and state, local, contractual and cross-border rules can be more protective or simply different. Before changing a classification, withholding a commission, signing a release, or calculating penalties, confirm the applicable law with a qualified local professional.

The best wage dispute is not the one with the most aggressive opening letter. It is the one where the workweek, hours, pay components, commission terms and jurisdiction are clear enough that the parties can see exactly what remains disputed.

Turn the checklist into a reproducible calculation file

A good checklist ends in a file another person can reproduce without asking what the author meant. Put each disputed workweek on its own row. Record the scheduled hours, recorded hours, reconstructed additional hours, straight-time earnings, nondiscretionary incentives, commissions allocated to the period, the regular-rate inputs used, overtime hours, and the arithmetic that produces the claimed or corrected amount. If a number is disputed, mark the cell as disputed instead of silently choosing a side. A payroll team can then correct an obvious coding error without adopting a legal conclusion, while counsel or an investigator can see exactly where the disagreement begins.

The same discipline helps with commission disputes. Create a separate sale-level table showing the transaction, credited salesperson, date of sale, contractual earning event, cancellation or return rule, amount credited, amount paid, and any later adjustment. Do not force sales data into the overtime worksheet until the applicable compensation rule is understood. The two tables answer different questions and should be joined only through an explicit calculation note.

Keep a short assumptions register beside the worksheets. Typical entries include “meal period treated as unpaid because no contrary evidence has been found,” “bonus assumed nondiscretionary for this preliminary calculation,” or “commission allocation remains unresolved pending plan version dated March 1.” An assumptions register prevents a preliminary estimate from hardening into a supposed fact.

Test the file from both sides before escalating

Before sending a demand, denial, or correction notice, ask one person who did not build the file to reproduce the result. Give that reviewer the source records and calculation rules, but not the answer. If the reviewer cannot reach the same figure, the case is not ready for an aggressive position. The problem may be a missing workweek definition, a duplicated earning code, a commission reversal, or a mistaken assumption about which payment belongs in the regular rate.

Then run a “best case / supported case / open issue” review. The best case is the strongest plausible position for the reviewing side. The supported case uses only facts that can presently be tied to records. Open issues are matters that could materially change the result. This is more useful than a single headline number because wage disputes often change as time records, compensation plans, or manager communications are recovered.

Finally, separate business choices from legal conclusions. A company may decide to correct payroll quickly even while a classification question remains under review. A worker may choose an agency complaint instead of extended negotiation even when the dollar calculation is still approximate. Those are strategy decisions; the checklist should make the factual foundation clearer, not pretend to choose the legally correct path for every jurisdiction.

What a reviewer should be able to answer in five minutes

A finished file should let a new reviewer answer five questions quickly: Which workweeks are disputed? What evidence supports the hours? Which earnings were included in the regular-rate analysis? Which commission rule applies? What factual or legal question is still unresolved? If any answer requires searching through hundreds of pages without an index, the file needs one more organization pass. The goal is not to make the dispute simple; it is to make the remaining complexity visible and traceable.

Sources

Related Reading