Foreign creditors pursuing Russian tech assets via letters rogatory face distinct procedural hurdles. A practical step-by-step guide. Make an enquiry.
In nearly fifteen years of advising foreign creditors on Russian asset tracing and recovery matters, one instrument stands out for the frequency with which it is misunderstood: the international letter rogatory directed at Russian authorities. Foreign counsel routinely approach Russian courts or the Ministry of Justice expecting a procedural symmetry with Hague Evidence Convention machinery — only to discover that Russia has not acceded to that Convention, and that the applicable framework is treaty-specific, routed through diplomatic or central authority channels, and subject to domestic procedural rules that differ materially from Western assumptions. In technology and software disputes — where evidentiary targets include source code repositories, software licensing records, domain ownership data, and Rospatent filings — the procedural stakes are especially high. This guide sets out the steps a foreign creditor or its counsel should follow when initiating international letters rogatory directed at Russian authorities in a technology or software matter.
Creditors who arrive at the Russian end of the process without adequate preparation consistently encounter delays that can extend an already lengthy timeline by months. Before initiating the request, gather and organise the following:
For creditors whose matter involves intellectual property assets — registered software, database rights, or platform infrastructure — early coordination with the firm's Asset Tracing & Recovery practice is advisable before the request is drafted, not after.
If you are preparing an international letters rogatory request targeting Russian technology or software assets, make an enquiry before the documentation stage: info@vetrovpartners.com |
The first, and most consequential, step is identifying the treaty or convention that governs the request. Russia is not a party to the Hague Convention on the Taking of Evidence Abroad in Civil or Commercial Matters (1970). This means that the streamlined central authority mechanism familiar to practitioners in common law jurisdictions is not available for requests directed at Russian authorities.
The applicable legal basis will typically fall into one of three categories. First, a bilateral treaty on legal assistance in civil and commercial matters: Russia has concluded such treaties with a significant number of states, including many EU member states, China, and a range of CIS members. The treaty will define the scope of permissible requests, the language requirements, and the designated central authority on the Russian side — typically the Ministry of Justice of the Russian Federation. Second, the 1993 Minsk Convention on Legal Assistance and Legal Relations in Civil, Family and Criminal Matters, which applies between CIS member states and provides a working framework for cross-border evidentiary requests among those jurisdictions. Third, where no treaty applies, requests may be transmitted via diplomatic channels through the Ministry of Foreign Affairs — a route that, in practice, involves substantially longer processing times and a higher rate of non-response.
In technology and software matters, the treaty assessment must also account for the nature of the evidentiary target. Requests directed at Rospatent — the Federal Service for Intellectual Property — for software registration records or patent filings require identification of Rospatent's status as an executing authority under the relevant treaty. Not all bilateral treaties expressly address requests directed at administrative bodies rather than courts. Practitioners should verify this point before the request is drafted. See also the firm's comparative analysis of letters rogatory frameworks: Comparative analysis: international letters rogatory across key jurisdictions.
Drafting a letter rogatory that Russian authorities will accept requires adherence to both the formal requirements of the applicable treaty and the domestic procedural rules of the Russian Federation. Deficiencies at this stage are the single most common cause of rejection or non-execution.
The request must, as a general rule, include: the identity and jurisdiction of the requesting court or tribunal; the nature of the proceedings and the legal questions at issue; a precise description of the evidence or information sought; the identity of the parties to the proceedings; and the legal basis for the request, including the applicable treaty. For technology and software matters, the description of evidentiary targets warrants particular care. A request for "all records relating to the respondent's software" is unlikely to be executed; a request specifying "records of software licence agreements entered into by [named entity] between [date range], held by [named registrar or custodian], in connection with [identified product or platform]" has a materially higher chance of execution.
Authentication requirements vary by treaty. Most bilateral treaties require the letter to be signed by a judge of the requesting court and to bear the court's official seal. Some treaties additionally require legalisation or apostille. Russia is a party to the Hague Apostille Convention, and apostillised documents are generally accepted by Russian authorities in the absence of a treaty provision to the contrary.
The letter must be translated into Russian by a certified translator. Some bilateral treaties permit the requesting authority to attach translations in a second language (commonly English or French), but the Russian translation is invariably required. Costs of translation and authentication are typically borne by the requesting party.
Once drafted and authenticated, the letter rogatory must be transmitted through the channel specified by the applicable treaty. For most bilateral treaty requests, this means submission to the Ministry of Justice of the Russian Federation as central authority, either directly (where the treaty permits direct central authority-to-central authority transmission) or via the Ministry of Justice of the requesting state.
The Ministry of Justice will carry out a preliminary review of the request before transmitting it to the competent Russian court or administrative body for execution. This review is primarily formal: the Ministry checks completeness, translation, authentication, and treaty compliance. It does not assess the merits of the underlying claim. However, Russian law permits the executing authority to decline a request on public policy or sovereignty grounds — a provision that, in practice, is more frequently invoked in matters with a political or regulatory dimension than in straightforward commercial or technology matters.
Creditors who delay initiating the rogatory process risk losing access to critical digital evidentiary assets: in technology disputes, source code repositories, cloud-hosted records, and domain registrar data are inherently mobile, and a counterparty that is aware of foreign proceedings may migrate or delete data before execution is completed. This underscores the importance of initiating the process at the earliest opportunity — and, where interim preservation orders are available in the foreign proceedings, obtaining them before the rogatory request is transmitted.
After transmission, progress tracking is limited. Russian procedural rules do not provide a real-time status notification mechanism for foreign parties. In practice, the requesting party's counsel in Russia must maintain periodic contact with the Ministry of Justice's international cooperation department to monitor the status of the request.
For assistance monitoring the progress of a letters rogatory request or coordinating with the Russian Ministry of Justice, speak to our team: info@vetrovpartners.com |
Once the Ministry of Justice has transmitted the request to the competent Russian court or authority, the execution stage begins. In technology and software matters, the executing body is likely to be one of the following: an arbitrazh court (for commercial matters), Rospatent (for intellectual property registration records), a domain registrar or hosting provider (subject to their cooperation obligations under Russian law), or the Federal Tax Service (for corporate records of technology entities).
The arbitrazh court will schedule a hearing to consider the request. The parties to the Russian execution proceedings are typically the executing court, the Ministry of Justice, and — where the respondent entity is located in Russia — that entity. The foreign creditor does not participate as a party in the Russian execution proceedings, but may be represented by Russian counsel acting as an authorised representative of the requesting court, if the treaty so provides.
For requests targeting Rospatent records — which are common in technology and software matters involving contested software ownership, licence disputes, or parallel import issues — note that Rospatent maintains publicly accessible registers for registered software and databases. If the relevant records are already publicly accessible, a rogatory request may be unnecessary; Rospatent's online registry should be checked before initiating the full process. The firm's related briefing on Rospatent's guidance on international letters rogatory provides further detail: Rospatent issues guidance on international letters rogatory: implications for foreign IP owners.
Execution timelines in Russia vary widely. Under standard bilateral treaty frameworks, the executing authority is typically requested to complete execution within a period specified by the treaty — commonly three to six months. In practice, actual processing times frequently extend beyond this, particularly for requests that involve third-party custodians (such as software registrars or cloud platform operators) rather than court or government records. Budget for a total process of nine to eighteen months from initiation to receipt of executed materials, and communicate this realistically to the foreign court.
The final step is deploying the executed materials effectively in the foreign proceedings. This stage raises distinct questions that practitioners sometimes underestimate.
First, admissibility. Materials obtained via letters rogatory from Russian authorities will have been produced in Russian and authenticated according to Russian procedural rules. Foreign courts will require certified translations, and some jurisdictions require additional authentication before the materials can be adduced as evidence. This should be planned before execution — the form of authentication required by the foreign court should, where possible, be built into the rogatory request itself.
Second, completeness and reliability. Russian execution does not guarantee that all responsive materials will be produced. Executing authorities in technology matters may produce only records held in official registries, not underlying business documents. If the evidentiary gap is material, a supplementary rogatory request or alternative collection methods (such as disclosure orders against Russian entities with assets in other jurisdictions) may be required. The firm's matters page includes illustrative examples of asset tracing mandates in which multiple collection mechanisms were deployed in combination.
Third, timing. If the foreign proceedings have advanced while the rogatory process was ongoing — a common occurrence given the timelines involved — the foreign court may need to be informed and, if necessary, deadlines extended. Proactive case management in the foreign proceedings is essential, and close coordination between foreign counsel and Russian counsel throughout the execution period is the norm, not the exception.
Q: How long does the full letters rogatory process typically take when directed at Russian authorities in a technology matter?
A: The full process, from initiating the request in the foreign proceedings to receiving executed materials from Russian authorities, typically takes between nine and eighteen months under bilateral treaty frameworks. Several variables influence this range: the completeness of the original request, the workload of the executing Russian court or administrative body, whether the evidentiary target is a court or government record or a third-party custodian, and whether supplementary requests become necessary. Requests directed at Rospatent for registered software or database records tend to move more quickly than those requiring production from private custodians. Foreign counsel should factor these timelines into procedural planning at the outset and seek extensions of time in the foreign proceedings if necessary.
Q: What documents are required to accompany an international letter rogatory directed at a Russian authority?
A: As a general rule, the letter rogatory package should include: the signed and sealed letter rogatory itself (in Russian translation and, where required, the original language); a certified translation into Russian of all accompanying documents; legalisation or apostille where required by the applicable treaty; a copy of the foreign court's order or authorisation; a description of the proceedings and the parties; and a precise specification of the evidence or information sought. In technology and software matters, this specification should describe the evidentiary target with particularity — generic descriptions of records or data are a common basis for non-execution. The applicable bilateral treaty may impose additional requirements, and these should be checked before the package is assembled.
Q: What happens if Russian authorities decline to execute the letter rogatory?
A: Russian executing authorities may decline a rogatory request on grounds of public policy, sovereignty, or formal non-compliance with the applicable treaty. In commercial and technology matters, declination on substantive grounds is less common than declination for formal reasons — inadequate translation, missing authentication, or insufficient specification of the evidentiary target. If a request is declined for formal reasons, it is generally possible to correct and resubmit. If declined on substantive grounds, the foreign creditor's options are more limited: it may seek reconsideration through diplomatic channels, pursue alternative collection mechanisms in third jurisdictions where assets or records are also held, or rely on adverse inference arguments before the foreign court if non-production can be attributed to the respondent's conduct. Experienced Russian counsel should be involved from the drafting stage to minimise the risk of formal non-compliance.
This briefing is general information and does not constitute legal advice. For advice on a specific matter, write in confidence to info@vetrovpartners.com.
Our team advises foreign clients on exactly these questions across Russia and the EAEU region. Initial 30-minute consultation — complimentary.
Make an enquiry