1C-Bitrix integration with SBIS for counterparty verification

1C-Bitrix Integration with SBIS Counterparty Verification

SBIS (Tensor) is a business services ecosystem covering electronic document management (EDM), reporting, telephony, and counterparty verification. The SBIS counterparty verification module competes with Kontur.Focus and has its own strengths: deep analytics on affiliated companies, a history of changes in the Unified State Register, and a proprietary reliability scoring system. Integration with 1C-Bitrix is built through the SBIS REST API.

SBIS API: Authentication and Structure

SBIS uses a proprietary authentication protocol. To obtain a token:

POST https://online.sbis.ru/auth/service/
{
  "jsonrpc": "2.0",
  "method": "СБИС.Аутентифицировать",
  "params": {
    "Логин": "[email protected]",
    "Пароль": "hashed_password",
    "АппКлюч": "app_key_from_cabinet"
  },
  "id": 0
}

The response contains "sid" (session ID). All subsequent requests must include X-SBISSessionID: {sid} in the header. The session lives for several hours and then must be re-authenticated.

This differs from OAuth2/API keys — session-based authentication requires maintaining an active session and renewing it. Implement a dedicated authentication service that stores the sid in a cache (Redis/Memcache) with a TTL slightly shorter than the actual session lifetime.

Methods for Counterparty Verification

SBIS API uses JSON-RPC 2.0. All methods are passed in the "method" field as Russian-language strings — this is a platform-specific feature.

• СБИС.ПрочитатьКонтрагента — basic record by TIN/OGRN
• СБИС.ОтчётОКомпании — detailed report: finances, court cases, licences
• СБИС.НадёжностьКонтрагента — SBIS proprietary scoring (numeric value from 0 to 100)
• СБИС.СписокАффилированных — affiliated companies through founders and directors

Sample TIN lookup request:

{
  "jsonrpc": "2.0",
  "method": "СБИС.ПрочитатьКонтрагента",
  "params": {
    "Контрагент": {"ИНН": "7707083893"}
  },
  "id": 1
}

The response contains "Название", "КПП", "ОГРН", "Адрес", "Руководитель", "Статус" (Active/Liquidated/...).

Integration with Bitrix24 CRM

The integration pattern mirrors the Kontur.Focus integration but accounts for SBIS API specifics.

Auto-filling registration details. When a TIN is entered into the CRM company record → request to SBIS API → populate KPP, OGRN, address, and director fields. In on-premise Bitrix24, implement via the company record change event. In cloud Bitrix24 — via a webhook and the Bitrix24 REST API.

Reliability scoring. Save the SBIS reliability score to the custom field UF_SBIS_SCORE. Based on this field, configure CRM robots: if the value falls below 30 — create a task "Verify counterparty" and notify the manager.

Data updates. Counterparty data changes: a company may replace its director or receive enforcement proceedings. Schedule periodic updates via an agent — once a week for all active CRM counterparties.

SBIS vs Kontur.Focus for Integration

If a company already uses SBIS for electronic document management, integrating through SBIS is the logical choice: a single vendor, one contract, consistent data.

Estimated Timelines

Pricing is calculated individually. For estimation, the following are needed: Bitrix24 deployment type (cloud/on-premise), size of the CRM counterparty database, and data refresh frequency requirements.