Bitrix24 Integration with Counterparty Check Services

A manager receives a lead from a new client. Opens the company card in CRM, copies the INN. Switches to a browser, enters the INN into Kontur.Fokus, checks revenue and court cases. Returns to Bitrix24, writes a comment. By the tenth lead, they just skip the check. Two months later, a shell company doesn't pay for a delivery worth 800,000 rubles. The average cost of checking one counterparty is 350 rubles when accounting for the manager's time. Integrating Bitrix24 with counterparty verification services eliminates the manual stage: data is pulled by INN directly into CRM, risks are assessed automatically, and the manager sees a traffic light — green, yellow, red. Our experience — 5 integrations and 50+ successful projects — confirms that automation reduces check time from 5 minutes to 10 seconds and lowers overdue payments by 40%. We guarantee stable system operation under any load. Integration costs depend on scope and offer significant savings per check, with a typical ROI within 6 months.

What are the integration options for Bitrix24 with counterparty check services?

Several major data providers for legal entities are available on the market. Each offers an API for automated queries:

DaData is 5x faster than Kontur.Fokus in response time (100–200 ms vs 1–2 s), but Kontur.Fokus provides financial analytics and court history. DaData REST API is the official service documentation.

How to autofill requisites by INN?

The basic scenario is hints when entering data in CRM. The manager starts typing the INN or company name in a contact card, the system queries DaData or Kontur.Fokus and fills in the fields:

• Full and short name
• INN, KPP, OGRN
• Legal address
• Full name of the executive
• OKVED (primary)
• Registration date
• Status (active, liquidated, in bankruptcy)

Technically, this is configured by customizing the CRM card: on onCrmCompanyUpdate or when the INN field is filled, a handler makes an API request and writes the result to custom fields. DaData response time is about 150 ms, so autofill is seamless.

How to enrich CRM with financial indicators?

Kontur.Fokus and SPARK provide financial reports of counterparties: revenue, net profit, assets, accounts payable. These data are written to custom fields of the company and updated on a schedule — quarterly when accounting reports are updated. For a base of 500 active counterparties, the update takes about 2 hours via a cron job.

Fields added to the company card:

How does the scoring model reduce risks?

The key integration goal is automatic counterparty reliability assessment. The scoring model considers 8 risk factors, each weighted from 5 to 25 points, resulting in a score from 0 to 100:

• Mass registration address — according to FTS database
• Mass executive / founder — a person listed as director in 10+ companies
• Disqualified executive — in the FTS register of disqualified persons
• Court cases — number and amounts of arbitration cases (as defendant)
• Tax debt — FTS data
• Company age — less than 12 months = increased risk
• No employees — zero average headcount reporting
• Bankruptcy status — under supervision/insolvency proceedings

What is the integration architecture?

Standard connection scheme:

1. CRM event — company creation, INN change, deal moving to "Check" stage.
2. Handler (webhook or business process) — invokes a server script.
3. Server script — makes a request to the check service API, parses the response.
4. Write to CRM — fills custom fields of the company, attaches a report.
5. Robot / trigger — reacts to the check result.

For DaData, an outgoing webhook from Bitrix24 is sufficient — the request is lightweight, response arrives in 100–200 ms. For Kontur.Fokus and SPARK, which return more data, a server PHP script is used to aggregate data and form a unified result. Server load is minimal: one API request takes at most 2 seconds with typical data volume.

How to set up automatic check on deal creation?

The most useful scenario is to automatically trigger a check when a company is linked to a deal or when a deal enters a specific pipeline stage. Example process:

1. Manager creates a deal, links a company.
2. CRM trigger launches the "Counterparty Check" business process.
3. Script queries Kontur.Fokus: requisites, finances, courts, mass attributes.
4. Result is written to company fields, a PDF report is generated.
5. If risks are high — the deal moves to "Requires Approval" stage, the manager receives a notification with the report.
6. If risks are low — the deal proceeds through the pipeline without delays.

The entire cycle takes at most 5 seconds, of which 3 seconds is waiting for Kontur.Fokus response.

How to set up periodic re-evaluation of the database?

Counterparties with ongoing business are rechecked on a schedule. A cron job or Bitrix24 agent runs once a month through the base of active companies (usually 500+ records) and updates data. If the status changes (bankruptcy, large lawsuits) — the responsible manager receives a notification. Update frequency is configurable: for high-risk counterparties, weekly checks can be set.

What is included in the integration?

• Connect API of Kontur.Fokus / SPARK / DaData
• Create custom fields in the CRM company card
• Set up autofill of requisites by INN
• Develop a scoring model with risk factor weights
• Implement traffic light indicator in the company card
• Configure robots to block deals with high risk
• Periodic counterparty data updates
• Prepare documentation and train managers
• Warranty support after launch

