The Resume Claim and Its Source of Record, Field by Field

You have an offer and a background-check form open, and you are about to certify that every line of your resume is accurate. Before you sign, you want to know which record each field will be checked against, what that record returns, and where a completely honest claim legitimately diverges from it. This guide is a jump-to-one-row reference for candidates at that exact moment: find your field, see its source of truth, and phrase the line so a true claim still clears.

Most public advice tells you screeners confirm "titles, dates, and companies" and stops there. That is not enough to certify a form. You need to know that a title resolves from a payroll database and not from your manager's memory, that a degree resolves from a conferral record and not your graduation ceremony, and that a role through a staffing agency resolves to the agency and not the brand on your badge. Each of those is a place where a true statement and the record of truth can disagree.

What does employment verification check, and against what record?

Employment verification confirms your employer, job title, and dates of employment, and sometimes duties, reason for leaving, and pay. Each field has a specific source of truth, and the phrasing that clears is the phrasing that matches that source rather than your self-description.

The single most useful fact for a candidate is who sits on the other side of the desk. In Refolk's index of professional profiles, there are far more payroll record-holders than dedicated investigators, which tells you the field is resolved by a system and a clerk, not by human judgment about your career.

The implication is direct: the person who can confirm your line is 17.6 times more likely to be a payroll clerk pulling a database record than an investigator weighing your story. So phrase every field to match the payroll system, not what a former manager would say if asked.

Here is the map. Find your field, note its source, and note what that source returns.

The qualitative check, references, sits outside this table and is covered in a separate guide. Everything above is factual verification against a record you cannot argue with, only reconcile to.

How does a background check verify employment: database first, HR second?

A screener pulls employment fields from an automated payroll database first, and only falls back to a manual call to former HR when no record returns. The two sources return different things, and knowing which one your employer feeds tells you what will be checked.

The dominant automated source is The Work Number by Equifax. A verification of employment confirms job title, dates, and employment status; a separate income verification releases earnings. Where an employer feeds a payroll file, the system can release gross earnings for the current year to date, including base pay, overtime, and special compensation, plus prior tax years. That is a deep, precise record, and it updates every pay cycle.

Two consequences fall out of that scale. First, roughly 400,000 requests move through on any given day, so verification is routine, not a special investigation into you. Second, and more important for how you phrase a line, the database is a permanent archive fed by weekly payroll files. A title you accepted years ago is now the "truth" a new verifier pulls. You reconcile the field to that archive, not to how you describe yourself today.

When there is no automated record, the CRA calls former HR or a designated service. A manual HR call typically returns only dates, title, and rehire eligibility. Increasingly the caller is redirected: many employers will tell a verifier they use a third-party service, decline to respond directly, and point to one of over thirty third-party providers. So even the "human" path often ends at another database.

Where does an honest resume legitimately diverge from the record?

Four divergences are documented and legitimate: functional title versus payroll title, brand versus legal entity, staffing and employer-of-record arrangements, and graduation versus conferral date. In each, the resume can be completely true and still not match the source of record, so each needs deliberate phrasing.

Functional title versus the HR record

HR can confirm the official title on file, but many workers use a different title on a resume or LinkedIn than the employer's formal record, and verifiers report the employer's record when available. A documented case: an employer's letter used a "business title" for immigration purposes, which is legal, while the official HR title that shows in a background check omitted "Lead." Both were real; only one is what the verifier returns. The fix is to put the exact HR title on the background-check form and carry your functional title into a description line under the role.

Brand versus legal entity, and staffing or EOR roles

Payroll returns the legal entity that paid you, which may be a parent company, a staffing agency, or an employer of record rather than the brand on your badge. Applicants who work for temp agencies often list the end client instead of the staffing agency. But the agency is the entity that requests the check, obtains authorization, and is the FCRA "user" of the report, so it is the agency's record that exists. With an employer of record, the EOR formally acts as the employer on behalf of a client that has no registered legal entity in that place, so the payroll record shows the EOR. Listing the client brand alone guarantees a mismatch. Name the legal payroll entity first, note the client brand alongside.

Conferral date versus walk date

The Clearinghouse returns the actual conferral date rather than the last-attendance or ceremony date. A "graduated May" claim can flag if the degree was conferred in August. This is a true statement that still diverges from the record. Use the conferral date the registrar will return.

A true statement and the record of truth can disagree, and the fix is phrasing, not a better argument.

What substitutes when an employer cannot be verified?

When a business has closed or will not respond, the screener falls back to tax records and candidate-supplied documents with your consent. A "not found" is not proof of fraud, and the burden simply shifts to what you can produce.

