Bitrix24 Integration with Kontur.Focus
A lawyer opens Kontur.Focus in a separate tab before contract signing, searches for counterparty by TIN, browses sections — courts, financials, affiliations, government contracts. Copies needed data into spreadsheet, attaches to B24 task. Manager doesn't see this and continues the deal. Two days later, lawyer reports the counterparty has three bankruptcy lawsuits — invoice is already issued. Integrating B24 with Kontur.Focus moves verification into CRM: data is available in the company card, verification runs automatically, result affects deal movement.
What is Kontur.Focus
Kontur.Focus is a counterparty verification service from SKB Kontur. It aggregates data from EGRUL/EGRIP, Rosstat, arbitrage case registry, bankruptcy registry, execution service registry, government contracts registry, and other sources. Provides REST API for programmatic access to all sections.
Main data blocks:
| Section | Content |
|---|---|
| Credentials | TIN, CPP, OGRN, address, director, founders, charter capital |
| Financials | Revenue, net profit, assets, ROI for 3–5 years |
| Arbitrage | Court cases (plaintiff/defendant), claim amounts, current status |
| Bankruptcy | Procedure stage, arbitrage manager, start date |
| Executions | Debts, collected amounts |
| Government Contracts | Procurement participation, contract amounts |
| Mass Indicators | Mass address, mass director |
| Affiliations | Related companies via common founders/directors |
Kontur.Focus API: Key Methods
Integration works through Extern API Kontur.Focus. Authentication — via API key in request header. Response format — JSON.
Methods used for CRM integration:
-
/req— basic company credentials by TIN/OGRN. Returns name, address, director, status, registration date. -
/analytics— financial indicators: revenue, net profit, asset value for multiple years. -
/arb— arbitrage cases. Filter by role (plaintiff/defendant), amounts, dates. -
/buh— accounting reports (balance sheet, income statement). -
/fyul— current list of founders and shares. -
/egrDetails— full EGRUL extract including change history. -
/briefReport— summary report for express check (key facts + risk signs).
API limits depend on Kontur.Focus plan. Typical restrictions: 1000–10000 requests per day. Mass base verification requires plan with higher limits.
Enriching Company Card in CRM
When integrating, custom fields are added to B24 company card, auto-filled from Focus data:
"Credentials" block (filled on company creation):
- Full name
- Legal address
- Director name and title
- Main OKVED
- Registration date
- Status (active / liquidated / liquidation in process)
"Financials" block (updated quarterly):
- Revenue for last reporting year
- Net profit / loss
- Asset value
- Average employee count
"Risks" block (updated on each check):
- Arbitrage cases count (defendant) last 12 months
- Total claim amount (defendant)
- Mass address indicator (yes/no)
- Mass director indicator (yes/no)
- Execution records present
- Bankruptcy stage (if any)
- Overall risk status (low / medium / high)
Automatic Verification in Sales Funnel
Counterparty verification is embedded as mandatory step in CRM funnel:
- Deal moves to "Qualification" stage (or any other defined in process).
- CRM robot starts verification business process.
- Server handler sends requests to Focus API:
/req,/analytics,/arb. - Results are recorded in company custom fields.
- Scoring algorithm calculates total score based on risk factors.
- Based on score:
- Green (low risk) — deal continues automatically.
- Yellow (medium risk) — deal stays on stage, manager gets task for manual review.
- Red (high risk) — deal is blocked, manager gets notification with reasons.
Checking Mass Addresses and Directors
Kontur.Focus returns mass address and director indicators — one of key markers of shell companies. Integration checks:
- Registration address — matches FTS mass address registry.
- Director — is director or founder in more than 5 companies simultaneously.
- Founder — are there disqualified persons among founders.
Results are shown in company card with tags: "Mass Address," "Mass Director." CRM robot can use these fields in routing conditions.
Court Cases: Monitoring and Alerts
Method /arb returns list of counterparty arbitrage cases. Integration processes them:
- Counts total cases where counterparty is defendant.
- Sums total claim amounts.
- Identifies bankruptcy cases (case category).
- Filters by date — cases last 12 months get higher weight.
For regular counterparties, monitoring is set up: periodic check (weekly or monthly) sees new cases. If case count or amounts exceed thresholds — manager gets notification.
PDF Report Generation
Verification results form PDF report attached to company card and deal. Report contains:
- Counterparty credentials
- Financial indicators (table for 3 years)
- Arbitrage cases list (last 12 months)
- Mass markers
- Overall risk assessment with factor breakdown
Report is used for executive review and archival — if a question arises later "why worked with this counterparty," the answer is in CRM.
Connection Architecture
| Component | Purpose |
|---|---|
| Webhook / CRM robot | Initiates check on event (company creation, deal stage transition) |
| Server middleware | PHP/Node.js service querying Focus API, aggregating data, calculating scoring |
| Kontur.Focus API | Data source |
| B24 REST API | Records results in CRM custom fields |
| Cron / B24 agent | Periodic re-assessment of active counterparties |
There is no direct "B24 → Kontur.Focus" connector in marketplace — integration is implemented as custom development. Alternative — iPaaS platform (Albato, Make), but limited in data processing depth and scoring.
What We Configure
- Kontur.Focus API connection (key retrieval, limit setup)
- Custom company card fields: credentials, financials, risks
- Automatic credentials auto-fill by TIN
- CRM robot for check trigger on deal stage transition
- Scoring algorithm with configurable risk factor weights
- Visual risk indicator in company card
- PDF report generation and attachment
- Periodic monitoring of regular counterparties
- Staff training: result interpretation