How does permanent establishment risk work in Armenia?

Armenia maintains double-tax treaties with over 40 countries, most following the OECD Model Tax Convention. When a treaty applies, the PE analysis follows OECD Articles 5 and 7: does the foreign company have a taxable presence, and what profits are attributable to it?

If a PE is triggered, Armenia's State Revenue Committee (SRC) gains the right to tax the profits attributable to that PE. The foreign company must:

• Register with the SRC for Armenian profit tax purposes
• File annual Armenian profit tax returns attributing profits to the Armenian PE
• Maintain Armenian accounting records sufficient to support that attribution
• Pay Armenian profit tax at the applicable rate on attributable profits

Armenia's standard corporate profit tax rate is 18%. That is the headline cost. The overhead of Armenian accounting books, transfer-pricing analysis, and SRC enquiries adds to that. For companies that discover PE exposure retroactively, interest and penalties apply to the period of unregistered activity.

Under the OECD commentary and Armenian treaty interpretation, a fixed place of business requires three elements:

1. A place of business: premises, facilities, or machinery
2. That is fixed: in a specific geographical location, with a degree of permanence
3. Through which the business of the enterprise is wholly or partly carried on

The bar for 'at the parent's disposal' is often lower than companies expect. A regularly-used home office, a co-working desk used most working days, or a short-term serviced office can all qualify if the pattern is consistent and the work performed there is the parent's core business activity rather than preparatory or auxiliary support.

The activity exemption

Some activities do not count even if conducted through a fixed place. These are activities that are 'preparatory or auxiliary' in character. Classic examples include storage facilities, purchasing offices, and information-gathering functions. Post-2017 OECD anti-fragmentation rules tightened this considerably. The SRC now reads 'preparatory or auxiliary' narrowly, and deliberately splitting activities across locations to stay below the threshold is unlikely to succeed if the overall function is core business activity.

In Armenia's context, the post-2022 influx of tech talent means many foreign companies rent co-working spaces or small offices for teams that grew beyond individual home offices. That transition from a scattered home-office setup to a shared team space is often the moment a fixed-place PE crystallises without the parent noticing.

Before 2017, companies sometimes argued: 'our Armenian person does not conclude contracts; they only introduce prospects and headquarters signs.' Post-2017, that defence largely fails. If the Armenian person plays the principal role in bringing a deal to the point of signature and headquarters simply confirms, the Armenian person is treated as the dependent agent.

What principal role looks like in practice

• Pitching to Armenian or regional clients, presenting commercial terms, and leading negotiations
• Setting material commercial provisions (price, scope, delivery) that headquarters does not routinely alter
• Holding out as the customer's main point of contact for contract-related questions
• Customer-facing job titles such as 'Armenia Country Manager', 'Head of CIS Sales', or 'Regional Director Caucasus'

The independent-agent carve-out

The PE rules do not apply to agents acting in the ordinary course of their own independent business. A genuine third-party Armenian distributor is not a dependent agent. An EOR sits in a more complicated position. Teamed's partner entity in Armenia is legally independent and commercially separate. But the Armenian employee's day-to-day work arrangement is with the foreign parent, not with the partner entity's own business operations. That distinction matters in the SRC analysis.

One Armenia-specific consideration is the regional sales role. Many foreign companies hire an 'Armenia-based' commercial lead whose territory actually covers several CIS markets. That regional scope does not reduce the dependent-agent risk in Armenia; it may compound it if the employee is concluding contracts with Armenian and Georgian clients from the same Yerevan base.

EOR helps in three specific ways:

1. The legal employer is an Armenian entity, so payroll, employee-side taxes, and pension contributions flow through a locally-registered company
2. The contract chain is 'parent to EOR partner to employee', not 'parent to employee directly', which gives some treaty-analysis room on the attribution question
3. EOR-employed Armenian staff do not hold formal authority on the parent's legal entity (they cannot bind the parent as a director or officer)

What EOR does not fix:

• If the Armenian employee functionally concludes contracts for the parent (presenting, negotiating, setting terms), the dependent-agent test still triggers regardless of who the employment contract is with
• If the Armenian employee operates from a fixed location rented or paid for by the parent (rather than the EOR or the employee personally), the fixed-place test still applies
• If customer-facing materials describe a Yerevan presence as 'our Armenia office' or the Armenian employee as part of the parent's local operations, the SRC will read that as PE evidence

