How does using an EOR in Nepal impact our company's tax obligations and permanent establishment risk?

You've found the right talent in Nepal. The hire makes strategic sense. But before you move forward, your CFO wants to know exactly what tax exposure this creates for your UK or EU-headquartered company. It's the right question to ask, and the answer is more nuanced than most EOR providers will tell you.

Using an Employer of Record in Nepal shifts payroll tax compliance to the EOR as the legal employer, but it does not automatically eliminate your company's corporate tax nexus or permanent establishment risk. The distinction matters because PE risk is driven by your company's business activities and authority to bind contracts in Nepal, not simply by who runs the payroll. Teamed's GEMO approach treats PE risk as a governance and operating-model issue rather than a payroll issue, because the highest-impact PE triggers usually sit in contracting authority, revenue generation, and local management conduct.

Let's break down what actually changes with an EOR in Nepal, what stays the same, and how to structure roles to keep your tax position clean.

What actually changes when you use an EOR in Nepal

Nepal's corporate tax sits at 25% for most companies, though specific sectors get different treatment.

Your EOR becomes the legal employer in Nepal. They handle payroll, tax withholding, and all the statutory paperwork. You manage the actual work.

PE risk comes from what your company does in Nepal and who can bind it to deals, not from who signs the employment contract.

If someone in Nepal regularly negotiates your deals or plays the key role in closing them, you've likely got a dependent agent PE. The test is whether they're acting for you, not independently.

EU tax authorities expect 5-10 years of documentation. When they audit, they'll want to see your PE analysis and payroll positions, so keep everything.

HMRC can look back 6 years for carelessness regarding PAYE and NI issues, or up to 20 years for deliberate behaviour.

What tax obligations does an EOR handle in Nepal?

An Employer of Record in Nepal takes on the legal employer responsibilities for your workers, which means they handle payroll withholding, employment tax remittance, and statutory compliance documentation. The EOR withholds income tax from employee salaries and pays it to Nepal's tax authority on the employee's behalf under local rules. They also manage social security contributions at 31% of basic remuneration split between employer and employee, along with mandatory benefits administration.

This arrangement means your company doesn't need to register as an employer in Nepal or navigate the local tax filing requirements directly. The EOR maintains the employment agreements, processes monthly payroll, and ensures compliance with Nepal's labour regulations. For mid-market companies testing a new market or hiring their first few employees in Nepal, this removes significant administrative burden and compliance risk from the employment relationship itself.

But here's what most EOR providers won't emphasise: the EOR's role is limited to employment tax compliance. Your company's potential corporate tax obligations in Nepal operate on an entirely separate track, and if you trigger PE status, Nepal levies 5% tax on income sent abroad by foreign permanent establishments.

Does using an EOR eliminate permanent establishment risk?

No. Using an EOR in Nepal reduces but does not eliminate permanent establishment risk because PE is determined by your company's in-country business activities and authority to bind, not solely by who employs the worker. This is the critical distinction that separates payroll compliance from corporate tax exposure.

Permanent establishment under domestic law and tax treaties can treat your foreign company as having a taxable business presence in Nepal when you have a fixed place of business or a dependent agent that habitually concludes contracts there. The EOR handles the employment relationship, but if your Nepal-based employee is negotiating deals, signing customer contracts, or making pricing decisions on your behalf, you may be creating PE regardless of who signs their payslip.

The dependent agent PE test focuses on contract conclusion and the principal role leading to it rather than headcount alone. A single sales representative with authority to commit your company to customer agreements creates more PE risk than a team of ten back-office support staff who have no contracting authority whatsoever.

What triggers dependent agent permanent establishment in Nepal?

A dependent agent permanent establishment typically arises when your Nepal-based personnel habitually negotiate or conclude contracts on your company's behalf, or play the principal role leading to contract conclusion. The key word is "habitually" because occasional activity may not meet the threshold, but regular patterns of contract-related behaviour will draw scrutiny.

The activities that create the highest PE risk profile include sales and contract negotiation, pricing authority, customer relationship management where the local person makes binding commitments, and signing contracts on behalf of the foreign company. Back-office roles like customer support, technical assistance, or administrative functions carry significantly lower PE risk because they don't involve the authority to bind your company to commercial agreements.

For UK-headquartered groups, creating a local signing authority in Nepal for customer contracts can materially increase PE risk under dependent agent concepts. Contracting authority should be reserved to UK or EU officers and implemented through signature policies and deal desk processes. This isn't about the EOR arrangement at all. It's about how you structure your Nepal-based employee's role and authority.

How should you structure roles to minimise PE risk?

The most effective PE risk mitigation comes from documented limits on authority rather than the employment structure itself. When any Nepal-based worker interacts with customers or vendors, you need a contracting authority matrix that explicitly restricts their ability to bind your company.

Consider a hypothetical mid-market company hiring a business development representative in Nepal through an EOR. If that representative can negotiate pricing, agree to contract terms, or sign customer agreements, the company has created dependent agent PE risk regardless of the EOR arrangement. But if the same representative is limited to lead generation, relationship building, and scheduling calls with UK-based sales leadership who handle all negotiations and contract execution, the PE risk profile changes dramatically.

Teamed's compliance playbooks for EOR governance standardise "no authority to bind" controls because restricting contract-signing and negotiating authority is one of the most repeatable ways to reduce dependent agent PE risk in practice. The EOR service agreement should explicitly allocate employment, payroll, and compliance responsibilities while your internal policies restrict local authority to bind the company.

