1С/BAS ↔ KeyCRM integration

Orders from KeyCRM land in 1С/BAS as sales documents, and stock and payments from 1С/BAS come back to the sales team

Sales work in KeyCRM, accounting works in 1С/BAS, and between them lives a spreadsheet or a person who re-enters orders, checks stock by phone and marks payments by hand. The 1С/BAS ↔ KeyCRM pair makes the two systems share one picture: a confirmed order becomes a sales document in 1С/BAS, and stock balances and incoming payments from 1С/BAS return to the order and the customer card in KeyCRM. 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: KeyCRM →

What moves between the systems

KeyCRM → 1С/BASA confirmed order in KeyCRM becomes a sales document in 1С/BAS with the customer, items, quantities and prices already in place.
KeyCRM → 1С/BASA new customer or company from KeyCRM 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 → KeyCRMStock balances from the 1С/BAS warehouses go to KeyCRM products, so the manager sees what is actually available before promising it to the buyer.
1С/BAS → KeyCRMAn incoming payment posted in 1С/BAS marks the order in KeyCRM as paid, and a partial payment is shown as partial.
KeyCRM → 1С/BASA status change in KeyCRM — cancelled, returned — is reflected in 1С/BAS, so accounting does not keep a document for an order that no longer exists.

What we connect

We look at your 1С/BAS configuration and which documents accounting expects from sales: an invoice, a sales document, or both.
You create a separate access key in the KeyCRM settings for the exchange; on the 1С/BAS side we use the open exchange interface the platform builds itself.
We map the two catalogs: which KeyCRM product corresponds to which 1С/BAS item, and which warehouses count as available stock.
We agree on the condition: which KeyCRM status sends the order to 1С/BAS, and what happens to the 1С/BAS document when the order is cancelled.
We set the exchange rhythm within the KeyCRM limits: order events go instantly, stock balances are refreshed in batches at a set interval.
We run it on a test batch of orders and a test counterparty, reconcile with the accountant, and only then switch it on for the whole flow.

Automation scenarios

Orders re-entered by hand

Before the accountant re-enters every KeyCRM order into 1С/BAS at the end of the day, and about once a week an item or quantity is mistyped.

After the confirmed order arrives in 1С/BAS on its own with the same items and prices the manager saw.

Sold what was out of stock

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

After KeyCRM shows the 1С/BAS stock balance on the product card, and the manager sees the shortage before confirming.

Has the customer paid?

Before the manager asks the accountant in a chat whether the money has arrived, and the accountant searches the bank statement.

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

One customer, three cards

Before the same company exists in 1С/BAS under three spellings, and the sales history is split between them.

After the customer from KeyCRM is matched with the 1С/BAS counterparty by code or phone, 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
The Open API covers orders, funnel/deal cards, customers, companies, products and stock, files, payments and call history.
Source: help.keycrm.app ↗ checked 2026-09-25
Webhooks in KeyCRM are outgoing only and are set up through automation; they cover exactly three events: order status change, order payment status change, funnel card status change.
Source: help.keycrm.app ↗ checked 2026-09-25
The API limit is 20 requests per minute per key; exceeding it returns a 429 Too Many Requests error.
Source: help.keycrm.app ↗ checked 2026-09-25
The REST API and all native integrations are part of KeyCRM's single plan — there's no separate paid tier just for API access.
Source: keycrm.app ↗ checked 2026-09-25

Limits

The limits come from both systems. KeyCRM allows 20 requests a minute per key, so stock balances are refreshed in batches at an interval rather than instantly on every change, and KeyCRM's own outgoing notifications cover only three events: order status, order payment status and lead status. 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

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 KeyCRM, while the manager's discount on a specific order goes back to 1С/BAS with the order. We fix this in writing before launch.

How quickly do stock balances update in KeyCRM?

Order events go instantly. Stock balances are refreshed in batches at an interval we agree on, because KeyCRM allows 20 requests a minute per key; for most stores this is a few minutes.

Does the accountant have to work in KeyCRM?

No. Everything accounting needs arrives in 1С/BAS: the sales document, the counterparty and the order status. The accountant keeps working where they always did.

Do we need a separate KeyCRM plan for the exchange?

KeyCRM's own materials state that the open exchange interface is included in its single plan without a separate add-on. What does depend on the plan is the monthly volume of orders and leads, so we check it against your flow at the start.