Hiring a Remote Employee Across the Border: the Employer's Guide to Payroll, Permanent Establishment, and the EOR Shortcut

The employee works where the employee lives, and that single fact assigns the rulebook: employment exercised in a country belongs to that country's payroll, social security, and employment-standards systems, whatever the employer's flag. The northbound case — US company, employee in Canada: Canadian federal and provincial income tax withholding, CPP and EI contributions (employer portions included), a Canadian payroll account, T4s, provincial employment standards (vacation, termination, leaves — Ontario's rules apply to Ontario employees of Texas companies), workers' compensation registration by province, and possibly provincial payroll taxes at scale. The southbound case — Canadian company, employee in a US state: federal income tax withholding and FICA (employer match included), FUTA, state income tax withholding and state unemployment insurance in the employee's state, workers' compensation, W-2s, and the state's employment law — plus the state-by-state variance that makes a Colorado hire and a New York hire two different projects. Over both directions sits the totalization agreement, which assigns social security coverage to one system (the local hire belongs in the local system; temporary assignments of existing staff can stay home with a certificate of coverage — the distinction between hiring there and sending there that drives which social contributions apply), and the permanent-establishment question, which is about the role, not the payroll: a remote developer, analyst, or support engineer generally doesn't create a PE for the foreign employer, while an employee who habitually concludes contracts — the country manager, the closing salesperson — is the dependent-agent trigger, and the services-PE day-count rules add a second path for teams delivering on-site work; the offer letter's authority language and the role design are tax documents, drafted accordingly. The build-versus-rent decision then prices itself: building — registering the accounts, running the foreign payroll (usually through a local payroll bureau), administering benefits (the Canadian hire expects a health plan that means something different than the US one; the US hire's expectations run the other way), and owning the employment-law compliance — costs setup weeks and ongoing administration, and is the right answer at team scale or for permanent market commitment; renting — an employer-of-record legally employs the person in-country and leases them back, bundling payroll, contributions, benefits, and employment-law compliance for a per-employee monthly fee — is the right answer for the first hire, the test market, and the timeline that can't wait for registrations, with the honest caveats that EOR fees compound at scale, the triangular employment relationship needs a real contract review (IP assignment, confidentiality, and non-competes flowing properly through the EOR to the client), and the PE analysis doesn't disappear because the payroll moved — the EOR solves employment compliance, not the tax character of what the person does. The conversion path — EOR for hires one and two, entity and native payroll at hire five or the first enterprise deal — is the standard arc, and planning it up front (offer letters and benefits designed to transition) avoids re-papering the team midstream.

Key takeaways

• The employee's country runs the payroll: registration, withholding, employer social contributions, workers' comp, and employment standards all follow the desk, not the head office — and the employer portions (CPP/EI north, FICA/FUTA/SUI south) belong in the compensation budget from the first offer.
• Hiring there vs sending there: local hires join the local social security system; temporary assignments of existing employees can keep home-country coverage via totalization certificates — two different structures with two different contribution answers.
• The PE question is role design: contract-concluding authority and habitual dealing are the triggers; offer letters for cross-border sales roles carry authority limits on purpose, and the services-PE day-count watches teams doing on-site delivery.
• EOR rents the whole employment stack: speed, compliance, and benefits for a monthly fee — right for first hires and tests; reviewed for IP/confidentiality flow-through; and never a substitute for the PE analysis of the role itself.
• Building is a project with a threshold: payroll accounts, a bureau, benefits, and employment-law counsel — the per-employee economics beat EOR somewhere around a handful of staff or a permanent commitment, and the conversion is smoother when the first offers anticipated it.
• Misclassification is the false shortcut: the contractor label on a full-time, integrated, exclusive worker fails in both countries' tests and surfaces in the worst venues — terminations, injuries, and audits; the EOR exists precisely so the honest answer costs a fee instead of a finding.

The first-hire checklist

Before the offer: the role's PE screen (authority, activities, on-site days); build-or-rent decided against the twelve-month hiring plan; compensation budgeted with employer contributions and the benefits the local market expects; the offer letter drafted for the chosen structure (EOR paper or direct employment) with authority limits where the screen said so; and the totalization posture noted if the hire is actually a transfer. After the start: payroll running before the first payday (obvious, missed constantly), the calendar of filings owned by someone, and the conversion triggers — headcount, revenue, permanence — written into the expansion plan rather than left to the moment the EOR invoice starts to sting.

Worked example

A Vancouver SaaS company makes its first US hire — a customer success manager in Denver — and eighteen months later a Chicago account executive. Hire one: the PE screen is clean (no contract authority, no on-site pattern); build-versus-rent prices EOR at US$599 a month against a Colorado registration stack the company doesn't want to own for one person; the EOR employs her with a benefits package that made the offer competitive, the IP and confidentiality terms flow through a reviewed tripartite agreement, and payroll runs on time from day one. Hire two forces the real decisions: an AE's draft offer includes "authority to negotiate and close" — rewritten to proposals-and-negotiation with head-office signature, keeping the dependent-agent analysis clean while the sales process barely notices; and the company's plan now shows five US hires within two years, so the conversion project starts — a Delaware subsidiary (the expansion playbook's stage-three answer), state payroll registrations in the employees' states, a payroll bureau, a US benefits broker matching the EOR's plans so the transition letters change the employer's name and nothing the employees feel. The EOR relationship winds down at hire four with everyone re-papered on schedule. Total compliance surprises across the arc: zero — because the checklist ran before each offer, and the one clause that would have created a tax problem was caught in a Google Doc instead of an audit.

Official sources

The Social Security Administration explains that the totalization agreement between the United States and Canada helps people who have worked in both countries qualify for benefits by combining credits, and assigns coverage so that workers pay social security taxes to only one country for the same work. — Social Security Administration, Totalization Agreement with Canada, https://www.ssa.gov/international/Agreement_Pamphlets/canada.html

"Subject to the provisions of Articles XVIII (Pensions and Annuities) and XIX (Government Service), salaries, wages and other similar remuneration derived by a resident of a Contracting State in respect of an employment shall be taxable only in that State unless the employment is exercised in the other Contracting State." — Canada-United States Tax Convention, Article XV, https://www.canada.ca/en/department-finance/programs/tax-policy/tax-treaties/country/united-states-america-convention-consolidated-1980-1983-1984-1995-1997.html

Practitioner note

Cross-border hiring is an employment-systems problem with a tax question riding on the role: payroll and standards follow the desk, coverage follows the totalization rules, and the PE risk lives in the offer letter's authority clause. Our first-hire protocol is screen-the-role, price build-versus-rent against the real hiring plan, and draft the conversion into the first offers — because the EOR is a superb bridge and an expensive destination, and the companies that plan the crossing never notice the toll.

See also: For Regulation 105 and the 15% Canada withholds on services, see Regulation 105 and the 15% Canada withholds on services; and browse every cross-border tax topic guide, organized by situation · Short version: Cross-Border Payroll: What an Employer Owes When the Employee Is on the Other Side of the Border.

Next step

Fairlight prepares the cross-border hiring program — role PE screens and offer-letter drafting, EOR selection and tripartite contract review, build-out of native payroll and benefits at conversion, and the totalization postures for hires versus transfers. See cross-border pricing or book a call.