Setting Up Electronic Document Signatures in Bitrix24

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?

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:

1. The user opens the document in the deal card (document generator crm.documentgenerator)
2. Clicks 'Sign' — Bitrix24 via JS calls cadesplugin
3. The plugin requests certificate selection and token PIN
4. A detached signature CAdES-BES or CAdES-XLT1 is generated
5. 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?

We guarantee that signing will work without failures, and if necessary, we customize standard scenarios.

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.

Why is 1C-Bitrix the flagship of e-commerce?

A faceted index on a catalog of 200,000 SKUs is not built — bitrix:catalog.smart.filter takes 4 seconds instead of 200 ms, and the customer leaves. Our online store development on 1C-Bitrix eliminates such scenarios: from infoblock architecture and price types to cluster balancing under peak loads. With over 12 years of experience and 200+ completed e-commerce projects, we have solved every performance bottleneck.

Two-way synchronization with 1C via CommerceML — catalog, prices, balances, orders, and statuses. Configured from the admin panel via the catalog module -> 'Exchange with 1C'. Export to marketplaces via YML feeds (catalog.export) for Yandex.Market, Google Shopping, Ozon, Wildberries. According to Wikipedia, 1C-Bitrix is used by more than 70,000 commercial sites in Russia and the CIS (https://en.wikipedia.org/wiki/1C-Bitrix). Contact us to evaluate your current architecture.

How do we solve key performance problems?

bitrix:catalog.smart.filter without faceted index generates queries that bring down MySQL. Solution: build b_catalog_iblock_index — response time drops from 4 seconds to 100–200 ms. For SEO filters, we use catalog.seo.filter — indexable filter intersection pages with unique meta tags.

Composite cache (bitrix:main.composite) speeds up page loading by 3–5 times compared to regular. Goal — product card TTFB < 200 ms. For sessions we use Redis (SESSION_SAVE_HANDLER = redis in .settings.php). Lazy load images, CDN for static, SQL optimization (especially JOINs on b_iblock_element_property). As noted in the official Bitrix documentation, composite cache delivers a page from HTML, bypassing PHP execution and database requests, giving a speed advantage of up to 5x.

Why is caching critical for an online store?

Each second of page load delay reduces conversion by an average of 7%. At TTFB > 400 ms, 32% of users leave the site. Composite cache delivers a page from HTML, bypassing PHP execution and database requests — this gives a speed advantage of up to 5 times. For product cards with frequent price and stock changes, we use tagged caching: invalidation occurs only for affected entities. In practice, we have reduced TTFB from 1.2 seconds to 180 ms. Time savings on catalog loading — up to 60%.

Store types and their features

Integrations: payment systems, delivery, CRM, marketplaces

Payment systems. Handlers in sale.handlers: YooKassa, CloudPayments, Tinkoff, Sberbank, Apple Pay, Google Pay, installment. Callback sale.payment.notify for status confirmation. Delivery. Handlers sale.delivery for CDEK, Boxberry, Russian Post, DPD — real-time cost calculation via API, tracking. Warehouse management. Reservation (RESERVED = Y in b_sale_basket), automatic write-off upon shipment, notifications when stock falls below threshold, pre-order for goods in transit. CRM. Bitrix24 or amoCRM — orders from b_sale_order are sent automatically, client base is synchronized. Triggers: abandoned cart, review request, reactivation. Marketplaces. Export via YML to Ozon, Wildberries, Yandex.Market. Orders flow into a single system. Analytics and marketing. GA4, Yandex.Metrica, email newsletters (Unisender, SendPulse). Logistics. MyWarehouse, Antor — labels, picking lists.

Migration from other CMS

Migration from OpenCart, WooCommerce, Shopify, MODX: transfer of catalog (elements, properties, sections, images, SEO-URLs), migration of client base (b_user) and order history (b_sale_order), 301 redirects via urlrewrite.php. Parallel operation during the transition period — old site sells, new one is accepted. Team experience — 50+ migration projects.

What is included in the work (deliverables)

Stages and timelines

Average project duration — 2 to 4 months:

1. Analytics (1–2 weeks) — business requirements, catalog structure, integrations, technical specification
2. Design (2–3 weeks) — prototypes, design system, layouts
3. Development (4–8 weeks) — components, templates, integrations, content
4. Testing (1–2 weeks) — functional, load, acceptance
5. Launch (2–3 days) — deployment, monitoring, operational support

Budget range: from $10,000 for a basic store to $60,000+ for a complex marketplace with multiple integrations. Clients typically see a 20–30% increase in conversion after optimization. Contact us for a precise estimate — we tailor the solution to your specific catalog size and business logic.

Loyalty program and conversion

Bonus system: points for purchases, reviews, recommendations. Accrual rules by categories, points payment limit, expiration period — all in personal account. VIP levels (bronze, silver, gold, platinum) with increased cashback and free shipping. Recommendations 'You may also like', 'Complete your purchase' — built-in Bitrix tools + RetailRocket or Mindbox. Triggers: birthday discount, promo code for return, interest chain. Personalization via catalog.recommended.products and catalog.viewed.products. A/B testing of two card variants on real traffic. Enhanced E-commerce in GA4 and Yandex.Metrica — full path from click to return visit.

Request a free technical audit of your current store. Our engineers will identify performance bottlenecks and migration risks. Order turnkey online store development — get a ready solution with warranty and support.