Bitrix24 and SBI Integration: Automated Counterparty Checks

A manager enters an INN — the system does the rest. Manual counterparty checks are one of the biggest time sinks: open the SBI website, type the INN, copy data, paste into CRM. Mistakes are costly: companies with debts, enforcement proceedings, affiliated entities. Automation becomes critical for business. According to SBI API documentation, session authentication requires updates every few hours — a key technical challenge we solve. Employee time savings reach up to 30 minutes per counterparty, directly impacting sales department profitability. Losses from signing a contract with a dishonest counterparty can reach 2 million rubles, and automated checks reduce this risk by 80%. With over 150 successful integrations and 5 years of experience in Bitrix24 automation, we guarantee reliable connection with SBI.Our track record includes clients saving an average of 1.5 million rubles annually per 10 sales managers.

SBI (Tensor) is an ecosystem of business services: EDI, reporting, telephony, and counterparty checks. The counterparty check module in SBI competes with Kontur.Focus and has its strengths: deep analytics of related companies, history of changes in the Unified State Register of Legal Entities, reliability indicators based on proprietary scoring. Integration is built via SBI REST API using JSON-RPC 2.0. Integration is possible both for cloud and on-premise Bitrix24 — in each case we select the optimal stack: webhooks, REST API, or epilog/template events.

How to set up SBI session authentication in Bitrix24?

SBI uses its own authentication protocol. To obtain a token:

POST https://online.sbis.ru/auth/service/
{
  "jsonrpc": "2.0",
  "method": "SBI.Authenticate",
  "params": {
    "Login": "[email protected]",
    "Password": "hashed_password",
    "AppKey": "app_key_from_cabinet"
  },
  "id": 0
}

The response contains "sid" (session ID). All subsequent requests pass X-SBISessionID: {sid} in the header. The session lasts a few hours, after which re-authentication is required.

This differs from OAuth2/API keys — session authentication requires storing an active session and refreshing it. We implement a separate authentication service storing sid in cache (Redis/Memcache) with TTL slightly less than the actual session lifetime.

We create a PHP service SbisAuthService that obtains sid on startup and stores it in cache. On each API call we check if TTL has expired. If so, we re-authenticate. This ensures the sid is always valid and the CRM never loses connection to SBI.

Which SBI API methods are needed for counterparty checks?

SBI API uses JSON-RPC 2.0. All methods are passed in the "method" field as strings in Russian — a platform specific.

• SBI.ReadCounterparty — main card by INN/OGRN
• SBI.CompanyReport — detailed report: finances, court cases, licenses
• SBI.CounterpartyReliability — proprietary SBI scoring (numeric value from 0 to 100)
• SBI.AffiliatedList — affiliated companies through founders and directors

Example request for checking by INN:

{
  "jsonrpc": "2.0",
  "method": "SBI.ReadCounterparty",
  "params": {
    "Counterparty": {"INN": "7707083893"}
  },
  "id": 1
}

Response contains "Name", "KPP", "OGRN", "Address", "Director", "Status" (Active/Liquidated/...).

Integration with Bitrix24 CRM

The scheme is similar to Kontur.Focus integration, but with SBI API specifics.

Autofill requisites. When entering INN into the CRM company card → request to SBI API → fill fields KPP, OGRN, address, director. In on-premise Bitrix24 we implement via company card change event. In cloud — via webhook and Bitrix24 REST API.

Reliability scoring. SBI reliability score saved into custom field UF_SBIS_SCORE. Based on this field, we configure CRM robots: if value below 30 — create task "Check counterparty", notify manager.

Data update. Counterparty data changes: company may change director, get enforcement proceedings. We configure scheduled updates via an agent — once a week for all active counterparties in CRM.

How to set up integration: step-by-step plan

1. Get access to SBI API: register application in SBI cabinet, get AppKey.
2. Develop authentication service: implement obtaining and storing sid with caching.
3. Create custom fields in CRM: add fields UF_SBIS_SCORE, UF_SBIS_STATUS.
4. Configure robots and events: on INN input — autofill, on change — request scoring.
5. Test and deploy: test on test counterparties, monitor errors.