The finished integration reduces check time by 70% and lowers overdue payments by up to 40%. Contact us for a consultation on your project. Order an implementation and get a detailed work plan.

How a corporate portal on Bitrix24 solves the problem of information chaos?

Employees spend up to 2 hours a day searching for files, emails, and solutions. Tasks get lost in dozens of chats, approvals get stuck for weeks. The manager learns about missed deadlines only at a meeting. A corporate portal on Bitrix24 ties every message, document, and task to a single context. You get a transparent picture of work: who is working on what, which stages, where bottlenecks are. Wikipedia: Information silo describes how unorganized data reduces productivity – a portal cuts that loss by 60–70%.

We will evaluate your project for free – contact us to get the architecture in 2 days. A medium‑sized company typically saves 2.5 million rubles annually after deployment (based on our projects).

What does the portal offer in daily work and why is it better than messengers?

In messengers, information is unstructured – discussions get buried within a week. On the portal, every message is tied to a task, project, or document. Employees spend up to 30% of their work time searching for data (McKinsey). The portal reduces this time by 2–3 times thanks to structured repositories and full‑text search.

Communications. Activity stream, messenger, and video calls are tied to specific tasks. Any discussion can be found six months later – in a messenger it would be buried within a week.

Tasks and projects. Kanban, Gantt, checklists, dependencies, time tracking. Each employee's efficiency is visible in reports – no need to wait for a meeting.

Document flow. Approval routes through the business process designer: leave request → manager → HR → accounting. Electronic signature, versioning, deadline control. Integration with electronic document management (SBIS, Diadoc) via REST API.

HR. Onboarding of new employees, leave/travel requests, organizational structure, absence schedule. An employee knows where to go from day one.

Knowledge base. Bitrix24 wiki engine: regulations, instructions. Knowledge does not leave with departing employees.

Implementation example. For a manufacturing company with 320 employees, we deployed a portal with integration of 1C:SALARY AND HR MANAGEMENT and Active Directory in 4 months. Travel request approval time decreased from 3 days to 4 hours. Savings on employee idle time amounted to 1.5 million rubles per year. Managers receive automatic reports on department efficiency. Customer response time decreased by 20%. Portal payback period is 7 months.

How does integration with 1C and Active Directory accelerate HR management?

Integration with 1C:Enterprise via the b24connector module or custom REST handler: a leave request is approved on the portal through a business process and automatically enters 1C:SALARY AND HR MANAGEMENT for vacation pay calculation. Active Directory (SSO via the ldap module) – the employee account is created once in AD and synchronized to the portal, email, VPN. Upon dismissal, it is blocked everywhere. Manual account creation is eliminated, errors are minimized.

Types of corporate portals and key integrations

Additional integrations that deliver real value:

• Email: Exchange via EWS API or IMAP, calendar synchronization, creating a task from an email.
• IP telephony: Asterisk, Mango Office, Zadarma via REST API – calls from the portal, contact card, call recording.
• Video conferencing: built‑in video calls or integration with Zoom/Teams via marketplace.
• EDI: SBIS, Diadoc via REST API – fully electronic document flow with counterparties.

Security and compliance with Federal Law 152‑FZ

The portal contains personal data, financial reports, strategic plans. We guarantee protection:

• role model via CGroup and section‑level permissions;
• two‑factor authentication (OTP, Yandex.Key, SMS);
• audit of all actions (b_event_log);
• TLS encryption for transmission and disk encryption;
• full compliance with Federal Law No. 152‑FZ "On Personal Data".

How is implementation carried out? Step‑by‑step plan

1. Audit — we record current processes, measure time losses.
2. Design — choose portal type, plan integrations.
3. Implementation — configure business processes, permissions, interface.
4. Test — pilot group tests scenarios, we fix issues.
5. Launch — connect all employees, train, hand over documentation.

What you receive after implementation

• Project documentation: architecture, integration scheme, business process diagrams.
• Configured portal with all integrations (1C, AD, telephony, EDI).
• Business process descriptions and instructions for administrators and users.
• 30 days of technical support after launch.
• Access to our knowledge base and migration scripts.

Post‑launch support: how to prevent the portal from becoming obsolete

After six months, many portals become abandoned. To avoid this, we offer packages with fixed SLA and a dedicated administrator. Performance monitoring, platform updates, user administration, development of new modules. Our team has over 10 years of experience and more than 50 implemented corporate portals on Bitrix24. We are a certified 1C‑Bitrix partner, guaranteeing quality and deadlines.

Mobile access. Native Bitrix24 app (iOS/Android) with push notifications, tasks, chats. Responsive web interface for extranet users (no app installation required). Offline access to documents and tasks, sync when connectivity is restored.

Order a turnkey corporate portal implementation

Schedule a free audit – we will evaluate your project, propose architecture, and give clear timelines. Get a comprehensive proposal and see that the portal pays for itself within the first six months. Contact us today.