Vertex User Guide: State Unemployment Tax (SUTA) Calculations in CMiC

Purpose

To provide CMiC payroll administrators, support teams, and implementation consultants with a complete understanding of how State Unemployment Tax (SUTA) is calculated in CMiC, how it integrates with Vertex PTX, and how to configure the system correctly for both single-state and multi-state employees.

1. Introduction

SUTA (State Unemployment Tax Act), also known as State Unemployment Insurance (SUI), is an employer-paid payroll tax used to fund unemployment benefits for workers who lose their jobs through no fault of their own.

CMiC’s payroll system integrates with Vertex Cloud (PTX) to automate SUTA calculation and ensure compliance with federal and state localization rules.

2. SUTA Calculation Overview

What is SUTA?

Employer-paid state-level unemployment tax.
Supports unemployment benefit programs.
Separate from FUTA (Federal Unemployment Tax) — both feed into the unemployment compensation system.

How It Works

Employers pay SUTA on employee wages up to a state-specific wage base limit.
Tax rate varies by state and is typically reassigned each year based on:
- Employer experience (claims history)
- Industry
- Tenure (new employer rates differ)

Basic Formula

SUTA Tax = Taxable Wages × SUTA Rate

Example:

State: California (2025)
Wage Base: $7,000
Rate: 3.4%

SUTA = $7,000 × 0.034 = $238 per employee

3. Integration with Vertex PTX

Data Flow

CMiC sends the following to Vertex PTX via the Payroll Tax API:

Data Element	Source in CMiC	Purpose
Primary Work Location	Derived from SUI/SDI override, Job, or Profile	Determines SUTA state.
Employee Wages	Payroll transactions	Used in tax calculation.
Employer SUTA Rate	Stored in CMiC or synced from Vertex	Multiplied against taxable wages.
YTD Wages per State	CMiC tracking	Prevents overpayment beyond wage caps.

Vertex Limitation

Vertex only supports one SUTA state per pay period per employee.
CMiC must determine which state to pass as the Primary Work Location before calling Vertex.

4. Work Location Hierarchy in CMiC

Priority	Source	Description
1	SUI/SDI Override (Tax Tab)	Manual override; always takes precedence.
2	Employee Profile > Company Tab	Default work location if no override.
3	Job Work Location (if enabled)	Used for job-based state tracking.
4 (Planned)	Timesheet “Most Worked State”	For employees with hours in multiple states.

5. Federal 4-Tier Localization Rules

When an employee works in multiple states, determine SUTA based on the Department of Labor’s Four-Tier Rule:

Localization of Services: All/most work done in one state → use that state.
Base of Operations: If multiple states, use the employee’s home base.
Direction & Control: If no base, use where supervision occurs.
Residence: If none apply, use the state where the employee resides.

NOTE: Only one SUTA state is valid at a time. Double taxation is not allowed.

6. CMiC Scenarios and Examples

Example 1: Remote Worker in Another State

Scenario:

Employer in Texas; employee lives and works remotely in Georgia.
All work was performed from home.

Rule Applied:

Localization of Services → Georgia
SUTA Applies: Georgia

CMiC Handling:

Profile Setup: Work Location = Georgia; leave SUI/SDI blank.
Override Option: Set SUI/SDI = Georgia for guaranteed control.
System Behavior: CMiC passes Georgia as Primary Work Location to Vertex.

Example 2: Employee Moves Mid-Year

Scenario:

Employee works Jan–Jun in California, moves to Nevada in July.

Rule Applied:

Localization of Services (split-year)
SUTA Applies: CA → NV (switch mid-year)

CMiC Handling:

Automated (Job-Based): If work location derived from job, system automatically changes from CA to NV.
Manual (Profile-Based): If there is no job location, user must update Profile or SUI/SDI override to NV effective July 1.

NOTE: Wage base resets separately for CA and NV; CMiC tracks both.

Example 3: Traveling Consultant

Scenario:

Employee travels nationwide, lives in Illinois, reports to a manager in New York.

Rule Applied:

Direction & Control → New York
SUTA Applies: New York

CMiC Handling:

Must explicitly assign SUI/SDI = New York on Employee Tax Tab.
Profile or Job location not suitable (too many states).
Ensures Vertex receives NY as Primary Work Location.

Example 4: Split Week: NJ/PA

Scenario:

Mon - Wed in NJ, Thu - Fri remote from PA. Reports to NJ.

Rule Applied:

Direction & Control → New Jersey
SUTA Applies: New Jersey

CMiC Handling:

Legacy Vertex: Without SUI/SDI defined, Vertex may choose random state (non-compliant).
Current Best Practice: Assign SUI/SDI = NJ manually.
Enhancement: CMiC will detect where the employee worked the most hours (3 days NJ vs. 2 days PA) → auto-assign NJ as Primary SUI location.

7. Current Logic vs. Planned Enhancements

Function	Current Behavior	Planned Enhancement
Primary Work Location	Derived from override or profile.	Derived from most-worked state (if no override).
Multi-State Handling	Only one state per pay period.	Still one per period (Vertex constraint).
Job Work Location	Optional, user-configurable	Recommended default for construction users.
Override Validation	Manual	Audit flag if override ≠ most-worked state.

8. Compliance and Best Practices

Best Practices for Setup:

Use Job Work Location for field employees.
Use SUI/SDI override sparingly; only when justified.
Always validate state changes Employee history (employee moves).
Review Employee Tax Tab for accidental overrides.
Keep an audit trail of overrides and location changes.

Compliance Notes:

CMiC + Vertex calculate one SUTA per pay period, compliant with DOL guidelines.
Wage base tracked per employee per state to prevent overpayment.
Overrides logged for audit consistency.

9. Key Takeaways

SUTA = Taxable Wages × State Rate, capped by wage base.
CMiC hierarchy determines Primary Work Location.
Only one SUTA state can be processed per period.
“Most-worked state” as a primary SUI location enhancement improves accuracy.
Vertex integration requires clean data and proper overrides.