A familiar wage dispute starts on a Monday morning. A salesperson says the last payroll is short. The manager checks the total annual compensation and replies that the employee is “well paid.” Payroll points to a salary code. The employee sends screenshots from late-night messages. By Friday, the disagreement is no longer about one paycheck; it is about classification, overtime, commissions, recordkeeping and trust.

Most expensive wage disputes are not created by one dramatic mistake. They grow because a series of small shortcuts makes the facts harder to reconstruct. The sequence below shows where files usually go off track and what a better next move looks like.

Mistake 1: using annual salary as proof that overtime cannot be owed

What goes wrong: a manager assumes high compensation or salary automatically means exempt.

Better move: identify the exact exemption and test its current requirements against actual duties and pay. Salary is a payment method, not a universal legal classification.

If no one can name the exemption being relied on, pause before making a categorical statement to the worker.

Mistake 2: averaging busy and quiet weeks

What goes wrong: payroll says, “The employee averaged 40 hours over the two-week pay period.”

Better move: rebuild each fixed workweek separately. Federal FLSA overtime generally turns on hours over 40 in an individual workweek for covered nonexempt employees.

This correction is simple but often changes the amount materially.

Mistake 3: treating the timesheet as conclusive when managers knew more

What goes wrong: the official timecard shows 40 hours, so the company assumes there can be no off-the-clock issue.

Better move: compare time records with schedules, system activity, customer calls, messages and manager instructions. The real question is what work occurred and what the employer knew or should have known.

A “no unauthorized overtime” rule helps manage conduct but does not automatically erase compensable work already performed.

Mistake 4: calculating overtime from the base hourly rate only

What goes wrong: payroll multiplies the hourly rate by 1.5 while ignoring a nondiscretionary bonus or other remuneration that belongs in the regular rate.

Better move: list every earning code for a representative week and determine which components are included or excluded under the governing rules.

The number printed beside “hourly rate” is not always the legal regular rate.

Mistake 5: assuming commission pay means no overtime

What goes wrong: sales staff are told that commissioned employees are automatically exempt.

Better move: separate the commission plan from the exemption analysis. Federal Section 7(i), for example, has specific conditions for certain employees of retail or service establishments. If those conditions are not established, the role should not be treated as exempt merely because a commission exists.

Mistake 6: changing the commission rule after the sale

What goes wrong: a current plan or dashboard is used to decide a dispute about an older transaction.

Better move: retrieve the plan version that applied when the underlying sales events occurred. Then map the facts—booking, shipment, customer payment, cancellation, returns, territory and termination—to that version.

Version control is often the difference between a real analysis and a retroactive explanation.

Mistake 7: mixing “earned,” “payable” and “paid”

What goes wrong: everyone uses the word “due” but means something different.

Better move: put three dates on the timeline: when the compensation became earned under the plan and law, when it was required to be paid, and when money actually reached the employee.

That distinction quickly exposes whether the dispute is about entitlement, timing or payroll execution.

Mistake 8: responding to a wage complaint as a performance problem

What goes wrong: a manager reacts defensively, cuts desirable shifts, excludes the worker from opportunities, or sends messages implying the complaint shows disloyalty.

Better move: route the wage issue through a neutral investigation, document legitimate performance actions separately, and train managers on retaliation risk.

A debatable overtime claim should not be allowed to turn into a clearer retaliation file.

Mistake 9: sending a demand or denial before the arithmetic can be reproduced

What goes wrong: one side writes an aggressive letter using a lump-sum number that no independent reviewer can reconstruct.

Better move: attach or maintain a week-by-week schedule showing hours, pay components, disputed assumptions and the calculation method. If commissions are involved, tie each line to the plan and sales record.

A number without a model is difficult to negotiate and difficult to defend.

The better timeline

A more disciplined wage dispute often looks like this:

Day 1–2: preserve records, define the workweek and identify the governing locations.

Day 3–5: rebuild representative weeks, identify claimed exemptions, review commission plan versions and separate undisputed from disputed amounts.

Week 2: resolve factual gaps, obtain local legal input where needed, and decide whether internal correction, negotiation, agency review or a formal claim is appropriate.

