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.