Bitrix24-MoeDelo Integration
The accountant works in MoeDelo, the manager in Bitrix24. Between them is a chat where screenshots of invoices, voice messages with payment details, and questions like payment status inquiries fly around. We provide seamless CRM accounting document exchange, enabling full invoice automation. Our middleware setup takes only 3–7 days. With 30+ deals per week, manual reconciliation generates errors faster than the accountant can find them. On one project, such losses amounted to 15 hours per week, and errors in payment details—12% of all invoices. After integration, both figures dropped to 0.5% and 0 hours of manual work. This results in significant accountant time saving. The payback period for integration is 1–2 months due to reduced labor costs and elimination of fines for incorrect data. Our team has 5+ years of experience and has completed 50+ similar integrations. We developed a middleware that connects both systems without manual transfer—the setup cost is $2,500 with average monthly savings of $1,500, so payback occurs within 2 months. Contact us for a free project assessment—we will evaluate your project in one business day.
Perimeter and Integration Results
| Object | Bitrix24 → MoeDelo | MoeDelo → Bitrix24 |
|---|---|---|
| Counterparties | Create/update by INN | Updated details |
| Invoices | Auto-create from deal | Status (issued, paid, canceled) |
| Payments | — | Fact and amount of receipt |
| Acts | Request creation from CRM | PDF attached to deal |
| Products/services | CRM catalog → nomenclature | — |
| Metric | Before Integration | After Integration |
|---|---|---|
| Time to issue one invoice | 10 minutes | 30 seconds |
| Error rate in payment details | 12% | 0.5% |
| Weekly payment reconciliation time | 15 hours | 10 minutes |
| Duplicate counterparty rate | 5–8% | 0.1% |
| Monthly labor cost savings | $1,500 | – |
Architecture and Key Scenarios
Middleware Operation
MoeDelo provides a REST API with OAuth 2.0 authorization. Our MoeDelo API integration is robust and reliable. Bitrix24 offers REST API + webhooks for CRM events. According to Bitrix24 documentation, webhooks provide instant event notification. The integration is built through a middleware service—a PHP 8.1+ application using Guzzle and Monolog libraries, deployed on a separate server with IP whitelist.
- Event in CRM—the deal moves to the invoice issuance stage; Bitrix24 sends a webhook.
- Middleware fetches deal data: counterparty (INN), items, amounts, VAT.
- Search for counterparty in MoeDelo by INN. If not found, it is automatically created with details from CRM.
- Create invoice via MoeDelo API with all items and details.
- Invoice number and link are saved in the deal's custom field.
Source: Bitrix24 REST API documentation at https://dev.1c-bitrix.ru/rest_help/ EGRUL data via DaData API: https://dadata.ru/api/find-party/
Why Counterparty Sync Matters
The counterparty sync by INN eliminates duplicates and errors. The key rule is one INN, one record. When creating a company in CRM, the manager enters the INN, and the script validates the format and checksum; it requests data from the Unified State Register of Legal Entities/Individual Entrepreneurs (EGRUL/EGRIP) via DaData or Kontur.Focus, then fills the card: full name, legal address, KPP, OGRN. During synchronization with MoeDelo, it finds or creates the counterparty. Reverse synchronization: if the accountant added a counterparty in MoeDelo, the middleware creates a company in Bitrix24. Conflicts are resolved by priority: data from EGRUL has highest priority, then MoeDelo, then CRM. This eliminates duplicates and errors in details.
How Invoices Are Issued from CRM
The manager works in the familiar Bitrix24 interface. The invoice issuance process:
- In the deal card, they click "Create Invoice" (custom button or automatic stage trigger).
- Middleware checks for required data: counterparty INN, at least one product item, VAT rate.
- If something is missing, the manager sees a specific message about what to fill.
- The invoice is created in MoeDelo; PDF is generated and attached to the deal.
- The manager sends the PDF to the client from the card—by email or messenger.
For recurring invoices—copy previous one with updated date and number. Time savings: instead of 10 minutes per invoice—30 seconds.
How Payments Are Tracked
MoeDelo processes bank statements and matches payments to invoices. When a payment is recorded, the middleware receives a "paid" status with amount and date. In Bitrix24, the deal automatically moves to the "Paid" stage; a timeline entry appears with details. If partial payment—the deal remains on the current stage, and the actual amount is recorded in a field. Overdue invoices: middleware daily checks unpaid invoices against the due date; if overdue, the manager receives a notification with the invoice number and days overdue. This payment tracking in CRM ensures full visibility.
Financial Reports and Closing Documents
The integration adds data to CRM that wasn't there initially: accounts receivable per counterparty, average payment time, period turnover. These metrics give the manager context when working with a client and enable financial reports in Bitrix24. After obligations are fulfilled, from the deal card they can initiate the creation of an act—middleware transfers data to MoeDelo, the document is generated and returned to CRM as PDF. If the company uses electronic document management via MoeDelo, the document is sent to the counterparty through an EDI operator.
Error Handling and Security
When MoeDelo API is unavailable, the middleware performs three retries with exponential backoff (5, 15, 45 seconds). If the service does not respond, the task is queued and processed when connectivity is restored; the administrator receives a notification. Invalid data is returned to the manager as a clear message, e.g., "KPP not specified for legal entity," instead of an error code. Counterparty deduplication by INN (counterparties) and by internal invoice ID (documents) prevents duplicates. OAuth tokens for MoeDelo are stored on the middleware server and automatically refreshed via refresh token. All data transfer is over HTTPS; access is via IP whitelist; personal data in logs is masked. Our certified Bitrix24 developers guarantee 99.9% uptime and data consistency. We also ensure 54-FZ and MoeDelo compliance for fiscal data.
What's Included in the Integration
What's Included
- Documentation of the exchange scheme and middleware description. - Server access and error logging. - Training managers on using the "Create Invoice" button. - Support for 30 days after launch.We configure the integration for specific business processes: from the basic scenario (invoice from deal) to the full cycle with acts, payment tracking, and financial analytics in CRM. Get a turnkey integration in 3–7 days—we will set up the solution for your processes. The integration ensures compliance with Federal Law 54-FZ for fiscal data. On average, clients save over $1,500 per month and reduce error rates to below 0.5%. Write to us for a free project assessment.







