We have been working with Bitrix24 for over 7 years and have implemented 50+ electronic document management projects. An electronic signature in Bitrix24 is not just a checkbox in settings — it's a complex of crypto provider, plugin, and certificate. If one element is misconfigured, the chain breaks. We help companies transition to paperless workflow with guaranteed legal validity.
A manager creates an invoice in CRM, prints it, takes it to the director for signature, scans it, attaches the scan to the deal, sends it to the client. One document takes 15 minutes. With a flow of 30-50 documents per day, that's a full work shift spent on paper. An electronic signature in Bitrix24 reduces the operation to a few clicks directly from the deal card. Signing with a QES is 50 times faster than paper, and operational cost savings can reach 200,000 rubles per year for an average sales department. Our team configures the full cycle: from installing CryptoPro to integrating with 1C.
What is an electronic signature and what types exist?
| Type | Tool | When used |
|---|---|---|
| Simple ES (SES) | Login/password Bitrix24 | Internal approvals, memos |
| Enhanced unqualified (UES) | Software certificate | Document flow between parties by agreement (263-FZ) |
| Enhanced qualified (QES) | CryptoPro CSP + certificate from accredited CA | Legally significant documents, exchange with tax authorities, counterparties (63-FZ) |
For invoices and acts sent to external counterparties, QES is required. For internal approval, SES or UES is enough if an agreement on recognition of such signature is signed between the parties.
How to set up document signing in Bitrix24?
There are three components, and each must work correctly, otherwise the chain breaks.
CryptoPro CSP 5.0 is installed on the signer's workstation. License is perpetual or annual, per workstation. Without it, the crypto provider works in demo mode for 90 days, then rejects.
CryptoPro EDS Browser plug-in — extension for Chrome, Firefox, Edge, Yandex.Browser. Through the JavaScript API cadesplugin, the web application accesses the local crypto provider. The plugin is finicky: after browser updates, it periodically loses compatibility. In a corporate environment, it's best to fix browser versions.
QES certificate on a USB token (Rutoken, JaCarta) or in the Windows registry. Installation: CryptoPro CSP -> 'Service' tab -> 'Install personal certificate'. For verification — CryptoPro test page.
The document signing process:
- The user opens the document in the deal card (document generator
crm.documentgenerator) - Clicks 'Sign' — Bitrix24 via JS calls
cadesplugin - The plugin requests certificate selection and token PIN
- A detached signature CAdES-BES or CAdES-XLT1 is generated
- The signature is saved with the document in CRM
For cloud Bitrix24, the browser accesses the local crypto provider via the Browser plug-in. In the on-premise version, server-side signing is available through CryptoPro JCP or .NET — the document is signed on the server without the workstation.
Pitfalls
Tied to a workstation. The token and CryptoPro CSP must be on the signer's computer. Signing from a phone without CryptoPro DSS (cloud signature) is impossible. This is a critical limitation for mobile employees.
Signature format. CAdES-BES is a simple format that does not contain data about the certificate validity at the time of signing. For long-term document storage (over 1 year), use CAdES-XLT1 — it includes a timestamp and OCSP response. The difference appears in legal disputes: CAdES-BES may be challenged if the certificate was revoked after signing. Read more about formats in the CAdES specification.
Mass signing. The standard Bitrix24 interface signs documents one at a time. With a volume of 50+ documents per day, this is inconvenient. Batch signing is implemented through custom development: REST API for document selection + a loop of cadesplugin calls on the client.
What is included in our service?
| Stage | Duration |
|---|---|
| Current infrastructure audit | 1 hour |
| Installation and configuration of CryptoPro | 1-2 days |
| Integration with 1C and external services | from 0.5 day |
| Employee training | 2 hours |
| Technical support | 30 days |
We guarantee that signing will work without failures, and if necessary, we customize standard scenarios.
Case study: implementation in a wholesale company
One of our projects involved a distributor network with 40 managers. Monthly, 1500 invoices and acts were issued. After setting up QES and integrating with 1C, the processing time per document decreased from 10 minutes to 30 seconds. Total annual savings exceeded 1.2 million rubles. For more details on setup, see the official instruction.
Timeline and cost
Setup time: from 1 to 3 business days depending on infrastructure complexity. Cost is calculated individually after an audit.
If you want to eliminate paper document flow, contact us — we will select the optimal solution for your business. Request a consultation, and we will analyze your current document flow scheme for free.