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:
| Parameter | Description |
|---|---|
| Data source | Bitrix24 REST API (URL + app key) |
| Document type | "Invoice issued" |
| Mapping rules | CRM field → 1C attribute |
| Trigger condition | Deal status = "Won" or separate invoice status |
| Duplicate mode | Check by invoice number from CRM |
Field mapping is the most time-consuming part. Typical mapping table:
| Bitrix24 field | 1C attribute |
|---|---|
COMPANY_ID → TIN |
Counterparty (search by TIN) |
OPPORTUNITY |
Document total |
PRODUCT_ROWS[].PRICE |
Line price |
PRODUCT_ROWS[].TAX_RATE |
VAT rate |
DATE_CLOSE |
Document date |
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
- Audit of current exchange scheme and identification of bottlenecks.
- Configuration of counterparty details and item catalog in Bitrix24.
- Creation of exchange plan in 1C and field mapping.
- Development of webhook handler (if custom logic is needed).
- Testing with real documents and verification.
- Documentation of process and staff training.
- 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.