Setting up digital signature signing via Bitrix24

Setting Up Digital Signature Document Signing in Bitrix24

Contract agreed in CRM, PDF formed, manager sends via email. Client prints, signs by hand, scans, sends back. Manager uploads scan to deal. Month later turns out the scan isn't original, accounting requires signed copy. Digital signature solves this: document signed with electronic signature, gains legal force without paper, stored in system with authenticity proof.

Types of Electronic Signature

In B24 context, two types used:

• Simple Electronic Signature (SES). Essentially — action confirmation via login/password or SMS code. B24 supports SES for internal documents: approval, authorization. Legal force limited — only if parties agreed to recognize SES.
• Qualified Electronic Signature (QES). Issued by certification center, equals handwritten signature. Mandatory for invoices, reporting, government contracts. Requires cryptographic provider (CryptoPro CSP, VipNet CSP).

Internal Document Signing in B24

For internal approvals (orders, statements, memos) use "Signature" module in Bitrix24:

1. Document created in "Signature" section or PDF uploaded.
2. Signers assigned — portal employees.
3. Each signer gets notification, opens document, places signature (graphic or SES).
4. Signed document saved with marks: who signed, when, IP address.

This mechanism works without CryptoPro — standard B24 tools enough. Fits HR documents, internal regulations, NDAs.

QES Signing via CryptoPro

For legally significant signing (counterparty documents, tax authority, EDI) requires QES and cryptographic provider:

Requirements:

• QES issued by accredited certification center (tax authority, commercial center)
• CryptoPro CSP 5.0+ — installed on employee workstation
• CryptoPro Browser Plugin — browser extension enabling web signature
• QES Certificate — installed in Windows storage or on token (Rutoken, eToken)

Signing Process from CRM:

1. Manager forms document from deal (via B24 document template or external generation).
2. Clicks "Sign with QES" — B24 via Browser Plugin contacts CryptoPro CSP.
3. CryptoPro reads certificate from token or storage, forms signature (detached .sig or embedded).
4. Signed file + signature file saved to deal card.
5. Robot sends signed document to counterparty or transmits to EDI system.

Signing Route in CRM

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

• Deal stage "On Signing" → robot creates tasks to signers in queue order.
• First signer signs → task closes → second signer task created.
• All signatures collected → robot moves deal to "Signed" stage, attaches final file.
• Signature refusal → deal returns to "Revision" stage, manager notified with reason.

Storage of Signed Documents

Signed documents stored on B24 Disk linked to deal. Recommendations:

• Separate "Signed Documents" folder in Disk structure.
• Document file + detached signature file (.sig) — stored together.
• No deletion of signed files — via folder access rights.
• QES-signed document retention — minimum 5 years (legal requirement).

What We Configure

• Setting up "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 formation
• Creating signing routes: signer sequence, refusal actions
• Organizing signed document storage: folder structure, access rights, retention policy
• Training employees: browser signing, signature verification, typical errors (expired certificate, missing plugin)