Working from another state: what your employer actually cares about
The objection is rarely about trust. It is payroll registration, workers' comp and unemployment insurance, and it comes with a lead time.
Almost nobody refuses an out-of-state move because they doubt you will keep working. They refuse because the company may not be set up to pay someone who lives there, and fixing that is a registration project with a lead time in weeks. The trust conversation you rehearsed is not the one you are about to have.
That is mostly good news, because a procedural objection has procedural answers. The bad version is moving first and telling payroll after, because then you have handed a small team a problem with filing deadlines on it, and one cheap fix is to end the arrangement.
What your employer is actually checking
Four things, roughly in this order.
- Payroll registration. Whether the company can withhold and remit in that state. If it has no other employee there, the answer is often no, and opening a state is a filing with its own timeline.
- Unemployment insurance. Which state the employer pays into for you, which tracks where the work is performed rather than where the office sits.
- Workers' compensation. Whether the policy covers an employee working in that state, including one at a kitchen table.
- Anything in the role with a location of its own. A license issued by state, a client contract naming where work may be performed, a clearance.
Why "we have no presence there" is a real answer
It is usually not a polite no. Adding a state can mean a registration, a state revenue account, an unemployment account, an insurance endorsement, and an obligation to keep filing there as long as one person lives in it. A small employer weighs that against one employee; a large one often has the state open already and can say yes inside a week.
Find out which before you ask for a decision. "Are we already registered to run payroll in that state?" is a question payroll answers in a minute.
The request to send before you move
Send it to your manager and copy HR or payroll. It is a request for information, not a case.
Subject: [Your name] - work location change, [month]
"I am planning to move to [city, state], with a target date of [date]. I wanted to raise it before anything is committed, so the company-side checks happen first.
Three questions, for whichever team owns them:
1. Is the company already registered to run payroll in [state]? If not, is opening it something you would consider, and what is the lead time?
2. Does our workers' compensation coverage extend to an employee working from home in [state]?
3. Does anything in my role carry a location requirement I should flag - client contracts, licensing, systems access?
My hours, availability and on-site commitments would stay as they are. I am not asking for a decision today, only for the checks to run in the right order. I am holding off on signing anything until I hear back."
The last line does the work. It tells them the move is still reversible, which is when people actually spend effort on it.
The four things to get confirmed in writing
- The approval and its effective date. One sentence, from someone with authority to say it, naming the date your official work location changes.
- What payroll will look like and from when. Which state your stub will show withholding for, the first pay period affected, and who to contact when a stub looks wrong.
- Workers' compensation coverage in the new state. Confirmation it applies, the number to call, and the steps if you are injured working. Your home is a worksite now, and that process is worth having before you need it.
- Everything that changes as a result. On-site days, travel, equipment shipping, whether the role is tied to a location-based pay band, and who to notify if you move again.
Keep all four on one thread. Verbal approval from a manager who leaves in March is worth nothing in April.
Company first, lease second
The sequence that goes wrong is always the same: sign, move, then tell payroll. By then the only people who can fix it are the ones you surprised. One email sent while the move is still reversible turns a compliance problem into a calendar problem.
The questions your employer cannot answer for you
Where you owe income tax, what counts as residency, how two states treat the same wages, whether any agreement between them touches your situation - none of it belongs to your manager. Payroll's job is to run the setup the company has, not to advise you on your own filing.
Take those to a tax professional the same week you send the message above. If the arrangement is written into a contract, or the answer is "move, we will sort it out later," that is a question for an employment attorney.
Ask before you move and it is a scheduling problem. Ask after, and it is somebody else's compliance problem with your name on it.
Who has to know, and in what order
If you have already gone, say so now in writing, with the date you started working from the new address. A dated sentence lets payroll fix things forward. A vague one leaves them guessing when it started.
After that the order matters more than the reasoning. Payroll owns your stub and the withholding on it, so payroll hears it first. HR owns whether the employer is registered where you are, because registration, workers' compensation and unemployment accounts differ from state to state. A tax professional owns your own return, and an employment attorney owns anything you signed.
General information about work in the United States, not legal, tax, immigration, medical or financial advice. Pay, hours, leave and licensing rules differ by state, by city and by contract, and change over time. Check anything here against your own documents and, for anything you would act on, take advice from a qualified professional in your state. Get in touch with any questions about this post.