Free Payroll Tool
See what your payroll provider really charges
Most providers hide per-run and add-on fees. Audit your real cost per employee in about 30 seconds, free.
Run the Payroll Fee Auditor →Blog · Payroll Management · Security Companies
Security Company Payroll Compliance: State Licensing, Workers Comp, and Guard Payroll Rules
Security company payroll compliance operates across three regulatory layers simultaneously: federal FLSA wage and overtime rules, state licensing requirements for security companies and individual guards, and state payroll tax registration and workers compensation obligations. Companies that expand into new states often discover these layers only after guards have already started working, which creates retroactive compliance risk. This post covers the state-level compliance requirements that security company operators most frequently encounter.
State Guard Licensing and Payroll Timing
Most states require private security companies to obtain a company-level license and require individual guards to hold personal security guard licenses before performing guard services. The licensing timeline matters for payroll: if a guard starts working before their license is issued, the security company may face regulatory penalties from the state licensing board and potentially liability for guard work performed during the unlicensed period.
Some states have expedited temporary license provisions that allow guards to work while their full license application is processed. Others have strict prohibitions on working without a current license. The payroll department should have a checklist that confirms license status before a new guard is activated in the payroll system and receives their first paycheck.
The DOL's compliance assistance resources cover the federal wage and hour obligations that apply to security companies, which operate alongside state licensing rules to create the full compliance framework.
Workers Compensation Classification for Guards
Workers compensation premiums for security companies are calculated based on classification codes that reflect the risk profile of different job functions. Armed guards carry a higher risk profile than unarmed guards and are typically classified under higher-rate codes. Supervisors and management staff may be classified separately from field guards at lower rates.
Workers compensation audits by insurers typically occur annually and review actual payroll by classification code. If a security company has been classifying all employees under a single guard code without distinguishing armed from unarmed or field from administrative, the audit may result in a premium deficiency assessment for the underpaid portion. Payroll must track employee classification by workers comp code and report separately when the policy requires it.
Some states require specific workers compensation coverage for armed guards beyond standard commercial policies. Before deploying armed guards, confirm that the workers compensation policy explicitly covers armed security operations and that the coverage limits are appropriate for the risk.
Multi-State Payroll Registration
Security companies that operate in multiple states must be registered for payroll taxes in every state where they have employees working. This includes: state income tax withholding account registration, state unemployment insurance account registration, and local tax registration in jurisdictions that impose local income taxes (such as New York City, Philadelphia, and many Ohio and Pennsylvania municipalities).
State new hire reporting is also required in each state where a new employee works. Most states require that new hire reports be filed within 20 days of the employee's first day of work. Failure to file on time results in penalties, and some states share new hire data with child support enforcement agencies, making timely reporting a legal obligation for child support withholding purposes.
The administrative burden of multi-state registration and ongoing compliance is one of the primary drivers of payroll outsourcing for security companies. A managed payroll provider handles all state registrations, calculates and remits state taxes for each state, and files all state payroll tax returns on the correct schedule.
FLSA Record-Keeping for Security Operations
- Employee name, address, and Social Security Number
- Daily and weekly hours worked for all non-exempt guards
- Wage rate, including shift differentials and SCA rates for covered contracts
- Total daily and weekly straight-time and overtime earnings
- All deductions from wages with authorization documentation
- Dates of payment and period covered by each payroll
- Records retained for: 3 years (payroll records) and 2 years (time records)
Security Company Payroll Compliance Managed
BEG manages security company payroll compliance including multi-state registration, workers comp reporting, and FLSA record-keeping at $25 to $45 PEPM. Setup in 3 to 5 business days.
Frequently Asked Questions
What are the payroll registration requirements when a security company expands into a new state?
When a security company places guards in a new state, it must register for payroll tax withholding in that state, register for state unemployment insurance (SUI), obtain state workers compensation coverage for guards working in the new state, register the guard licensing entity with the state's licensing board (most states regulate private security companies separately from general business registration), file new hire reports for all new employees in that state, and in some states, register for local income tax if operating in cities with local income taxes. The sequence matters: workers compensation coverage should be obtained before any guards begin work in the new state, and payroll tax registration should be complete before the first payroll is processed. Failure to register before employees work can result in penalties.
How do state guard licensing requirements affect payroll?
State guard licensing requirements do not directly affect payroll calculations, but they create obligations that intersect with payroll administration. Most states require that licensed guards meet minimum training and background check requirements before working. Some states prohibit guards from working until their license application is processed, which affects when they can be added to payroll and begin earning wages. License renewal requirements may include continuing education that the employer pays for and tracks. If guards work without required licenses, the security company faces regulatory penalties and potentially employment law liability for work performed during an unlicensed period. Payroll records showing when each guard started should be cross-referenced against licensing records to confirm that guards were licensed before their first paycheck.
What workers compensation code applies to armed vs unarmed security guards?
Workers compensation classification codes for security guards vary by state, but the National Council on Compensation Insurance (NCCI) maintains standard codes that most states use. The primary guard classifications are: Code 7720 (Detective or Patrol Agency and Drivers) for most general security guard operations; Code 7380 for building cleaning and maintenance operations that includes some security roles; and Code 7722 for armored car operations. Armed guards may be classified separately from unarmed guards in some states, with higher premium rates reflecting the elevated risk. Misclassifying armed guards under the unarmed rate is an audit risk that results in premium deficiency assessments. Payroll must track armed vs. unarmed hours separately if the workers comp policy applies different codes.
What is the correct way to handle pre-employment screening costs in relation to payroll?
Background check costs, drug testing fees, and pre-employment physical expenses are generally employer costs and are not deducted from employee wages. Taking these costs from employee paychecks (either directly or through a negative adjustment) is a wage deduction that requires written employee authorization under state law and cannot reduce wages below minimum wage. Some states prohibit pre-employment cost deductions entirely. If the security company has a policy that recovers training costs from guards who leave within a specified period, the cost recovery provision must comply with state wage deduction laws and cannot be deducted from the final paycheck in states that restrict final pay deductions.
How do we handle payroll records for guards with high turnover?
FLSA requires retaining payroll records for at least 3 years and time records for at least 2 years. For a high-turnover security company, this means maintaining records for a large number of former employees. Electronic payroll records stored in a cloud-based payroll system satisfy the retention requirement as long as the records are accessible and can be produced upon request. Former employee records should not be deleted when an employee separates; they should be archived and retained for the required period. At year-end, W-2s must be produced for every employee who worked during the calendar year, including those who worked only one shift. The payroll system should maintain each employee's record for the full calendar year plus the required retention period.
Are there any payroll tax incentives specific to security companies for hiring veterans?
The Work Opportunity Tax Credit (WOTC) is available to employers who hire eligible veterans, among other target groups. Security companies that actively recruit and hire veterans, which many do given the transferable skills from military service, can claim WOTC credits ranging from $1,200 to $9,600 per eligible veteran depending on their target group and hours worked. The credit requires that the veteran be certified through the state workforce agency and that the certification form be submitted within 28 days of hire. Security companies with high hiring volumes and veteran recruitment programs should integrate WOTC screening into their new hire onboarding process to capture these credits systematically.
From the blog