Bitrix24 and Kontur.Accounting Integration

A manager closes a deal in CRM, the accountant learns about it from a messenger — time is lost. You have to manually create an invoice in Kontur.Accounting, verify counterparty details with the CRM card, monitor payment in the bank statement, and return to Bitrix24. Each deal takes 3-5 switches between systems. With 50+ deals per week — guaranteed losses: forgotten invoices, duplicate counterparties, errors in details.

We set up a middleware that connects Bitrix24 and Kontur.Accounting via REST API. In 5-10 days we configure the exchange: counterparties, invoices, payments, closing documents. Manual processing of one deal takes up to 15 minutes, automated — 2-3 seconds. Automation reduces invoice creation costs from 250 rubles to 5 rubles — savings up to 300,000 rubles per year with 100 deals.

How is the Bitrix24 and Kontur.Accounting Integration Structured?

Kontur.Accounting provides a REST API for working with counterparties, invoices, and documents. Bitrix24 has a REST API and webhook mechanism. The connection is built through an intermediate service (middleware) that listens to Bitrix24 events and sends requests to Kontur.

1. Listens to Bitrix24 events — moving a deal to the "Issue Invoice" stage generates a webhook.
2. Retrieves data — from the deal card and linked contact/company, it fetches details, amount, and product list.
3. Creates or finds the counterparty in Kontur — by TIN. If the counterparty is new, it creates a card.
4. Creates an invoice — with items, amounts, VAT.
5. Returns the invoice number — writes it to a custom field of the deal in Bitrix24.

Reverse flow: middleware periodically (or via webhook from Kontur) checks payment statuses and updates deal stages in CRM.

How to Avoid Duplicate Counterparties? — Bitrix24 Integration with ...

Counterparties are the biggest friction point. In CRM, a manager may create a company with minimal data (name + phone), while accounting needs full details: TIN, KPP, legal address, bank details.

We solve this with two mechanisms:

• Auto-fill by TIN. In the company card in Bitrix24, the manager enters the TIN — a script queries the Kontur.Focus (or DaData) service and pulls all details. The data is immediately valid for accounting.
• Reverse synchronization. If an accountant adds a counterparty in Kontur (e.g., a supplier), the middleware creates the corresponding company in CRM with filled details.

Record matching — by TIN. Duplicates are tracked during each synchronization: if Bitrix24 has two companies with the same TIN, the integration logs the conflict and does not create a duplicate in Kontur.

What to Do in Case of Synchronization Errors?

The middleware logs each operation: request, response, result. In case of API errors (timeout, invalid data, rate limiting) — three retry attempts with increasing delay. If still unsuccessful — notification to the administrator in a Bitrix24 chat.

Typical errors:

• Invalid TIN — the counterparty in CRM was created with an error. The integration checks the TIN checksum before sending.
• Mismatched nomenclature — a product in CRM is not found in the Kontur directory. Solution: map nomenclature during initial setup.
• Duplicate payment — the same statement processed twice. Solution: deduplication by payment order number and date.

Manual Process vs. Automation: Which Is More Effective?

Implementation Stages

What's Included in the Work

• Middleware design — tailored to your CRM architecture and business processes.
• REST API configuration — for Bitrix24 and Kontur.Accounting.
• Data mapping — counterparties, nomenclature, invoices.
• Testing — 3-day pilot launch with your data.
• Documentation — description of all scenarios and failure points.
• Training — 2-hour webinar for managers and accountants.
• Support — 30 days after launch (bug fixes, fine-tuning).

Security and Monitoring

Data between systems is transmitted via HTTPS. API tokens are stored in environment variables on the middleware server, not in code. Middleware access is restricted by IP addresses of Bitrix24 and Kontur servers. Logs containing personal data are rotated — storage no more than 90 days.

We configure the integration for your specific business process: from a minimal "invoice → payment" link to a full document flow with EDI.

// Example webhook handler in PHP $event = json_decode(file_get_contents('php://input'), true); if ($event['event'] === 'ON_CRM_DEAL_UPDATE' && $event['data']['FIELDS']['STAGE_ID'] === 'C7:NEW') { $dealId = $event['data']['FIELDS']['ID']; // Get deal data via REST $deal = $this->bitrix24->call('crm.deal.get', ['id' => $dealId]); // Create invoice in Kontur $this->kontur->createInvoice($deal); }