Novosibirsk · Russian-qualified counsel Recognised by Pravo-300 · Best Lawyers · Kommersant
Armenia · Corporate & Regulatory

Compliance checklist: competition law and merger clearance in Armenia in the technology and software sector

Anahit Sargsyan · June 2026 · 9 min read

Foreign tech companies entering Armenia face SCPEC filing requirements and EAEU overlap. Six-step compliance checklist. Make an enquiry.

Foreign technology and software companies pursuing acquisitions, joint ventures, or market-entry transactions in Armenia must navigate two parallel competition regimes before completion: the domestic framework administered by the State Commission for the Protection of Economic Competition (SCPEC), and the supranational layer arising from Armenia's membership of the Eurasian Economic Union (EAEU). Both regimes can require prior approval, both carry the risk of a transaction being declared void if clearance is bypassed, and the interaction between them is not always intuitive for counsel accustomed to EU or US merger control practice. This six-item checklist sets out the threshold questions, filing requirements, substantive assessment standards, and post-clearance obligations that foreign technology companies should address before completing a transaction with an Armenian dimension.

1. Determine whether the transaction meets the SCPEC prior-approval threshold

The starting point for any competition clearance analysis in Armenia is whether the transaction triggers the mandatory prior-approval requirement under Armenian competition legislation. Prior approval from the SCPEC is required when a concentration — defined broadly to include acquisitions of controlling interests, mergers, and certain asset purchases — involves parties whose combined assets or turnover on the Armenian market exceed the thresholds set by the SCPEC and, where applicable, by Government decree.

For technology and software companies, the asset threshold is frequently the operative measure, since revenue on the local Armenian market may be modest even where the acquirer is a large multinational. The threshold test examines the Armenian-market presence of both parties: if neither party generates meaningful turnover or holds registrable assets in Armenia, the domestic filing obligation may not arise. However, counsel should not assume this without a documented analysis, because the SCPEC has taken an expansive view of "assets" in the technology sector to include locally registered intellectual property rights, server infrastructure, and Armenian-entity equity interests.

Note: A transaction completed without required SCPEC prior approval is liable to be declared void under Armenian competition legislation. The SCPEC may also impose administrative liability on the controlling persons of the parties. This is not a curable defect after the fact — the only reliable remedy is pre-completion filing.

2. Assess EAEU-level competition review exposure

Armenia has been a member of the EAEU since 2015, and the EAEU Treaty — together with its Protocol on Competition Policy — creates a supranational merger control regime administered by the Eurasian Economic Commission (EEC) in Moscow. The EEC's jurisdiction covers concentrations where the combined worldwide assets or turnover of the parties exceed the EEC thresholds and where the transaction affects competition in two or more EAEU member states.

For technology companies, the EEC filing obligation is most likely to arise in three situations: (a) the acquirer already has operations in Russia, Kazakhstan, or Belarus, and the target has an Armenian presence; (b) the target provides software or digital services distributed across multiple EAEU jurisdictions under a single entity or through affiliated distributors; or (c) the transaction involves the acquisition of IP rights that are registered in, or exclusively licensed to, entities in more than one EAEU member state.

Where both the SCPEC and the EEC have jurisdiction, the EAEU Protocol provides that EEC clearance takes precedence — but this does not mean the domestic filing is automatically dispensed with. Counsel should seek confirmation of the applicable sequencing with the SCPEC directly, since practice on this coordination point has not always been consistent.

Note: The EEC review period is up to 45 calendar days, extendable by a further 90 days in complex cases. A transaction subject to EEC jurisdiction that proceeds without approval is similarly void and may attract supranational penalties.

3. Evaluate market-definition and dominance risk in the technology sector

Even where a transaction does not meet the prior-approval thresholds, it may still trigger SCPEC scrutiny if it creates or strengthens a dominant position on the Armenian market. Under Armenian competition law, a company (or group of affiliated companies) holds a dominant position where its market share exceeds the threshold level set by the SCPEC, and the SCPEC has consistently applied a market-share analysis in technology and software sector investigations.

For foreign technology companies, the relevant market question requires care. The SCPEC will define the geographic market as Armenia (or a sub-national region), regardless of the fact that the acquirer's platform or software may be globally distributed. The product market in technology matters is typically defined narrowly: separate relevant markets have been identified for enterprise software licensing, cloud infrastructure services, payment processing, and e-commerce platforms in prior SCPEC assessments. A transaction that appears to involve parties with low combined shares nationally may nonetheless create a locally dominant position in a narrowly defined product segment.

Companies should conduct a preliminary market-share analysis using available Armenian market data — sector reports, SCPEC published decisions, and data from the Statistical Committee of the Republic of Armenia — before concluding that the transaction is dominance-risk-free.

4. Prepare and file the merger notification dossier

Where prior approval is required, the notification dossier submitted to the SCPEC must contain prescribed information about the parties, the transaction structure, and the competitive effects. For technology and software companies, the dossier typically includes: a description of the parties' products and services and their distribution in Armenia; an explanation of the transaction rationale; financial data showing Armenian-market revenues and assets; a description of existing contractual relationships between the parties in Armenia (including licensing and distribution agreements); and, where relevant, information on intellectual property registrations in Armenia.

