1. LandOffer
  2. Blog
  3. All articles
  4. Employment Verification Salary Key: Understand When Your Work Number Record Needs One

Job search

Employment Verification Salary Key: Understand When Your Work Number Record Needs One

Separate employment-only and income requests, confirm the verifier and consent process, and clarify whether a one-time salary key is actually needed.

10 min readLandOffer team

A request involving The Work Number does not automatically mean you need to create a salary key. First identify whether the verifier needs employment information, income information or both, and ask which authorization process applies. Ask what fields the verifier needs when a message says only “proof of employment.”

This guide reviews current public instructions checked October 23, 2026, including the provider’s rendered employee pages. The two completed examples are fictional request records, not actual accounts or verification results. LandOffer publishes the guide and provides recent job listings; it does not generate keys, receive identity documents or perform employment verification.

Two request folios are compared while a single key remains enclosed in a separate tray.

Read the current salary-key description before using an old handout

The Work Number’s current salary-key page describes a six-digit code allowing one-time access to employment information and says salary keys remain active for 90 days. It says a lender, employer, government agency or another verifier may request one. The public page describes generation inside the employee platform; we read it without logging in or creating a code.

Its employee FAQ likewise says a verifier sometimes requests a salary key. That wording does not establish a universal requirement for every employment-only verification. Nor does it establish that every income request requires the employee to create a new key rather than use another applicable consent process.

Check the current provider entry and your actual employer’s instructions. A dated employer handout can still appear prominently in search, including California instructions revised in 2019. Do not carry its old login fields, default PIN conventions or validity period into a current account. This article does not reproduce those authentication details or use them as a current guide.

Keep three concepts apart: the identity checks needed to access your own account, consent for a verifier’s particular request, and a one-time salary key. A password or an authentication code is not a substitute item to give someone who asks for verification. A key should not become a public credential on a resume or a broadly shared application note.

Confirm the requested data and the verifier’s role

Write down the requesting organization, the named verifier, purpose, employee or employer record involved, requested fields and time period. A prospective employer checking work dates and a lender reviewing income can use the same service while asking different questions. The service’s name alone does not define the scope. Your field list records the stated request; it does not establish that a salary key technically limits access field by field or employer by employer.

Separate employment-only fields from income fields in your reading record. For example, an expressly stated request for title and employment dates differs from a request for earnings over a specified period. Do not add pay history merely because the verification platform can hold it. If the request says “employment and income,” ask which income measures and periods are actually needed.

The provider’s current FAQ describes credentialed verifiers, a permissible purpose and permission obtained in most cases through an application. Those public descriptions explain the provider’s framework. They do not verify a particular sender’s credentials, purpose or authorization for your information. We did not inspect an employer order, verifier account or consent record.

Confirm the request through the employer’s established contact and the verifier’s official route. A recognizable logo or a forwarded email is not enough to verify the recipient. Keep the purpose and recipient attached to any later authorization decision rather than treating a general screening conversation as permission to disclose all available employment and income data.

Employer examples show why the current route matters

Penn State’s public verification FAQ says employee consent for income verification is obtained during the application process in most instances, and describes a salary key as an additional consent mechanism. That employer example supports asking what is already in place; it does not let a candidate or recruiter assume that consent was obtained in a different case.

Yale’s current verification page directs an employee to its employee route if a verifier requests a salary key. Its instructions apply to Yale’s service arrangement, not every employer. We did not use either institution’s employee sign-in or test its private interface.

The two examples should not become a merged click-by-click tutorial. Navigation, identity checks and employer arrangements can differ or change. Use the current official route for the employer concerned, and ask its designated support contact if the request or public instructions do not match what you see.

If a verifier insists on a key for an employment-only request, ask it to identify the actual product, the reason and the current instructions supporting that requirement. Do not respond by declaring that a key is impossible or always unnecessary. Obtain the explanation for that particular product instead of inferring its requirements from the name “salary key.”

Worked comparison: Jonas separates two requests

Jonas’s fictional packet contains two unrelated requests. A prospective employer’s screening notice names an invented verifier, Seabrook Screening, and asks for a former employer’s name, job title and start and end dates. Its generic follow-up says “send a salary key,” without explaining why. A separate housing application names an invented property manager and expressly asks for employment plus gross earnings for a stated period.

All organizations, notices and dates in this example are invented. No actual earnings, account identifiers or key appear. Jonas has not authorized a release, generated a code or submitted either request during this exercise.

Record field JOB-21 employment request LEASE-22 income request
Stated purpose Employment-history verification for a prospective job Income and employment review for a separate housing application
Requested fields Employer, title and employment dates; no pay fields listed Employment and gross earnings for January–September 2026
Salary-key wording Generic follow-up requests one No specific key instruction supplied
Consent evidence Actual authorization and product not supplied in the teaching packet Application references permission, but completed consent evidence is not supplied
Current missing answer Why a key is requested for the stated employment-only scope Which verifier and current income-consent process apply
Completed action record Ask for product-specific explanation; no key created Confirm scope, recipient and authorization process; no key created

