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 150,000 rubles. Companies save from 500,000 rubles 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:

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:

1. Seller. Company requisites: TIN, KPP, legal address, bank details. Stored in B24 settings or a separate directory.
2. Buyer. Requisites from the company card in CRM: TIN, KPP, address. TIN must be filled and verified.
3. Items. Product positions from the deal: name, quantity, price, VAT rate, unit of measure.
4. 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 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:

1. Periodically checks incoming documents via document.list.
2. Identifies the counterparty by TIN, finds the company in CRM.
3. Creates an activity in the deal card: "Incoming UPD from LLC 'Counterparty'."
4. Attaches a PDF version of the document.
5. 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

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.

How a corporate portal on Bitrix24 solves the problem of information chaos?

Employees spend up to 2 hours a day searching for files, emails, and solutions. Tasks get lost in dozens of chats, approvals get stuck for weeks. The manager learns about missed deadlines only at a meeting. A corporate portal on Bitrix24 ties every message, document, and task to a single context. You get a transparent picture of work: who is working on what, which stages, where bottlenecks are. Wikipedia: Information silo describes how unorganized data reduces productivity – a portal cuts that loss by 60–70%.

We will evaluate your project for free – contact us to get the architecture in 2 days. A medium‑sized company typically saves 2.5 million rubles annually after deployment (based on our projects).

What does the portal offer in daily work and why is it better than messengers?

In messengers, information is unstructured – discussions get buried within a week. On the portal, every message is tied to a task, project, or document. Employees spend up to 30% of their work time searching for data (McKinsey). The portal reduces this time by 2–3 times thanks to structured repositories and full‑text search.

Communications. Activity stream, messenger, and video calls are tied to specific tasks. Any discussion can be found six months later – in a messenger it would be buried within a week.

Tasks and projects. Kanban, Gantt, checklists, dependencies, time tracking. Each employee's efficiency is visible in reports – no need to wait for a meeting.

Document flow. Approval routes through the business process designer: leave request → manager → HR → accounting. Electronic signature, versioning, deadline control. Integration with electronic document management (SBIS, Diadoc) via REST API.

HR. Onboarding of new employees, leave/travel requests, organizational structure, absence schedule. An employee knows where to go from day one.

Knowledge base. Bitrix24 wiki engine: regulations, instructions. Knowledge does not leave with departing employees.

Implementation example. For a manufacturing company with 320 employees, we deployed a portal with integration of 1C:SALARY AND HR MANAGEMENT and Active Directory in 4 months. Travel request approval time decreased from 3 days to 4 hours. Savings on employee idle time amounted to 1.5 million rubles per year. Managers receive automatic reports on department efficiency. Customer response time decreased by 20%. Portal payback period is 7 months.

How does integration with 1C and Active Directory accelerate HR management?

Integration with 1C:Enterprise via the b24connector module or custom REST handler: a leave request is approved on the portal through a business process and automatically enters 1C:SALARY AND HR MANAGEMENT for vacation pay calculation. Active Directory (SSO via the ldap module) – the employee account is created once in AD and synchronized to the portal, email, VPN. Upon dismissal, it is blocked everywhere. Manual account creation is eliminated, errors are minimized.

Types of corporate portals and key integrations

Additional integrations that deliver real value:

• Email: Exchange via EWS API or IMAP, calendar synchronization, creating a task from an email.
• IP telephony: Asterisk, Mango Office, Zadarma via REST API – calls from the portal, contact card, call recording.
• Video conferencing: built‑in video calls or integration with Zoom/Teams via marketplace.
• EDI: SBIS, Diadoc via REST API – fully electronic document flow with counterparties.

Security and compliance with Federal Law 152‑FZ

The portal contains personal data, financial reports, strategic plans. We guarantee protection:

• role model via CGroup and section‑level permissions;
• two‑factor authentication (OTP, Yandex.Key, SMS);
• audit of all actions (b_event_log);
• TLS encryption for transmission and disk encryption;
• full compliance with Federal Law No. 152‑FZ "On Personal Data".

How is implementation carried out? Step‑by‑step plan

1. Audit — we record current processes, measure time losses.
2. Design — choose portal type, plan integrations.
3. Implementation — configure business processes, permissions, interface.
4. Test — pilot group tests scenarios, we fix issues.
5. Launch — connect all employees, train, hand over documentation.

What you receive after implementation

• Project documentation: architecture, integration scheme, business process diagrams.
• Configured portal with all integrations (1C, AD, telephony, EDI).
• Business process descriptions and instructions for administrators and users.
• 30 days of technical support after launch.
• Access to our knowledge base and migration scripts.

Post‑launch support: how to prevent the portal from becoming obsolete

After six months, many portals become abandoned. To avoid this, we offer packages with fixed SLA and a dedicated administrator. Performance monitoring, platform updates, user administration, development of new modules. Our team has over 10 years of experience and more than 50 implemented corporate portals on Bitrix24. We are a certified 1C‑Bitrix partner, guaranteeing quality and deadlines.

Mobile access. Native Bitrix24 app (iOS/Android) with push notifications, tasks, chats. Responsive web interface for extranet users (no app installation required). Offline access to documents and tasks, sync when connectivity is restored.

Order a turnkey corporate portal implementation

Schedule a free audit – we will evaluate your project, propose architecture, and give clear timelines. Get a comprehensive proposal and see that the portal pays for itself within the first six months. Contact us today.