Automatic setup of invoice exchange between Bitrix24 and 1С

We often encounter a situation where accounting asks to copy invoices from Bitrix24 to 1С manually. The result — errors in numbers, duplicates, discrepancies in payment statuses. Clients lose time, managers don't see the real picture. Our task is to configure automatic invoice exchange so that data flows without human intervention. With 10+ years of Bitrix work, we have conducted over 50 integrations and know all the pitfalls. An error in one field can cost a deal closure — that's why automation must be flawless.

Every day, accountants spend hours reconciling statuses, while managers cannot promptly tell the client if the invoice is paid. We fix this: after setup, the invoice is created in CRM, automatically sent to 1С, processed there, and the status returns instantly. No manual input. Time savings — over 10 hours per week per accountant. Typical savings for a mid-size business — 400,000 RUB per year on accounting reconciliation. Errors are virtually eliminated.

Why is invoice exchange automation necessary?

Manual invoice transfer leads to:

• status discrepancies (paid in CRM but not posted in 1С);
• document duplicates;
• item mismatches (article numbers don't match);
• delays in month-end closing.

Automation eliminates the human factor and speeds up month-end closing. Comparison: automated exchange processes an invoice in 1 second, manual takes from 5 minutes with risk of error. That's 300 times faster.

How the exchange works

Standard exchange is built on the crm module and the CommerceML protocol (XML format for commercial documents). For invoices, a mechanism different from internet store orders is used: CRM invoices are transferred via Bitrix24 REST API or through the standard 1С integration module. Two options:

1. Via REST API (crm.invoice.* or crm.item.* for smart invoices). An external script polls Bitrix24 and fetches new/changed invoices. Requires development on the 1С side but gives full control.
2. Via CommerceML — Bitrix24 standard module. 1С initiates a session, Bitrix outputs XML. Less code but stricter format.

According to official documentation, CommerceML is suitable for most standard scenarios.

Invoices in CRM: old and smart

Bitrix24 has two invoice entities:

• Old invoices (CRM_INVOICE) — legacy type, table b_crm_invoice. Accessible via crm.invoice.list, crm.invoice.get.
• Smart invoices (SMART_INVOICE) — based on CRM smart processes. crm.item.list with entityTypeId = 31.

During setup, it is important to determine which type is used. If the portal switched to smart invoices, old methods won't work.

Comparison of integration methods

CommerceML is better if you already have order exchange and need a single integration point. REST API is more flexible for complex logic but requires more development on the 1С side. Most often, REST is chosen for smart invoices, CommerceML for old ones.

What is transferred to 1С

Minimum required data for posting:

How to set up exchange considering invoice types?

1. Determine the invoice type (old or smart) via CRM settings.
2. Choose protocol: REST (recommended for smart) or CommerceML.
3. Create an integration user with CRM read permissions.
4. Set up a webhook to notify 1С about a new invoice.
5. On the 1С side, configure the exchange node and frequency.
6. Conduct test synchronization.
7. Set up reverse transfer of payment status.

Case study

On one project, the client was losing up to 15% of invoices due to article number mismatches. We identified that 1С and Bitrix24 used different item identifiers. Solution — add XML_ID to the trade catalog and configure matching via CommerceML. After that, errors completely disappeared. The synchronization has been running for 2 years without failures. Errors led to losses of up to 300,000 RUB quarterly — the automation paid off in the first month.

What's included in the setup

• Analysis of current exchange and identification of bottlenecks.
• Setting up integration user and access permissions.
• Configuring the 1С module or REST script.
• Testing the cycle: invoice creation — export — posting — status.
• Documentation of the exchange scheme.
• Support for 2 weeks after launch.

Process of evaluation and work

Our work process follows these stages: data collection → audit/analysis → design → estimate → development → testing → launch. We first assess your infrastructure and requirements, then provide a fixed-price estimate based on the scope. No hidden costs.

Timeline estimates

Basic setup takes from 4 to 8 hours, provided a 1С specialist is available. A full cycle with testing and feedback typically requires 1-2 working days. Longer timelines apply if additional customizations are needed.

If you want to speed up month-end closing and eliminate errors, order invoice exchange setup now. Our experience — 10+ years in Bitrix development, over 50 successful integrations. Get a consultation on invoice exchange automation — we will analyze your infrastructure and offer the optimal solution.

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.