Changing the EIN on a QuickBooks Payroll Account: What Trips Users Up

QuickBooks payroll subscribers who restructure or change ownership keep hitting the same snag. The Employer Identification Number is not one field. It lives in the company file, in the payroll tax settings, and on a signed form that has to reach the payroll side before filings change. Update the visible field first and payroll can keep filing under the old number, which then disagrees with IRS records.

The number sits in more than one record

On QuickBooks Desktop, the federal EIN appears under Company, then My Company, then Company Information. The Edit control there opens Company Identification, and the Federal Employer Identification No. field takes the new number. That field governs the company file. It does not govern payroll filings.

In payroll settings the number appears again. Open Settings, then Payroll settings, and work through General tax and Federal tax. General tax holds the company legal name. Federal tax holds the EIN. Each section has its own Edit control, and each has to be saved and confirmed on its own. A name saved in one place does not carry into the other.

Online payroll accounts follow a similar split, with legal information edited from the company profile rather than from a desktop company file. The principle holds either way: the profile and the tax record are separate records, and both have to agree.

A signed packet covers what the screens cannot

The settings screens accept whatever number gets typed. They do not verify it, and they do not notify anyone. The part that actually moves the EIN onto the payroll account is the entity change packet.

You download it, fill it in, sign it, and attach the supporting documents the packet itself lists. The completed set goes to the intake address printed inside the packet. Ownership and identity documents are usually on that list, which is why this step cannot be finished in a few minutes at the keyboard.

Successor and non-successor changes are not the same job

The payroll tier decides the path. On QuickBooks Workforce Payroll, a successor entity change is handled on the payroll side first, so the new EIN is recorded there before anything else moves. A non-successor entity change is different: a new payroll account is set up rather than the existing one amended, and users who start editing fields before they know which case applies usually have to undo work.

Premium and Elite accounts split on automation. Where automatic tax payments and filing are switched on, the filing calendar sets the timing, and a change dropped mid-period can leave a return filed under the old number. Where those are switched off and payments and filings are handled manually, the timing is yours to choose. Confirm which mode the account is in before touching the Federal tax field.

The legal-name checkbox most people skip

On the Assisted Legal Name Change form there is a checkbox sitting under the field for a new fax number. It reads like an afterthought. It is not. Tick it when the account name has to change as well as the payroll legal name. Leave it blank and the payroll record moves to the new name while the account keeps the old one, and the mismatch resurfaces later at sign-in or in correspondence.

The form must be signed and dated, then printed and uploaded, or sent to the intake address. An unsigned copy is not processed.

A sequence that avoids a second correction

1. Establish whether the change is successor or non-successor, since that decides whether the existing payroll account continues.
2. Complete, sign, and send the entity change packet with its supporting documents.
3. Update the company legal name in General tax, save, then done.
4. Update the EIN in Federal tax, then save.
5. Correct the company file EIN through Company Identification.
6. Tidy the remaining details: a DBA address, payroll contacts, the primary principal, the payroll admin.

Steps three and four sit in payroll settings, step five sits in the company file, and none of them replaces the packet. Treat them as three surfaces of a single job.

What finally resolved the mismatch?

The accepted answer treats the change as one job across those three surfaces: the packet, the two payroll tax sections, and the company file field. Users who got it working did all of them, with the packet sent first. Where only the settings were touched, the EIN on the payroll record stayed stale and the mismatch persisted until the packet caught up.

One caution is worth adding. If automatic tax payments and filing are switched on, choose the moment deliberately. Changing the number the day before a scheduled filing is how a period ends up reported under the old EIN, and correcting that costs more time than waiting a week would have.