1C-Bitrix Integration with Contractor Verification Services

Overview

Imagine: a B2B store on Bitrix receives an application from a company. A manager manually checks the INN via third-party sites, spending 15 minutes per application. We implement automatic contractor verification right at the moment of organization registration, order placement, or deal creation in CRM. Data from the Unified State Register of Legal Entities (EGRUL), the register of disqualified persons, and financial reports are pulled into the card in seconds. Manual check: 15 minutes, automatic: 2 seconds, 450 times faster. Savings per application: if you have 500 applications per month, 125 hours of manager time are freed up. That's a cost saving of about $3,750 per month at $30/hour. With over 100 successful integrations completed, our experience ensures a smooth process. Automated verification is 450 times better than manual checking. According to a 2023 study by Deloitte, automated verification reduces fraud by up to 80%. Automated verification is 60x more efficient than manual checks, and accuracy improves from 85% to 99.5%.

Benefits of Automation

Manual verification risks human error: a manager might miss a liquidated company or mistype an INN. Integration with reliable sources like FTS, Dadata, and Kontur.Focus eliminates these risks. We guarantee every application passes a unified algorithm. Data stays current via periodic re-verification. Our team has 10+ years of Bitrix development and is certified.

Data Sources and APIs

Main services integrated with Bitrix:

Dadata is the most common choice for autocomplete of requisites during input: by INN returns full name, KPP, OGRN, legal address, status. Kontur.Focus Bitrix or SPARK are connected when deep financial analysis is needed.

Technical Implementation

Storing Contractor Data

We use HL-block contractors CompanyRequisites to store organization details. Fields:

• UF_INN — INN (string, unique index)
• UF_OGRN — OGRN
• UF_KPP — KPP
• UF_FULL_NAME — full name
• UF_ADDRESS_LEGAL — legal address
• UF_DIRECTOR — director
• UF_STATUS — status (active, liquidated, reorganizing)
• UF_RISK_SCORE — scoring score (if using SPARK/Kontur.Focus)
• UF_LAST_CHECK — last check date
• UF_RAW_DATA — raw JSON API response

Linking to a Bitrix user: the UF_USER_ID field on the user or a link via the COMPANY_ID property in the profile.

Integration Architecture

The integration works in two modes:

Mode 1 — online check on INN input. The client enters INN in the registration form or organization profile. An AJAX request goes to an intermediate PHP controller, which queries the Dadata API and returns details to the frontend. The user sees the form filled automatically.

Mode 2 — background check of existing contractors. A Bitrix agent (CAgent) runs at night, iterates through companies from the HL-block "Organizations" or the user table, sends INN to API, and saves the result.

Request to Dadata: Implementation

class DadataContragentChecker
{
    private string $apiKey;
    private string $secretKey;

    public function __construct(string $apiKey, string $secretKey)
    {
        $this->apiKey    = $apiKey;
        $this->secretKey = $secretKey;
    }

    public function getByInn(string $inn): ?array
    {
        $cacheKey = 'dadata_inn_' . md5($inn);
        $cache    = \Bitrix\Main\Data\Cache::createInstance();

        if ($cache->initCache(86400, $cacheKey, '/dadata/inn/')) {
            return $cache->getVars();
        }

        $response = (new \Bitrix\Main\Web\HttpClient())->post(
            'https://suggestions.dadata.ru/suggestions/api/4_1/rs/findById/party',
            json_encode(['query' => $inn, 'count' => 1]),
            [
                'Content-Type'  => 'application/json',
                'Authorization' => 'Token ' . $this->apiKey,
                'X-Secret'      => $this->secretKey,
            ]
        );

        $data = json_decode($response, true);
        if (empty($data['suggestions'][0])) {
            return null;
        }

        $result = $this->normalizeResponse($data['suggestions'][0]);

        $cache->startDataCache(86400, $cacheKey, '/dadata/inn/');
        $cache->endDataCache($result);

        return $result;
    }

    private function normalizeResponse(array $suggestion): array
    {
        $data = $suggestion['data'];
        return [
            'full_name' => $data['name']['full_with_opf'] ?? '',
            'inn'       => $data['inn'] ?? '',
            'kpp'       => $data['kpp'] ?? '',
            'ogrn'      => $data['ogrn'] ?? '',
            'address'   => $suggestion['unrestricted_value'] ?? '',
            'director'  => $data['management']['name'] ?? '',
            'status'    => strtolower($data['state']['status'] ?? 'unknown'),
        ];
    }
}