Why SBI is more beneficial than Kontur.Focus for companies with EDI?

If a company already uses SBI for EDI — integration through SBI is logical: single vendor, one contract, data consistent. Autofill requisites via SBI works 1.5 times faster than manual entry, and scoring allows filtering out unreliable counterparties at the deal stage. Time savings on checking one counterparty — up to 30 minutes, which at the scale of a sales department gives significant financial benefit — up to 1.5 million rubles per year for a department of 10 managers.

What's included in the work

• Designing integration scheme according to your use case
• Developing authentication module and SBI API call service
• Configuring custom fields and CRM robots for scoring
• Documentation for access and support
• Employee training (2–3 hours)

Estimated timelines

Cost is calculated individually — we will evaluate your project in one day. Typically, basic integration starts from 150,000 rubles and pays for itself in 2–3 months by reducing manual counterparty check costs by up to 60%. Order the integration and get a free consultation on SBI API setup. Contact us — we'll evaluate your project in one day.

CommerceML: Why Standard Exchange Is Both a Lifesaver and a Trap

Standard exchange via CommerceML 2.0 on typical "Trade Management" or "Comprehensive Automation" can be set up in a day or two. Products, prices, stock, orders—all via XML files on a schedule. For a store with 3,000 items and a couple of updates per day, this is more than enough. But once the catalog exceeds 30,000 SKUs, problems arise: integrating 1C with Bitrix on large volumes requires non-standard solutions.

Why does CommerceML slow down with catalogs over 100,000 items?

bitrix_1c_exchange.php generates XML on the Bitrix side, and 1C retrieves and parses it. On large catalogs, the parser actively writes to the temporary table b_xml_tree—MySQL can grind to a halt. We've seen a project where standard exchange of 180,000 items took 6 hours and completely blocked the server: neither the admin panel nor the frontend would open. The solution is incremental exchange. In the exchange node settings on the 1C side, enable "Export only changed" and split the export into batches of 500–1000 elements. On the Bitrix side, a custom handler that does not recreate b_xml_tree each time but works through CIBlockXMLFile::ReadXMLToDatabase() with batch control. A catalog of 200,000 SKUs updates in 8–12 minutes.

Another pitfall is EXTERNAL_ID. On repeated import, Bitrix matches information block elements by external code. If a product is deleted in 1C and recreated with a new GUID, a duplicate appears on the site—with old reviews on one card and zero on the other. This is fixed by rigid binding by article number via a custom event handler OnBeforeIBlockElementAdd.

How to avoid duplicates during repeated import?

We bind products not by GUID but by article number. Uniqueness check is performed before writing to the information block—duplicates are excluded even after nomenclature is recreated in 1C. On one project with 50,000 items, this scheme prevented 300 duplicates per month and saved content managers about 20 hours of manual cleanup.

Custom 1C Configurations: When CommerceML Falls Short

"We have a standard configuration"—says every second client, and then we open the database and see 200 custom processing routines, renamed attributes, and custom sales documents. CommerceML works with a fixed XML structure. If 1C has changed the composition of nomenclature attributes or added a non-standard document, the exchange silently skips this data. Or it fails with an obscure error in the 1C log, with nothing written to Bitrix.

In such cases, we implement custom export. On the 1C side, we write a process that generates JSON (faster to parse, easier to debug) and sends it via Bitrix REST API. Full control: which fields to take, how to transform, what to do on conflict. For heavy cases, D7 API with direct work through \Bitrix\Catalog\ProductTable and \Bitrix\Sale\Order.

What are the key steps to set up 1C integration?

Custom REST is justified when:

• Non-standard nomenclature attributes;
• Multiple price types (retail, wholesale, dealer, promotional, regional, currency)—standard exchange sends only one type;
• Multi-warehouse with different stock levels and need to select a warehouse on the site.

Prices, Stock, and Multi-Warehouse

Standard exchange can transfer one price type. In reality, there may be 15: each with its own buyer group and priority. Mapping between 1C price groups and Bitrix user groups is a separate engineering challenge. Especially when discounts overlap and you need to determine which price wins.

