Bitrix24 and 1C Integration: Automatic Invoice Generation

The Problem of Manual Invoice Creation: Time Loss and Errors

When manually transferring invoices from Bitrix24 to 1C, accountants spend 5–8 minutes per document, and managers wait for the number for hours. Errors are inevitable: wrong SKU, extra line, incorrect quantity. Each such error leads to returns, re-approvals, and loss of customer trust. For a wholesale company with 30–50 orders per day, this means dozens of lost man-hours per week. Our team has over 10 years of experience and 40+ integration projects. We automate this process: the invoice is created automatically in 1C when the deal status changes. Integration pays off in 2–3 months by eliminating errors and speeding up work.

Types of Invoices and Their 1C Counterparts

Before setting up integration, you need to determine the document type. In Bitrix24, events are tied to deal statuses; in 1C, each document has its own operation type.

For online stores and wholesale trade, TORG-12 → 'Sales of goods' is most commonly needed.

Mandatory Data for the Invoice

The invoice field set is stricter than for an act. Besides standard parties and items, you must transfer:

• Shipping warehouse. In Bitrix24, the warehouse can be a custom field of the deal or taken from the inventory module. In 1C, the warehouse is tied to the department.
• Units of measurement (OKEI). Bitrix24 often uses simplified units (pcs, kg), while 1C uses a reference with codes. Mapping is required.
• Serial numbers and batches (if batch accounting is used). The handler must be able to select a batch when creating the invoice.

How Two-Stage Integration Works

The optimal scheme for trading companies is two-stage transfer with reservation. This reduces error risk and locks goods immediately after the order.

Stage 1 – Reservation. When the order is confirmed in Bitrix24 (status 'Order accepted'), a 'Customer Order' document is created in 1C. Goods are reserved in stock before actual shipment.

Stage 2 – Invoice creation. When the deal moves to 'Shipped' status, the handler creates a 'Sales of Goods' document based on the 'Customer Order'. The link is through the external code of the document.

Bitrix24: status 'Shipped'
    ↓ webhook
PHP handler:
    crm.deal.get → deal data
    crm.deal.productrows.get → items
    crm.requisite.get → counterparty details
    ↓
OData 1C: create 'Sales of Goods'
    ↓
1C: document in 'Not posted' status → accountant posts
    ↓ reverse webhook
Bitrix24: update field 'Invoice Number 1C'

Why Reverse Sync of Invoice Number Matters

After the invoice is posted in 1C, the manager must see its number in the deal. This is needed for customer responses and document reconciliation. We configure a scheduled task in 1C: every 5–10 minutes it checks posted sales and updates the 'Invoice Number' field in Bitrix24 via crm.deal.update. The manager gets the number immediately, without manual entry. This saves tens of thousands of rubles per month in operational costs.

How We Do It: Stack and Approach

We use REST API of Bitrix24 to send webhooks and OData or CommerceML for exchange with 1C. The PHP handler runs on the server, receives events, and generates XML for 1C. For complex cases, we use external connectors. Comparison with manual entry shows a speedup of 10–15 times – our implementation is more stable and eliminates transfer errors.

Case Study: Wholesale Supplier of Building Materials

Our client processed 30–50 orders per day. Managers worked in Bitrix24, warehouse and accounting in 1C:UT 11. Previously, invoices were created manually by an operator using printed deal data – each took 5–8 minutes plus verification.

During setup, a non-standard task arose: one order could contain goods from two different warehouses (in different cities). In 1C, an invoice must be created separately for each warehouse. We implemented grouping via a custom field 'Warehouse' in deal product items. The handler splits items and creates separate sales documents.

Result: invoice processing time per order decreased from 6 minutes to 20–30 seconds. The accountant only checks and posts the document.

Stages of Integration Setup

1. Audit of current business processes and document flow.
2. Scheme design: reservation, invoice creation, reverse sync.
3. Development of PHP handler (webhooks + Bitrix24 REST API).
4. Setting up exchange with 1C via OData or CommerceML.
5. Mapping of units of measurement, warehouses, counterparties.
6. Testing on real orders (pilot run).
7. Deployment on the production server and employee training.
8. Warranty support for one month after delivery.

<?php
// webhook handler example
require_once 'crest.php';
$dealId = $_GET['deal_id'];
$deal = CRest::call('crm.deal.get', ['ID' => $dealId]);
$products = CRest::call('crm.deal.productrows.get', ['ID' => $dealId]);
// ... send to 1C

What's Included in the Scope

• Project documentation: integration scheme, field mapping.
• Repository access with handler code and deployment instructions.
• Employee training (accounting, managers).
• 30-day warranty support after launch.

Comparison: Manual Entry vs Automated Integration

Automation speeds up invoice processing by 10–15 times compared to manual entry and completely eliminates data transfer errors. Get a consultation from an engineer on your project. Leave a request on our website, we will evaluate the project 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.