Setting Up Exchange Between 1C:Document Management and Bitrix24
The link between 1C:Document Management (1C:DM) and Bitrix24 closes the gap between the accounting environment and the team's workspace. Documents are stored in 1C:DM with legal force and versioning, while employees work with tasks and approvals within Bitrix24 — without switching between systems.
We set up bidirectional exchange so that changes in either system are correctly reflected in the other, conflicts are handled automatically, and approval routes are not duplicated.
What Synchronizes
The exchange is built in three directions:
- Documents → Bitrix24.Disk. Files from 1C:DM are published to specified folders on Disk. When the version is updated in 1C:DM, the file on Disk is overwritten. Reverse upload — by trigger or schedule.
- Orders ↔ Tasks. A task in 1C:DM creates a task in Bitrix24 with binding to the responsible person. Closing a task in B24 changes the order status in 1C:DM.
- Approvals via business processes. The document approval route in 1C:DM is translated to a BP in Bitrix24 — participants receive notifications and vote within the portal.
Technical Stack of Integration
The exchange is realized through the REST API of Bitrix24 and HTTP services of 1C:DM. Interaction scheme:
| Component | Role |
|---|---|
| REST API Bitrix24 | Task creation, file upload to Disk, BP launch |
| Webhooks (incoming) | Receiving events from 1C:DM — new document, status change |
| Webhooks (outgoing) | Notification of 1C:DM about approval completion in B24 |
| HTTP service 1C:DM | Endpoint for receiving commands from Bitrix24 |
| Message queue | Buffering during peak loads (optional — RabbitMQ) |
Authorization is via OAuth 2.0 for server applications or an incoming webhook with token. For production use, we use a server application: the token is automatically updated, there's no binding to a specific user.
Field Mapping
Directories in 1C:DM and Bitrix24 do not match. We set up a correspondence table:
- Counterparties 1C:DM → CRM Companies. Matching by INN or external code.
- Document types → Disk Folders. Each document type from 1C:DM is bound to a specific folder.
- Executors → Bitrix24 Users. Mapping by email or employee ID in a custom field.
- Approval statuses. "Approved" / "Rejected" / "On revision" in 1C:DM correspond to voting results in Bitrix24 BP.
Document Approval Routes
This is the key element of the integration. The route in 1C:DM contains stages: initiation, sequential or parallel approval, signing. In Bitrix24, this route is reproduced through a business process template:
- Initiation. A webhook from 1C:DM starts a BP in Bitrix24 with transmission of the document ID, list of approvers, and deadline.
- Parallel stage. The BP creates tasks for all stage participants simultaneously. The result is recorded in BP variables.
- Sequential stage. A task for the next participant is created only after the previous one is completed.
- Result return. Upon BP completion, an outgoing webhook sends the final status and approvers' comments to 1C:DM.
If the route in 1C:DM changes (a stage is added, an approver is replaced), the BP template is updated manually or through a script for template recreation. Full auto-generation of BP templates from 1C:DM is possible but requires separate development of a handler.
Conflict Resolution
In bidirectional exchange, collisions are inevitable. Resolution rules:
-
Documents. Priority is with 1C:DM — it's the accounting system. If a file is changed in both systems, the version from 1C:DM overwrites the version on Disk, the conflicting copy is saved with the suffix
_conflict_YYYYMMDD. - Tasks/orders. Priority is with the system where the last change occurred (by timestamp). If the discrepancy is less than 60 seconds — manual resolution through admin notification.
- Approvals. Conflict is not constructively possible: the voting result is formed in one system and transmitted to the other.
Schedule and Monitoring
Document synchronization works on a schedule (cron task on the 1C side, agent on the B24 side) with an interval from 5 minutes. Tasks and approvals are in real time via webhooks.
For monitoring, we set up:
- Exchange log in 1C:DM (register of information with sending history)
- Journal of incoming webhooks in Bitrix24
- Admin notification in case of HTTP errors (statuses 4xx/5xx) or timeout
What You Get in the End
Employees approve documents in the familiar Bitrix24 interface without going into 1C:DM. Accounting and legal teams continue working in 1C: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.