What documentation do you need to defend your PE position?

When tax authorities test PE assertions during corporate tax audits, they apply "substance over form" analysis. This means contractual labels like "no authority to bind" are less persuasive if emails, signatures, or meeting notes show the person effectively negotiated or committed the business. Your documentation needs to demonstrate that the reality matches the contractual position.

The governance blueprint should link your EOR agreement, client-side signature policy, and deal desk controls into one audit-ready pack. You need clear evidence that Nepal-based personnel don't have authority to conclude contracts, that all customer agreements are signed by authorised officers outside Nepal, and that pricing and commercial terms are set by headquarters rather than local staff.

For UK companies, Companies House and HMRC governance expectations mean boards are expected to evidence reasonable procedures and risk oversight. PE and tax governance for EOR hiring should be captured in board minutes, risk registers, and delegated authority policies. This isn't bureaucracy for its own sake. It's the evidence trail that protects you when questions arise.

When should you choose an EOR versus establishing an entity in Nepal?

Choose an EOR in Nepal when you need to hire and pay employees compliantly without registering a local entity and you can keep contracting, pricing, and revenue-acceptance decisions outside Nepal. This structure works well for support roles, technical staff, and positions where the employee doesn't need authority to bind your company commercially.

Choose an owned Nepal entity when you need local executives with authority to sign customer or supplier contracts, bid for tenders, open local bank facilities, or hold local licences that cannot be practically operated through third parties. At this point, you're not avoiding PE. You're accepting it and structuring appropriately.

The Graduation Model that Teamed uses guides companies through this progression from contractor to EOR to entity as headcount, revenue impact, and local risk increase. The model is designed to keep your employment structure aligned to tax, cost, and compliance realities rather than staying in one structure indefinitely because changing seems complicated.

Teamed typically sees mid-market groups underestimate their internal time cost of multi-country employment administration. The Graduation Model planning reduces rework by anticipating when EOR will need to graduate to an entity as activities become commercial and locally embedded.

What about contractor arrangements versus EOR?

Choose a contractor arrangement rather than EOR only when deliverables are project-based, the individual has genuine business independence, and you can evidence autonomy in working time, methods, and substitution rights under Nepal-appropriate contracting practices. The control factors matter enormously here.

Choose an EOR rather than a contractor model when the worker will be managed like an employee with set working hours, ongoing supervision, company equipment, and integration into internal teams. These control factors increase misclassification risk, and the consequences of getting it wrong include back taxes, penalties, and potential employment claims.

EOR means proper employment with all the protections and deductions. Contractor means invoices and hoping you've classified them right. One shifts risk to the EOR, the other keeps it with you.

How does this affect UK-headquartered companies specifically?

UK-headquartered groups should assess whether Nepal-based personnel create UK transfer pricing and corporate tax documentation needs because cross-border related-party service arrangements and cost allocations can be examined even when staff are employed through an EOR. The tax authority's interest extends beyond whether you have PE in Nepal to how you're pricing intercompany arrangements.

UK IR35 off-payroll working rules require medium and large businesses to make and document contractor status determinations for UK tax purposes. Poor governance can create back-tax exposure even when the worker is overseas. If you're engaging anyone in Nepal as a contractor rather than through an EOR, the IR35 analysis still applies.

For regulated UK industries, storing HR and payroll records that include special category data may trigger UK GDPR controller-processor due diligence on the EOR, including documented data processing agreements and cross-border transfer safeguards. EU and UK anti-bribery and sanctions compliance programmes should extend to Nepal EOR arrangements through third-party due diligence because the EOR and any local partners are part of the controlled third-party chain even when there is no local entity.

What should finance teams understand about EOR costs?

EOR pricing for mid-market employers commonly consists of a fixed monthly fee per employee plus pass-through statutory costs. Teamed advises finance teams to model total landed employment cost rather than headline fees to avoid budget variance from FX margins, levies, and off-cycle payroll.

The Three Layers of Opacity in EOR spend include hidden FX margins, bundled compliance fees, and undisclosed in-country partner markups. Few sources address finance visibility on these costs, so ask your EOR provider for a line-item breakdown that separates their fee from pass-through costs and identifies any FX markup applied to local currency payments.

From a CFO controls perspective, an EOR model is usually easier to budget as an operating expense line than an entity build-out, but it can be harder to optimise at scale because per-employee fees persist even as headcount grows. The economics shift as your Nepal team expands, and the right structure today may not be the right structure in two years.

The bottom line on Nepal EOR and tax exposure

Using an EOR in Nepal handles your employment tax compliance effectively. It doesn't handle your corporate tax exposure. The two are separate issues that require separate governance approaches.

If your Nepal-based employees are performing back-office functions without authority to bind your company commercially, the EOR structure works well and your PE risk is low. If those same employees are negotiating deals, setting prices, or signing contracts, you have PE risk regardless of the EOR arrangement, and you need to either restructure their roles or accept that you're creating taxable presence.

The right structure for where you are depends on what your Nepal-based team actually does, not just how many people you have there. If you're unsure whether your current setup creates PE exposure, or you're planning to expand your Nepal presence and want to get the structure right from the start, book your Situation Room with Teamed. We'll review your specific situation and tell you what we'd recommend, whether that includes us or not.