You can change states without changing your favorite restaurant, your employer or your airport. In a cross-border metro, the move can feel wonderfully small. The paperwork may disagree.
Portland, Oregon, and Vancouver, Washington, make an unusually good test of this. The Columbia River separates two states within one regional economy. Kansas City adds another twist: the regional name belongs to separate municipalities in Missouri and Kansas, while an important earnings-tax boundary is municipal, not simply the state line.
These are not four contestants in a lowest-tax contest. They reveal a more interesting comparison: what happens when the place you sleep, the place you work and the place whose name you put on your weekend plans are different jurisdictions?
Portland and Vancouver: The River Is a Tax Boundary
Consider a Washington resident employed by an Oregon company. Oregon's nonresident guidance ties wage taxation to where the work happens: days physically worked in Oregon count; work performed at home in Washington does not become Oregon work merely because headquarters is in Portland.
That distinction makes the weekly schedule part of the housing decision. Two people living on the same Vancouver street, earning the same salary from the same company, can have different amounts of Oregon-source wages. One crosses the river every workday. The other works mostly from home.
Here is a simplified illustration for an ordinary salaried nonresident employee, not a calculation of anyone's final tax bill. Assume $100,000 in annual wages and 200 actual working days. Oregon's published allocation formula gives these results:
| Work location | Oregon days / total days | Oregon-source wages |
|---|---|---|
| Every workday in Oregon | 200 / 200 | $100,000 |
| 120 days in Oregon, 80 in Washington | 120 / 200 | $60,000 |
| Every workday in Washington | 0 / 200 | $0 |
Method: Oregon Publication OR-17, 2025, page 53. Working-day counts exclude holidays, vacation and sick days; total wages include their pay. Special employment exceptions and other income are outside this illustration.
The difference between the first two rows is $40,000 of allocated wages, not $40,000 of savings. Deductions, rates and the rest of the return still matter. But the example is enough to expose the flaw in a claim like "move over the river and the Oregon income tax disappears." The employee may still cross right back into it every morning.
The Address Can Stay Still While the Deal Changes
Imagine choosing a Vancouver home during a two-day-office arrangement. A year later the employer asks for five days in Portland. The mortgage has not changed, and neither has the state line. Both the commute and the work-location calculation have changed.
This is why a cross-border move should be evaluated against the job you actually have permission to perform, not an informal hope that remote work will continue. The useful question for an employer is specific: which location will be recorded as my work location, and on which days? A regional salary figure cannot answer it.
The policy date matters too. Washington currently has no general individual income tax, but its Department of Revenue describes a high-income tax beginning in 2028. A permanent "no income tax" label is a poor substitute for checking the rules that apply to the year and household in question.
There is another frequently missed boundary: consumption. Oregon has no general sales tax, but buying a taxable item there for use in Washington does not automatically make it tax-free. Washington's use-tax guidance covers purchases on which sales tax was not collected. Living north and shopping south is not a universal tax loophole.
Kansas City: Same Name, Different Municipality
Kansas City, Missouri, and Kansas City, Kansas, make the naming problem visible. "I work in Kansas City" is not sufficiently precise for the local earnings tax. Which municipality contains the worksite?
Kansas City, Missouri, levies a 1% earnings tax. Its filing guidance includes residents and nonresidents working in the city. A Kansas address alone does not erase the city tax on wages earned at a Missouri-side workplace inside that boundary.
At 1%, $100,000 of wages fully subject to that city tax would mean $1,000 per year. That arithmetic is deliberately narrow: it is not a combined state-and-local tax estimate, and it assumes the entire wage amount is subject to the city tax. For nonresidents who work some days outside the city, the city has a separate allocation and refund process.
Notice how this differs from the Columbia River example. In Portland and Vancouver, we started with a state boundary. Here a city boundary can matter even to someone who stays within Missouri. A state-level comparison misses that second layer entirely.
Compare the Arrangement, Not Just the Addresses
A household choosing between these places needs three concrete points on a map: home, the actual worksite and the destinations it will keep visiting. Then attach the relevant jurisdictions to each. That produces a more useful comparison than assigning a single tax personality to an entire metro.
The Portland–Vancouver comparison can frame the housing and climate context; the two Kansas Cities show how much a shared name can conceal. Neither comparison should decide the move by subtracting one headline rate from another.
The appeal of these metros is that the border does not divide everything. Friends, jobs and familiar places remain close. The mistake is assuming that because everyday life crosses the line easily, every obligation crosses with it.
