Electronic Signature Setup in Bitrix24

Setting Up Digital Signature Document Signing via Bitrix24

A deal is approved in the CRM, a PDF is generated, the manager emails it to the client. The client prints, signs with a pen, scans, and sends back. A month later, it turns out the scan has no legal force — accounting demands the original. Sound familiar? We implement electronic signing with digital signatures in Bitrix24 so that documents instantly gain legal validity without paper. You maintain full control: from internal orders to invoices for counterparties. Experience the convenience: we configure SES and QES turnkey, integrate with CryptoPro and EDI.

Types of Electronic Signatures

Bitrix24 uses two types:

• SES — confirmation via login/password or SMS. Bitrix24 supports SES for internal documents: approving orders, confirming requests. Legal force is limited — only if parties have signed an agreement recognizing it.
• QES — issued by an accredited certification authority (Federal Tax Service, commercial CA). Requires a crypto provider: CryptoPro CSP 5.0+ or VipNet CSP.

How to Configure QES Signing in CRM

For legally binding signing (documents for counterparties, tax authorities, EDI) you need QES and a crypto provider. The signing process from CRM:

1. Manager generates a document from a deal (via Bitrix24 document template or external generation).
2. Clicks 'Sign with EDS' — Bitrix24 via Browser Plugin contacts CryptoPro CSP.
3. CryptoPro reads the certificate from a token or store, creates a signature (detached .sig or embedded).
4. Signed file + signature file are saved in the deal card.
5. A robot sends the signed document to the counterparty or transfers it to the EDI system.

Workstation Requirements:

• QES issued by an accredited CA (Federal Tax Service, commercial)
• CryptoPro CSP 5.0+ installed
• CryptoPro Browser Plugin — browser extension
• QES certificate — installed in Windows store or on a token (Рутокен, eToken)

Why QES is 10x Faster Than Paper Workflow?

Compare: the usual cycle 'print → sign → scan → send' takes an average of 2–3 days. QES in Bitrix24 — 10 minutes. Documents are signed in seconds, instantly saved in the deal, and the counterparty receives a link. We guarantee correct configuration of signing routes for any business processes.

Signing Internal Documents in Bitrix24

For internal approvals (orders, applications, memos) the 'Signature' module is used in Bitrix24:

1. Document created in the 'Signature' section or a PDF uploaded.
2. Signers are assigned — portal employees.
3. Each signer receives a notification, opens the document, and places a signature (graphical or SES).
4. The signed document is saved with markers: who signed, when, IP address.

This mechanism works without CryptoPro — standard Bitrix24 tools are sufficient. Suitable for HR documents, internal regulations, NDAs.

Signing Route in CRM

For documents requiring multiple signatures (director + chief accountant), a route is configured:

• Deal stage 'Pending Signature' → robot creates tasks for signers in order.
• First signer signs → task closes → task created for second.
• All signatures collected → robot moves deal to stage 'Signed', attaches the final file.
• Rejection → deal returns to stage 'Revision', manager receives a notification with reason.

Storage of Signed Documents

Signed documents are stored on Bitrix24 Drive linked to the deal. Recommendations:

• A separate 'Signed Documents' folder in the Drive structure.
• Document file + detached signature file (.sig) stored together.
• Prevent deletion of signed files via folder access rights.
• Retention period for QES-signed documents — at least 5 years (legal requirement).

What's Included in the Work

• Diagnostics of current IT infrastructure and document workflow
• Configuring the 'Signature' module for internal documents: templates, approval routes
• Installing and configuring CryptoPro CSP + Browser Plugin on workstations
• Setting up document signing from CRM: button in deal card, certificate selection, signature generation
• Creating signing routes: sequence of signers, actions on rejection
• Organizing storage of signed documents: folder structure, access rights, retention policy
• Training staff: signing via browser, signature verification, common errors (expired certificate, missing plugin)
• Technical documentation and access to final configuration

Common Errors and How to Avoid Them

We have been working with Bitrix24 for over 5 years and completed 50+ document workflow integrations. Contact us — we will assess your project for free. Turnkey setup takes 3 to 7 working days.