...

USRLE and USRIE extract via API

Look up a company in the register through the API: pass the INN and the USRLE or USRIE data arrives in your CRM, 1C or procurement system as fields, not as a file. Details, director, members, OKVED codes, licences and inaccuracy entries — for a single company or your entire counterparty base.

1 INN enough to get a company or sole proprietor card
7 working days the period within which a company must report changes to the register
JSON + webhook data straight in your system
5 ₽ a director or founder check against a single register
Data is stored in Russia Russian software registry no. 19972 Cloud or your own perimeter

Register data instead of a PDF: why you need a USRLE extract in your system

The register in fields, not in a folder

Every item arrives with its entry date, so you see not only “what is now” but also “since when”.

  • 01

    The file stays out of the process

    An employee opens a PDF extract, reads it and copies the data by hand — name, address, directors, KPP. Data from the API fills the card fields on its own, with no typos in the contract details.

  • 02

    One company is not a stream

    A manual request is built for one company. When a marketplace onboards dozens of sellers a day and a procurement department manages thousands of suppliers, you need a bulk export by INN list and a response your system understands.

  • 03

    The register changes after the contract

    The director changed, the address was found inaccurate, the company is in liquidation — these are new register entries. A repeat export shows them before a payment goes wrong or the wrong person signs.

  • 04

    USRLE and USRIE — in one request

    Your system does not choose the register: a 10-digit INN is a company, a 12-digit one is a sole proprietor. The response comes in one format for both.

  • 10 / 12 digits INN of a company and a sole proprietor
  • 30 days for a company to respond after an inaccuracy notice
  • 5 days the longest time to issue an extract on request to the Federal Tax Service

What comes from USRLE and USRIE: company and sole proprietor fields

The content of the registers is set by Article 5 of the state registration law. NeuroVision returns these data in JSON with the entry number and date, and does not pass on what the law closes to public access.

  • Company — USRLE

    A legal entity by INN or OGRN.

    Company card example

    Details and status

    • full and short name
    • legal form
    • OGRN, INN, KPP
    • address and email address
    • registration date
    • status: active, liquidation, reorganisation

    Management and activity

    • a director who acts without a power of attorney
    • founders and members with their shares
    • share capital
    • OKVED codes
    • licences
    • branches and representative offices
  • Sole proprietor — USRIE

    A sole proprietor by INN or OGRNIP.

    Sole proprietor card example

    Details

    • last name, first name, patronymic
    • OGRNIP and INN
    • dates of registration and of ceasing activity
    • citizenship

    Activity

    • OKVED codes
    • licences
    • status: active or ceased activity
  • What is not in open data

    Closed by law, not returned.

    Discuss the data scope

    Closed

    • passport data of directors and members — only for public authorities, courts and funds
    • a sole proprietor’s home address — only in person, with an ID
    • information whose access the company has restricted

    Where to get the rest

The counterparty card fills itself: CRM, 1C, procurement

The user enters the INN — the other fields are filled from the register. Six places where this saves time and removes errors. How a person check lands in the deal card — on the page for the  KYC module for CRM, ERP and 1C.

  • Contract details

    Name, OGRN, KPP and address are taken from the register, not from the counterparty’s email. The contract and invoice get the details recorded in USRLE.

  • Signatory

    A director who acts without a power of attorney. If someone else signs the contract, your system will request a power of attorney right away.

  • Seller or customer profile

    A marketplace or B2B platform fills in the profile by INN: name, region, registration date, lines of business. The seller only has to check and confirm.

  • Risk profile

    OKVED codes, registration date and share capital are input for your rules: a young company with minimum capital and an atypical line of business goes to manual review.

  • Licences and branches

    For licensed activities you can see whether a licence is in the register; for a contract with a separate division — the branch address and KPP.

  • Matching against what a person entered

    Your system compares questionnaire or invoice data with the register and highlights mismatches: a different address, a different director, a company in liquidation.

Bulk export by INN list: how to refresh your counterparty base

A scenario for a procurement department, bank or marketplace with thousands of companies in the base and details collected over the years.

Step 1

Export the INNs from your system

A list of INNs of companies and sole proprietors — from your CRM, 1C or supplier directory. Your system removes duplicates and empty rows before sending.

List of INNs from your system
Step 2

Send requests through the API

Each INN is a separate request. Your system sends the whole base in batches, at a convenient time, for example at night.

Requests sent in batches through the API
Step 3

Receive the cards