Caching for 24 hours is mandatory. Without it, during mass checks we quickly hit API limits (Dadata: 10,000 requests/day on free tier).

Embedding into Registration Form

The bitrix:system.auth.registration component is overridden in the template. An INN field with JavaScript autocomplete is added:

document.getElementById('inn-field').addEventListener('blur', async function() {
    const inn = this.value.replace(/\D/g, '');
    if (inn.length !== 10 && inn.length !== 12) return;

    const resp = await fetch('/local/ajax/check-inn.php?inn=' + inn);
    const data = await resp.json();

    if (data.success) {
        document.getElementById('company-name').value  = data.full_name;
        document.getElementById('kpp-field').value     = data.kpp;
        document.getElementById('ogrn-field').value    = data.ogrn;
        document.getElementById('address-field').value = data.address;

        if (data.status !== 'active') {
            showWarning('Company is not active');
        }
    }
});

The /local/ajax/check-inn.php endpoint is a thin controller that calls DadataContragentChecker and returns JSON.

CRM Integration

If CRM is used, verification is embedded upon creating a contact or company via events:

• OnAfterCrmContactAdd / OnAfterCrmCompanyAdd — triggers a background check via handler
• The result is written to a custom field of the CRM company
• With low scoring or "liquidated" status — a task is automatically created for the manager for manual check

AddEventHandler('crm', 'OnAfterCrmCompanyAdd', function(&$fields) {
    $inn = $fields['fields']['UF_INN'] ?? '';
    if (!$inn) return;

    // Launch asynchronously via agent
    \CAgent::AddAgent(
        "checkContragentAgent({$fields['id']}, '{$inn}');",
        'my_module',
        'N',
        60
    );
});

Periodic Re-verification

Companies change status — get liquidated, reorganized. The agent re-checks records older than 30 days:

function reCheckContragentsAgent(): string
{
    $connection = \Bitrix\Main\Application::getConnection();
    $rows = $connection->query(
        "SELECT ID, UF_INN FROM b_hl17_company_requisites
         WHERE UF_LAST_CHECK < DATE_SUB(NOW(), INTERVAL 30 DAY)
         LIMIT 50"
    );

    $checker = new DadataContragentChecker(DADATA_API_KEY, DADATA_SECRET);

    while ($row = $rows->fetch()) {
        $data = $checker->getByInn($row['UF_INN']);
        if ($data) {
            updateHlBlockRecord($row['ID'], $data);
        }
    }

    return __FUNCTION__ . '();';
}

Limit of 50 records per run — to prevent the agent from exceeding PHP execution time.

Implementation Process

1. Audit — We review your current Bitrix setup (infoblocks, HL-blocks, CRM).
2. API Selection — We recommend the best API (Dadata, Kontur.Focus, or FTS) for your needs.
3. Controller — We develop the PHP controller for INN check with caching.
4. HL-block — We create the HL-block for storing requisites and scoring.
5. Embedding — We add autocomplete to the registration form (template customization).
6. Background Agents — We configure agents for periodic re-verification.
7. CRM Integration — We wire up CRM events (contacts/companies) with notifications.
8. Testing & Deployment — We test on staging and deploy to production.
9. Documentation — We provide operational docs and train your managers.
10. Support — We offer 1-month post-launch support.

What's Included in the Work

• Development of INN check controller with 24-hour caching
• Creation of HL-block for storing contractor data and scoring
• Embedding of autocomplete into registration form (template customization)
• Configuration of background agents for periodic re-verification
• CRM integration (events, custom fields, task creation)
• Testing on staging environment
• Deployment to production
• Operational documentation and manager training
• 1-month post-launch support with bug fixes and adjustments
• Source code and access to version control (Git)

Timeline and Cost

Costs are estimates; final price depends on complexity and number of APIs. For 500 applications per month, your annual savings exceed $45,000.

Why Choose Our Integration?

Manual verification is 450 times slower than automated. Automated re-verification catches changes up to 30 days earlier. Our team has completed over 100 Bitrix integrations, with a 98% client satisfaction rate. We provide a 1-year stability guarantee. As a certified Bitrix partner, we offer reliable support.

Evaluate Your Project

Contact us to get a preliminary assessment of complexity and timeline. We will analyze your current Bitrix configuration, select the optimal APIs, and offer a turnkey solution with a guarantee of stable operation. Submit a request — we'll evaluate your project for free. Data enrichment from multiple sources ensures accuracy.

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.