The first US pay run is rarely wrong about the money. It is wrong about which rules applied.

There is no single US payroll law. Federal rules set a floor, each state adds its own requirements, and some cities add another layer. The rules can cover minimum wage, overtime, pay frequency, pay statements, leave, final pay and worker classification.

That means a company hiring its first employee in Texas and its second in California is not simply running two people through the same federal payroll rules. It is running payroll under different combinations of federal, state and sometimes local requirements.

The important point for a first US payroll is simple:

Know where the employee works, how they are classified, which rules apply, and when those rules took effect before you calculate the pay.

The federal floor

The Fair Labor Standards Act (FLSA) is the main federal layer for minimum wage, overtime and recordkeeping.

For most covered employees, the FLSA requires:

  • At least the federal minimum wage, although a higher state or local minimum may apply.
  • Overtime at one and a half times the regular rate for hours worked over 40 in a workweek, unless an exemption or other rule applies.
  • A defined workweek: a fixed, recurring period of 168 hours. An employer can choose when the workweek starts, but cannot move it around to avoid overtime.

The regular rate is where payroll calculations often become less straightforward.

It is not necessarily the employee's basic hourly rate. Certain non-discretionary bonuses, incentive payments, shift differentials and commissions can affect the regular rate used to calculate overtime. A bonus paid during a particular workweek can therefore change the overtime calculation for that week.

The practical lesson is that overtime is not simply:

hourly rate × 1.5 × overtime hours

The payroll system first needs to determine what belongs in the regular rate.

Exempt or non-exempt: the classification that can change the calculation

One of the most expensive payroll mistakes is assuming that salary means exempt.

It does not.

For many executive, administrative and professional exemptions under the FLSA, the employee generally has to satisfy a salary-basis test, a salary-level test and a duties test. The job title alone does not determine exempt status.

As of 2026, the DOL is applying the restored 2019 federal salary threshold of $684 per week, or $35,568 per year, for the standard executive, administrative and professional exemptions. The threshold was affected by litigation over the DOL's 2024 overtime rule, which was vacated in November 2024; the DOL subsequently restored the operative 2019 regulatory text in 2026.

But the number is only one part of the test.

The duties matter. An employee called a "manager" does not automatically qualify as exempt because of the title or because they receive a salary. The actual work they perform has to fit the relevant exemption.

And state law can impose additional or different requirements.

That is why exemption status should be checked before the first payroll run, rather than inferred from the employment contract or job title.

What the states add

This is where a federal-only payroll setup starts to break down.

States can add requirements around:

  • Minimum wage. A state or local minimum wage can be higher than the federal rate.
  • Pay frequency. States can specify how often employees must be paid and may apply different rules to different types of employees.
  • Pay statements. Federal law does not generally require a pay stub, but many states do. The required information and rules for electronic delivery can differ.
  • Final pay. The deadline for paying a departing employee is largely a matter of state law and can depend on whether the employee resigned or was dismissed.
  • Paid sick leave. Many states and local jurisdictions have their own accrual, usage and carry-over requirements.
  • Paid family or medical leave. Some states operate paid-leave programs with their own eligibility, contribution and payroll requirements.
  • Local requirements. Certain cities and counties add requirements on top of state and federal rules.

This is why "US payroll" is not really one payroll rule set.

It is a jurisdictional problem.

The employee's work location determines which additional rules you need to consider.

Employee or independent contractor?

The second expensive mistake is treating an employee as an independent contractor.

The IRS does not determine worker status simply from what the contract calls the person. For federal tax purposes, it looks at the relationship between the business and the worker, including behavioral control, financial control and the type of relationship between the parties.

The Department of Labor has its own framework for worker classification under the FLSA. As of 2026, the DOL has proposed a new federal analysis based on economic reality, with control and opportunity for profit or loss identified as core factors. That proposal is not the same thing as a universal classification test for every federal or state purpose.

States can apply their own tests as well, sometimes with stricter requirements.