The SCPEC may request supplementary information at any stage of its review. Failure to respond to an information request within the stipulated timeframe can suspend the review clock and, in practice, significantly extend the overall clearance timeline. Counsel should designate a named point of contact within the filing entity — or a locally authorised representative — for the duration of the SCPEC review.

Note: The standard SCPEC review period for merger notifications is 30 calendar days from the date of receipt of a complete dossier. If the SCPEC determines that a more detailed review is warranted — which is more likely in technology sector matters involving novel market definitions or potential dominance concerns — the period may be extended by a further 60 days. Budget for a realistic 90-day clearance timeline when structuring transaction documents and conditions precedent.

5. Manage the SCPEC review process and conditions of approval

The SCPEC may approve the transaction unconditionally, approve it subject to behavioural or structural conditions (similar in concept to EU merger remedies), or prohibit it. In the technology sector, behavioural conditions have included requirements to maintain interoperability with competing platforms, caps on exclusive licensing arrangements, and data-sharing obligations with Armenian competitors.

During the review period, the parties should monitor the SCPEC docket and be prepared to respond promptly to any request for a hearing or supplementary submissions. Third-party competitors in the Armenian technology market may submit observations during the review, and the SCPEC is required to take these into account. Counsel should assess the third-party competitive landscape early and anticipate the objections most likely to be raised.

Where conditions are imposed, the approval order will specify compliance milestones and reporting obligations. Non-compliance with conditions — even technical or administrative non-compliance — may result in the approval being revoked and the transaction being revisited as an unclearanced concentration.

6. Post-clearance compliance obligations for technology companies

SCPEC approval and, where applicable, EEC approval do not extinguish competition law exposure for the combined entity. Post-completion, the technology company operating in Armenia is subject to the full range of Armenian competition law obligations, including prohibitions on abuse of dominance, restrictions on anti-competitive agreements, and SCPEC market-monitoring powers.

Technology companies with a dominant position in an Armenian product market should establish an ongoing competition compliance programme that covers: pricing practices and margin-squeeze risk; exclusivity provisions in reseller, distributor, and licensing agreements; interoperability and access obligations where these were conditions of merger clearance; and data practices that may constitute a barrier to competitive entry under the SCPEC's evolving approach to digital market analysis.

The SCPEC has, in recent periods, increased the frequency and depth of sector-specific inquiries into technology markets. Companies that operate in payment processing, cloud services, and enterprise software segments should treat competition compliance as a recurring governance item rather than a transaction-specific exercise.

Frequently asked questions

Q: What is the SCPEC and what authority does it have over foreign technology companies in Armenia?

A: The State Commission for the Protection of Economic Competition is the independent Armenian regulatory body responsible for enforcing competition law, including merger control. Its authority extends to any transaction or commercial practice that affects the Armenian market, regardless of where the parties are incorporated. A foreign technology company that acquires an Armenian entity, purchases assets located in Armenia, or obtains IP rights registered in Armenia may fall within SCPEC jurisdiction even if neither party has a physical presence in the country. The SCPEC has the power to approve, condition, or prohibit transactions within its jurisdiction and to declare unclearanced concentrations void.

Q: Do EAEU merger thresholds always require a filing with the Eurasian Economic Commission in addition to the SCPEC?

A: No. EAEU-level merger control applies only where the transaction meets the supranational asset or turnover thresholds set out in the EAEU Protocol on Competition Policy, and where the transaction affects competition in two or more EAEU member states. Many technology company transactions with an Armenian nexus will not meet the EAEU thresholds — particularly where the acquirer's operations are confined to a single EAEU jurisdiction or where the target operates exclusively in Armenia. The analysis requires a transaction-specific assessment of where the parties generate turnover and hold assets across all five EAEU member states (Armenia, Russia, Kazakhstan, Belarus, and Kyrgyzstan).

Q: What are the main risks of proceeding with an Armenian acquisition without checking competition clearance obligations?

A: The primary legal risk is that a transaction requiring SCPEC or EEC prior approval, if completed without that approval, is void under applicable law — meaning the transfer of ownership or control has no legal effect. Beyond voidness, the SCPEC may impose administrative liability on the parties and their controlling persons, order the unwinding of a completed transaction, and impose conditions on any retrospective approval application. In the technology sector, where acquisitions often involve IP transfers or platform integration steps that are difficult to reverse, the practical consequences of a void transaction can be severe. A preliminary threshold assessment — which typically requires no more than basic financial and structural information — is the appropriate first step before any transaction proceeds to documentation.

Practitioner note

This briefing is general information and does not constitute legal advice. For advice on a specific matter, write in confidence to info@vetrovpartners.com.

Facing a matter like this?

Our team advises foreign clients on exactly these questions across Russia and the EAEU region. Initial 30-minute consultation — complimentary.

Make an enquiry