For each INN you get the register fields with entry dates. If an INN is not found in the register, the response says so — a reason to check for a typo.

A register card arrived for each INN
Step 4

Compare with what you have

Your system compares what it received with what is stored: address, director, KPP, status. Mismatches go to a separate list for review.

Mismatch with the stored data
Step 5

Review the signals

Companies in liquidation, with an inaccuracy entry or struck off the register go to an employee: suspend payments, request documents, update the contract.

Companies with register signals — to an employee
Step 6

Repeat on a schedule

Once a month or before a large payment. To learn about changes without a repeat export, enable counterparty monitoring.

Scheduled repeat export

Inaccuracy, liquidation, strike-off: signals in register data

  • Inaccuracy record

    The tax service checked an address, director or member and did not confirm the data. The company has 30 days from the notice to correct or confirm it. Until then — a reason to request documents.

  • Liquidation

    The company decided to liquidate and this is recorded in the register. A new long-term contract with it is a risk.

  • Reorganisation

    Merger, accession, split: the obligations may gain a successor and the contract a new party.

  • Strike-off from the register

    The registration authority may strike off an inactive company. A payment to such a company is a payment into the void.

  • A fresh change of director

    The entry date for a new director shows how long they have been signing documents. A change a week before a large deal is a reason to check them against registers.

  • Bankruptcy

    Bankruptcy information in the register — a signal to stop before talking to a lawyer: settlements with such a company follow special rules.

Register data are considered reliable until changes are made to them. A signal is a reason for your employee’s decision, not an automatic refusal.

Official Federal Tax Service extract or API data: which for which case

We do not replace the tax service: only it issues a signed document. But most processes need data, not a document. How to check a counterparty by INN manually — in the blog article.

  • You need a document — a Federal Tax Service extract

    When: a bank, notary, court or tender customer asks for an extract.

    What: an electronic extract with the tax service’s qualified electronic signature — equivalent to a paper one. The Federal Tax Service generates it on its website on a request about a specific company.

    • Federal Tax Service
    • Document
  • You need data — the API

    When: fill in a card, check details, refresh a base, trigger a rule.

    What: register fields in JSON, by a single INN or by a list, in your CRM, 1C or procurement system.

    • NeuroVision
    • Data
  • Prove due diligence

    When: you need to show that the counterparty was checked before the deal.

    What: save the response with the request date in the counterparty card. For the full picture, add checks of the director and founders.

    • Report
    • Request date
  • Track changes

    When: the contract runs for years.

    What: a scheduled repeat export or monitoring with alerts on new entries.

    • Repeat
    • Monitoring

How fresh the data is: entry dates and terms under 129‑FZ

The register reflects what the company reported and the tax service registered. Time passes between an event and its entry — it matters how much.

  • A company and a sole proprietor report a change within seven working days of the change, unless the law sets another term (para. 5, Art. 5) 129‑FZ
  • So the director may have changed yesterday while the register still shows the previous one: for a large deal, ask the counterparty for documents on authority Your system

  • Each entry is assigned a state registration number and an entry date (para. 4, Art. 5) 129‑FZ
  • In the API response every item has an entry number and date: you see since when the director or address has been valid NeuroVision

  • Register data are considered reliable until changes are made to them (para. 4, Art. 5) 129‑FZ
  • If the tax service did not confirm the data, an inaccuracy entry appears in the register and the company has 30 days to respond (para. 6, Art. 11) 129‑FZ

  • The tax service issues an extract on request within five days at most (para. 3, Art. 6); via the API data arrives in response to a request NeuroVision
  • Make a repeat request before payment, signing and a change of details; refresh the whole base on a schedule Your system
  • Tags: 129‑FZ · Your system · NeuroVision.
  • A guide to the law on state registration of legal entities and sole proprietors (129‑FZ, as amended 04.08.2026); for the exact text see ConsultantPlus. Which 115‑FZ and tax due diligence deadlines continuous monitoring helps you meet — on the page for  counterparty monitoring.

Banks, marketplaces, leasing, procurement: where USRLE data is needed in the flow

  • Banks and MFIs

    • A corporate client card by INN
    • the signatory and members before account opening
    • a repeat request when details change
  • Marketplaces and B2B platforms

    • A seller profile is filled in by INN
    • liquidation and inaccuracy — before the first payout
    • the whole seller base — on a schedule
  • Leasing and factoring

    • Status and reorganisation before a deal decision
    • the signatory from the register
    • branch and KPP in the contract
  • Procurement and supply

    • Supplier details from the register
    • licences for licensed work
    • refreshing the supplier directory
  • Accounting

    • Details in 1C and ERP without manual entry
    • matching an invoice against the register
    • struck-off and liquidated counterparties in a separate list

