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

A practical guide to related-party transaction approval under Russian corporate law for Emirati shareholders

Stanislav Lastovsky · October 2026 · 10 min read

Emirati shareholders in Russian companies face strict related-party approval rules. Understand the Russian corporate law framework. Make an enquiry.

Unlike the UAE's related-party framework — which centres on board-level disclosure and audit committee sign-off — Russian corporate law imposes a parallel procedural track that can require formal approval by disinterested participants or shareholders before a transaction closes. For Emirati companies holding stakes in Russian limited liability companies or joint-stock companies, this divergence is a practical governance challenge, not merely a technical one. Transactions that would be unremarkable under UAE governance practice may, under Russian corporate legislation, require advance notification, shareholder consent, or both — and a transaction concluded without the required approval is voidable under Russian law at the suit of any participant or shareholder.

This guide sets out the approval steps that Emirati shareholders and their in-house counsel should follow when their Russian entity proposes to enter a related-party transaction. It covers the threshold determination, the notification and approval mechanics, the documentation standard, and the risk of non-compliance.

Step 1. Determine whether the transaction falls within the related-party rules

The first step is identifying whether the proposed transaction meets the statutory definition of a related-party transaction under Russian corporate legislation. Russian law uses the concept of an "interested party" — broadly, any person who, by reason of their position, ownership, or affiliation, has an interest in the outcome of the transaction distinct from that of the company itself.

In an LLC context, interested parties typically include participants holding significant stakes, members of the management board or supervisory board, the sole executive (general director), and their close relatives or affiliated persons. In a JSC, the same categories apply at board and executive level, with share ownership thresholds determining whether a controlling shareholder qualifies.

For Emirati shareholders, two scenarios recur in practice. First, where the Emirati entity itself is the counterparty to the transaction — for example, a service agreement, a loan, or an asset sale between the Russian subsidiary and its UAE parent. Second, where a director or officer of the Russian entity is also connected to the counterparty through a separate corporate or personal relationship. Both scenarios engage the related-party rules, but the procedural consequences differ.

What to prepare before the approval process begins

The following documents and confirmations should be assembled before initiating any notification or approval procedure:

If you are assessing whether a proposed transaction requires approval — make an enquiry: info@vetrovpartners.com |

Step 2. Notify the disinterested participants before the transaction closes

Following the 2017 reform of Russian corporate legislation, the prior-approval model was largely replaced by a notification-based approach for standard related-party transactions. The company is now required to notify all disinterested participants or shareholders of the proposed transaction before it is concluded.

The notification must include sufficient information to allow a recipient to assess the transaction: the nature and subject matter of the proposed deal, the counterparty's identity, the proposed financial terms, and the identity of the interested party or parties. Russian courts have scrutinised the adequacy of notifications — a notification that is vague on material terms does not satisfy the statutory obligation.

Timing is critical. The notification must be dispatched before the transaction is signed or otherwise concluded. Backdated notifications, or notifications delivered simultaneously with execution, do not satisfy the requirement and leave the transaction exposed to challenge. For Emirati shareholders managing governance across time zones, this means the notification step must be built into the transaction timetable explicitly, with confirmation of despatch documented.

Note: If a disinterested participant or shareholder holding at least one per cent of the charter capital requests prior approval following receipt of the notification, the company must convene an approval procedure before the transaction can proceed. Failure to do so renders the transaction voidable — a risk that is particularly acute in joint ventures where minority participants are commercially adverse to the majority.

Step 3. Obtain prior approval where it is required

Prior approval by a meeting of disinterested participants or shareholders is mandatory in specific circumstances — most significantly, when any disinterested participant or shareholder of the threshold holding formally requests it after receiving the notification described in Step 2. It is also required where the company's articles of association impose prior approval as a standing requirement for categories of related-party transaction.

The approval resolution must be adopted by the disinterested participants or shareholders only — interested parties are excluded from the vote. For Emirati majority shareholders who are themselves the interested party, this means the approval decision rests entirely with the minority. In practice, this is the governance moment that carries the highest risk of deadlock, particularly in joint ventures formed with Russian partners who hold minority positions.

The resolution must adequately describe the transaction — parties, subject matter, value, and material terms. An approval resolution that describes the transaction in general terms may not protect against a subsequent challenge if the transaction as executed differs materially from what was approved. General pre-approvals covering a category of transactions are permitted in limited circumstances under Russian corporate legislation, but their scope is narrowly construed by Russian courts.

For in-house counsel, the practical implication is that each related-party transaction should be assessed separately. Bundling distinct transactions into a single approval resolution, or relying on a prior general authorisation, carries a litigation risk that is difficult to quantify in advance.

