Configuring 1C:Enterprise Accounting and 1C-Bitrix Exchange
Enterprise Accounting (BP) is not a trade system, but in practice it is often the only accounting software in small businesses. An online store runs on 1C-Bitrix, items and prices are maintained in BP — and the request arises: "make the products on the site update from 1C." The standard BP exchange module exists, but it is significantly more limited than in UT or KA.
What the BP Exchange Supports Out of the Box
In 1C:Enterprise Accounting (edition 3.0), the website exchange module is located under Administration → Data Exchange. Functionality is limited:
- Item export (name, article, unit of measure)
- Price export (one type — "Base Sales Price")
- Stock export (total stock, no breakdown by warehouse)
- Customer order import (creates an "Invoice to Buyer" document)
What is missing: characteristics (variants), multiple price types, warehouse breakdown, images, categories (the group hierarchy is transmitted as a flat list with no nesting beyond one level).
For a small store (up to 5,000 items, one price type, one warehouse) this is sufficient. For anything beyond that — customization is required.
The Category Hierarchy Problem
This is the most common pain point when working with BP. In the "Items" reference book in BP, groups are simply folders with no depth restriction. The XML export transmits groups correctly (with ParentID), but 1C-Bitrix sometimes creates a flat structure instead of a tree during import.
The cause: in the 1C-Bitrix exchange module settings, the option "Do not update section binding" may be enabled by default. If it was enabled during the first import and later disabled — the hierarchy is not automatically restored. You need to reset the XML_IDs of sections and run a full re-import.
Configuring Price Export
BP has only one price type — "Base Sales Price." This is the price from the ItemPrices information register. On the 1C-Bitrix side, it is mapped to the base price type in the trade catalog.
If the website needs retail and wholesale prices but BP does not maintain them — the typical solution is to export the base price from BP and calculate markups using 1C-Bitrix formulas (Settings → Trade Catalog → Price Types → Formula).
// Example formula for wholesale price with a 15% discount
BASE_PRICE * 0.85
This works when pricing logic is simple. If discounts depend on volume, customer type, or promotions — either migrate to UT/KA or implement custom logic in 1C-Bitrix.
Loading Orders into BP
Orders from 1C-Bitrix arrive in BP as "Invoice to Buyer" — not "Customer Order" as in UT. This matters: BP has no full-featured sales module, so the manager in 1C sees an invoice rather than an order in a status-tracking system.
Accountants in BP should not manually post every invoice — that is unnecessary work. Configure automatic invoice posting upon receipt from the exchange via the AutomaticPosting = Yes flag in the exchange node settings.
Counterparties. When creating an invoice, BP searches for the counterparty by TIN or name. If the buyer is an individual — no TIN, search by name (full name). Duplicate counterparties are a very common problem with individual buyer orders that have similar names. I recommend transmitting a unique external buyer ID (XML_ID) from 1C-Bitrix and configuring BP to search by it.
Case Study: Jewelry Online Store
A jewelry store, 3,000 items, all prices maintained in BP. Problem: prices in BP changed multiple times per day (gold, silver — exchange-traded prices), while the website updated only once a day.
Configured incremental exchange — price changes only — every 30 minutes. In BP, wrote a scheduled task: when the metal exchange rate changes — recalculate item prices and update the ItemPrices register. 1C-Bitrix picks up the changes at the next exchange session.
Average XML volume during incremental exchange — 200–400 items instead of 3,000. Processing time — 8 seconds instead of 90.
Limitations and When to Move to UT
BP is suitable for 1C-Bitrix integration when:
- Up to 10,000 item positions
- One price type (or simple formula-based markups)
- One or two warehouses
- No product characteristics (color/size variants)
If any of these conditions are not met — consider migrating to 1C:UT or KA. Migrating data from BP to UT using standard tools takes 1–2 days.