EOR is appropriate cover for back-office, engineering, product, design, marketing operations, and support roles where the Armenian hire is part of the global team rather than a commercial presence. EOR is not appropriate cover for sales, business development, country management, or customer-success-with-commercial-authority roles where the hire is the parent's face to Armenian or regional clients.

1. The post-2022 tech-team scale-up with a shared office. A company starts with two or three engineers working from home. They grow to ten or fifteen and rent a co-working space or small office, which the parent pays for. The fixed-place PE crystallises at the point the parent-paid location becomes consistent and the team's work is the parent's core product development, not a preparatory function.
2. The CIS sales lead based in Yerevan. Armenia became a convenient base for regional commercial roles after 2022. A 'CIS Sales Director' or 'Regional Head of Growth' based in Yerevan and selling to clients across the region is almost always a dependent agent under the post-2017 BEPS rules, wherever the contracts are formally signed.
3. The 'Armenia office' on the website or in sales materials. Even without a formal lease, describing a Yerevan presence as 'our Armenia office' or listing an Armenian address on the parent's website creates fixed-place evidence that the SRC will use if it opens an enquiry.
4. The customer-success or account-management hire with renewal authority. A hire described as managing Armenian or regional client relationships, with authority to quote renewals or expand scope, sits squarely in the dependent-agent risk zone. The fact that a different team member in headquarters countersigns does not fix the problem post-2017.

Low-risk patterns in our experience: Armenian engineers building product for the global team with no client-facing role; Armenian designers contributing to global brand work; Armenian support agents handling tickets for a global user base rather than a specifically Armenian one; Armenian finance or ops hires in internal roles with no external commercial authority.

Step 1: honest assessment

For each Armenian hire, ask: does this person have customer-facing commercial authority? Do they operate from a fixed location the parent pays for? How would the SRC characterise the role if they read the job description and the customer-facing materials? Most PE risk is foreseeable from the hiring brief. The post-2022 wave of Armenia hires means many companies made these decisions quickly, under pressure, without the PE question on the checklist.

Step 2: tax memo

A short PE-risk memo from an Armenian-qualified tax adviser gives you a defensible position with the SRC. Fees vary depending on the complexity of the engagement, but are typically a fraction of the tax exposure they address. The memo does not bind the SRC. But it is strong evidence of reasonable care if the SRC challenges, and it matters to the penalty position on any backdated assessment.

Step 3a: structure to avoid

If the activities can be done without triggering PE, most operational, engineering, and support roles can, structure the engagement accordingly. EOR through a partner entity, no parent-paid Armenian office, no Armenian customer-facing commercial authority, and working arrangements consistent with a remote member of a global team rather than a local presence of the parent company.

Step 3b: incorporate an Armenian entity

If the activities genuinely require a commercial Armenian presence, or if the parent wants the brand equity of a named Armenian operation, the right answer is the parent's own Armenian LLC or JSC. The PE becomes explicit and controlled rather than accidental, and the profit attribution analysis runs on the parent's terms rather than the SRC's.

1. Assess each hire honestly

   For every Armenian hire, check whether the role has customer-facing commercial authority and whether it operates from a location the parent pays for. Most PE risk is visible from the hiring brief.

2. Get a tax memo

   Commission a short PE-risk memo from an Armenian-qualified tax adviser. It gives you a defensible position with the SRC and matters significantly to any penalty calculation if the SRC challenges.

3. Structure to avoid or incorporate

   Either shape the engagement to stay outside the fixed-place and dependent-agent tests, using EOR with no parent-paid office and no commercial authority, or incorporate an Armenian entity and accept the PE on your own terms.

real HR and legal experts handle your Armenian hires, from the first offer letter through every SRC payroll filing and pension contribution. an actual person, not a chatbot or a pooled queue. There is no setup fee and no exit fee. Employer cost passes through at cost, itemised on every invoice.

Start small with EOR, then graduate to your own Armenian entity when the team size makes it worth it, until it isn't worth staying on EOR. EOR payroll, contractor onboarding, and entity setup all live on one platform. Run the Crossover Calculator to see the month the model flips from EOR to a owned Armenian entity. Start from the Armenia hiring overview; each guide here takes one layer of Armenian employment law.

Key sources: State Revenue Committee of Armenia: tax legislation and Vardanyan and Partners: payroll and employment law guidance.