Bitrix24 Integration with Counterparty Verification Services
A manager receives a request from a new client. Opens the company card in CRM, copies the TIN (tax ID), switches to browser, enters into Kontur.Focus, checks revenue and lawsuits, returns to B24, writes comment. On the next request — same again. By the tenth time — just skips the check. Two months later, a shell company doesn't pay for supplies worth 800K. Integrating B24 with counterparty verification services removes the manual step: data is pulled by TIN directly into CRM, risks are assessed automatically, manager sees a traffic light — green, yellow, red.
Which Services Integrate
There are several major data providers about legal entities on the market. Each provides API for automated requests:
| Service | What It Provides | API |
|---|---|---|
| Kontur.Focus | Credentials, financials, court cases, affiliations, mass addresses/directors | REST API (JSON/XML) |
| SPARK-Interfax | Credentials, ratings, arbitrage cases, affiliation, due diligence index | SOAP/REST |
| DaData | Standardization and enrichment: TIN → full name, address, OKVED, status, director | REST API (JSON) |
| Rusprofile / ZaChestnyiBiznes | Basic credentials, reporting (limited API) | REST |
| FTS (EGRUL/EGRIP) | Registry extract | СМЭВ / egrul.nalog.ru |
DaData is the easiest to start: free enrichment tier, quick setup. Kontur.Focus and SPARK are full solutions for due diligence with financial analytics and court history.
Auto-filling Credentials by TIN
Basic scenario — autocomplete when entering data in CRM. Manager starts entering TIN or company name in contact/company card, system queries DaData or Kontur.Focus and fills in fields:
- Full and short name
- TIN, CPP, OGRN
- Legal address
- Director full name
- OKVED (main)
- Registration date
- Status (active, liquidated, bankruptcy in process)
Technically, this is implemented by modifying the CRM card: on event onCrmCompanyUpdate or when the TIN field is filled, a handler makes an API request and writes the result to custom fields.
For DaData — endpoint /suggestions/api/4_1/rs/findById/party, pass TIN, get JSON with full credentials. For Kontur.Focus — method req which returns organization card by TIN.
CRM Enrichment: Financial Indicators
Kontur.Focus and SPARK provide counterparty financial reporting: revenue, net profit, assets, accounts payable. This data is written to custom fields in the company card in CRM and updated per schedule (quarterly when accounting reporting updates).
Which fields are added to company card:
| Field | Source | Update Frequency |
|---|---|---|
| Revenue (last year) | Kontur.Focus / SPARK | Quarterly |
| Net profit / loss | Kontur.Focus / SPARK | Quarterly |
| Charter capital | EGRUL | On creation |
| Employee count | Kontur.Focus | Annually |
| Government contracts presence | Kontur.Focus | Monthly |
Risk Checking and Scoring
Key integration task — automatic counterparty reliability assessment. Risk factors checked:
- Mass registration address — from FTS base
- Mass director / founder — person is director in 10+ companies
- Disqualified director — in FTS disqualified persons registry
- Court cases — count and amounts of arbitrage cases (defendant)
- Tax debt — FTS data
- Company age — less than 12 months = elevated risk
- No employees — zero reporting for headcount
- Bankruptcy status — in observation/bankruptcy procedure
Each factor gets a weight. Total score is recorded in "Counterparty Scoring" field in company card. Robot in CRM reacts to value: if score is below threshold — deal is blocked or sent for manager approval.
Integration Architecture
Standard setup scheme:
- CRM event — company creation, TIN change, deal move to "Verification" stage.
- Handler (webhook or business process) — calls server script.
- Server script — makes API request to verification service, parses response.
- CRM write — fills custom company fields, records scoring, attaches report.
- Robot / trigger — reacts to verification result.
For DaData, outgoing webhook from B24 is enough — request is light, response comes in 100-200 ms. For Kontur.Focus and SPARK with more data, use server middleware: PHP script or Node.js service that aggregates data from multiple API methods and forms single result.
Automatic Verification on Deal Creation
Most useful scenario — automatic verification check when company is linked to deal or when deal moves to certain funnel stage. Example process:
- Manager creates deal, links company.
- CRM trigger starts "Counterparty Verification" business process.
- Script queries Kontur.Focus: credentials, financials, courts, mass markers.
- Result is recorded in company fields, PDF report generated.
- If risks are high — deal moves to "Requires Approval" stage, notification with report sent to manager.
- If risks are low — deal continues through funnel without delays.
Periodic Database Re-assessment
Counterparties with whom company works regularly are checked again per schedule. Configure cron task or B24 agent that monthly goes through active companies and updates data. If status changed (bankruptcy procedure started, major lawsuits appeared) — notification goes to responsible manager.
What We Configure
- Connect Kontur.Focus / SPARK / DaData API
- Custom company card fields: credentials, financials, scoring
- Auto-fill credentials by TIN on company creation
- Automatic verification check trigger on deal stage transition
- Scoring model with configurable risk factor weights
- Visual reliability indicator (traffic light) in company card
- Periodic counterparty base re-assessment
- Staff training: reading report, actions on high risk