Integration of Bitrix24 with SBIS

Bitrix24 Integration with SBIS

Accounting works in SBIS, managers — in Bitrix24. Closing documents form in one system, deal data — in another. Manager asks accountant to issue an act, accountant asks for details, manager finds them in CRM, sends in chat. Two days later client asks: "Where are the documents?" Turns out the act was prepared but not sent via EDI. Integration of B24 with SBIS closes the chain: deal in CRM → document in SBIS → sending to counterparty → status back to CRM.

What is SBIS

SBIS (developer — Tensor company) is a platform for electronic document exchange, accounting, reporting, and business management. In context of B24 integration, the EDI module is relevant: exchanging legally significant documents with counterparties through EDI operators.

Documents transmitted via SBIS:

• UPD — Universal Transfer Document (invoice + act/shipment)
• Act of Work / Service Completed
• Shipping Document (Torq-12)
• Payment Invoice (unformalized)
• Contract, amendment, specification (unformalized)
• Invoice — for VAT operations

Integration Architecture

SBIS provides REST API for document work. Integration built per scheme:

Key SBIS API methods:

• Authorization — auth.getToken for session token
• Document Creation — document.create with type, details, nomenclature
• Sending — document.send to transmit to counterparty
• Status Retrieval — document.getStatus for tracking signing
• Incoming List — document.list with type and status filter

Auto Document Creation from CRM

Scenario: manager moves deal to "Document Prep" stage → robot starts business process → handler forms document in SBIS.

Document data:

1. Seller. Company details: tax ID, registration code, legal address, bank account. Stored in B24 settings or separate reference.
2. Buyer. Details from company card in CRM: tax ID, registration code, address. Critically important — tax ID must be filled and verified.
3. Nomenclature. Deal product positions: name, quantity, price, VAT rate, unit.
4. Number and Date. Generated automatically per company numbering rules.

Handler transforms data to SBIS API format and calls document.create. Response contains document ID, saved to deal custom field.

Signing and Sending

After creation, document is in "Draft" status in SBIS. Next:

• Manual Signing. Responsible employee enters SBIS, reviews document, signs with QES. Fits companies with strict document control.
• Auto Signing. QES configured on server or SBIS cloud — document signs and sends without human. Fits mass distribution of uniform documents (monthly service acts).

After signing — automatic sending to counterparty via EDI.

Returning Statuses to CRM

Integration tracks document statuses in SBIS and updates B24:

Status polling via periodic cron script (every 15-30 minutes) or callback mechanism if SBIS API supports it for your plan.

Processing Incoming Documents

Counterparty sends document via SBIS. Integration:

1. Periodically checks incoming via document.list.
2. Determines counterparty by tax ID, finds matching company in CRM.
3. Creates activity in deal card: "Incoming UPD from LLC 'Counterparty'".
4. Attaches PDF version.
5. Assigns manager task: "Review and sign incoming document."

Implementation Timeline

What We Configure

• Connecting SBIS API: authorization, access rights setup, organization box binding
• Mapping CRM details → SBIS: tax ID, registration code, addresses, bank account
• Auto document formation from deal: UPDs, acts, shipments
• Setting up signing: manual via SBIS interface or automatic via server/cloud QES
• Syncing document statuses: SBIS → deal custom fields → CRM robots
• Processing incoming documents: notifications, counterparty binding, signing tasks
• Training managers: initiating document send from CRM, status control, rejection handling