Bitrix24 Integration with 1C: Deals, Invoices, Payments and Inventory
Contents
Thousands of companies use Bitrix24 and 1C together: sales reps work in CRM, while accounting and warehouse teams use the accounting system. The same data constantly moves between them: clients, products, invoices, payments and shipments. If the data is transferred manually, the sales rep does not know whether the client has paid, and accounting does not know what the sales rep promised.
A poor integration is even worse than manual transfers: it creates duplicates, silently loses documents and undermines trust in both systems. Let’s look at how to make the connection reliable.
What data moves between systems
| Data | Typical system of record | Service line |
|---|---|---|
| Leads, deals, tasks | Bitrix24 | remain in CRM |
| Business partners | as decided by the company | both ways, according to rules |
| Products and prices | 1C | 1C → Bitrix24 |
| Inventory levels | 1C | 1C → Bitrix24 |
| Orders and invoices | created from a deal, recorded in 1C | Bitrix24 → 1C |
| Payments | 1C | 1C → Bitrix24 |
| Shipments | 1C | 1C → Bitrix24 |
| Outstanding balances | 1C | 1C → Bitrix24 |
Integration methods
Built-in sync
Bitrix24 and 1C offer built-in sync mechanisms that cover standard scenarios: catalogs, business partners and documents. Their capabilities depend on the 1C configuration and Bitrix24 version. For small companies with standard processes, this is a good starting point.
Sync through the Bitrix24 REST API and 1C HTTP services
A custom integration using the APIs of both systems. It gives you full control over logic, formats and error handling. You need it when built-in sync does not cover your company’s processes.
Integration layer
A separate service through which all data exchanges pass. It is necessary if, in addition to CRM and 1C, you have a B2B portal, MoySklad, multiple databases or high reliability requirements.
| Method | When it fits | Limitations |
|---|---|---|
| Built-in sync | standard configuration, simple processes | difficult to customize, limited error control |
| Custom API integration | custom rules, one system pair | requires developer support |
| Integration layer | multiple systems, growth, demanding requirements | higher upfront cost |
Key decisions before you start
Where the master client directory resides
If sales reps start working with clients in CRM, it makes sense to use Bitrix24 as the source and send the business partner to 1C when the first invoice or contract is created. If accounting creates client records based on contracts, 1C becomes the primary source. There should be one source, and records should be matched by BIN or IIN, not by name.
When a document is created in 1C
At which deal stage is an order or invoice created in 1C? What happens if the deal changes afterward: is the document updated, is a new one created, or is the change blocked?
How sales reps see payments
A payment is recorded in 1C from the bank statement and sent back to the deal: the “paid” field, a stage change and a notification to the sales rep.
Which prices are used in the deal
Prices from 1C, based on the client’s price type. If a sales rep can change the price in a deal, the change should be visible and approved.
Example workflow for a wholesale company
| Deal stage in Bitrix24 | Event in 1C |
|---|---|
| Proposal review | prices and inventory balances are pulled from 1C |
| Approved | a customer order and invoice are created |
| Awaiting payment | invoice sent to the client |
| Paid | a payment from the bank statement in 1C automatically moves the deal to this stage |
| Shipped | a sales transaction in 1C automatically moves the deal to this stage |
| Closed | all documents have been posted |
Common problems
- Duplicate business partners due to different name spellings and a lack of matching by BIN.
- Products in a deal that do not exist in 1C, because a sales rep added an item manually.
- Prices in a deal that differ from 1C prices without approval.
- Payments that do not reach CRM, causing a sales rep to call a client to remind them about an invoice that has already been paid.
- Sync breaks after a 1C update, and no one notices for several days.
Reconciliation and monitoring
- daily reconciliation of deals and documents;
- a list of business partners not matched between systems;
- sync error notifications sent to the person responsible;
- sync verification tests after every 1C update.
Built-in module or custom integration: how to decide
Ask four questions:
- Do your deal stages and documents fit the standard sync workflow?
- Do you have 1C customizations that need to be included in the sync?
- Do other systems need to be included in the sync: a portal, MoySklad or multiple databases?
- Is it important to see an operations log and the causes of errors?
If the answer to the first question is “yes” and the others are “no,” start with built-in sync. If the answer to at least two of the last three questions is “yes,” plan for a custom integration or an integration layer.
How to launch
- Audit current processes and data in both systems.
- Create a data map and a mapping table for stages and documents.
- Match and clean up business partner records using BIN and IIN.
- Set up sync on a test database.
- Run a pilot with a subset of sales reps.
- Launch for everyone and reconcile daily.
Frequently asked questions
Will the built-in sync work?
Often, yes, for standard scenarios. If you have custom rules, multiple pipelines, multiple legal entities or a portal, you will need customization or a custom integration.
Cloud or self-hosted Bitrix24: is there a difference?
There are differences in customization options and where data is hosted. Consider these when choosing an integration method.
Can you see inventory balances on a product record in CRM?
Yes, if inventory balances are regularly sent from 1C. For items in short supply, you can add an inventory check when an invoice is created.
What should you do with historical data?
Typically, directories and open deals are migrated, while sales history is shown through reports from 1C.
How long does the integration take?
Standard sync takes weeks to set up; a custom integration with nonstandard logic takes 1-3 months.
Can client debt be sent to a Bitrix24 record?
Yes. Outstanding and overdue balances from 1C are updated on the company record, and you can use them to set up automation rules and tasks.
