Configuring Invoice/Waybill Generation from Bitrix24 to 1C
A delivery note is a goods-accompanying document, and in trading companies it must appear in 1C at the moment the manager confirms shipment. If there is no integration between the CRM and the accounting system, the warehouse operator or accountant creates the delivery note manually from the deal data in Bitrix24. This is not just a waste of time — it is also a risk: an incorrectly entered product code, an error in quantity, and the delivery note will not match the actual release.
Types of delivery notes and corresponding documents in 1C
The word "delivery note" refers to different documents. Before configuring the integration, it is necessary to clarify exactly what is required:
| Document type | 1C document | Bitrix24 event |
|---|---|---|
| Trade invoice (TORG-12) | "Sales of Goods and Services" (type "Goods") | Deal status change to "Shipped" |
| Material release note | "Goods Movement" / "Sales" | Warehouse shipment confirmation |
| Return note | "Goods Return from Buyer" | Return creation in the deal |
| Transport waybill | Separate register or additional attributes | Linked to shipment |
For online stores and wholesale trade, TORG-12 → "Sales of Goods" is most commonly required.
Data that is mandatory for a delivery note
A delivery note has stricter attribute requirements than an act. In addition to the standard deal parties and line items, the following are needed:
Warehouse data. From which subdivision's warehouse the shipment originates, and which employee authorized the release. In Bitrix24, the warehouse may appear in CRM as a custom deal field or via a warehouse management module (if used).
Units of measurement per OKEI. Products in Bitrix24 often have simplified units — "pcs", "kg", "pkg". In 1C, the OKEI reference book is used, where each unit is assigned a code. Mapping units of measurement is a mandatory configuration step.
Serial numbers and batches (if batch accounting is maintained). If batch tracking is configured in 1C, the handler requires logic for batch selection when generating the delivery note.
Integration architecture
The optimal scheme for trading companies is a two-stage transfer:
Stage 1 — reservation. When an order is confirmed in Bitrix24 (status "Order Accepted"), a reservation is created in 1C via a "Customer Order" document. This blocks the goods in the warehouse before the actual shipment.
Stage 2 — delivery note creation. When the deal is moved to the "Shipped" status, the handler creates a "Sales of Goods" document based on the "Customer Order". The link via the external document code ensures the delivery note is created for the correct order.
Bitrix24: status "Shipped"
↓ webhook
PHP handler:
crm.deal.get → deal data
crm.deal.productrows.get → line items
crm.requisite.get → counterparty requisites
↓
1C OData: create "Sales of Goods"
↓
1C: document in "Not Posted" status → accountant posts it
↓ reverse webhook
Bitrix24: update field "1C Delivery Note Number"
Case study: wholesale building materials supplier
The company processed 30–50 orders per day. Managers worked in Bitrix24, while the warehouse and accounting operated in 1C:UT 11. Delivery notes were created manually by an operator from printed deal data — each one took 5–8 minutes plus verification time.
A non-trivial challenge arose during integration setup: in Bitrix24, a single order could contain products from different warehouses (two warehouses in different cities), while in 1C a delivery note must be created separately per warehouse. Solved via a custom "Warehouse" field in the deal's product rows — the handler groups items by warehouse and creates a separate sales document for each.
Time for delivery note processing per order: from 6 minutes of manual entry to 20–30 seconds for review and posting.
Delivery note number: reverse synchronization
After a delivery note is posted in 1C, the manager must see its number in the Bitrix24 deal. This is needed for client responses and document reconciliation. A scheduled task in 1C checks posted sales documents every 5–10 minutes and updates the "Delivery Note Number" field in the Bitrix24 deal via crm.deal.update.
Full setup timeframe (including two-stage scheme and reverse synchronization): 5–8 business days.