Jonas’s finished comparison reads: “The job request identifies non-income fields but contains an unexplained key request. The housing request expressly includes income but does not establish the applicable authorization mechanism. I cannot use either document to decide that a key is universally required, or carry consent from one purpose into the other.”

JOB-21 lists no pay fields; the packet does not establish whether that list covers the entire order. Jonas still asks whether the stated list is complete. LEASE-22’s income wording is more specific, but an income label alone does not verify the recipient or show that an authorization was completed.

Jonas retains JOB-21 and LEASE-22 as separate request files with separate purpose and consent questions. Jonas does not copy a code from one into the other, send an entire personal report to satisfy either request, or treat an unopened income request as a reason to grant broader access for a job application. The completed asset is the scope comparison and its two precise unanswered questions.

Independent inquiry: Seren asks who needs what before sharing

Seren’s separate fictional onboarding message says “employment/income verification” and asks that a salary key be returned to a recruiter. It names an invented screening company, Brookfield Verification, but gives no product name, fields, earnings period or explanation of whether the recruiter is the intended verifier. The secure delivery route is not identified.

Seren has the employer’s established recruiting contact available for clarification. The example does not stipulate that the message sender or the screening company has been independently verified. No account has been opened and no code exists. The complete gap record is:

Gap Completed entry
Purpose and product Onboarding is the stated context; exact employment-only versus income product unresolved
Data scope Requested fields, earnings measure and period not stated
Verifier identity Brookfield Verification named; official recipient and role still need confirmation
Consent mechanism No completed authorization evidence or reason for a salary key supplied
Delivery method No designated secure route; ordinary reply email not accepted as established instructions
Action state Clarification draft prepared only; no key generated, identity data transmitted or verification result received

Full UNSENT clarification draft:

Subject: Scope and secure process for the verification request

Hello Recruiting Team,

I am reviewing the onboarding message that asks for a salary key for “employment/income verification.” Before taking an account action or providing information, could you confirm the exact verification product, requested fields and purpose? If income is needed, please identify the earnings measure and period requested.

The message names Brookfield Verification but asks me to return information to a recruiter. Please confirm the organization acting as verifier, its official contact route and whether it or another designated recipient would receive any key. I would appreciate the current employer or provider instructions supporting that process.

Does this request require a salary key, or is another consent mechanism applicable? Please identify what authorization is already recorded, if any, and explain why an additional key is requested. I have not assumed that a general onboarding message establishes consent for every income field.

If a key is required for the identified request, what designated secure delivery process should I use, and how would I confirm receipt and the status of that specific verification? Please distinguish receiving information from completing the report.

I have not generated or shared a key, entered identity details or authorized a release through this draft. This message contains no Social Security number, password, authentication code or financial attachment. Thank you for clarifying the scope and route first.

Seren

The completed note remains “purpose, recipient and authorization mechanism unresolved.” A reply identifying only the verifier would leave the product, data scope, consent and delivery questions unanswered. A message acknowledgment would not establish that a key was generated, a release occurred or a report was completed.

A verifier request, purpose cards and unsent envelope sit beside a closed key box.

Treat any later key as sensitive and request-specific

If the current instructions and your independently reviewed request call for a key, use the provider’s official employee route and the relevant employer guidance. This article does not walk through authenticated generation, ask for a code or supply a sample that resembles a real key. Do not give a verifier your account password or let an unrelated recipient control the account.

The provider’s public page mentions sharing key information by email or print. That description is not a recommendation to place a real code in an ordinary recruiting thread, a public post or an application tracker. Confirm the designated recipient and delivery process for the particular request. Ask for an authorized alternative if the supplied route is unclear.

One-time access and a limited active period are different from a reusable password. The published 90-day period does not establish that an already used code remains usable or that every verifier will accept a code created for another request. Record any actual creation, permitted delivery and subsequent provider status privately; do not label a verification complete merely because information was delivered.

If a request changes purpose, recipient or data scope, obtain clarification rather than reusing an earlier assumption. No delivery or consent decision in this guide applies to a real person’s account, and no hiring, lending or housing outcome is predicted.

Keep your personal disclosure separate from verification

The Work Number’s current Employment Data Report page states that the EDR is for your own information and cannot be used as a verification. Sending the entire disclosure is therefore not a substitute for determining the requested product and following its authorized process.

A missing employer or an incomplete field also requires its own review. Generating a key does not create payroll data that was never supplied, establish coverage for every past job or resolve a disputed value. Ask the appropriate employer or provider about that specific issue without treating access and data accuracy as the same task.

Retain a short private record: request ID, verified recipient, purpose, fields, period, applicable authorization instructions and the actual state of the request. Keep unresolved items visible. A draft, a code generated, a delivery acknowledgment and a completed verification need different labels and evidence.

As you browse recent roles on LandOffer.ai, keep employment-verification records outside public search materials. Put the unanswered scope or authorization question beside the request ID, and resolve it through the verified route before deciding whether a key is needed.

Sources and Further Reading