So worker classification is not a box you tick because someone:

  • invoices you,
  • works remotely,
  • works part-time,
  • has an LLC, or
  • signs a contractor agreement.

The actual working relationship matters.

Misclassification can create exposure for unpaid wages and overtime, employment taxes and other obligations. The IRS specifically notes that a misclassified employee can result in liability for employment taxes that should have been withheld or paid.

What payroll records do you need to keep?

Payroll records are not just an administrative archive. They are evidence of how the payroll was calculated.

Under the FLSA, employers generally must retain payroll records for at least three years. Records used to calculate wages, including time cards, wage-rate tables, work schedules and records of additions to or deductions from wages, generally need to be kept for two years.

The records include information such as:

  • hours worked,
  • total hours in each workweek,
  • regular pay rate,
  • overtime earnings,
  • additions and deductions,
  • total wages paid,
  • payment dates, and
  • the pay period covered.

State requirements can be longer or more specific.

The important distinction is that a payroll system should preserve not just what was paid, but enough information to explain why that amount was paid.

If there is a wage dispute, that history can matter.

What your payroll system needs to handle

The common thread across these rules is not just complexity. It is change.

Payroll rules have two properties that matter enormously to software:

They vary by jurisdiction, and they change over time.

A minimum wage can change on a specific date. A leave entitlement can change. A salary threshold can be revised or, as the federal overtime rules demonstrate, changed through litigation and subsequent regulatory action. The payroll calculation therefore needs to know not only *which rule* applies, but *which version of that rule applied on the pay date or during the relevant period*.

That makes effective dating important.

Instead of hard-coding a rate or threshold, a payroll system should be able to store rules with an effective date and apply the correct configuration to the relevant payroll period.

That also matters for historical payroll.

If you need to reproduce a payroll calculation from last year, the system should not simply use today's configuration. It should be able to reconstruct the rules that applied when the original payroll was processed.

How Work Mint approaches this

This is the kind of problem that should be treated as normal payroll configuration, not as an exception.

In Work Mint, currencies, tax slabs, pension and gratuity settings are configured per organisation with effective dates. A payslip carries the currency and configuration used when it was generated rather than simply inheriting whatever the system's current default happens to be.

For organisations operating across jurisdictions, that distinction matters.

The goal is not to pretend that US payroll is governed by one neat rulebook. The goal is to make the changing rules explicit in the system so that payroll calculations can be traced back to the configuration that applied at the time.

Before your first US payroll run

A practical first-payroll checklist looks like this:

1. Confirm where the employee actually works. 2. Determine whether they are an employee or independent contractor. 3. Determine whether the employee is exempt or non-exempt where applicable. 4. Check the federal minimum wage and overtime rules. 5. Check the employee's state and local wage requirements. 6. Confirm the state's pay-frequency and pay-statement requirements. 7. Check state and local leave requirements. 8. Check the state's final-pay rules. 9. Set up the required federal, state and local payroll tax obligations. 10. Make sure time, wage and payroll records are retained. 11. Store rules and rates with effective dates so historical payroll can be reproduced.

The last point is easy to overlook.

Payroll is not just a calculation engine. It is a record of which rules were applied to which person at a particular point in time.

The first US payroll is a rules problem

The difficult part of running US payroll for the first time is rarely adding up gross pay.

It is identifying which rules apply to which employee, in which jurisdiction, during which period.

Federal law provides the baseline. States and local jurisdictions can add requirements. Worker classification determines which protections and tax obligations apply. Exemption status can determine whether overtime is owed. And the rules themselves can change.

Work Mint is not a US tax filing engine, and this article is not legal advice. Federal and state tax registration, filing and deposit obligations are separate from calculating payroll, and businesses may choose to handle them internally, through a payroll provider, payroll bureau or professional employer organisation.

The important thing to get right before the first US pay run is the structure:

employee → work location → classification → applicable rules → effective date → payroll calculation → records.

Once that structure is correct, the arithmetic is the easy part.