Bitrix24 integration with Zoho Books, QuickBooks, Odoo and 1C
Sales run in the CRM, while invoices, payments and VAT live in the accounting system. Until the two are connected, accounting retypes deals into invoices and the sales manager does not know whether the client has paid. We connect Bitrix24 to your accounting so that every figure has one master system and the other one receives it automatically
What breaks while the CRM and accounting are apart
Four typical losses while sales and accounting work in separate systems
Every invoice is typed twice
A manager closes the deal in the CRM, and accounting types the client, the lines and the amounts into the accounting system again. A typo in the TRN or the company name shows up when the client sends the invoice back for correction
Sales cannot see payments
The money has arrived and is recorded in accounting, but the deal in the CRM is still stuck at "Invoice sent". The manager chases a client who has already paid, or ships to one who has not
Two client lists
The CRM has "ABC Trading", accounting has "A.B.C. General Trading LLC", one record has a TRN and the other does not. Client reports do not match, and duplicates appear on both sides
Old prices in the CRM
Prices and VAT rates were updated in the accounting system, but the CRM catalog still has the old ones. A quote goes out with a price that later has to be recalculated
What goes where
One rule: every data set has one master system. The other system reads it but does not edit it, otherwise within a month the data in the two places drifts apart
Clients and company details
Legal name as on the licence, TRN, address, emirate, mainland or free zone. A client is created in accounting not at the lead stage but when the deal reaches invoicing, and it is matched by TRN so no duplicates appear
CRM → accountingProducts and prices
Items, codes, units of measure, prices and VAT rates are kept in the accounting system and flow into the Bitrix24 catalog. Managers build quotes from the current price list
accounting → CRMInvoice from the deal
At the "Issue invoice" stage an automation rule sends the deal to accounting: client, lines, currency and discounts. The accounting system assigns the invoice number so numbering stays in one place, and a link to the invoice comes back to the deal
CRM → accountingPayments and invoice status
Paid, partly paid, overdue. The deal moves to "Paid" by itself, the manager gets a notification, and management sees money rather than promises
accounting → CRMBalances and credit limits
Receivables, overdue invoices and the credit limit are visible in the company record. A new order over the limit goes to management for approval
accounting → CRMStock
If stock is kept in the accounting system, stock levels by warehouse flow into the CRM catalog, so managers do not promise goods that are not there
accounting → CRMLeads, tasks, chats and calls do not go to accounting: the finance team does not need them, and extra sync only adds errors
What is specific to each system
Zoho Books
Has a UAE edition with VAT. We connect through the Zoho Books API with OAuth. The limit is 1,000 to 10,000 API calls a day depending on the plan, so the sync is event-driven rather than polling every minute. Zoho is on the UAE Ministry of Finance list of accredited e-invoicing providers, so Zoho Books sends e-invoices itself
QuickBooks Online
Sold in the UAE, handles VAT and invoices in several currencies. The ready-made QuickBooks app in the Bitrix24 Market syncs clients and three invoice statuses (new, sent, paid) but not products: invoice lines are picked in QuickBooks. If a deal has to become an invoice with lines and partial payments by itself, we build the integration on the QuickBooks API
Odoo
UAE localization out of the box: 5% VAT, the VAT201 return and a corporate tax report. On Odoo Online the external API is available only on the Custom plan, so on the Standard or free plan Odoo cannot be connected to Bitrix24 through the API. We check the Odoo plan before the work starts
1C
For the Russian, Belarusian and Kazakh editions of 1C (Accounting, Trade Management, ERP and other standard configurations) Bitrix24 has a built-in exchange: clients, deals, invoices, products, payments and shipments both ways, prices and stock from 1C. It works with cloud and on-premise Bitrix24. If 1C is customized or adapted for the UAE, we build the exchange through 1C HTTP services
If your books are kept in another system with an open API, the approach is the same: a data map, one master system for every data set and a sync log
Electronic invoices from 2027
From 1 January 2027 for companies with revenue of AED 50M or more, and from 1 July 2027 for the rest, a B2B invoice in the UAE becomes a PINT AE file sent through an accredited service provider (ASP). The first group has to appoint a provider by 30 October 2026. The e-invoice is produced by the accounting system, not the CRM, but its data starts in the CRM
- A UAE electronic tax invoice has 51 mandatory fields under the Ministry of Finance specification. Nine of them describe the buyer, including the name, TRN, address, city, emirate and country
- These fields are filled in the client record in Bitrix24 and go to accounting with the deal. Required fields do not let a deal move to invoicing until the details are complete
- Zoho itself is on the Ministry of Finance list of accredited providers. Intuit, Odoo and 1C are not on it as of 28 September 2026, so for QuickBooks, Odoo and 1C a provider is connected separately
- The e-invoice status (sent, accepted, rejected) comes back to the deal if the accounting system exposes it
- Deadlines, penalties and client data clean-up are covered on the VAT and e-invoicing page
Ready-made app or custom integration
- A ready-made app from the Bitrix24 Market fits when the process is standard and what the app does is enough. It is quick to install, but its logic cannot be changed
- Make or Zapier handle simple chains, such as a new company in the CRM creating a customer in accounting. The more conditions there are, the harder such a setup is to maintain
- A custom integration on the Bitrix24 REST API and the accounting API is needed when there are currencies, partial payments, credit limits, duplicate checks by TRN and several legal entities
- Whichever option is used, we keep a sync log: if an invoice was not created, the responsible person gets a notification with the reason instead of hearing about it from the client
How the work goes
Review
We look at where clients, products, invoices and payments live today and what is retyped by hand
Data map
For every data set we decide which system is the master, what is sent, in which direction and at which deal stage
Integration and testing
We set up the sync and test it on a test organization in accounting before switching it on for live data
Launch
We clean up duplicates, fill in missing TRNs, switch the sync on and stay on support
Experience: 1C and ERP in one loop with Bitrix24
For Unilin, a flooring manufacturer, we have run an on-premise Bitrix24 on their own server for the third year. We built end-to-end integrations with 1C and the ERP, so product data, shipments and other records move between systems without manual transfer, and management sees BI on the market, retail points, products and the company. The project runs in Russia; for a company in the UAE the exchange logic is the same. Read the case
This is not tax advice. E-invoice requirements come from the UAE Ministry of Finance mandatory fields specification (version 1.0, 23 February 2026), deadlines from Ministerial Decision No. 244 of 2025 as amended in 2026, and the provider list from the Ministry of Finance page as of 28 September 2026. System capabilities are described from Zoho, Intuit, Odoo and Bitrix24 documentation as of September 2026. Discuss the choice of provider and tax questions with your accountant