US Payroll Compliance: The Errors That Show Up in Production

A company opens a remote office in Colorado. Employees start working there six months before anyone tells payroll. By the time the issue surfaces, the company has six months of payroll run under the wrong state income tax withholding, six months of employer contributions calculated against the wrong unemployment insurance rate, and a potential nexus exposure it didn't know it had.

This is not an unusual scenario. It is the most common category of payroll compliance failure RJR encounters during assessments: configuration that was accurate when it was set up but was never updated when the business changed.

Multi-state taxation and economic nexus

US payroll compliance begins with a question most companies don't ask clearly enough: in which states does this company have employees, and what tax obligations does each state create?

Remote work has made this significantly more complex. An employee who lives in New Jersey but works for a New York employer creates a reciprocal tax agreement situation that requires withholding in both states, or a resident credit calculation, depending on the employee's specific work location. An employee who travels regularly to client sites in multiple states may create nexus in states where the employer has no other presence.

RJR conducts nexus assessments as part of HCM implementations and as standalone engagements. The assessment maps every state where the client has employees or business activity against the client's current payroll configuration to identify gaps before they become audit exposure.

FLSA regular rate of pay

The most commonly misconfigured payroll rule in the HCM systems RJR works with is the FLSA regular rate of pay calculation for overtime. Most employers know that overtime is paid at 1.5x the regular rate. Fewer have configured their HCM system to calculate that rate correctly when employees receive non-discretionary bonuses, shift differentials, commissions, or other supplements.

The FLSA requires that these payments be included in the regular rate before overtime is calculated. An employee who earns a $500 non-discretionary production bonus in a week where they also worked ten hours of overtime is owed overtime calculated on an inflated regular rate, not on their base hourly rate alone. Most default HCM configurations do not handle this automatically. The system pays overtime at the base rate, the underpayment accumulates, and the liability surfaces during a Department of Labor audit.

RJR reviews overtime calculation configuration as a standard step in every payroll implementation. For clients with existing configurations, RJR offers a standalone overtime audit that traces the regular rate calculation logic through a representative set of pay periods.

Garnishment processing

Garnishment processing failures are high-visibility compliance problems because they affect employees directly and create simultaneous liability to the issuing court and the affected employee. Common failure modes RJR encounters:

• Garnishment priority sequencing not configured when multiple orders exist for the same employee
• Consumer Credit Protection Act (CCPA) disposable earnings calculation using gross earnings rather than net after mandatory deductions
• Child support income withholding order maximum percentages applied at the federal ceiling rather than the stricter state ceiling when applicable
• Garnishment continuation after the underlying debt is satisfied, because case closure wasn't entered into the system

UKG Pro, Ceridian Dayforce, and ADP Workforce Now all have garnishment modules that handle the calculation mechanics correctly when configured correctly. The configuration is the problem, not the platform.

Year-end W-2 configuration

Year-end W-2 configuration errors are discovered at the worst possible time: in January, when corrected W-2s create both employee relations problems and potential IRS examination risk. Common errors RJR identifies during pre-year-end reviews:

• Employer-paid group term life insurance over $50,000 not reported in Box 12 (Code C)
• Non-cash fringe benefits (personal use of company vehicle, awards) not included in taxable wages
• Section 125 cafeteria plan deductions included in Box 1 wages when they should be excluded
• State wages not reconciled to state quarterly returns before W-2 printing

RJR conducts year-end payroll readiness reviews, typically in October and November, that walk through each of these categories against the client's current configuration and generate a remediation checklist before the January deadline.

Payroll tax remittance and filing discipline

Payroll tax deposits follow deposit schedules that depend on lookback period liability (monthly depositors vs. semiweekly depositors) with different rules for new employers. Late deposits carry a penalty that scales with the number of days late, starting at 2% and reaching 15% for deposits more than ten days late. Failures to file quarterly 941s or state equivalents carry separate penalties.

RJR reviews deposit schedule classification, remittance timing, and reconciliation between payroll records and filed returns as part of compliance assessments. For clients who have identified a historical underpayment, RJR assists with voluntary disclosure analysis and correction mechanics.

Payroll compliance is not a one-time configuration activity. It requires ongoing attention to regulatory changes, workforce changes, and business changes. RJR offers ongoing compliance monitoring as part of managed payroll services engagements, tracking regulatory changes, flagging configuration drift, and conducting annual audits before they become IRS audits.