Setting Up 1C and Bitrix Mutual Settlement Exchange

A wholesale client on a building materials portal has a debt of 2.5 million rubles, and the sales department spends 10 hours a week on phone calls—a familiar pain. We configure the exchange of mutual settlements between 1C and 1C-Bitrix so that the buyer sees the exact balance in their personal account and the system automatically blocks the order when the credit limit is exceeded. Our integration experience shows: without automating this task, a company loses up to 15% of revenue due to delays, and managers are forced to manually reconcile debts.

Mutual settlements in the personal account are a standard for B2B stores and wholesale portals. The client should see the current debt, payment history, and debt on specific orders. All this data lives in 1C (UT, ERP, KA)—and it needs to be transferred to Bitrix without losses and with acceptable performance. Below we'll break down the solution architecture with an emphasis on reliability and speed. Proper configuration of mutual settlement exchange pays for itself in 2-3 months by reducing delays and speeding up the sales department.

Mutual Settlement Data: What is Stored in 1C

In 1C (UT, KA, ERP, BP), mutual settlements with counterparties are stored in the accumulation register ВзаиморасчётыСКонтрагентами. Key data:

• Current accounts receivable—how much the counterparty owes the organization
• Accounts payable—if the organization owes the counterparty (overpayment, return)
• Overdue debt—debt exceeding the credit limit or term
• Payment history—when and how much was paid
• Source documents—invoices, orders against which there is debt

Standard CommerceML does not transfer mutual settlements. This needs to be implemented separately.

Solution Architecture: How to Transfer Debts?

To transfer mutual settlements to Bitrix, we use one of two approaches—the choice depends on the data freshness requirements.

Approach 1: 1C HTTP Service

In 1C, an HTTP service is created that returns mutual settlements for a specific counterparty on request. Bitrix calls this service when opening the "My Balance" page in the personal account.

$response = file_get_contents(
    "https://1c.example.com/ut/hs/balance/get?counterparty_id={$guid}&key={$apiKey}"
);
$balance = json_decode($response, true);

Steps to configure:

1. Create an HTTP service in 1C with a GET method to get the balance.
2. Implement a function that returns the current and overdue debt and credit limit by the counterparty's GUID.
3. In Bitrix, configure the service call with an API key, cache the response in Redis for 10 minutes.
4. Handle 1C availability errors—show cached data when unavailable.

Advantage: data is always up-to-date. Disadvantage: dependence on 1C server availability. An HTTP service provides real-time data freshness; for critical checks (order placement) it is 6 times faster than periodic synchronization.

Approach 2: Periodic Synchronization

A scheduled task in 1C generates a file with mutual settlement data and transfers it to Bitrix (via FTP, API, or direct request to a script). Bitrix saves the data in its own database and displays it to the client.

Advantage: independence from 1C availability at the moment of page load. Disadvantage: data delayed (equal to the synchronization interval, usually 30-60 minutes). An HTTP service provides greater freshness, but synchronization is more stable—we choose according to the task. For B2B with frequent orders, an HTTP service is preferable; for budget projects, synchronization.

What Is Included in Our Work to Configure the Exchange?

After implementation, you get a guarantee of stable synchronization: we leave monitoring for 14 days and promptly fix incidents. Plus a free consultation on improvements after one month of operation.

Implementation in Bitrix: HighloadBlock Structure

To store mutual settlements in Bitrix, I recommend creating a HighloadBlock—for example, ContractorBalance:

For payment history—a separate HighloadBlock ContractorPayments with records for each payment.

Linking a Counterparty to a Bitrix User

The main technical challenge: knowing which Bitrix user corresponds to which counterparty in 1C. Options:

1. By user XML_ID. When registering on the site, a counterparty is created in 1C (via REST API), its GUID is saved in the Bitrix user profile (field UF_1C_CONTRACTOR_ID).

2. By TIN (Taxpayer Identification Number). The user enters a TIN during registration, and the system looks up the counterparty in 1C by TIN.

3. Manual mapping. The administrator in Bitrix manually links a user to a counterparty. Suitable for B2B with a small number of clients.

Credit Limit and Order Prohibition

A popular scenario: if the counterparty has overdue debt—prohibit placing new orders on the site. Or: if the debt exceeds the credit limit—show a warning.

Implementation via Bitrix event OnSaleOrderBeforeSaved:

AddEventHandler('sale', 'OnSaleOrderBeforeSaved', 'checkDebtLimit');

function checkDebtLimit(\Bitrix\Main\Event $event) {
    $order = $event->getParameter('ENTITY');
    $userId = $order->getUserId();
    $debt = getContractorDebt($userId);
    $limit = getContractorCreditLimit($userId);

    if ($debt['overdue'] > 0) {
        $result = $event->getParameter('RESULT');
        $result->addError(new \Bitrix\Main\Error(
            'Order placement is not available: there is overdue debt'
        ));
    }
}

This code works for any limit management scenarios.

Case Study: Wholesale Building Materials Portal

B2B portal: 300 active counterparties, each with a credit limit. Task: show the balance in the personal account and prohibit orders when the limit is exceeded. We used the HTTP service approach from 1C to get the current debt in real time. We cached the response for 10 minutes (Redis). When placing an order—always a fresh request, no cache.

Additionally: we displayed a breakdown on the personal account page—a list of open invoices with amounts and payment dates. Data from the HighloadBlock, updated once an hour.

We measured the result after 3 months: managers stopped manually informing clients about debts—the number of calls "why can't I order" dropped by 70%. Clients themselves see the debt and pay before placing a new order. Compare: manual calling took 10 person-hours per week, automation reduced it to 3 hours—3 times faster. Average savings on manager salaries amounted to 30,000 rubles per month. Automation paid for itself in 2 months.

How Long Does It Take to Set Up Mutual Settlement Exchange?

We estimate the project at 2 working days after filling out the brief. Basic setup (one approach, no custom rules) takes from 5 to 10 working days. If complex scenarios are needed (multiple currencies, automatic blocking by credit limit, integration with Bizproc)—we clarify timelines individually. Contact us—get an accurate estimate for your project.

Why Order the Setup from Us?

We have been working with Bitrix and 1C for 10+ years and have completed 50+ integration projects. Our team includes certified 1C engineers and Bitrix developers. We provide a code guarantee—6 months of free support. After implementation, you will be able to manage the data yourself through the administrative interface.

Order the setup today—and start managing debts without manual labor. Get a consultation on the architecture of mutual settlement exchange: we will evaluate your register, choose the optimal transfer method, and implement a turnkey solution with documentation.

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.