Setting up electronic document exchange via Bitrix24

Configuring Electronic Document Exchange via Bitrix24

Electronic document exchange through Bitrix24 eliminates routine manual invoicing and UPD document preparation. Instead of exporting PDF, sending via email, and waiting for a signed scan — documents reach the counterparty in seconds, and signed copies return directly to the CRM. Let's examine how to set this up from operator selection to automatic incoming document binding to deals.

Choosing an EDI Operator

Bitrix24 supports integration with three main operators:

• Kontur.Diadoc — largest subscriber base, convenient API, stable roaming operation
• SBIS (Tensor) — strong analytics, deep reporting integration
• Takskom — broad government sector coverage, marking support

The choice depends on which operator your key counterparties use. If 70% of partners are on Diadoc — connect to Diadoc. Roaming between operators works, but adds 2-4 hour delay on initial routing setup.

Connecting to Bitrix24

Integration is performed via applications from the Bitrix24 Marketplace. For Diadoc it's "Kontur.Diadoc for Bitrix24", for SBIS — Tensor's built-in connector.

Connection procedure:

1. Install operator app from Marketplace → Integrations
2. Authorize with your EDI operator account (digital signature certificate required)
3. Set up organization mapping — your legal entity in Bitrix24 must match the mailbox in EDI by TIN/BRN
4. Specify default mailbox if company has multiple divisions

After connecting, an EDI block appears in company cards with exchange status with specific counterparty.

Automatic Sending from CRM

Main scenario — sending an invoice or UPD when deal moves to specific stage. Implemented via robots or business processes.

"Send document via EDI" robot triggers on deal stage change. Settings specify:

• Document type (invoice, UPD, act)
• Generation template from deal data and attached invoice
• Signer — employee with digital signature having signing rights

Data is taken from "Invoice" entity (crm.invoice) or smart process. Nomenclature, amounts, counterparty details are pulled automatically. If deal has multiple invoices — robot processes the last unsent one.

Incoming Documents and Deal Binding

Incoming EDI documents arrive in operator app "Documents" section. Automatic deal binding works by counterparty TIN:

• System searches company in CRM by sender's TIN
• If found with open deal — attaches document to it
• If no deal — creates new deal in specified pipeline (configured in integration settings)

For incoming document signing, responsible person gets notification in Bitrix24 feed. Signature is applied via browser CryptoPro plugin or operator application.

Roaming Between Operators

If your counterparty uses different EDI operator, documents transfer via roaming. Configuration:

1. In operator personal account send roaming invitation by counterparty TIN
2. Wait for confirmation (usually automatic, takes 10 minutes to a day)
3. After roaming setup, exchange works same as within one operator

Roaming limitations: not all document types supported (formatted acts and invoices — yes, unformatted attachments — depends on operator pair). Roaming status shown in CRM company card.

Common Setup Issues

Details mismatch. TIN/BRN in Bitrix24 and in EDI mailbox must match character-for-character. Extra space or dash — matching won't work.

Digital Signature Certificate. CryptoPro CSP browser plugin must be installed on each signer. Chrome and Edge require CryptoPro Extension for CAdES Browser Plug-in.

Document Duplication. If robot is set for multiple pipeline stages without "already sent" check — document sends repeatedly. Add condition checking "EDI Status" field in deal card.

API Timeouts. With large document flow (50+ per hour), delays possible on operator side. Use sending queue with retries via business process with pause.

What You Get in the End

Configured EDI via Bitrix24 closes the "deal → invoice → sending → signing → closure" chain. Manager stays in CRM, accounting gets signed documents to accounting system via operator sync with 1C. Average implementation time — 2-3 business days with existing digital signature and EDI operator contract.