Bitrix24-1С Integration: Orders, Payments, Documents Sync

When a company grows to 15–20 managers, customer data, orders, and payments live separately in the CRM and accounting system?

A manager sees a deal in Bitrix24 but doesn't know if payment went through in 1С. An accountant sees a payment but can't link it to a specific deal without a phone call. We solve this problem: we design and successfully implement a two-way data exchange channel between Bitrix24 and 1С:Enterprise, handling Bitrix24-1C Enterprise setup for seamless synchronization. Our engineers have extensive experience in integrations and have completed over 50 successful projects for various configurations: 1С:Trade Management, 1С:Retail, 1С:Accounting, and others. A typical project takes 2 to 4 weeks, full document flow up to 3 months. We guarantee stable exchange and round-the-clock technical support. Request a free integration audit — we will assess your project within one day.

What data do we synchronize?

The integration scope depends on business processes. In practice, three levels are distinguished:

Basic — one-way data transfer from 1С to Bitrix24 (or vice versa):

• Counterparties from 1С → companies and contacts in CRM (contact synchronization)
• Products from 1С → Bitrix24 catalog (product catalog sync)
• Orders from Bitrix24 → "Customer order" documents in 1С (order exchange)

Extended — two-way synchronization with feedback:

• Payments from 1С → change deal stage in Bitrix24 (payment synchronization)
• Counterparty debt from 1С → field in company card
• Shipments from 1С → update order status

Full — document flow synchronization (document exchange bitrix24 1c):

• Invoices from Bitrix24 → invoices in 1С
• Certificates of completed work
• Waybills, invoices
• Real-time stock balances

Complexity of counterparty synchronization

In 1С, a counterparty is a legal entity with an INN. In CRM, a contact is an individual representing a company. Data structures are fundamentally different. Typical problems when merging databases:

• The same client is entered as "LLC Romashka" and "Romashka LLC" — without INN as a key, duplicates arise.
• In Bitrix24, one contact can be linked to several companies; in 1С, no such relationship exists.
• Individuals in CRM have no INN but may make purchases.

Solution: synchronization key — INN for legal entities, phone or email for individuals. During initial load, we run deduplication: find a match by key, update if match, create a new record with XML_ID for subsequent identification if no match.

Technical connection options

The integration architecture is determined by whether cloud or on-premise Bitrix24 is used and which 1С configuration.

REST API + webhooks — a universal option. Bitrix24 provides REST API for all CRM objects. An HTTP service is deployed on the 1С side. Works with any Bitrix24. REST API is 2–3 times faster than traditional CommerceML file exchange, reducing latency significantly.

Standard 1С-Bitrix24 module — built into on-premise Bitrix24. Exchanges data via CommerceML or COM connection (Windows only). Synchronizes products and orders, but does not transfer financial documents — requires customization.

Enterprise service bus (ESB) — for complex scenarios with multiple legal entities or 1С databases. We use 1С:Data Conversion or custom PHP middleware.

How to synchronize products and balances?

Products are transferred from 1С to Bitrix24 (or both directions). For each product, critical attributes:

• SKU (product code) — key for identification, also XML ID.
• Unit of measurement — mapping OKEI to CRM units.
• Prices — if 1С has multiple price types, determine which goes into which price list.
• Balances — by warehouse and frequency (active trading: every 15–30 minutes, B2B: once per hour).

How are payments transferred from 1С to Bitrix24?

Transferring payments from 1С to Bitrix24 is key for managers. The deal card should show: payment fact, amount, date, balance. In 1С, a scheduled task checks processed receipts and incoming cash orders, finds the deal by invoice number, and calls crm.deal.update.

Case from our practice: wholesale and retail company, 3 legal entities

Our client — a company with three legal entities, 25 managers, and two 1С databases (retail and wholesale). The task — a single Bitrix24 with visibility of finances from both databases. Architectural solution: an intermediate PHP service aggregates data. The source is encoded in a custom deal field ("Seller legal entity") so the handler knows where to write. A separate complexity — mutual settlements between legal entities: when moving a deal between funnels, we zero out the debt for one and create for another. Implemented via a custom event in the business process.

What's included (deliverables)

1. Audit of current processes and data (deduplication, mapping)
2. Selection of architecture and exchange protocol
3. Development and configuration of integration
4. Testing on database copies
5. Documentation of scheme and fields
6. User training
7. Post-launch support (monitoring, alerts, fixes)
8. Access to integration logs and monitoring dashboards

Deliverables ensure a smooth transition and long-term stability. With over 5 years of integration experience and 50+ successful projects, we deliver reliable solutions that save clients 20-30 hours of manual data entry monthly. Typical integration investment ranges from $3,000 to $15,000, with payback in 3–6 months. Compared to manual processes, our integration reduces data entry errors by 80%.

Common pitfalls and solutions:

• Duplicate counterparties: use INN as synchronization key.
• Data loss during failure: configure retry sending.
• Currency mismatch: map currencies at the start.

Estimated timeline

The integration pays off by eliminating manual entry and reducing operational costs. We guarantee stable exchange and prompt support. Contact us for a consultation.

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.