Employment and income verification services: how to verify income, run a candidate employment verification, use automated employment verification or an employment verification api, and what a work history background check returns

What each provider publishes about its own price

How to specify verification before you buy it

1. Decide the depth before you compare quotes. The most recent employer, the last two positions, or every employer in seven years are three different purchases at three different prices and three different turnaround times. Providers assume differently, so state it.
2. Ask what happens when nobody answers. Every provider makes a defined number of attempts over a defined period before returning unable to verify. Ask what those numbers are, because that is the actual service level on the slowest element of your report.
3. Do not ask for salary history in restricted states. A growing number of states and cities bar employers from asking an applicant or a previous employer about salary history. A national provider will often decline to seek it for that reason, and you should not press.
4. Treat an unverifiable employer as a question, not a finding. Small and defunct employers are the usual cause. Ask the candidate for documentary evidence rather than treating silence from a third party as an adverse fact about them.

Three methods, very different speeds

A database lookup against a commercial payroll-derived record is instant where the employer contributes data and useless where it does not, which covers most small employers. A verbal verification means the screening company telephoning HR or payroll and documenting who was spoken to, when and what was confirmed. Documentary verification uses a written request or the applicant's own records such as a W-2 or pay statement.

Providers work down that list, which is why verification timing is unpredictable in a way criminal searching is not. A candidate whose employers are all on a payroll database verifies in minutes; one whose last employer has closed may not verify at all.

What actually comes back

In practice most employers confirm dates of employment and job title, and some will say whether the person is eligible for rehire. That is a policy choice driven by defamation exposure rather than a legal limit, and it means a verification usually proves somebody was there in roughly that role, not how they performed.

Income verification is a narrower product used more in lending than in hiring, and where it is used in employment it is increasingly constrained: salary history bans in a number of states and cities restrict asking an applicant or a previous employer what they were paid. Where you need to know whether somebody can afford something, as in tenant screening, income verification against pay records is the right instrument and salary history from a former employer is not.

Where the API layer helps

An employment verification API integrated with an applicant tracking system removes rekeying, which removes the transposed dates of birth and misspelled names that put the wrong person's record on a report. For employers hiring at volume that is the largest single accuracy gain available, and it also removes a day or two of administrative latency.

It does not change what can be verified. An API returns a database result instantly where the record exists and falls back to the same manual process where it does not, so the slowest cases stay slow. Ask a provider what proportion of its verifications complete in-database rather than what its average turnaround is, because the average hides exactly the cases that will hold up your hire.

Questions buyers ask before they order

What does an employment verification confirm?

Usually dates of employment and job title, sometimes rehire eligibility. Most employers will not discuss performance, which is a policy choice about defamation exposure rather than a legal restriction.

Why is verification the slow part?

Because it depends on a third party answering. Court indexes respond on demand; a former employer's HR contact may take days, and small or closed employers may never respond at all.

Can I ask what someone was paid?

In a growing number of states and cities, no. Salary history bans restrict asking either the applicant or a previous employer, and national providers often decline to seek it for that reason.

Does an API make verification faster?

Only where the record is in a database. It removes rekeying and its errors, which is the biggest accuracy gain at volume, but the manual fallback cases take exactly as long as before.

Screening rules by state