A firm can request an IRS W-2 or 1099 income transcript with your consent to confirm employment and pay for the requested years, with a typical turnaround of three to five days. You can also supply offer letters, pay stubs, contracts, and staff-profile links to resolve a title flag. For education, a transcript substitutes where the school does not participate in the Clearinghouse.

This fallback matters more than it sounds, because blanks are common. Best-in-class screeners have an unable-to-verify rate under 10%, but many companies exceed 20%. Roughly 8% of online degree verifications hit complications because institutions rebranded, merged, or closed after conferral. A blank return is expected, not damning.

Assemble the documents before you certify. Once a field comes back "not found," the fastest path is to hand over the record directly rather than dispute the absence of one.

Where you need to see, before you apply, who holds the record for a particular arrangement, Refolk can surface the specific record-holders. That removes the guesswork of not knowing whether a staffing agency or an EOR sits behind a past role.

The reconciliation procedure, field by field

Work the fields against the process the CRA will run, in the order the CRA runs it. The goal is that every line matches its source of record, or is annotated to explain a legitimate divergence, before you certify.

One point on the report itself: there is no "pass" or "fail" returned. The screener supplies results to the employer along with any discrepancies encountered. Your job is to leave no discrepancy unexplained, which is why the annotation lines matter as much as the raw fields.

How this goes wrong: the flags a true resume still trips

The most damaging failures come from true claims that mismatch a record, and from process steps taken out of order. Each has a tell and a check you can run before you certify.

• "Not found" read as a lie. A miss is expected given a 20%+ industry rate. Check: supply the record directly. False positive: a legitimate role at a small employer that was never fed to any database.
• Functional title flagged against the HR title. Resume says "Lead," payroll says the base title, and verifiers report the employer's record. Check: put the HR title on the form, the functional title in a description line.
• Brand listed instead of the legal entity or EOR. Payroll returns the EOR or staffing agency, not the brand you worked under. Check: list the legal payroll entity first and note the client brand alongside.
• Date rounding. Dates remembered off by a month or two read as a gap or overlap. Check: use payroll start and end dates, not remembered ones; a pay stub confirms them.
• A salary-history question that should not be asked. In an 18-state and DC footprint, the question is unlawful even through the screener. Check: know the governing state; decline and cite a range instead.
• Adverse action taken too early. Marking a candidate rejected before the process completes signals the response was never considered. Check: confirm a pre-adverse notice with report and rights summary arrived before any final decision.
• Disputing with HR instead of the CRA. Accuracy disputes routed to HR break the FCRA path. Check: file with the named CRA so the 30-day reinvestigation clock starts.

The salary-history point deserves its own note, because it changes what can even be checked. In 18 states plus Washington, DC, the ban extends to background-check companies and staffing agencies asking on the employer's behalf. In those states the compensation field often cannot be verified at all, which means a pay discrepancy there is legally inert. Know which state governs before you worry about a pay number matching.

What the FCRA guarantees you before an offer is withdrawn

Before any adverse action, the employer must run a two-step notice process, and you have a documented window to respond. Knowing this stops a fixable flag from quietly becoming a rescinded offer.

The pre-adverse action notice must include a copy of the background check and a copy of "A Summary of Your Rights Under the Fair Credit Reporting Act." The FCRA sets no exact waiting period; guidance clusters around five business days, though some sources say three to five and best-practice advice runs to seven to ten. Treat five business days as your planning number and confirm the specific window in the notice.

If you dispute with the CRA, the agency has 30 days to complete its reinvestigation and provide updated results. You also have a documented right to an additional free report within 60 days. Route the dispute to the named CRA, not to HR, or the clock never starts.

Keep the record current: manage it before the next check

You can control what the payroll database releases, and you can pre-empt the next verification by reconciling your own record now. This is maintenance, not a one-time task, because the archive persists and each new job triggers a fresh pull.

The Work Number lets an employee generate a Salary Key for controlled income disclosure, or freeze the record entirely so no one pulls it without your say-so. Use the self-service Employment Data Report to see exactly what the database holds under your name before a verifier does. If a title or date is wrong at the source, that is where to fix it, because correcting the record is cleaner than annotating around it forever.

A closing note on scope. This guide covers the factual verification path: payroll, HR, registrar, and boards. It does not cover the qualitative reference check, which runs on a different track. And where sources disagree, such as the exact adverse-action waiting period, I have given you the mechanism and the planning number rather than a false precision. Re-check the specific window in any notice you receive, because that document, not a general rule, governs your timeline.