2.4 State, Local, and Multijurisdiction Payroll

Why jurisdiction changes payroll answers

The FPC blueprint includes compliance, legislative and regulatory requirements, reporting, record retention, penalties, global awareness, and wage-hour fundamentals. Those subjects become practical when an employee works in one state, lives in another, travels temporarily, or works remotely from a city with its own wage or tax rules. Federal law gives important baselines, but payroll often pays and reports under a more specific state or local rule.

Start with a jurisdiction map. Identify the employee’s work location, resident address, legal employer, pay frequency, unemployment insurance state, local tax area, and remote-work pattern. Then check official state labor and revenue sources, not only a payroll vendor table. DOL maintains state minimum wage and state labor-office references, but many payroll answers require the state agency that administers the exact rule.

State and local issue map

Higher wage and more protective rule

DOL’s federal minimum wage page states that covered nonexempt employees are entitled to the higher minimum wage when both state and federal laws apply. That “higher or more protective rule” concept is the safe payroll instinct, but apply it carefully. Some state rules are about minimum wage; others are about overtime, meal/rest periods, wage statements, deductions, final pay, paid leave, or local employer taxes. A state rule may also have coverage thresholds by employer size, industry, occupation, or city.

Example: A nonexempt employee works in a city with a local minimum wage above both the state and federal rates. Payroll should not set the employee at the federal rate just because the FLSA floor is $7.25. It should configure the city rate for hours worked in that location, test the effective date, and retain the official local source or agency page used for setup. If the employee later transfers to a different city, the rate and local tax setup may need review.

Remote and mobile employees

Remote work turns payroll setup into a facts exercise. If an employee lives and performs services in a different state from the employer’s office, payroll may need state income tax withholding, state unemployment registration, paid-leave contributions, local taxes, and wage-hour rules tied to the work location. Some states have reciprocity agreements or special sourcing rules; some localities impose taxes based on worksite or residence. The FPC does not require mastery of every state rule, but it expects candidates to know that one headquarters setup is not enough.

Mobile employees create timing issues. A salesperson who works two days in State A, two days in State B, and one day from home may create withholding and wage-hour questions in more than one jurisdiction. A payroll team should define thresholds, collect accurate work-location data, and escalate unusual travel patterns. “We did not know where the employee worked” is weak audit evidence if the employer had systems capable of capturing time, projects, or location.

Effective-date controls

DOL’s state minimum wage table is updated by date, and many state or local wage changes occur on January 1, July 1, or another statutory date. Payroll should maintain an effective-dated rate table and test it before the first impacted payroll. A strong control includes an owner, official source link, implementation date, parallel calculation, signoff, and post-payroll exception review. This is especially important when a semimonthly payroll crosses an effective date. Hours before and after the rate change may need different treatment under local rules.

Payroll example: employee moves midyear

An employee originally works in Ohio for a company headquartered in Texas, then permanently moves to Colorado and works remotely. Payroll should not leave the employee under the old state setup. The change may affect state withholding, unemployment reporting, paid-leave deductions or employer contributions, local taxes, minimum wage, overtime, wage statements, and required notices. The correct response is to collect the move date and work-location facts, verify official Colorado and local agency requirements, update payroll master data prospectively, and decide whether any retroactive correction is needed.

Compliance traps

• Headquarters trap: the employer’s office state is not always the payroll jurisdiction.
• Residence-only trap: work location and residence can both matter.
• Federal-only trap: federal wage-hour compliance does not eliminate stricter state or local duties.
• Effective-date trap: using the right rate one pay period late still creates underpayment.
• Unclaimed-pay trap: stale payroll checks may become state escheatment property, not miscellaneous income.

For exam purposes, choose the answer that gathers jurisdiction facts, checks official state and local sources, applies the higher or more protective applicable rule, and preserves evidence for reporting, audit, and employee inquiries.