How much a USRLE extract via API costs

Pay for completed requests, with no subscription fee or annual licence. Check prices — in the price matrix.

Calculate the cost
  • 01

    USRLE and USRIE data — on request. The price depends on volume and scope: only the company card or the full KYB scenario. We will calculate it for your flow

  • 02

    Checks of a director, founders and sole proprietors — 5 ₽ per register. Bankruptcy, arbitration, tax debts, lists and sanctions — each check is enabled separately. International compliance screening — 36 ₽

  • 03

    Discounts as volume grows and a 1-month trial period. Start with your counterparty base on test access

Integration: REST API, webhook and export to an accounting system

REST API

A request by INN — a JSON response. Pass an INN or OGRN — get the register fields with entry dates. The result can be delivered by webhook so you do not have to hold the connection.

API documentation

Terms

  • A 1-month trial period
  • A dedicated manager
  • Pay for completed requests

Glossary: OGRN, GRN, USRIE and the inaccuracy entry

State register
Unified State Register of Legal Entities. Maintained by the Federal Tax Service.
Unified State Register of Legal Entities
Unified State Register of Individual Entrepreneurs
Unified State Register of Individual Entrepreneurs.
Register of Individual Entrepreneurs
OGRN and OGRNIP
The primary state registration number of a company or sole proprietor. Assigned at registration and does not change.
PSRN
GRN
The state registration number of a single register entry: each change of director or address has its own GRN and date.
record number
Extract
Register data on a specific company or sole proprietor in document form. An electronic extract with the tax service’s signature is equivalent to a paper one.
registry extract
Person without a power of attorney
The director or managing organisation that acts on behalf of the company without a power of attorney.
authorised signatory
Inaccuracy record
A tax service mark that the company data were not confirmed.
unreliable record
OKVED
Codes of economic activity types that the company stated at registration.
activity codes
KPP
Tax registration reason code. A branch may have its own.
tax registration reason code
Strike-off from the register
Termination of a company by decision of the registration authority, for example as inactive.
strike-off

Questions about the USRLE and USRIE extract via API

Your system passes an INN or OGRN to the NeuroVision API and receives the register data in JSON: details, status, director, members, OKVED codes, licences and entry dates. This is a company lookup in the register through the API, not a file for printing.

No. The official document with a qualified electronic signature is generated by the tax service. The API returns the same register data as data — for CRM, accounting and rules. If a bank or tender requires a document, request the extract from the Federal Tax Service.

An extract is the register’s own data on a company. A counterparty check adds checks of the people behind the company: bankruptcy, arbitration, tax debts, lists and sanctions. Both work from a single INN and combine in one request.

Yes. A 12-digit INN is looked up in USRIE: full name, OGRNIP, registration or termination date, OKVED, licences. A sole proprietor’s home address is by law not part of the open data.

The law opens passport data from the register only to public authorities, courts and funds. To check a director against databases that need a date of birth or passport, the company representative goes through KYC, or you provide the data yourself.

A company must report changes within seven working days, after which the tax service makes the entry. Each item in the response has an entry date — it shows since when it has been valid. Make a repeat request before payment and signing.

The tax service did not confirm data on the company — most often the address, director or a member. The company has 30 days from the notice to respond. For you it is a reason to request documents before the deal.

Yes. The request is connected to the counterparty card: the user enters an INN and the name, KPP, address, director and OKVED are filled in from the register. Your developer or an integrator connects it through the API.

Enable counterparty monitoring: companies from your list are matched against the registers and you get an alert with “was → became” for changes. For a deep check before a large deal there is a due diligence.

USRLE and USRIE data — on request, depending on volume and scope. A check of a director, founder or sole proprietor against one register — 5 ₽, international screening — 36 ₽. No subscription fee, trial period — 1 month.

We will connect USRLE data to your system

Tell us how many companies are in your base and where the data should go — CRM, 1C, procurement system — and we will propose an integration scheme and a quote.

Can't put your request into words? Book a call and our team will contact you at a convenient time

Book a call

The company is included in the register of IT companies and the register of personal data operators of the Russian Ministry of Digital Development.

Address: Moscow, Presnenskaya Embankment 12 — Moscow City business centre, Federation Tower. Nearest metro stations: Delovoy Tsentr and Mezhdunarodnaya.