1С/BAS ↔ Bitrix24 integration

A won deal in Bitrix24 becomes a sales document in 1С/BAS, and stock, payments and shipments from 1С/BAS come back to the deal

Sales live in Bitrix24: leads, calls, deals and their stages. Accounting lives in 1С/BAS: counterparties, invoices, payments and stock. Without a link, a manager sends the accountant a deal by chat, the accountant re-types it, and the manager asks twice a day whether the money has arrived. The 1С/BAS ↔ Bitrix24 pair gives both teams one picture: a deal that reaches the agreed stage becomes an invoice or sales document in 1С/BAS, and the payment, shipment and stock balance from 1С/BAS return to the deal card and the product catalogue in Bitrix24. Below: what exactly moves, which scenarios we cover and which capabilities of both systems we rely on.

Request an integration System page: 1С/BAS →System page: Bitrix24 →

What moves between the systems

Bitrix24 → 1С/BASA deal that reaches the agreed stage in Bitrix24 becomes an invoice or a sales document in 1С/BAS with the counterparty, items, quantities and prices already in place.
Bitrix24 → 1С/BASA new company or contact from Bitrix24 is created as a counterparty in 1С/BAS, and an existing one is matched by registration code or phone, so the directory is not doubled.
1С/BAS → Bitrix24An incoming payment posted in 1С/BAS marks the invoice in Bitrix24 as paid and moves the deal to the agreed stage; a partial payment is shown as partial.
1С/BAS → Bitrix24Stock balances from the 1С/BAS warehouses go to the Bitrix24 product catalogue, so the manager sees what is actually available before promising it in the deal.
1С/BAS → Bitrix24A shipment or return posted in 1С/BAS is written to the deal timeline in Bitrix24, so the manager answers the client without calling the warehouse.
Bitrix24 → 1С/BASA deal cancelled in Bitrix24 cancels the unpaid invoice in 1С/BAS, so accounting does not chase money for a deal that no longer exists.

What we connect

We look at your 1С/BAS configuration and your Bitrix24 plan: ongoing exchange with Bitrix24 Cloud needs a paid plan from the Vibe+ lineup, and we check this before anything else.
Together with the accountant we decide which document each deal stage produces in 1С/BAS: an invoice at «invoice sent», a sales document at «won», or both.
In Bitrix24 you create an inbound and an outbound connection for the exchange under a dedicated employee; on the 1С/BAS side we use the open exchange interface the platform builds itself.
We map the catalogues: which Bitrix24 product corresponds to which 1С/BAS item, which warehouses count as available stock, and which price type goes to the deal.
We set the exchange rhythm within the Bitrix24 request limits of your plan: deal and payment events go instantly, stock balances are refreshed in batches at a set interval.
We run it on a test batch of deals and a test counterparty, reconcile with the accountant, and only then switch it on for the whole sales team.

Automation scenarios

Deals re-typed into 1С/BAS

Before the manager sends the deal to the accountant in a chat, the accountant re-types the invoice, and the client waits for it until the evening.

After the invoice appears in 1С/BAS the minute the deal reaches the agreed stage, with the same items and prices the manager saw.

Has the money arrived?

Before the manager asks the accountant twice a day whether the client has paid, and the accountant searches the bank statement.

After the payment posted in 1С/BAS marks the invoice as paid in the deal, and the manager ships without asking.

Sold what was out of stock

Before the manager promises delivery in the deal, and the warehouse later reports the item ran out yesterday.

After the Bitrix24 product card shows the 1С/BAS stock balance, and the manager sees the shortage before promising.

One client, three counterparties

Before the same company exists in 1С/BAS under three spellings because each manager created their own, and the debt is split between them.

After the company from Bitrix24 is matched with the 1С/BAS counterparty by registration code, and new duplicates are not created.

How it works technically

For those who want to check: each point links to the official documentation page it comes from.

The official BAS support portal documents its integration technologies under the title «Технології інтеграції 1С:Підприємства 8.3» — BAS is built on the 1C:Enterprise 8.3 platform.
Source: its.bas-soft.eu ↗ checked 2026-09-25
According to the same documentation, the platform automatically builds a REST interface using the OData protocol, through which outside systems can read, change, create and delete data over HTTP.
Source: its.bas-soft.eu ↗ checked 2026-09-25
Ongoing REST API access in Bitrix24 Cloud is available only on paid plans in the Vibe+ lineup; the entry Essentials plan does not include API access.
Source: apidocs.bitrix24.com ↗ checked 2026-09-25
CRM API methods manage leads, deals, contacts, companies, estimates, invoices and Smart Processes: creating and updating entities, moving them through funnel stages, logging the history in the timeline, generating documents, and launching automation.
Source: apidocs.bitrix24.com ↗ checked 2026-09-25
Bitrix24 supports two kinds of webhooks: an inbound one that calls API methods on behalf of the employee who created it, and an outbound one that sends a Bitrix24 event to an external handler URL.
Source: apidocs.bitrix24.com ↗ checked 2026-09-25
The REST API rate limit runs on a leaky-bucket counter: exceeding the threshold blocks further requests with a 503 QUERY_LIMIT_EXCEEDED error; on Enterprise the counter drains at 5 requests/sec up to a threshold of 250, on other plans at 2 requests/sec up to a threshold of 50.
Source: apidocs.bitrix24.com ↗ checked 2026-09-25

Limits

The limits come from both systems. Ongoing exchange with Bitrix24 Cloud needs a paid plan from the Vibe+ lineup; the entry plan does not include it, and the request rate before throttling also depends on the plan, so stock balances are refreshed in batches at an interval rather than instantly on every change. A single request to Bitrix24 Cloud must finish within 60 seconds, so large catalogues are exchanged in parts. 1С/BAS is on the official prohibited software list: we do not take projects for state bodies, critical infrastructure or systems with state data, and with private businesses we discuss the risk openly.

How to start

Three steps from a first message to work on your project.

01
Leave a request
Describe the task in the form — in text or by voice. Budget and timing are optional.
02
We review and estimate
A developer studies the brief, asks about anything unclear and sends an estimate.
03
We start
Once scope and price are agreed, the work begins.

Leave a request

or write to info@coreviaflow.space

Live project We built and run Gemalli — a B2B export platform with producer pages, a CRM and a deal chat. Read the case →

Questions

We are on the entry Bitrix24 plan. Will it work?

For ongoing exchange, no: Bitrix24's own materials state that continuous access is available on the paid plans of the Vibe+ lineup. There is a one-time 15-day trial of the Professional plan, and we use it to test the connection before you decide on the plan.

Which system is the source of truth for prices?

Whichever you choose at the start. Usually the price list lives in 1С/BAS and goes to the Bitrix24 catalogue, while the manager's discount on a specific deal goes back to 1С/BAS with the invoice. We fix this in writing before launch.

Does the accountant have to work in Bitrix24?

No. Everything accounting needs arrives in 1С/BAS: the invoice, the counterparty and the deal status. The accountant keeps working where they always did, and the manager sees the result in the deal.

What about deals that were closed before the link?

We do not touch them by default. If you want history, we load the counterparties and the paid invoices for an agreed period once, reconcile the totals with the accountant, and only then switch on the live exchange.