Automate Invoice Generation from Bitrix24 to 1C

Let's talk about a classic pain point we solve: a manager closes a deal in Bitrix24, and the accountant waits for data to be passed via email or written into a shared file. The invoice is created manually in 1C with frequent errors—TIN mismatch, product name difference, amount discrepancy due to rounding. Our experience shows this leads to payment delays and extra negotiations. Automating invoice generation from Bitrix24 to 1C bridges this gap and saves hours of an accountant's time.

How data is transferred from Bitrix24 to 1C

Bitrix24 does not generate invoices directly—that's 1C's job as the accounting system. Bitrix24 passes deal data, and 1C creates the document. Data transfer happens via one of two paths.

The standard synchronization module—Bitrix24 ↔ 1C via REST API or COM connection. The module is included in on-premise Bitrix24 (crm.requisite, crm.invoice). When a deal is closed or an invoice is issued in CRM, data is replicated to 1C.

Direct integration via REST API—a webhook on OnCrmInvoiceAdd/OnCrmInvoiceUpdate event triggers a handler that creates the document "Invoice issued" in 1C via OData service or XML exchange.

For most companies, the standard module is sufficient when the details are properly configured.

What needs to be configured in Bitrix24 before launch

Item catalog. Products in the Bitrix24 catalog must be linked to 1C item entries. This is the XML ID or external code of the item. Without it, 1C won't know what to create in invoice lines.

VAT rates. In Bitrix24 catalog settings, each product's VAT rate (0%, 10%, 20%, no VAT) must be set and exactly match the settings in 1C—otherwise amounts will differ.

How to configure the Bitrix24-to-1C connection for documents

In 1C (e.g., 1C:Accounting 3.0), you configure the exchange plan BitrixCRM or use an external loading handler.

Key handler parameters:

Field mapping is the most time-consuming part. Typical mapping table:

Example webhook handler in PHP:

<?php
require_once($_SERVER["DOCUMENT_ROOT"]."/bitrix/modules/main/include/prolog_before.php");
use Bitrix\Crm\InvoiceTable;
$event = json_decode(file_get_contents('php://input'), true);
if ($event['event'] == 'ONCRMInvoiceAdd') {
    $invoiceId = $event['data']['FIELDS']['ID'];
    $invoice = InvoiceTable::getById($invoiceId)->fetch();
    // Generate XML for 1C
    // Send via OData
}
?>

Case study: manufacturing company, 40 deals per month

Our client is a company supplying industrial equipment. Before automation, the accountant spent 2-3 hours daily manually entering invoices into 1C from Bitrix24 data. Errors in counterparty TIN occurred on 2-3 documents per month—causing payment delays and extra negotiations.

After integration: when a deal is moved to "Invoice issued" status in Bitrix24, a webhook triggers a PHP handler that calls 1C's OData service and creates a draft "Invoice". The accountant sees the document in "Pending review" status, reviews it, and posts it with one click. Document processing time dropped from 7 minutes to 40 seconds—10x faster than manual entry.

Turnkey implementation time: 3-5 working days—including mapping setup, testing with real data, and accountant training.

Stages of integration setup

1. Audit of current exchange scheme and identification of bottlenecks.
2. Configuration of counterparty details and item catalog in Bitrix24.
3. Creation of exchange plan in 1C and field mapping.
4. Development of webhook handler (if custom logic is needed).
5. Testing with real documents and verification.
6. Documentation of process and staff training.
7. Post-launch warranty support.

Typical problems and solutions

Why is the invoice created with an empty buyer?

In CRM, the counterparty is not filled in, or the TIN in the details contains spaces. Before transfer to 1C, we add validation via regex: TIN must be 10 or 12 digits without spaces.

How to avoid duplicate documents?

If the webhook fires multiple times (e.g., due to repeated status change or amount update), duplicates appear in 1C. This is solved by checking uniqueness by the document's external code before creation.

What to do if VAT amounts differ by pennies?

Different rounding orders in Bitrix24 and 1C can cause discrepancies. We fix this by explicitly passing the VAT amount per line, not recalculating it.

—All work is performed by certified specialists with over 10 years of experience.

What's included in the work

• Audit of current exchange scheme and documentation.
• Configuration of counterparty details and item catalog.
• Creation of exchange plan in 1C and field mapping.
• Development of webhook handler if necessary.
• Testing with real documents.
• Accountant training and access documentation.
• One month of warranty support.

If you want to speed up your accounting and eliminate errors, contact us for a consultation. Order the Bitrix24-to-1C exchange setup and get a ready integration with a guaranteed result. Contact us to accelerate your accounting department.

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.