Bitrix24 Integration with Elba
Sole proprietors and small companies on simplified tax track accounting in Elba, and sales in Bitrix24. The link between systems usually looks like: manager closes deal, writes to accountant, accountant manually creates invoice, sends PDF, manager forwards to client. Two days later — "did they pay?" — accountant digs into bank statement. Multiply by 20 deals per week and get a process that eats time from both.
Bitrix24 integration with Elba automates the route "deal → invoice → payment → closing document".
What We Connect
| Data | Bitrix24 → Elba | Elba → Bitrix24 |
|---|---|---|
| Counterparties | Create by INN from CRM card | Updated details |
| Invoices | Auto-generate from deal | Status (issued / paid / overdue) |
| Payments | — | Fact receipt with amount and date |
| Acts | Create request | PDF document |
| Goods | Positions from deal CRM | — |
Architecture
Elba provides API for working with counterparties, invoices and payments. Integration is built via intermediate service:
- Bitrix24 → webhook on deal stage transition.
- Middleware → processes event, collects data, sends request to Elba.
- Elba → creates object (counterparty, invoice), returns result.
- Middleware → writes result back to CRM.
For reverse flow (payments, statuses) — middleware polls Elba API on schedule or processes callback if Elba supports it.
Automatic Invoice Creation from Deals
Main integration scenario. Manager works only in Bitrix24:
- Deal transitions to "Issue Invoice" stage — trigger sends data to middleware.
- Middleware checks: is counterparty INN present, are goods filled, is VAT rate specified (or "no VAT" for USN).
- Counterparty searched in Elba by INN. Not found — creates.
- Invoice formed in Elba: number, date, positions, total.
- PDF invoice generated and attached to deal in Bitrix24.
- Manager sends PDF to client from deal card.
For sole proprietors on USN "income" VAT is not charged — integration accounts for tax system and doesn't add VAT line to invoice.
Counterparties: Matching and Deduplication
Rule: one INN — one record in each system. On first sync:
- All companies with filled INN exported from Bitrix24.
- Matches searched in Elba.
- Found pairs linked via internal ID.
- Unmatched companies — created in target system.
On further work: each company creation/change in CRM checked for pair. If INN changed (input error, different entity) — re-matching.
Payment Reconciliation
Elba connects to bank via API and gets statements. When payment matched to invoice:
- Middleware gets info: invoice #127 paid, amount 85 000₽, date 12.03.2026.
- In Bitrix24, deal transitions to "Payment Received" stage.
- In timeline — entry with payment details.
- On partial payment — amount recorded in "Paid" field, deal stays on current stage.
Unpaid invoices with passed deadline — auto notification to manager. Configurable period: e.g., 3 and 7 days after payment deadline.
Closing Documents
After payment, Elba can auto-generate act of work or goods bill. Integration:
- Initiates act creation on deal transition to "Completed" stage.
- Sends data to Elba: counterparty, positions, period.
- Gets PDF and attaches to deal.
For sole proprietors this covers minimum document set: invoice → payment → act.
Special Features for Sole Proprietors and Small Business
Elba is tuned for simplified accounting. This affects integration:
- USN "income" — invoices without VAT, no need to pass tax rate.
- USN "income minus expenses" — expense documents from Elba not translated to CRM (not needed by manager).
- Patent — Elba keeps income record book; integration records only receipts.
- AUSN — automatic simplified system; Elba works with it, integration passes data unchanged.
Error Handling
- Elba API timeout — retry at 5, 15, 45 seconds. If fails — task queued, admin notified.
- Invalid INN — checksum checked before sending. Manager sees: "INN failed validation, check accuracy".
- Rate limit — middleware respects API rate limit, requests buffered.
- Nomenclature mismatch — if good from CRM not found in Elba's reference, creates automatically or logged for manual mapping.
Security
Authorization via OAuth 2.0. Tokens stored on middleware server, auto-updated. All requests — HTTPS. Middleware access limited by IP. Logs rotated, personal data masked.
Customize integration for specific tax regime and business process — from basic invoice issuance to full cycle with payment tracking and auto-closing document generation.