The timing can be faster or slower, but the order matters. Escalation before fact reconstruction usually creates more letters, not more clarity.

A manager’s five-question test before replying

Before telling a worker “payroll is correct,” ask:

  1. Which workweek did we analyze?
  2. Which exemption, if any, are we relying on?
  3. What did we include in the regular rate?
  4. Which commission plan version applies?
  5. Can another reviewer reproduce the result from the records?

If any answer is “we assume,” the file is not ready for a final response.

When the dispute is already bigger than payroll

Get specialized help when the issue involves multiple employees, systemic time-edit practices, a significant classification question, termination during a commission dispute, retaliation allegations, cross-border work, a looming limitation period, or an agency inquiry.

At that point the objective changes. You are no longer fixing one transaction; you are managing legal exposure, evidence preservation and consistent treatment across a group.

Legal boundary

This article uses U.S. federal wage concepts as a reference point. State and local law may impose daily overtime, different exemptions, commission-contract requirements, wage-statement rules, faster payment deadlines or additional penalties. Collective agreements and other countries can produce a different result.

This is general information, not legal advice. Confirm the governing jurisdiction and current law before changing pay practices, denying earned compensation, signing a release or calculating a claim.

The practical lesson is not “employees are usually right” or “payroll systems are usually wrong.” It is that wage disputes become expensive when assumptions are allowed to substitute for a reproducible factual record.

Run a “one-week proof” before scaling the dispute

When the disagreement covers months or years, people often start by multiplying an assumed weekly shortage across the entire period. That is fast but dangerous. Pick one representative workweek and prove it from beginning to end first. Identify the legally relevant workweek, recover the best available time evidence, map every earning code, test the regular-rate calculation, and trace the final amount into the payroll record. If commissions are involved, trace one sale from the plan language through crediting, payment, reversal, and any effect on overtime.

A one-week proof exposes the weak link early. If the team cannot explain one week, a 100-week spreadsheet merely scales the uncertainty. If the week can be reproduced, then sampling additional busy, ordinary, and unusual weeks can show whether the issue is systematic or isolated. The approach also reduces avoidable conflict because both sides can challenge the same small set of assumptions before anyone commits to a very large headline figure.

Do not treat sampling as a substitute for legal advice about proof or damages. Its role is operational: it helps find the data problem and prevents arithmetic from outrunning the evidence.

Distinguish correction from settlement

Another common mistake is assuming that every payroll correction needs a broad settlement agreement, or that every settlement can replace a lawful payroll correction. Those are different actions. A correction should identify the affected pay period, the earning code or hours being corrected, the calculation method, and the payment record. A settlement addresses disputed claims and may require additional legal analysis about enforceability, releases, agency rights, tax treatment, or required approvals.

Keeping the two tracks separate makes the record cleaner. If an employer discovers a simple missed earning and pays it, the correction file should say what was fixed rather than characterize the payment as consideration for every possible claim. If a broader dispute remains, the parties can negotiate that dispute on its own terms.

Use a closing checklist before calling the matter resolved

A wage dispute is not operationally closed merely because money changed hands. Confirm that the payment posted correctly; that the employee received a readable statement or explanation where required; that commission or payroll systems no longer reproduce the error; that managers know any changed timekeeping rule; and that preserved records remain accessible. If the matter involved a complaint, ensure no one has turned ordinary scheduling, discipline, or communication into a retaliatory response.

For recurring payroll issues, schedule a short follow-up audit after one or two pay cycles. The goal is not to relitigate the dispute. It is to verify that the correction survives real operations. A resolution that fails in the next payroll run is only a temporary patch.

Separate payroll defects from policy defects

A single underpayment may come from a data-entry error. Repeated errors across different managers or pay periods can point to a policy, system, or training problem. Classify the problem before choosing the remedy. Correcting one paycheck may close an isolated defect; a recurring defect may require configuration changes, manager instructions, revised commission documentation, or broader review. This distinction also prevents an investigation from expanding unnecessarily when the evidence supports only a one-off mistake.

Sources

Related Reading