Querying Russia’s EGRUL registry: what the FNS actually exposes

Source: Dev.to

Every Russian legal entity receives a 13‑digit OGRN at the moment it enters the Единный государственный реестр юридических лиц (EGRUL). The number does real work. Federal Law No. 129‑FZ “On State Registration of Legal Entities and Individual Entrepreneurs” treats the EGRUL entry as the authoritative corporate record for most statutory purposes. When a dispute reaches an arbitration court, lawyers usually place the EGRUL extract near the front of the evidence bundle. Russian corporate disclosure sits across two public systems run by the Federal Tax Service (ФНС). EGRUL stores registration data for companies. A separate platform, ГИР БО (GIR BO), publishes accounting statements. Each operates under its own legal framework. EGRUL exists under Federal Law No. 129‑FZ together with several Ministry of Finance orders that describe how a registry entry must be structured. GIR BO appeared later through Federal Law No. 402‑FZ “On Accounting”. Companies submit their annual financial statements to the tax authority. GIR BO publishes those filings once processed. On paper the split looks tidy. Actual registry queries tell a slightly messier story. Small quirks surface as soon as you start pulling the data through an API. Registry fields that actually appear in upstream records Most EGRUL entries revolve around three identifiers: OGRN, INN, KPP. OGRN is the state registration number issued at incorporation. INN identifies the taxpayer in the Russian tax system. KPP shows the reason for registration at a specific tax office. Those numbers appear on invoices, contracts, disclosure forms. They anchor the company to the tax infrastructure. A registry lookup also returns the canonical name fields recorded by the tax authority. The field full_name normally carries the statutory Russian name written in the charter. short_name appears when the charter defines one. The dataset also includes registration_date together with a status flag that indicates whether the entity remains active or has been liquidated. Director data sits directly in the EGRUL entry. The register records the individual authorised to act on behalf of the company without a power of attorney. Registry datasets usually describe that position as the head of the executive body. In day‑to‑day terms it maps fairly closely to a managing director entry in several European registers. Ownership disclosure is narrower than many compliance teams expect. EGRUL lists the founders or participants who contributed to the charter capital. In raw registry output the section usually appears as founders. Share percentages sometimes appear when the capital structure is simple. That field does not represent beneficial ownership. Russian companies must identify their beneficial owners internally under Federal Law No. 115‑FZ covering AML and counter‑terrorist financing duties. The public registry never publishes that information. Operational activity appears through OKVED classification codes. These sector codes matter during sanctions screening or export‑control analysis. Even when a company description says very little, the OKVED list often reveals what the firm actually does. What the registers do not provide EGRUL is not a beneficial ownership register. Teams familiar with the UK PSC framework under Companies Act 2006 s.790E will not find an equivalent dataset here. Russian AML law requires companies to maintain beneficial owner records and disclose them to banks or regulators when asked. Public access never became part of the model. GIR BO comes with its own constraints. The system publishes accounting statements filed with the tax authority, though the dataset updates only once per reporting year. Filings normally contain the balance sheet and the profit statement required under Russian accounting standards. Supporting schedules appear irregularly. Some entities submit abbreviated accounts. Another detail concerns extracts. The official “выписка из ЕГРЮЛ” still carries weight in litigation and due diligence. Machine‑readable registry responses mirror the same entry stored by the tax authority. Lawyers nevertheless attach the PDF extract to court filings or transaction disclosure bundles because judges recognise the format immediately. Querying the registry through OpenRegistry MCP OpenRegistry exposes Russian registry data through the same MCP interface used for other jurisdictions on the server such as GB, FR, NL and RU. The service queries Federal Tax Service sources and returns the raw upstream fields under jurisdiction_data. Most sessions start with a search by company name or identifier. Tool call example: search_companies({ “jurisdiction”: “RU”, “query”: “Газпром” })

The response lists candidate entities with their OGRN and INN numbers. Once you have the registration number you can pull the full registry entry. get_company_profile({ “jurisdiction”: “RU”, “company_number”: “1027700070518” })

That response includes identifiers, the registration date, the legal address, director information, and the founder section exactly as published by the tax authority. Financial statements from GIR BO appear through the filings endpoint when the tax service has released them. list_filings({ “jurisdiction”: “RU”, “company_number”: “1027700070518” })

If the register exposes an official extract or another statement document, the file can be retrieved directly. fetch_document({ “jurisdiction”: “RU”, “document_id”: "" })

The returned PDF uses the same выписка format that often appears in diligence memoranda. Russian corporate disclosure often feels opaque to teams used to the European BRIS datasets. The structure is simpler once you trace the legal boundaries. The operative corporate record lives in EGRUL. Accounting statements sit in GIR BO. Beneficial ownership information sits outside the public register under AML obligations. For sanctions analysis the director entry and the founder list still provide useful signals. Ownership chains frequently pass through domestic holding companies whose own EGRUL entries reveal the next layer of shareholders. Walk those entries step by step and a corporate structure begins to appear, even without a public UBO register. That detail matters when applying ownership thresholds such as the OFAC 50 percent rule or similar limits used in EU and UK sanctions regimes. The legal analysis depends on shareholdings recorded in the register rather than declared beneficial owners. Live access to the underlying registries is available through the MCP endpoint at https://openregistry.sophymarine.com.