Configuring Order Import from 1C-Bitrix to 1C:Accounting
Importing orders from 1C-Bitrix into 1C:Accounting (BP) is a compromise solution. Accounting is not designed for order management: there are no order statuses, no manager processing, no CRM. But if accounting is maintained in BP and migration to Trade Management (UT) is not planned — integration is still necessary.
What gets created in BP when an order is transferred
Unlike UT, where a "Customer Order" document is created, in BP an order from 1C-Bitrix is created as a "Customer Payment Invoice" or "Sales of Goods and Services" (depending on the BP version and configuration).
Most commonly it becomes a "Payment Invoice". This means: the manager sees the issued invoice, but until payment is received it has no effect on warehouse stock. There is no reservation — BP has no reservation mechanism. Warehouse movement only occurs when a "Sales" document is posted.
This is a fundamental difference from UT: in UT, an order = reservation + status flow. In BP, an order = an invoice that is manually converted into a sales document.
Configuring order intake in BP
Section in BP: Bank and Cash → Website Exchange → Settings. Versions vary, but the logic is the same.
Counterparty. When creating an invoice, BP looks up the counterparty:
- For legal entities — by TIN (INN)
- For individuals — by name (full name)
If not found — a new one is created. Duplicate individuals with identical names are an inevitable problem. Solution: pass email as an additional identifier and check it before creating a new counterparty.
Nomenclature. Invoice line items are populated using the XML_ID from the 1C-Bitrix order. If the XML_ID does not match the GUID in BP — the item is created with "unknown" nomenclature or a string name (depending on settings).
Configuration: in BP exchange parameters, enable "Create nomenclature if necessary". This allows the order to enter the system, but the accountant will need to manually clarify the nomenclature. Better approach: establish two-way nomenclature synchronization so that XML_IDs match.
Back-transfer of statuses
BP has no order status system. The only document states are "Posted / Not Posted". Reverse status synchronization to 1C-Bitrix works as follows:
- Invoice created in BP → 1C-Bitrix receives creation confirmation → order status can be updated (e.g., "Accepted for Processing")
- Invoice posted (after payment) → "Paid" status can be transferred to 1C-Bitrix
- Sales document posted → status "Shipped"
Technically: BP sends updated documents with current state to 1C-Bitrix at each exchange. 1C-Bitrix updates the order status via a mapping table.
Taxes and VAT in the invoice
If the store works with VAT — the invoice in BP must contain the correct rates. When transferring an order from 1C-Bitrix, the XML must specify the VAT rate for each line item:
<Товар>
<Ид>product-guid</Ид>
<Количество>2</Количество>
<ЦенаЗаЕдиницу>1000.00</ЦенаЗаЕдиницу>
<Налоги>
<Налог>
<Наименование>НДС</Наименование>
<УчтенВСумме>false</УчтенВСумме>
<Ставка>20</Ставка>
</Налог>
</Налоги>
</Товар>
In 1C-Bitrix, the VAT rate is stored in the cart item property. Ensure that when an order is created, VAT rates are correctly populated from the product card (trade catalog module).
Case study: retail store on BP without migrating to UT
A small household chemicals store: 1,200 SKUs, one manager, 15–30 orders per day. Accounting is maintained in BP; migrating to UT is not cost-effective at this scale.
Configuration: orders from 1C-Bitrix are transferred to BP every 5 minutes. BP creates a payment invoice. The manager views the list of invoices in BP and processes them sequentially.
Notification was added: when a new invoice is created in BP, a scheduled task fires and sends an email to the manager with a link to the invoice. Implemented via the "Mailing" feature in the BP "Mail" module.
After shipment: the manager converts the invoice to a "Sales" document in BP and posts it. On the next exchange, 1C-Bitrix receives the updated status and marks the order as "Completed". The customer receives an email.
Limitation: there is a delay of up to 5 minutes between posting the sales document in BP and the status update on the website (the exchange interval). At this business scale, this is acceptable.
When BP is not enough
If the order volume exceeds 50–80 per day, or you need:
- Stock reservation upon ordering
- Multi-stage status processing
- Multi-manager/multi-warehouse accounting
— it is time to migrate to 1C:UT. Data migration (nomenclature, counterparties, price history) takes 1–2 days and does not require reworking 1C-Bitrix: XML_IDs of nomenclature items are preserved when migration is carried out correctly.