Job search
ADP Still Shows Your Former Employer: Get Access to Your New Job’s Payroll Record
Ask the new employer to confirm its ADP product, provisioning and registration route while preserving former-employer tax access and separating login from payment.
If ADP still shows your former employer after a job change, start with your new employer’s payroll or HR contact. An old login that works does not establish access to the new employer’s payroll record. ADP’s employee FAQ specifically recommends asking the new employer’s manager or HR department to arrange the appropriate current login. ADP employee support.
Keep the old tax-document route intact while resolving the new one. Do not delete an account or assume two employers’ records should merge. We checked public ADP guidance on October 23, 2026, without accessing payroll, registering an employee or resetting credentials. Both completed cases below are fictional. For separate career plans, browse recent roles on LandOffer.ai.

Identify the employer record you actually reached
Record the employer name displayed, the product or service address, and what you were trying to retrieve. “The old employer’s prior-year tax form is visible” is more precise than “ADP is wrong.” That observation establishes what you reached, not whether the new company created your employee record or ran payroll.
Resolve four separate questions: can you authenticate; have you registered for the current organization’s service; has its administrator enabled the relevant access; and has the particular pay statement been issued? A yes to the first question does not answer the others. The missing statement could require a provisioning question, a publication-date question or a payroll question; the screen alone cannot choose among them.
Keep the actual first-pay date and pay period beside this record. Your first workday, payroll cutoff, scheduled payment date and online-statement availability can be different dates. Ask the employer which ones apply rather than calculating a missed paycheck from the date an old account was opened.
For a support description, record the old employer label and the missing new-employer context without attaching a full tax return, W-2 or bank screen. If HR requests a screenshot, provide only the relevant view through its verified route and remove unrelated sensitive information. Do not post the screenshot publicly to ask strangers to identify your payroll account.
Confirm the product and employer registration arrangement
ADP’s public login directory distinguishes employee routes such as MyADP, Workforce Now and RUN, alongside administrator and other services. A familiar ADP logo does not establish that a bookmarked route is the right entry point for this employer. Ask for the product name and approved employee URL in the new-company instructions.
For MyADP, the published support page says online access depends on the employer, and directs a first-time user to obtain the employer’s registration code. It also distinguishes MyADP credentials from a company-network login. If the employer instead uses an integrated company sign-in route, obtain its instructions before creating another password-based identity.
The 2023 employee registration quick-reference card, currently served by ADP, describes a Find Me route using information supplied to the organization and an alternative registration-code route. It distinguishes personal and organizational codes and notes that available options vary, including federated-use eligibility. This is evidence of configured alternatives, not a reason to try every route with repeated guesses. ADP employee registration card.
The administrator registration guide describes time-limited personal codes associated with an individual and dependent on employer-supplied records. It also explicitly excludes RUN Employee Access from its illustrated registration process. Do not carry its screen sequence into another product as a universal repair. Ask the administrator to confirm the supported route and current invitation.
Completed two-record audit: old taxes versus new payroll
Fictional case: Jordan leaves invented employer Maple Quay and joins invented employer Cedarline Systems on November 9, 2026. Both are stipulated ADP clients solely for this example. No company, account, employment relationship or screen below was actually tested.
Jordan’s old bookmark opens a page labeled Maple Quay. His local notes identify a 2025 W-2 there, while Cedarline’s welcome packet names Workforce Now but contains no employee registration invitation. His expected first-pay date is November 20 in this invented record. The missing invitation is the first question to resolve; the old tax document is not an error to erase.
| Record field | Historical Maple Quay route | New Cedarline route |
|---|---|---|
| Purpose | Retrieve prior-employer tax documents | Access current-employer pay information |
| Product context | Old bookmark, exact historical service unverified | Workforce Now stated in fictional welcome packet |
| Access evidence | Old employer label and 2025 tax document stipulated visible | No verified current-employer registration or statement |
| Responsible contact | Maple Quay’s former payroll contact for old documents | Cedarline HR/payroll administrator for setup |
| Information gap | Whether access will remain available later | Approved employee URL, invitation and access readiness |
| Completed decision | Preserve this route; no deletion or merger requested | Ask new HR to confirm provisioning and registration |
| Payment status | Not relevant to Cedarline’s first payroll | November 20 expected; actual payment unverified |
Jordan’s completed request note reads: “Please confirm Cedarline’s employee access route and whether my payroll record is ready for registration. My prior bookmark shows Maple Quay. I have no Cedarline registration invitation recorded. I am preserving the prior employer’s tax-document route and have not assumed the records will merge.”
That note avoids two common mistakes: treating old access as current setup, and destroying useful historical access to force a fresh start. It also gives the new administrator a narrow task. Jordan is not asking Cedarline to amend Maple Quay’s tax forms or asking former HR to create Cedarline’s employee record.
In the fictional follow-up, Cedarline’s administrator confirms an invitation has been issued to the address on file. Jordan’s audit now says “invitation issued; employee registration not performed in this exercise; current statement not checked.” That answer would not establish that he received his first pay or that registration is complete.
His November 10 preparation date is ten calendar days before the stipulated November 20 pay date. That is an example planning interval, not an ADP provisioning promise or mandatory lead time. If the expected pay date passes without payment, payroll must address that separate issue; a new login alone would not resolve it.
Preserve former-employer tax access without promising permanence
ADP’s current W-2 and 1099 guide says someone who previously accessed a former employer’s records may try that route again. If access is unavailable, the former employer may have removed it; the former company’s HR or payroll department is the contact for a copy. ADP does not promise indefinite former-employee portal access or supply the form itself. Former-employer W-2 guidance.
Keep the former employer’s verified contact and any tax documents already retained in an appropriate private location. Do not include credentials in the access map, and do not attach old tax documents to the new employer’s routine registration question. The fact that both organizations use one vendor does not establish that one company administers the other’s records.
If the issue is an incorrect old W-2, identify the form issuer and tax year. That is a correction request rather than “please enable my current pay statements.” Similarly, a removed former-employer login is not proof that the new employer deleted it. Keep the observation and the suspected cause separate until the responsible contact confirms what happened.

