Setting up auto-fill of company details by TIN in Bitrix24 CRM
A manager receives a client's TIN and manually searches for the full name, KPP, OGRN, legal address — copies from EGRUL, pastes into the CRM card. Four minutes per company, plus the risk of a typo in KPP or address that surfaces when issuing an invoice. When actively working with dozens of counterparties daily, errors accumulate: every tenth company in CRM contains an incorrect KPP or address — this blocks sending invoices via EDI and requires manual rechecking. Automatic filling solves both problems: enter the TIN — the rest of the details are pulled from the official Federal Tax Service register. We configure this integration turnkey in 2 days, guaranteeing no input errors and reducing card fill time from 4 minutes to 20 seconds — 12 times faster.
How does auto-fill by TIN work?
Bitrix24 uses the DaData service for requisites suggestions. The mechanism is simple: when entering a value in the TIN field (or the beginning of a company name), the CRM frontend sends a request to the suggestions API. DaData returns JSON with a full set of details from EGRUL/EGRIP:
- Full and short legal entity name
- TIN, KPP, OGRN (OGRNIP for sole proprietors)
- Legal address (structured: postal code, region, city, street, building)
- CEO full name and position
- Registration date
- Tax system (if available)
- OKVED codes
In the CRM card, data goes into the Requisites block — a standard B24 entity with its own table (b_crm_requisite in on-premise). Each requisite is linked to a company or contact. The address is stored separately in b_crm_addr.
| CRM field | Source in DaData | Notes |
|---|---|---|
| Company name | value, data.name.full_with_opf |
Full with OPF |
| TIN | data.inn |
— |
| KPP | data.kpp |
Only for legal entities |
| OGRN / OGRNIP | data.ogrn |
— |
| Legal address | data.address.value |
One line |
| Postal code | data.address.data.postal_code |
— |
| CEO | data.management.name |
Full name |
Why use auto-fill?
Manual entry is a source of typos. According to statistics, about 10% of companies in CRM contain an error in KPP or address, leading to failures when issuing invoices via 1C or fiscal services. Automatic TIN filling eliminates the human factor: data comes from the Federal Tax Service. Card fill time is reduced from 4 minutes to 20 seconds — 12 times faster. Additionally, manager workload decreases: they spend 75% less time on routine, and operational cost savings can reach 30% when processing a large flow of counterparties. The integration pays off in an average of 2 months by eliminating returns due to incorrect invoices.
How to set up auto-fill in cloud Bitrix24?
In cloud plans, auto-fill works out of the box. Setup takes 30 minutes:
- Go to CRM → Settings → My company details — ensure the requisite template contains the necessary fields (TIN, KPP, OGRN, address). The standard "Organization" template includes them.
- In the company card, open the "Requisites" block and click "Add" — when entering a TIN or name, suggestions appear. Select the required one — all fields are filled automatically.
- If the built-in request limit is insufficient (depends on B24 plan), connect your own DaData account via integration settings — this reduces blocking risk and speeds up responses.
Setup in on-premise version
In on-premise, requisites pull requires the crm module of the latest version and configuring a connection to DaData. Parameters are set in the .settings.php file or via the admin panel:
// Example configuration 'crm' => array( 'dadata_api_key' => 'your_key', 'dadata_secret' => 'your_secret_key' ) It is important to specify the correct API URL (default https://suggestions.dadata.ru/suggestions/api/4_1/rs). Outdated SSL certificates on the server can block requests — check the validity of root certificates.
Typical problems and their solutions
| Problem | Solution |
|---|---|
| KPP field is not filled | Check mapping: in the requisite template, the field must be named RQ_KPP, not RQ_INN |
| Address is not pulled | Make sure the template has a "Legal address" field |
| In on-premise, suggestion does not work | Update the CRM module to the latest version, check dadata_api_url settings and PHP version |
What's included in the setup
We deliver a complete result: working DaData integration, configured requisite templates, tested scenarios (legal entity, sole proprietor, non-existent TIN). Included are documentation, API key access, and manager training (1 hour). If needed, we configure fiscalization — data pull for 54-FZ receipts.
Estimated timelines
- Basic setup in the cloud: from 1 day.
- On-premise version with customization: from 2 days.
- Full cycle with training: up to 3 days.
The cost is calculated individually based on the scope of work. Contact us to set up auto-fill of requisites without surprises. Get a consultation to discuss your project.