If you are managing a joint venture where minority participants hold approval rights — request our practice review: info@vetrovpartners.com |

Step 4. Document the approval process correctly

Documentation of the notification and approval process is as important as the process itself. Russian courts examining a challenge to a related-party transaction will look first to the company's records — the notification despatch log, the response (or non-response) from disinterested participants, and the minutes of any approval meeting.

The notification should be sent by a traceable method: registered post to the participant's address of record, or electronic delivery where the articles of association or a shareholder agreement expressly permits it. For a UAE-based shareholder, electronic delivery to a confirmed address is the practical default, but this must be explicitly authorised in the company's governing documents.

Approval meeting minutes must be signed by the chairperson and, where required by the articles, by a notary or an independent registrar. For JSCs with more than fifty shareholders, the involvement of a registrar is typically required by law. For LLCs, notarisation of the minutes is the statutory default unless the articles specify an alternative confirmation method — a provision that many companies overlook until a dispute arises.

The complete approval file — notification, evidence of despatch, any responses received, and the approval resolution — should be retained for at least three years, which corresponds to the standard limitation period under Russian civil law for voidability challenges. The clock runs from the date the claimant learned or should have learned of the violation, not from the date of the transaction itself, so effective document retention is not merely good practice but a defence asset.

Step 5. Verify the company's articles and any shareholder agreement

The statutory rules on related-party transactions under Russian corporate legislation set a floor, not a ceiling. Emirati shareholders should confirm whether the company's articles of association (ustav) contain provisions that are more restrictive than the statutory baseline — for example, lower ownership thresholds for triggering the approval requirement, a broader definition of interested parties, or mandatory prior approval for all related-party transactions regardless of value.

Similarly, any shareholder agreement governed by Russian law may impose additional procedural steps — supermajority requirements, veto rights for minority participants, or reporting obligations to the supervisory board. Where the shareholder agreement is governed by foreign law, its interaction with the mandatory provisions of Russian corporate legislation should be assessed separately, as Russian law restrictions on related-party transactions apply by operation of law regardless of what the parties have agreed contractually.

For Emirati shareholders who entered the Russian entity through a UAE holding structure or via a Cyprus or other intermediate holding company, the position of the intermediate holding in the "interested party" analysis should also be confirmed. In practice, Russian courts have treated transactions involving a chain of affiliates as engaged by the related-party rules even where the direct counterparty is not itself a participant in the Russian entity.

The firm's Corporate Governance practice advises foreign shareholders on structuring and governance matters of this nature. For a comparative analysis of the Russian framework against other jurisdictions, see our comparative analysis of related-party transaction regimes. For background on recent court interpretation, see our note on the Russian Supreme Court's clarification on related-party transactions.

If you are reviewing your company's articles or shareholder agreement for related-party compliance — make an enquiry: info@vetrovpartners.com |

Frequently asked questions

Q: How long does the related-party transaction approval process typically take in a Russian LLC?

A: The timeline depends on whether prior approval is requested by a disinterested participant. If no prior approval request is made, the process reduces to issuing and documenting the pre-transaction notification — this can ordinarily be completed within five to ten business days, allowing time for confirmed despatch and any waiting period specified in the articles. Where prior approval is required, the timeline extends to include convening a general meeting of disinterested participants, which under Russian corporate legislation typically requires notice of at least ten days (or a longer period if specified in the articles). In practice, including document preparation, meeting logistics, and notarisation of minutes where required, allow four to six weeks for a contested or complex approval.

Q: What documents does the company need to prepare for the notification to disinterested participants?

A: The notification must contain the identity of the counterparty, the subject matter of the proposed transaction, its financial terms, and the identity of the interested party or parties. Supporting documents typically include a draft of the transaction agreement or term sheet, the company's current participant register, and any valuation or appraisal where the transaction involves an asset transfer or a loan above a material threshold. For Emirati shareholders participating remotely, the notification package should also include a translation into the language used in the shareholder agreement if that document requires notifications in a specified language.

Q: What is the consequence of proceeding with a related-party transaction without following the required approval process?

A: A related-party transaction concluded in breach of the notification or approval requirements is voidable under Russian corporate legislation. Any participant or shareholder — including a minority participant — may bring a claim to void the transaction before a Russian arbitrazh court. The limitation period runs from the date the claimant knew or should have known of the breach, which courts have construed broadly. If the transaction is voided, the parties are required to restore the pre-transaction position, which in cross-border transactions involving an Emirati counterparty can create significant practical difficulty. The financial loss resulting from an unwinding order may exceed the original transaction value where currencies, assets, or market conditions have moved materially. This is the primary reason that Emirati shareholders should treat the approval procedure as a compliance baseline rather than an optional formality.

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