Source-verified vs database employment verification

What a database verification is

Commercial employment-data databases aggregate payroll records contributed by employers and payroll providers. A database verification queries that pool and returns whatever record it holds — often quickly, which is genuinely useful when the employer contributes data and the record is current. This method is frequently marketed as instant employment verification. It is one legitimate verification method among several, and it is worth being precise about what the result actually is.

What the database record does and does not document

A database record shows what a contributor sent, as of whenever it was sent. Origin, freshness and contributor coverage vary: the record rarely shows how it was collected, when it was last updated, or whether the employer still stands behind it. And when a query returns nothing, that non-hit is an absence, not an answer — it usually means the employer does not contribute to that database, not that the employment did not happen.

• Origin: contributed by an employer or payroll provider, not confirmed at the time of your request
• Freshness: update schedules vary by contributor
• Coverage: many employers, especially smaller ones, do not contribute at all
• A non-hit documents nothing either way

What source verification adds

A source-verified result is confirmed with the employer of record — or its designated payroll or verification source — in response to your specific request. Each field carries its source type, verification method and verification date, so a reviewer can see exactly who confirmed what, and when. Where a source declines a field, the decline is recorded under the source's stated policy rather than estimated or filled in from elsewhere.

The honest tradeoff

Source responses take time, because sources answer on their own schedules — that is the real cost of provenance. HVR does not hide the wait: each case shows the outreach attempts made, who owes the next step, and when to expect the next update. For some roles a contributed database record may be sufficient; for decisions you may have to defend later, documentation of the source usually matters more than speed.

How HVR records each

Every value in an HVR report is attributed — source-provided, candidate-provided or document-derived — with its method and date, so a database-derived value and a source-confirmed value are never presented as the same thing. What a report can contain varies by case. The information available depends on your authorization, permissible purpose, jurisdiction, employer policy and source availability.