Compliance

Employment verification laws by state: what employers should know

Salary-history bans, stricter state reporting regimes, and consumer notice rules — the recurring themes, and what they mean for your workflow.

UPDATED AUG 2026 · EDUCATIONAL — NOT LEGAL ADVICE

One process, many jurisdictions

Federal law sets the baseline for consumer reports, and states and localities layer their own rules on top — sometimes binding the employer, sometimes the reporting agency, sometimes both. Those rules change, and how they apply turns on facts specific to your organization. Treat this page as a map of the recurring themes, not a summary of any state's law, and verify anything you rely on with qualified counsel.

Salary-history bans

Many states and localities restrict asking candidates about pay history, or relying on it when setting compensation — and some restrict requesting it from former employers at all. This is one reason compensation is treated differently from dates and title in a verification. Where a jurisdiction prohibits the request, HVR hides the compensation field entirely rather than leaving the rule to the verifier's memory.

Requires review by qualified counsel

Statutory processes, notices and rights summaries referenced here are described for product context only. Final language and applicability must be confirmed by qualified counsel.

Stricter state consumer-reporting regimes

Some states layer additional requirements on top of the federal framework: extra notices to the consumer, tighter rules on the purposes a report may serve, and broader rights to see what is in a file. If you hire in more than one state, it is safer to design your process around the strictest applicable regime — and to confirm the specifics with counsel before relying on them.

Requires review by qualified counsel

Statutory processes, notices and rights summaries referenced here are described for product context only. Final language and applicability must be confirmed by qualified counsel.

Limits on how far back a report reaches

Several jurisdictions apply seven-year-style limits on how long certain kinds of information may be reported, with thresholds and exceptions that vary by state. Employment verification is mostly a record of dates, title and status, but reporting-age limits still shape what an agency may include — so they belong in your compliance review even if they rarely change a verification's outcome.

Requires review by qualified counsel

Statutory processes, notices and rights summaries referenced here are described for product context only. Final language and applicability must be confirmed by qualified counsel.

Notice, fee and file-access rules

States also add consumer-facing rules: free or fee-capped copies of a file, additional notices when a report is ordered or acted on, and specific timelines for responding to disputes. These are the consumer's rights, not paperwork. A process that treats them as an afterthought tends to fail exactly when a decision is challenged.

Requires review by qualified counsel

Statutory processes, notices and rights summaries referenced here are described for product context only. Final language and applicability must be confirmed by qualified counsel.

What this means for your workflow

You do not need to memorize fifty regimes; you need a process that applies the right rules to each order. HVR applies jurisdiction rules at order time and stores each certification with its order — the obligations, and the review of your final language, remain with you and your counsel.

  • Configure candidate notices per jurisdiction, not globally
  • Certify a permissible purpose on every order
  • Document authorization and retain it on your schedule
  • Have qualified counsel review notice and adverse-action language

Requires review by qualified counsel

Statutory processes, notices and rights summaries referenced here are described for product context only. Final language and applicability must be confirmed by qualified counsel.

Questions a guide can't answer?

Employers, candidates and verifiers each have a direct line — no shared queue.