Bitrix24 and SBIS Integration: Document Workflow Automation
The accounting department works in SBIS, managers in Bitrix24. Closing documents are created in one system, while deal data is in another. Without integration, a manager asks the accountant to issue a statement, the accountant asks for requisites, the manager searches for them in the CRM and sends them via chat. Two days later, the counterparty asks where the documents are. It turns out the statement was prepared but not sent via EDI.
Our experience shows that integrating Bitrix24 with SBIS closes the chain. Deal in CRM → document in SBIS → send to counterparty → status back in CRM. This reduces document workflow time by 80% and eliminates human errors. After setup, every document goes from creation to sending without employee involvement, and statuses update automatically. The average savings per document is 20 minutes, which at 500 documents per month gives savings of up to $1.4k–1.9k. Companies save from $4.5k–6.5k per year on document workflow.
What is SBIS
SBIS is a platform for electronic document exchange, accounting, and reporting. The developer is Tensor. For integration with Bitrix24, the key module is EDI: exchange of legally significant documents through an operator network. The SBIS API supports over 50 document types: UPD, acts, invoices, contracts.
How Bitrix24 and SBIS integration works
SBIS provides a REST API for working with documents. The integration follows this scheme:
| Component | Purpose |
|---|---|
| B24 CRM | Source of deal data: requisites, items, amounts |
| Server handler | Receives webhook from B24, forms request to SBIS API |
| SBIS API | Creates document, sends to counterparty, returns status |
| Digital signature | Signature via SBIS (cloud or local) |
Key SBIS API methods:
-
auth.getToken— retrieve session token -
document.create— create a document with type, requisites, items -
document.send— send to counterparty -
document.getStatus— get signing status -
document.list— list incoming documents with filter by type and status
How to set up automatic document creation from CRM
The manager moves the deal to the "Document Preparation" stage. A robot triggers a business process. The handler creates the document in SBIS.
Data for the document:
- Seller. Company requisites: TIN, KPP, legal address, bank details. Stored in B24 settings or a separate directory.
- Buyer. Requisites from the company card in CRM: TIN, KPP, address. TIN must be filled and verified.
- Items. Product positions from the deal: name, quantity, price, VAT rate, unit of measure.
- Number and date. Generated automatically according to the company's numbering rules.
The handler transforms the data into the SBIS API format and calls document.create. The response returns a document ID, which is saved to the deal's custom field.
Signing and sending
After creation, the document is in "Draft" status in SBIS. Then:
- Manual signing: the responsible person logs into SBIS, reviews the document, signs it with a digital signature. Suitable for companies with strict control.
- Automatic signing: the digital signature is configured on the server or in the SBIS cloud — the document is signed and sent without human involvement. Suitable for mass sending of recurring documents (monthly acts for subscription services).
After signing, the document is automatically sent to the counterparty via EDI.
Returning statuses to CRM
The integration tracks document statuses in SBIS and updates data in B24:
| Status in SBIS | Action in B24 |
|---|---|
| Draft | Deal field "EDI" = "Document created" |
| Sent | "EDI" = "Sent to counterparty" |
| Signed by counterparty | "EDI" = "Signed by both parties", robot moves deal to "Closed" stage |
| Rejected | "EDI" = "Rejected", notification to manager with reason |
| Cancelled | "EDI" = "Cancelled", task to manager for re-sending |
Status polling is done by a cron script every 15–30 minutes, or via callback if the SBIS plan supports it.
Processing incoming documents
A counterparty sends a document via SBIS. The integration:
- Periodically checks incoming documents via
document.list. - Identifies the counterparty by TIN, finds the company in CRM.
- Creates an activity in the deal card: "Incoming UPD from LLC 'Counterparty'."
- Attaches a PDF version of the document.
- Assigns a task to the responsible person: "Review and sign incoming document."
Why API integration is more profitable than manual entry
Manual process: the manager asks the accountant, the accountant finds requisites, creates the document, checks it, signs it, sends it. For one deal — from 30 minutes. Integration via API works 120 times faster: the document is created and sent automatically based on the deal status in 15 seconds. This is especially noticeable for mass sending, e.g., monthly acts for 100 clients. Return on integration is 3–4 months due to time savings and error elimination (98% of documents go through without errors).
Implementation timelines
| Scope | What's included | Timeline |
|---|---|---|
| Basic | Creation and sending of non-formalized documents (acts, contracts) from CRM | 1-2 weeks |
| Standard | Formalized documents (UPD), auto-signing, status return to CRM | 2-4 weeks |
| Extended | Incoming document processing, 1C integration, mass sending, automatic counterparty matching | 4-6 weeks |
What's included in the work
- SBIS API connection: authorization, access rights setup, organization mailbox binding.
- CRM → SBIS requisites mapping: TIN, KPP, addresses, bank details.
- Automatic document creation from deals: UPD, acts, invoices.
- Signing setup: manual via SBIS interface or automatic via server/cloud digital signature.
- Document status synchronization: SBIS → deal custom fields → CRM robots.
- Incoming document processing: notifications, binding to counterparty in CRM, signing tasks.
- Manager training: initiating document sending from CRM, status monitoring, actions on rejection.
Contact us for project evaluation and get a commercial proposal within one day. Order integration and automate your document workflow today.