Registration of Active Pharmaceutical Ingredients (API) in Russia

For an international API manufacturer, the critical question is therefore not simply whether a DMF or ASMF exists. The real question is whether the CMC file, GMP status, Russian quality document, current pharmacopoeial requirements, samples, reference standards and import logistics can all become submission-ready on the same critical path.

Two API pathways that should not be confused

Russia maintains a national mechanism for a pharmaceutical substance manufactured for sale. At the same time, active-substance information also forms part of the quality dossier of medicinal products registered under the EAEU framework. A regulatory strategy should identify the intended commercial model before dossier preparation begins.

Federal Law No. 61-FZ also provides that pharmaceutical substances used in medicinal-product manufacture must be represented in the Russian State Register and/or the EAEU register, subject to specified exceptions. This is why the intended supply model, the finished-product portfolio and the registration status of the API should be reviewed together rather than as separate administrative questions.

Why API registration is a critical-path project

The formal expert-review period is only one part of elapsed time. In practice, the registration project is governed by several dependencies that must converge at the moment the quality expertise starts:

• CMC readiness: the manufacturing and analytical package must support the proposed Russian quality document and be internally consistent.
• GMP readiness: for a foreign manufacturing site, the application package must address the GMP evidence required by Article 34, including the applicable Russian federal conclusion or the decision to perform a pharmaceutical inspection against EAEU GMP requirements.
• Pharmacopoeial alignment: specifications and methods must be checked against the pharmacopoeial requirements applicable at the time of filing, not against the version used when the global dossier was first prepared.
• Sample logistics: import authorization, shipment, customs clearance and physical delivery to the expert institution must fit the statutory sample-delivery window.
• Analytical reproducibility: the official laboratory must be able to reproduce the proposed methods with the submitted samples, standards and required materials.

These workstreams are interdependent. Translating a DMF before deciding the Russian specification, for example, can create rework. Starting an official procedure before the sample and reference-standard package is shipment-ready can turn a statutory deadline into the project's main risk.

Current national procedure and statutory timing

As of August 2026, Article 34 of Federal Law No. 61-FZ remains the core legal basis for inclusion of a pharmaceutical substance manufactured for sale in the Russian State Register. The application is submitted electronically through the applicable state information system/portal and is signed electronically.

This statutory structure is why a responsible project plan should not be reduced to a headline promise of “registration in X months”. A submission-ready API may move efficiently through the official stages, while unresolved GMP, analytical-method, pharmacopoeial or sample-import issues can dominate the real calendar.

The CMC dossier: more than translating a DMF

Article 34 requires a technically substantive quality package. It covers the manufacturing process and in-process controls, process development, critical steps, process validation, substance characterization and impurities, the specification and its justification, analytical procedures and their validation, batch-analysis results, reference standards or substances, packaging, stability and shelf life.

In CTD terms, the scientific content corresponds primarily to the active-substance quality sections in Module 3.2.S. Under the EAEU medicinal-product dossier, Decision No. 78 expressly structures active-substance control as 3.2.S.4 and reference standards/materials as 3.2.S.5.

The Russian quality document (ND): where global CMC meets local pharmacopoeial requirements

The Russian regulatory quality document (commonly referred to in practice as the “ND”) is not a cosmetic translation of the manufacturer’s specification. It is the local quality-control document developed for the substance file and must be built from the actual CMC evidence while reflecting the pharmacopoeial framework applicable to the project.

For each API, we review the proposed specification and analytical methods against:

• the current EAEU Pharmacopoeia and its applicable general or individual monographs where relevant to the regulatory pathway;
• the current State Pharmacopoeia of the Russian Federation, XV edition, including general pharmacopoeial articles and individual monographs applicable to the substance or method;
• the manufacturer's existing Ph. Eur., USP, BP or other compendial basis and validated in-house methods;
• the submitted manufacturing process, impurity profile, batch data and stability package.

The objective is not to replace every global method with a Russian method. It is to identify where the applicable local or Union pharmacopoeial requirement creates an additional test, a different limit, a different method expectation or a justification requirement, and to resolve that difference before official testing.

This review has become more important, not less. The EAEU Pharmacopoeia continues to develop, and the Russian State Pharmacopoeia XV is actively maintained; individual general articles have been introduced or revised after the initial publication of the edition. A specification gap analysis performed several years ago should therefore not be reused automatically for a 2026 filing.

Preliminary testing before filing

One of the most effective ways to reduce avoidable analytical risk is to test the proposed Russian specification before the official expertise begins.

Pharegis can arrange preliminary testing of the API against the draft ND in an accredited laboratory. This is a diagnostic pre-filing activity and does not replace the official quality expertise. Its purpose is to discover problems while they can still be corrected without an active regulatory clock.

Depending on the API and methods, the pre-test can be used to verify:

• whether analytical procedures can be transferred and reproduced with the available equipment and system-suitability conditions;
• whether the proposed specification and limits are supported by actual sample results;
• whether required reference or impurity standards are available, correctly characterized and sufficient in quantity;
• whether special reagents, columns, organisms or other method-specific materials create a procurement or import dependency;
• whether CoA, DMF/ASMF, validation data and the draft ND describe the same analytical control strategy;
• whether additional pharmacopoeial tests need to be incorporated before filing.