Independent case: an invitation fails before registration
Fictional case: Priya has a new-company invitation in her preparation record, unlike Jordan. It was issued November 2, 2026; on November 23 she sees the invented error “registration code expired.” Her old employer remains accessible through an older route. The names, dates, employee suffix and error are synthetic; no actual code or account exists.
Her completed diagnostic record is: new employer Example Harbor Labs; employee-ID suffix EXAMPLE-Q; current product not confirmed; invitation age 21 calendar days; exact synthetic error retained; no further attempts after the failure; old tax access preserved. This identifies an invitation problem without declaring that her employment record is missing.
The administrator guide describes personal codes expiring after 15 days or use in the covered workflow. Priya’s invented invitation is older than that described interval, but the article cannot infer a real code’s expiry or product from its age. The observed error and administrator’s current instructions are what matter. She asks for confirmation or reissue rather than changing identity information to make registration match.
Her complete unsent draft is:
To: Verified new-employer HR/payroll administrator, role placeholder only
Subject: New-employer ADP registration — invitation and product confirmation
Hello HR/Payroll Team,
I am trying to access Example Harbor Labs’ payroll information. My earlier ADP route still shows my former employer. I have kept that historical tax-document access unchanged.
My local record shows a new-company registration invitation dated November 2. On November 23, the registration step displayed “registration code expired.” I stopped rather than repeatedly trying the code or creating additional accounts. My employee-ID suffix for this fictional record is EXAMPLE-Q; please tell me if you need further identification through the approved secure channel.
Could you confirm the ADP product and employee URL I should use, whether my current-employer record is ready, and whether a new invitation or personal registration code is required? Please also confirm the contact address used for the invitation without sending a password or verification code in this thread.
If our company uses a company-portal or federated sign-in arrangement, please send the appropriate instructions instead of assuming a separate ADP password is needed.
I have not attached a tax form, Social Security number, date of birth, password or registration code. Please identify the secure process for any further information required.
Thank you,
Priya Example
Priya’s completed next action is “await administrator confirmation of product, provisioning and valid invitation.” It is not “account reset,” “records merged,” or “payroll corrected.” A reply acknowledging the question would still be a support receipt, not evidence that the correct employer’s pay statement is visible.
Verify current access and payment as separate outcomes
Once the employer supplies the applicable route, follow its instructions privately. Inspect the actual company context and the relevant statement’s pay period and pay date before marking access resolved. A welcome screen or successful authentication is insufficient if the desired record still belongs to the former employer.
If authentication fails for an established current-employer account, use the product’s supported recovery route or administrator assistance. Do not reset an old account simply because it is the one you remember. Repeated attempts can create an additional lockout problem while leaving current-employer provisioning unanswered. We did not perform a reset, recovery or login for this guide.
For a missing payment, tell payroll the expected date and whether money actually arrived through the agreed payment method. For an unavailable statement, identify the employer, period and page that is missing. These reports can coexist: someone might have received pay but lack online access, or access a portal without finding the expected payment record. Neither observation proves the other.
Retain the verified result: correct employer reached, requested statement located, unresolved payroll issue assigned to its owner, and historical tax route preserved where available. Treat any account-linking arrangement as unconfirmed until the employer explains it. After recording the current issue’s next action, browse recent roles on LandOffer.ai for separate opportunities; LandOffer cannot provision ADP access or change payroll records.
Sources and Further Reading
Checked October 23, 2026. Current public ADP help pages and served registration PDFs were read. Native public paystub FAQ and W-2 guide were inspected; no credentials, employee registration, payroll record or recovery process was used. PDF dates and product exclusions are preserved.
- ADP: Support for Employees of ADP Clients.
- ADP: User login directory.
- ADP: MyADP login and support.
- ADP: Employee registration quick-reference card, copyright 2023, currently served.
- ADP: Registration best practices, administrator guidance with product exclusions.
- ADP: W-2 and 1099 guide for employees.



