We often see: a sole proprietor or small business on the simplified tax system keeps accounting in Elba, and sales in Bitrix24. The manager closes a deal, writes to the accountant, who manually creates an invoice in Elba, sends a PDF, the manager forwards it to the client. Two days later — 'Has it been paid?' — the accountant checks the bank statement. With 20 deals per week, the manual process eats up hours. Our integration automates the route: deal → invoice → payment → closing document. We implement it turnkey in 5–10 business days. The result is transparent document flow without double entry. Average time savings: 8 hours per week for the accountant, which is 4 times faster than manual processing. Assess — during a consultation we'll estimate the savings for your business. No need to replace your accounting system – everything works together.
Integration details
| Data | Bitrix24 → Elba | Elba → Bitrix24 |
|---|---|---|
| Counterparties | Creation by TIN from CRM card | Updated details |
| Invoices | Automatic generation from deal | Status (issued / paid / overdue) |
| Payments | — | Receipt fact with amount and date |
| Certificates | Request for creation | PDF document |
| Items | Line items from CRM deal | — |
How automatic invoice generation works
The main scenario. The manager works only in Bitrix24:
- The deal moves to the stage 'Issue invoice' — a trigger sends data to the middleware.
- Middleware checks: is the counterparty's TIN filled, are the item lines present, is the VAT rate specified (or 'without VAT' for simplified tax).
- The counterparty is searched in Elba by TIN. Not found — created.
- Invoice is generated in Elba: number, date, positions, total amount.
- The invoice PDF is generated and attached to the deal in Bitrix24.
- The manager sends the PDF to the client from the deal card.
For sole proprietors on simplified tax 'income', VAT is not charged — the integration considers the tax system and does not add a VAT line to the invoice. Compare: manual issuance takes 15 minutes, automatic — 10 seconds. The automation is 90 times faster per invoice. Time savings — 8 times per invoice.
Architecture and counterparty matching
Elba provides an API for working with counterparties, invoices, and payments. The integration is built via an intermediate service:
- Bitrix24 → webhook when the deal moves to the required stage.
- Middleware → processes the event, collects data, sends a request to Elba.
- Elba → creates an object (counterparty, invoice), returns the result.
- Middleware → writes the result back to the CRM.
For the reverse flow (payments, statuses) — middleware polls the Elba API on a schedule or processes callbacks.
Rule: one TIN — one entry in each system. During the first synchronization:
- From Bitrix24, all companies with a filled TIN are exported.
- In Elba, matches are searched.
- Found pairs are linked via internal ID.
- Companies without a pair are created in the target system.
During further work, each creation or change of a company in the CRM is checked for an existing pair. If the TIN changed — remapping. This reduces duplicates by 100%.
Payment reconciliation and closing documents
Elba connects to the bank via API and receives statements. When a payment is matched to an invoice:
- Middleware receives information: invoice #127 paid, amount 85,000 ₽, date March 12.
- In Bitrix24, the deal moves to the stage 'Payment received'.
- A timeline entry with payment details is added.
- For partial payment, the amount is written to the 'Paid' field; the deal remains at the current stage.
Unpaid invoices with an expired due date — automatic notification to the manager. The period is configurable: e.g., 3 and 7 days after the due date.
After payment, Elba can automatically generate a certificate of completed work or a delivery note. The integration initiates the creation of a certificate when the deal moves to the stage 'Completed', passes the data to Elba, and receives a PDF attached to the deal. For sole proprietors, this covers the minimal document set: invoice → payment → certificate.
Why integration is important for sole proprietors
Sole proprietors and micro-businesses on the simplified tax system often save on an accountant. Manually filling invoices and tracking payments takes time that could be spent on growth. The integration of Bitrix24 with Elba eliminates the human factor: no need to enter data twice, forget to issue an invoice, or miss a delay. According to simplified tax system, the tax rate depends on income accounting — the integration helps keep it more accurate. The company saves up to 200,000 rubles per year on operational errors and time. Our company has 5+ years of experience in CRM integrations, with over 50 successful projects and certified specialists (1С-Битрикс сертификат). We offer a 30-day guarantee on integration reliability.
Features for sole proprietors and small businesses: Elba is tailored for simplified accounting. This affects the integration:
- Simplified tax 'income' — invoices without VAT, no need to transfer tax rate.
- Simplified tax 'income minus expenses' — expense documents from Elba are not translated to CRM (they are not needed by the manager).
- Patent — Elba maintains a book of income; the integration only records receipts.
- Automated simplified tax system (ASN) — Elba works with it; integration passes data unchanged.
Comparison of processes before and after integration
| Stage | Manual process | Automated process |
|---|---|---|
| Invoice issuance | 15 min, manual entry in Elba | 10 sec, automatically from deal |
| Payment check | Accountant checks statement manually | Automatic status update |
| Certificate creation | Manually after payment | Automatically by stage |
| Overdue notification | None or manual reminder | Auto-notification after 3/7 days |
Error handling and security
- Elba API timeout — retry after 5, 15, 45 seconds. If unsuccessful — task in queue, notification to admin.
- Invalid TIN — check control sum before sending. Manager sees: 'TIN failed validation, check correctness'.
- Rate limit — middleware respects rate limit, requests are buffered.
- Nomenclature mismatch — if an item from CRM is not found in Elba's directory, it is created automatically or logged for manual mapping.
Authorization via OAuth 2.0. Tokens are stored on the middleware server, refreshed automatically. All requests over HTTPS. Access to middleware is restricted by IP. Logs are rotated, personal data is masked.
Technical requirements for middleware
For deploying the integration, a Linux server (Ubuntu 20.04+), PHP 8.1+, MySQL 5.7+, Composer and curl module are required. All required dependencies are specified in the documentation.What is included in the work
- Audit of current business processes and setup of integration scenarios.
- Development of middleware for linking Bitrix24 and Elba.
- Configuration of automatic invoice and certificate creation, and payment tracking.
- Employee training on working with the integration.
- Technical documentation and middleware source code.
- Access to middleware (login/password) and server setup assistance.
- Warranty support 30 days after launch (including free updates for Elba API changes).
- 5+ years of experience, 50+ implemented integrations, certified specialists.
Start with a consultation
The integration is configured for your specific tax regime and business process — from basic invoice issuance to a full cycle with payment tracking and automatic closing documents. Contact us to get a preliminary cost and timeline estimate. Typical integration cost starts from 50,000 rubles. We will analyze your workflow for free and propose the optimal solution.