1С:Document Management and Bitrix24 Exchange Setup

Problem: during two-way synchronization between 1С:Document Management (1С:DO) and Bitrix24, webhooks loop — updating a document in 1С creates a task in Bitrix24, updating the task sends a request back to 1С, and the cycle repeats. Without sync flags, this leads to data duplication and endless notifications. We solve this via control markers and intelligent mapping, ensuring stable operation of the bundle.

The 1С:Document Management and Bitrix24 bundle bridges the gap between the accounting circuit and the team workspace. Documents are stored in 1С:DO with legal force and versioning, while employees work with tasks and approvals inside Bitrix24 — without switching between systems. Our experience in this integration exceeds 5 years, with over 100 implementations, allowing us to avoid typical setup mistakes.

We configure two-way exchange so that changes in either system are correctly reflected in the other, conflicts are handled automatically, and approval routes are not duplicated. Everything works turnkey: from initial setup to monitoring in production.

What Gets Synchronized

Exchange is built in three directions:

• Documents → Bitrix24 Drive. Files from 1С:DO are published to specified folders on Drive. When a version is updated in 1С:DO, the file on Drive is overwritten. Reverse upload — by trigger or schedule.
• Assignments ↔ Tasks. An assignment in 1С:DO creates a task in Bitrix24 linked to the responsible person. Closing the task in B24 changes the assignment status in 1С:DO.
• Approvals via business processes. The approval route for a document in 1С:DO is translated into a Bitrix24 business process — participants receive notifications and vote inside the portal.

Technical Integration Stack

The exchange is implemented via Bitrix24 REST API. Official documentation and 1С:DO HTTP services. Interaction scheme:

Authorization — via OAuth 2.0 for server applications or incoming webhook with token. For production, we use a server application: token renews automatically, no tie to a specific user.

Field Mapping

Directories in 1С:DO and Bitrix24 do not match. We configure a correspondence table:

• 1С:DO Counterparties → CRM Companies. Matching by TIN or external code.
• Document types → Drive folders. Each document type from 1С:DO is linked to a specific folder.
• Executors → B24 Users. Mapping by email or employee number in a custom field.
• Approval statuses. "Approved" / "Rejected" / "Revision" in 1С:DO correspond to voting results in Bitrix24 business processes.

How to Set Up Approval Routes?

This is a key element of integration. The route in 1С:DO contains stages: initiation, sequential or parallel approval, signing. In Bitrix24, this route is reproduced through a business process template:

1. Initiation. A webhook from 1С:DO launches a business process in Bitrix24 with the document ID, list of approvers, and deadline.
2. Parallel stage. The business process creates assignments for all stage participants simultaneously. The result is recorded in BP variables.
3. Sequential stage. The next participant's assignment is created only after the previous one completes.
4. Result return. Upon BP completion, an outgoing webhook sends the final status and approvers' comments to 1С:DO.

If the route in 1С:DO changes (stage added, approver replaced), the BP template is updated manually or via a re-creation script. Full auto-generation of BP templates from 1С:DO is possible but requires separate development effort.

How Are Conflicts Handled?

In two-way exchange, collisions are inevitable. Resolution rules:

• Documents. Priority to 1С:DO as the accounting system. If a file is changed in both systems, the version from 1С:DO overwrites the Drive version; the conflicting copy is saved with the suffix _conflict_YYYYMMDD.
• Tasks/assignments. Priority to the system where the last change occurred (by timestamp). If discrepancy is less than 60 seconds — manual resolution via notification to admin.
• Approvals. Conflict is structurally impossible: the voting result is formed in one system and passed to the other.

How to Set Up Schedule and Monitoring?

Document synchronization runs on a schedule (cron task on 1С side, agent on B24 side) with an interval from 5 minutes. Tasks and approvals — in real-time via webhooks.

For monitoring, we configure:

• Exchange log in 1С:DO (information register with history of sends)
• Incoming webhooks log in Bitrix24
• Admin notification on HTTP errors (4xx/5xx statuses) or timeout

For an individual integration plan, get a consultation — we will analyze your document workflow scheme.

What You Get in the End

Employees approve documents in the familiar Bitrix24 interface without entering 1С:DO. Accountants and lawyers continue to work in 1С:Document Management. Both systems contain up-to-date data with a delay of no more than 5-10 minutes for documents and instant synchronization for tasks and approvals. Our approach with message queues (RabbitMQ) handles up to 5,000 documents per hour — 10 times faster than typical solutions without buffering.

Evaluate your project: we will prepare an integration plan in 1 day. Contact us for a consultation — we guarantee stable operation of the exchange.

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.