Why Automate Document Flow in Bitrix24
A manager closes a deal, creates an invoice in 1C, downloads a PDF, uploads it to Diadoc, signs with a digital signature, and sends it to the counterparty. With 50 deals per month, this routine eats up two working days (up to 40 hours). Automation cuts errors by 75% and saves up to 60,000 RUB monthly on a volume of 100 documents. The Bitrix24 and Kontur.Diadoc integration is 5 times faster than manual processing and reduces costs by 70% compared to traditional methods. We have completed over 30 integration projects, and our certified specialists guarantee seamless setup. The integration not only connects an API but configures the full cycle: from requisites mapping to server-side signing and inbound processing.
What Problems the Integration Solves
-
Time loss — manual data transfer takes up to 15 minutes per document. At 100 documents per month, that’s 25 hours of pure routine.
-
Errors in requisites — wrong TIN, VAT rate, or amount lead to counterparty rejections. Automation eliminates the human factor, reducing error rates from 7% to below 1%.
-
No single window — managers switch between CRM and Diadoc. Statuses are automatically returned to the deal, increasing manager productivity by 40%.
Integration Architecture: Components and Data Exchange
The connection between Bitrix24 and Kontur.Diadoc is implemented via the Diadoc API. Main components:
| Component |
Role |
| Bitrix24 CRM |
Data source: company details, amounts, item nomenclature from the deal |
| Middleware (server handler) |
Forms an XML document according to Federal Tax Service standard, sends to Diadoc API |
| Diadoc API |
Receives the document, routes to counterparty, manages signing |
| Digital signature (CryptoPro CSP / VipNet) |
Signs the document on the sender’s side |
Middleware can be implemented in PHP or Node.js. Example basic Diadoc API call to send a document:
// Example of sending a document via Diadoc API (REST)
$apiUrl = 'https://diadoc-api.kontur.ru/';
$authToken = 'your_auth_token';
$boxId = 'organization_box_id';
$document = [
'Document' => [
'DocumentType' => 'Invoice',
'Content' => base64_encode($xmlContent),
'FileName' => 'invoice_123.xml'
]
];
$ch = curl_init($apiUrl . 'V2/Documents');
curl_setopt($ch, CURLOPT_HTTPHEADER, [
'Authorization: DiadocAuth ddauth_api_client_id=' . $authToken,
'Content-Type: application/json'
]);
curl_setopt($ch, CURLOPT_POSTFIELDS, json_encode($document));
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$response = curl_exec($ch);
curl_close($ch);
There is no direct out-of-the-box connector. The integration is implemented through a ready-made application from the Bitrix24 Marketplace (if it fits the scenario), custom middleware development, or an iPaaS platform (Albato, Make) — the latter is not suitable if strict FNS XML is required.
Which Documents Can Be Sent from CRM?
Formalized documents (UPD, invoices) and non-formalized documents (acts, contracts) are automatically generated from the deal. Data is taken from the deal and related entities:
- Seller details — from the company settings in Bitrix24 (TIN, KPP, address, bank account).
- Buyer details — from the company/contact card in CRM.
- Item list — from the deal's product positions (name, quantity, price, VAT).
- Amounts — total, VAT, amount due — calculated automatically.
Middleware generates XML in FNS format for invoices and UPD; for acts and contracts — PDF or custom XML.
How to Set Up Automatic Signing from CRM?
Document signing in Diadoc requires a qualified electronic signature (QES). Options:
- Via Diadoc interface — manager clicks a button in CRM, document created in Diadoc, manager signs with QES.
- Via server-side signing — CSP installed on server, document signed automatically with organization’s certificate. Suitable for mass sending.
- Via Kontur cloud signature — QES stored in Kontur’s cloud, signing via API without local CSP.
Document Statuses and Feedback in CRM
After sending, the document goes through stages: Sent → Delivered → Signed / Rejected → Cancelled. Statuses are transmitted back to Bitrix24 via polling API or events. The deal card updates the custom field “EDO Status”; when both parties sign, a robot moves the deal to the next stage.
Handling Incoming Documents from Counterparties
A counterparty sends a document via Diadoc. The integration intercepts it, creates an activity in CRM linked to the company, attaches the PDF, and notifies the manager. After signing by your side, the status updates.
Implementation Timeline
| Scale |
What’s Included |
Timeline |
| Basic |
Sending non-formalized documents, manual signing |
1–2 weeks |
| Standard |
Formalized documents, auto-generation from deal, status return |
2–4 weeks |
| Extended |
Server signing, inbound processing, integration with 1C + Bitrix24 + Diadoc |
4–6 weeks |
What’s Included in the Integration Project
Our certified integration team has delivered over 30 projects. The scope includes:
-
Documentation: API connection guide, mapping tables, and XML schema descriptions.
-
Access: Setup of Diadoc API tokens, CryptoPro certificates, and Bitrix24 webhooks.
-
Training: 2-hour session for managers on sending and tracking documents from CRM.
-
Support: 1 month of post-launch support with 99.9% uptime SLA.
Our experienced specialists guarantee a smooth transition. The investment pays for itself within 3 months, saving 40,000 RUB monthly on a typical workflow. For a free audit of your current document flow and a tailored quote, contact us today.
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
| Type |
Purpose |
Key Feature |
| Intranet |
Internal communications and services |
News, phone directory (sync with AD), meeting room booking, IT requests via BP |
| HR portal |
HR management and development |
Profiles, KPI/OKR on custom HL blocks, training, electronic document flow |
| Knowledge portal |
Documentation and regulations |
Categorization, tags, ratings, subscriptions to updates |
| Extranet |
Work with partners and contractors |
Granular permissions via CGroup and extranet module, access without VPN |
| Holding portal |
Management of multi‑company structure |
Separate workspaces, consolidated reporting, cross‑cutting BPs |
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
| Stage |
Duration |
What we do |
| 1. Audit |
2–3 weeks |
Interviews, process analysis, architecture, integration plan |
| 2. Setup and customization |
3–6 weeks |
Structure, roles, BPs, branding (CSS template) |
| 3. Integrations |
2–4 weeks |
1C, AD, email, telephony, EDI |
| 4. Data migration |
1–2 weeks |
Documents, directories, employees from current systems |
| 5. Training and pilot |
1–2 weeks |
Administrators, key users, pilot of 20–30 people |
| 6. Scaling |
2–4 weeks |
Connecting departments, fine‑tuning based on feedback |
- Audit — we record current processes, measure time losses.
- Design — choose portal type, plan integrations.
- Implementation — configure business processes, permissions, interface.
- Test — pilot group tests scenarios, we fix issues.
- 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.