For complex APIs, this step can be materially more valuable than accelerating translation or submission by a few days: an analytical method that cannot be reproduced during official expertise can stop the project after the most expensive work has already been completed.

Samples, reference standards and import logistics

The sample workstream should start during dossier preparation, not after submission. Article 34 requires the API samples needed to reproduce the quality-control methods to be delivered to the expert institution within 15 working days after the relevant decision. The application package also includes the request for permission to import the unregistered material for the expertise.

In practice, Pharegis plans the analytical shipment as a controlled package that may include:

• the required quantity of representative API samples and supporting certificates of analysis;
• primary or working reference standards;
• specified impurity standards and, where required, degradation-product standards;
• method-specific reagents or other materials that are not routinely available to the testing laboratory;
• shipping, temperature-control and dangerous-goods documentation where applicable;
• import-permit and customs documentation aligned with the exact purpose and quantities of the expertise.

Quantities should be calculated against the actual methods and expected repeat testing, with a practical reserve where appropriate. A missing impurity standard or an incorrect quantity of an API sample can become a more serious schedule problem than an incomplete administrative translation.

GMP status for foreign API manufacturing sites

For an API manufactured outside Russia, Article 34 requires evidence relating to the manufacturing authorization in the country of manufacture and the Russian GMP workstream. The law provides for a copy of the relevant federal GMP-compliance conclusion or, alternatively at the applicable stage, a decision by the competent federal authority to conduct a pharmaceutical inspection of the manufacturing site against the EAEU GMP rules.

For this reason, EAEU GMP inspection readiness and API registration should be planned as one programme when the GMP status is not already in place. The two tracks can run in parallel, but only if the dossier, inspection scope, manufacturing-site information and target filing dates are coordinated from the beginning.

Where API projects most often lose time

The most expensive delays are usually created before the formal procedure, even if they only become visible during expertise. Typical examples include:

• starting the national commercial-API route when the actual business model only requires an API within a specific EAEU medicinal-product dossier, or vice versa;
• preparing the Russian ND from an old global specification without a current EAEU/Russian pharmacopoeial gap assessment;
• submitting before the API samples, impurity standards and special reagents are physically shipment-ready;
• discovering during official testing that an in-house method cannot be transferred without clarification or additional validation information;
• allowing the standalone API file and linked medicinal-product Module 3 sections to diverge in specifications, impurity limits, methods, retest period or manufacturing-site information;
• treating GMP as an independent certificate project instead of a dependency in the API registration critical path;
• responding to an expert request locally in one document without checking the impact on the rest of the CMC dossier and the ND.

Lifecycle control after inclusion

Inclusion in the State Register is not the end of the regulatory lifecycle. Article 34 expressly provides for changes to the documents of a pharmaceutical substance manufactured for sale, and a manufacturing or analytical change can affect several layers at once: the API record, the Russian ND, GMP information and one or more medicinal-product dossiers that rely on the substance.

Pharegis therefore treats post-approval changes as an impact-assessment problem rather than a form-filling exercise. Before a manufacturer changes a site, process, specification, analytical procedure, packaging system, shelf life or other registered quality element, the regulatory consequences should be mapped across the standalone API record and the affected finished-product dossiers.

What Pharegis manages in an API registration project

Engagements can cover a defined workstream or the full registration critical path. Typical deliverables include:

• regulatory pathway memo confirming whether standalone commercial API inclusion is required and how it interfaces with planned EAEU medicinal-product registrations;
• CMC gap matrix against Article 34 requirements, current pharmacopoeial expectations and the manufacturer's existing DMF/ASMF;
• preparation and reconciliation of the Russian ND with the source CMC dossier;
• review of 3.2.S.4/3.2.S.5 and, where relevant, the interface with finished-product 3.2.P.5;
• sample, reference-standard, impurity-standard and reagent matrix, including quantity planning and shipment readiness;
• coordination of preliminary testing in an accredited laboratory against the draft ND where this is useful for de-risking the filing;
• electronic application preparation, regulatory translations and submission coordination;
• coordination of import permission, customs and delivery of analytical samples/materials;
• CMC strategy and preparation of responses to expert requests;
• coordination with the GMP inspection workstream;
• post-inclusion change-impact assessment and lifecycle support.

Regulatory basis

• Federal Law No. 61-FZ “On Circulation of Medicinal Products”, in particular Articles 33, 34, 45 and 47.
• EEC Council Decision No. 78 of 3 November 2016, consolidated rules for registration and expert examination of medicinal products, relevant to the distinct EAEU medicinal-product/API dossier pathway.
• Eurasian Economic Commission — acts in the sphere of circulation of medicinal products, including EAEU GMP Decision No. 77 and the current amendments to Decision No. 78.
• EAEU Pharmacopoeia.
• State Pharmacopoeia of the Russian Federation, XV edition.
• Order of the Ministry of Health of Russia No. 880n of 25 August 2021, governing import permits for specified unregistered medicinal materials used for expert examination, including API inclusion procedures.

Regulatory status reviewed: August 2026.