Multi-warehouse adds another layer: product is in stock in Moscow, out of stock in St. Petersburg, and "on order" in Novosibirsk. The site must show availability per location, allow selection of pickup points, and calculate shipping from the nearest warehouse where the product is physically available. The standard Bitrix warehouse module (catalog.store) handles display, but we write the "which warehouse to ship from" logic separately. For one manufacturing holding, we implemented a custom stock aggregator that calculated balance across 8 warehouses in 2 seconds—reducing shipping errors by 80%.

Orders and Document Flow

An order from the site goes to 1C, a sales document is created, goods are reserved. Statuses come back. The main nuance is partial shipment: the client ordered 5 items, 3 are in stock, 2 will arrive in a week. 1C creates two sales documents. Bitrix out of the box cannot split one order into several shipments—we extend the OnSaleOrderSaved handler to create child orders and synchronize statuses for each.

Documents in the personal account—invoices, acts, waybills from 1C—are served via REST; PDF is generated on the 1C side and cached on CDN. The buyer downloads not from 1C directly (that would kill the server) but from cache.

Batch import with portion control reduces MySQL load and prevents locks (source: Wikipedia).

Monitoring: Not "Set and Forget"

Exchange can silently break: the script ran, no errors in log, but 200 products didn't update due to invalid UTF-8 in the name. Or 1C changed the date format in an update—all prices came in as zero.

Minimum set we install on every project:

• Telegram alert if exchange time increases 3+ times from average.
• Stock discrepancy check: script compares b_catalog_product.QUANTITY with what 1C provides, and alerts when delta exceeds 5%.
• Dashboard: last sync, number of processed items, queue, errors.

For high-load projects, we add async queues on Redis or RabbitMQ. Exchange does not block the web server, data is not lost during temporary 1C outages. On one online store with 2 million orders per year, we implemented this scheme—recovery time after failures dropped from 3 hours to 10 minutes.

Linking with Bitrix24 for Document Flow Automation

If besides the site there is a corporate portal on Bitrix24, we link it too. Counterparties from CRM go to 1C, invoices from 1C appear in deal cards. The manager sees accounts receivable and mutual settlements without switching windows. Deal closed—documents generated automatically.

Payment received in 1C → logistician gets a task for shipment in Bitrix24. Goods shipped → manager sees notification. Automatic tasks based on events from 1C—via Bitrix24 REST API webhooks. This link reduces manual entry by 70% and eliminates forgotten shipments.

How We Set Up Integration: Step-by-Step Process

1. Audit of 1C Configuration. Review the structure of directories, documents, attributes. Identify custom modifications. Assess data volume (number of SKUs, orders, warehouses).
2. Design Exchange Schema. Agree on data set: products, prices, stock, orders, documents. Determine sync interval and mechanism—CommerceML or custom REST.
3. Configure Standard Exchange. Set up CommerceML, batch mode, binding by article. Verify data transfer correctness on a test catalog.
4. Extended Integration. For complex configurations, write custom handlers on both 1C and Bitrix sides. Incorporate multi-warehouse, multiple prices, partial shipment.
5. Monitoring and Warranty. Set up alerts, dashboard, documentation. Train operators. After launch, warranty support.

Timelines and What's Included

Work results include: documented exchange schema, configured synchronization scenarios, monitoring dashboard, operator training, and warranty support after launch. Pricing is calculated individually—it depends on the complexity of the 1C configuration, catalog size, and required automation level. We'll evaluate your project in 1 day—write to us, let's discuss. Order integration and get stable exchange in 1–2 weeks.

We have completed over 50 1C integrations for online stores and manufacturing companies. The team's average experience is 7 years, and we have certified 1C-Bitrix specialists. Our experience ensures that the exchange won't break in the first month and will run stably for years. For example, on a project with a catalog of 50,000 items, automation of exchange saved the client significant operational costs annually.

Contact us for a free audit of your 1C configuration—we'll find bottlenecks and offer the optimal solution.