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);
}

Get a consultation on setting up the integration. Our team has 10+ years of experience in Bitrix24 integration and over 150 successful projects with external services. For more details, see the official Bitrix24 REST API documentation. Bitrix24 REST API Documentation.

Contact us for a free audit of your business processes. Minimize manual entry and eliminate errors.

How a corporate portal on Bitrix24 solves the problem of information chaos?

Employees spend up to 2 hours a day searching for files, emails, and solutions. Tasks get lost in dozens of chats, approvals get stuck for weeks. The manager learns about missed deadlines only at a meeting. A corporate portal on Bitrix24 ties every message, document, and task to a single context. You get a transparent picture of work: who is working on what, which stages, where bottlenecks are. Wikipedia: Information silo describes how unorganized data reduces productivity – a portal cuts that loss by 60–70%.

We will evaluate your project for free – contact us to get the architecture in 2 days. A medium‑sized company typically saves 2.5 million rubles annually after deployment (based on our projects).

What does the portal offer in daily work and why is it better than messengers?

In messengers, information is unstructured – discussions get buried within a week. On the portal, every message is tied to a task, project, or document. Employees spend up to 30% of their work time searching for data (McKinsey). The portal reduces this time by 2–3 times thanks to structured repositories and full‑text search.

Communications. Activity stream, messenger, and video calls are tied to specific tasks. Any discussion can be found six months later – in a messenger it would be buried within a week.

Tasks and projects. Kanban, Gantt, checklists, dependencies, time tracking. Each employee's efficiency is visible in reports – no need to wait for a meeting.

Document flow. Approval routes through the business process designer: leave request → manager → HR → accounting. Electronic signature, versioning, deadline control. Integration with electronic document management (SBIS, Diadoc) via REST API.

HR. Onboarding of new employees, leave/travel requests, organizational structure, absence schedule. An employee knows where to go from day one.

Knowledge base. Bitrix24 wiki engine: regulations, instructions. Knowledge does not leave with departing employees.

Implementation example. For a manufacturing company with 320 employees, we deployed a portal with integration of 1C:SALARY AND HR MANAGEMENT and Active Directory in 4 months. Travel request approval time decreased from 3 days to 4 hours. Savings on employee idle time amounted to 1.5 million rubles per year. Managers receive automatic reports on department efficiency. Customer response time decreased by 20%. Portal payback period is 7 months.

How does integration with 1C and Active Directory accelerate HR management?

Integration with 1C:Enterprise via the b24connector module or custom REST handler: a leave request is approved on the portal through a business process and automatically enters 1C:SALARY AND HR MANAGEMENT for vacation pay calculation. Active Directory (SSO via the ldap module) – the employee account is created once in AD and synchronized to the portal, email, VPN. Upon dismissal, it is blocked everywhere. Manual account creation is eliminated, errors are minimized.

Types of corporate portals and key integrations

Additional integrations that deliver real value:

• Email: Exchange via EWS API or IMAP, calendar synchronization, creating a task from an email.
• IP telephony: Asterisk, Mango Office, Zadarma via REST API – calls from the portal, contact card, call recording.
• Video conferencing: built‑in video calls or integration with Zoom/Teams via marketplace.
• EDI: SBIS, Diadoc via REST API – fully electronic document flow with counterparties.

Security and compliance with Federal Law 152‑FZ

The portal contains personal data, financial reports, strategic plans. We guarantee protection:

• role model via CGroup and section‑level permissions;
• two‑factor authentication (OTP, Yandex.Key, SMS);
• audit of all actions (b_event_log);
• TLS encryption for transmission and disk encryption;
• full compliance with Federal Law No. 152‑FZ "On Personal Data".

How is implementation carried out? Step‑by‑step plan

1. Audit — we record current processes, measure time losses.
2. Design — choose portal type, plan integrations.
3. Implementation — configure business processes, permissions, interface.
4. Test — pilot group tests scenarios, we fix issues.
5. Launch — connect all employees, train, hand over documentation.

What you receive after implementation

• Project documentation: architecture, integration scheme, business process diagrams.
• Configured portal with all integrations (1C, AD, telephony, EDI).
• Business process descriptions and instructions for administrators and users.
• 30 days of technical support after launch.
• Access to our knowledge base and migration scripts.

Post‑launch support: how to prevent the portal from becoming obsolete

After six months, many portals become abandoned. To avoid this, we offer packages with fixed SLA and a dedicated administrator. Performance monitoring, platform updates, user administration, development of new modules. Our team has over 10 years of experience and more than 50 implemented corporate portals on Bitrix24. We are a certified 1C‑Bitrix partner, guaranteeing quality and deadlines.

Mobile access. Native Bitrix24 app (iOS/Android) with push notifications, tasks, chats. Responsive web interface for extranet users (no app installation required). Offline access to documents and tasks, sync when connectivity is restored.

Order a turnkey corporate portal implementation

Schedule a free audit – we will evaluate your project, propose architecture, and give clear timelines. Get a comprehensive proposal and see that the portal pays for itself within the first six months. Contact us today.