We often see companies drowning in manual document flow: managers create invoices in Excel, send PDFs by email, wait for scanned signatures, and reconcile data. This takes 30 minutes to several hours per document. Automation via EDO cuts that to 30 seconds — 40 times faster. Bitrix24 with EDO integration automates the process: documents go to counterparties in seconds, and signed copies return directly to CRM. We configure the entire pipeline turnkey — from operator selection to attaching incoming documents to deals. Implementation takes 2–3 business days given a CEP certificate and an operator contract.
How to choose an EDO operator for Bitrix24?
Bitrix24 supports integration with three main operators. The choice depends on which operator your counterparties use. If 70% of partners are on Diadoc — connect to Diadoc. Roaming between operators works but adds 2–4 hours for initial setup.
| Operator | Subscriber base | Features |
|---|---|---|
| Kontur.Diadoc | Largest | Convenient API, stable roaming |
| SBIS (Tensor) | Significant | Strong analytics, reporting integration |
| Takskom | Wide in government sector | Labeling support |
Connecting to Bitrix24
Integration is done via apps from the Bitrix24 Marketplace (see documentation). For Diadoc — "Kontur.Diadoc for Bitrix24", for SBIS — a standard connector. Connection order:
- Install the app from Marketplace → Integrations.
- Authorize with the operator account (requires CEP certificate).
- Configure organization matching — your legal entity must match the EDO box by TIN/KPP.
- Specify the default box if there are multiple departments.
After connection, the CRM company card will get an EDO block with exchange status.
Automatic sending from CRM
The main scenario is sending an invoice or UPD when a deal moves to a certain stage. Implemented via robots or business processes.
The robot "Send document via EDO" triggers on stage change. Settings specify document type, template, signatory. Data is taken from the 'Invoice' entity (crm.invoice) or smart process. Items, amounts, details are pulled automatically. If the deal has multiple invoices, the last unsent one is processed.
Why automatic attachment to deals saves time?
Incoming documents land in the operator's app section. The system searches CRM companies by the sender's TIN. If an open deal is found, the document is attached to it. If not, a new deal is created in the specified funnel. The responsible person receives a notification in the feed for signing. Signing is done via the browser CryptoPro plugin or the operator's app. According to statistics, over 90% of documents are signed within an hour after sending.
Roaming between operators
If the counterparty uses a different operator, documents are transferred via roaming. Setup:
- In your personal account, send a roaming invitation by the counterparty's TIN.
- Wait for confirmation (usually automatic, from 10 minutes to 24 hours).
- After setup, exchange works as within one operator.
Limitations: not all document types are supported (formalized — yes, non-formalized — depends on the operator pair).
Typical problems during setup
| Error | Solution |
|---|---|
| Mismatched details | Check TIN/KPP for extra spaces |
| Missing CEP certificate | Install CryptoPro CSP and browser extension |
| Duplicate documents | Add an EDO status check condition in the robot |
| API timeouts | Use a queue with retry attempts |
Mismatched details. The TIN/KPP in Bitrix24 and the EDO box must match character by character. An extra space will break matching. Errors in details occur in about 15% of cases during manual entry; automation eliminates this.
CEP certificate. The CryptoPro CSP plugin is needed on each signatory's computer. In Chrome and Edge, the CryptoPro Extension is required.
Duplicate documents. If a robot is configured for multiple stages without a "already sent" check, the document will be sent again. Add a condition checking the 'EDO Status' field.
API timeouts. With a high flow (50+ documents per hour), delays can occur. Use a queue with retry attempts via a business process.
What does integration with 1C give?
After signing, documents sync with 1C via CommerceML. This eliminates manual entry: postings are generated automatically. The accounting department sees up-to-date data without delays. Time savings per operation — up to 3 hours a day for an accountant.
What's included in EDO setup
When ordering setup, you get:
- Selection of the optimal operator and connection to its API.
- Installation and configuration of the connector app.
- Development of document templates and robots for automatic sending.
- Configuration of attaching incoming documents to deals.
- Testing the entire cycle with one counterparty.
- Employee training (1 hour online).
- Written documentation of scenarios.
- Free consultation on further optimization.
Case study: logistics company
On a project for a logistics company handling 500 invoices per month, we reduced document processing time from 45 minutes to under 2 minutes per document. We automated invoice creation from CRM data, set up automatic sending upon deal stage change, and configured roaming for counterparties on different operators. The result: a 96% reduction in processing time and zero manual data entry errors.
Conclusion
A configured EDO via Bitrix24 closes the chain "deal → invoice → sending → signing → closure." The manager never leaves CRM; accounting receives signed documents in the accounting system. Processing time reduction — up to 85%, and error costs drop thanks to automatic checks. Order EDO setup — we'll help integrate your document workflow with Bitrix24. Get a consultation on implementation.