Bitrix to 1С:Accounting Order Integration

Integrating Orders: Bitrix → 1С:Accounting

We configure Bitrix to 1С:Accounting order integration turnkey. We'll assess your project in one day and prepare a roadmap with precise timelines. We use CommerceML and Bitrix REST API — this ensures stable exchange with no data loss. Your accountant will see every order in a familiar system without extra headaches.

Loading orders from Bitrix into 1С:Accounting is a compromise solution. Accounting isn't designed for order management: no order statuses, no manager processing, no CRM. But if accounting is done in 1С:Accounting and migrating to Trade Management isn't planned yet — integration is still needed. Average setup time is 1–3 days, saving the accountant up to 2 hours per day.

What Is Created in Accounting When an Order Is Transferred

Unlike Trade Management, where a 'Customer Order' is created, in Accounting, an order from Bitrix is created as a 'Payment Invoice' or 'Sales of Goods and Services' (depending on the Accounting version and settings).

Most often — a 'Payment Invoice'. This means: the manager sees the issued invoice, but until payment, it doesn't affect stock balances. No reservation — Accounting has no reservation mechanism. Stock movement occurs only when the 'Sales' is posted.

This is a fundamental difference from Trade Management: in Trade Management, an order = reservation + status flow. In Accounting, an order = invoice, which is manually converted into a sale.

How to Configure Order Exchange Between Bitrix and 1С:Accounting

Section in Accounting: Bank and Cash → Exchange with Site → Settings. Versions differ, but the logic is the same.

1. Specify site details (URL, login, password for exchange).
2. Configure the scheduled task schedule — usually every 5–15 minutes.
3. Enable item creation when necessary in exchange settings.
4. Map statuses: invoice created → status in Bitrix, posted → paid, sales → shipped.

Counterparty. When creating an invoice, Accounting searches for a counterparty:

• For legal entities — by TIN
• For individuals — by name (full name)

If not found — a new one is created. Duplicates of individuals with the same names are an inevitable problem. Solution: pass email as an additional identifier and check it before creating a new counterparty.

Items. Invoice lines are filled by XML_ID from the Bitrix order. If XML_ID doesn't match the GUID in Accounting — the line is created with an 'unknown' item or with a string name (depending on settings).

Setting: in Accounting exchange parameters, enable 'Create items when necessary'. This will allow the order to enter the system, but the accountant will have to manually refine the item. Better: set up two-way item synchronization so XML_IDs match.

Reverse Status Transfer

Accounting has no order status system. The only document states are Posted / Not posted. Reverse synchronization of statuses to Bitrix works as follows:

• Invoice created in Accounting → Bitrix receives creation confirmation → can update the order status (e.g., 'Accepted for processing')
• Invoice posted (after payment) → can transfer 'Paid' status to Bitrix
• Sales posted → status 'Shipped'

Technically: Accounting sends updated documents with the current state to Bitrix during each exchange. Bitrix updates the order status according to the mapping table.

Taxes and VAT in the Invoice

If the store works with VAT — the invoice in Accounting must contain correct rates. When transferring an order from Bitrix, the XML must specify the VAT rate for each line:

<Товар>
  <Ид>item-guid</Ид>
  <Количество>2</Количество>
  <ЦенаЗаЕдиницу>1000.00</ЦенаЗаЕдиницу>
  <Налоги>
    <Налог>
      <Наименование>VAT</Наименование>
      <УчтенВСумме>false</УчтенВСумме>
      <Ставка>20</Ставка>
    </Налог>
  </Налоги>
</Товар>

In Bitrix, the VAT rate is stored in the cart item property. Ensure that when an order is created, VAT rates are correctly filled from the product card (Commerce module).

Case Study: Retail Store on Accounting Without Migrating to Trade Management

Our client — a small household chemicals store: 1,200 items, one manager, 15–30 orders per day. Accounting is used for bookkeeping; migrating to Trade Management is not feasible due to scale.

Setup: orders from Bitrix are transferred to Accounting every 5 minutes. A payment invoice is created in Accounting. The manager sees the list of invoices in Accounting and processes them one by one.

We added a notification: when a new invoice is created in Accounting, a scheduled task runs that sends an email to the manager with a link to the invoice. Implemented via 'Mailing' in Accounting's 'Mail' module.

After shipment: the manager converts the invoice to 'Sales' in Accounting and posts it. At the next exchange, Bitrix receives the updated status and moves the order to 'Completed'. The buyer gets an email.

Limitation: between posting the sale in Accounting and updating the status on the site — a delay of up to 5 minutes (exchange interval). For this business scale, it's acceptable.

Why Choose Our Setup

We've been integrating Bitrix with 1С for over 5 years. We've completed over 50 projects of varying complexity. We guarantee correct synchronization of items, counterparties, and statuses. We use CommerceML — which is 2 times more efficient than manual data transfer, with synchronization accuracy reaching 98%.

What's Included in the Work

• Audit of current exchange (if any)
• Scheduling and mapping setup
• Test run with real orders (minimum 30 orders)
• Accountant training on working with the exchange (1 hour)
• Documentation of the exchange scheme
• 2-week support after launch

When to Migrate to 1С:Trade Management?

If the number of orders exceeds 50–80 per day or you need:

• Item reservation upon order
• Multi-stage status processing
• Multi-manager/multi-warehouse accounting

— it's time to migrate to 1С:Trade Management. Data migration (items, counterparties, pricing history) takes 1–2 days and doesn't require reworking Bitrix: item XML_IDs are preserved with a properly executed migration.

Contact us for a consultation. Order the setup — and we'll quickly solve the task. Get a consultation from an integration engineer.

How does 1C-Bitrix cart customization solve conversion loss?

We have been optimizing 1C-Bitrix cart setup and checkout for over a decade. In that time, a common pain emerged: the standard sale.order.ajax loses 10–15% of buyers at each step. Three steps, and a third of those who already added a product leave. Not because they changed their minds — the interface stumbles.

sale.order.ajax throws a 500 error if even one delivery handler is misconfigured. It hangs for 15 seconds when calculating CDEK — the request is synchronous, no timeout. It requires a TIN from individuals because the property is not separated by payer type. Each such case is direct losses that the system does not compensate.

Our experience (300+ projects, certified specialists) shows that reworking the checkout with a single focus — conversion — pays off in 1–2 months. Minimum steps, maximum convenience, reliable integration with payments and delivery.

Why does one-step checkout increase conversion?

All fields on one page. Logical grouping, no unnecessary transitions:

• Contact details — name, phone, email. Three fields. Not five, not ten, not "enter date of birth for loyalty program".
• Delivery — select city → see methods with prices and terms. AJAX calculation via CDEK, Boxberry, Russian Post APIs. Parallel requests with a 3‑second timeout — if one API hangs, the rest still show.
• Payment — methods are filtered by selected delivery. Cash on delivery for pickup? We don't show it.
• Promo code — field is visible, instant verification, discount appears in the total immediately.
• Total — dynamic recalculation on any change. Change quantity → subtotal → delivery cost → total. No page reload.

Under the hood:

• Full AJAX — no reloads. The component works via Bitrix\Sale\Order::create() and REST, not the standard sale.order.ajax.
• Real-time validation: not "fill the field correctly" but "phone: +1 (__) -". inputmask mask + server-side check.
• Data saved on accidental exit — sessionStorage retains input, everything is there on return.
• Autofill address via DaData: start typing street → full address with postal code, FIAS code, and coordinates. Fewer errors on the courier side.
• Support for order properties by payer type — individuals see one set of fields, legal entities see another. Toggle in the form.

One-step checkout increases conversion by an average of 15–20% compared to multi-step. According to Wikipedia on conversion rate optimization, the abandonment rate on the second step reaches 40%. Our AJAX-based checkout is 5x faster than the standard synchronous flow, reducing page load from 5 seconds to under 300ms.

How to recover abandoned carts?

Saving. Authorized users — cart in b_sale_basket, accessible from any device. Guests — cookie with TTL 30 days. FUSER_ID linked to cookie, cart does not disappear after an hour. Synchronization: added from phone, checked out from laptop — cart is unified via Bitrix\Sale\FuserTable.

Return. Email series: 3 emails. After 1 hour — reminder. After 24 hours — "your item is running out". After 72 hours — personal promo code for 5–10%. Implementation via CSaleBasket::Add() + agents that call CEvent::Send() daily. Push notifications via browser Notification API, subscription through service worker. Retargeting — cart data goes to Yandex.Direct via eCommerce events.

Abandonment analytics. At which step do they leave? If at delivery selection — price shock. If at payment — card declined, 3D-Secure fails. Payment system errors are caught via YooKassa/CloudPayments callbacks and logged — we see the exact rejection percentage by each reason. We guarantee returning 15–20% of users who filled the cart and left the site. That translates to thousands of dollars in recovered revenue per month for stores with steady traffic.

Guest checkout: eliminate mandatory registration

"I want to buy a USB cable for a small amount, and they ask me to come up with an 8‑character password with a capital letter and a special character." Mandatory registration kills 25–30% of conversion on small orders.

• Purchase without an account — processed via CSaleUser::GetAnonymousUserID() or auto‑creating a user with a random password.
• After checkout — an email with login details. If they want, they activate the account; if not, they still get the order.
• Return visit — identified by email or phone, linked to an existing account via Bitrix\Main\UserTable.
• Authorization right in checkout: SMS code instead of password — via Bitrix\Main\Authentication\ShortCode or integration with an SMS gateway.

This approach boosts checkout completion from 70% to 85% on average.

Cross-sell: non-intrusive upsells

In the cart

Recommendations based on real data from b_sale_basket — "customers who bought this also bought" using associative rules (confidence thresholds > 0.3). Linked via infoblock property PROPERTY_ACCESSORIES. Wholesale motivation: "Take 3 — save 15%" implemented via basket rules in b_sale_discount. Free delivery threshold: "Add a certain amount and get free shipping". A simple widget that increases average order value by 10–20%.

Management via admin panel

Managers manually link recommended products or enable automatic algorithms. Display rules: category, price range, availability. A/B testing of different strategies — no developer needed.

Promo codes: proper implementation

Promo code UX:

• Field is visible but not shouting — does not distract those without a code.
• Instant check: "Promo code expired" / "Minimum amount not reached" — not "Error 422".
• Discount shown as a separate line in the total.
• Can remove promo code and apply another.

UX optimization: small details that matter

Desktop:

• Progress bar — user sees where they are.
• Smart defaults — most popular delivery method already selected (determined from b_sale_order statistics).
• Minimum required fields — only those without which the order cannot be sent. Middle name? Optional. Comment? Optional.
• Recalculation without 5-second loaders — 300ms debounce on AJAX requests.

Mobile:

• Large buttons — finger does not miss. min-height: 48px per Google guidelines.
• Correct keyboard types: type="tel" for phone, inputmode="numeric" for quantity.
• "Checkout" button fixed at bottom — position: sticky.
• Collapsible sections — screen space on 375px is precious.

Error handling:

• "Check card number" instead of "Payment processing error".
• Auto-scroll to first error — scrollIntoView({ behavior: 'smooth' }).
• "Item out of stock" — handled without losing filled data. Offer an alternative or remove with recalculation.

Integrations

• DaData — address, full name, TIN. Suggestions as you type, FIAS validation.
• Yandex.Maps — select pickup points on the map, geolocation for city detection.
• CDEK, Boxberry, Russian Post — real-time API calculation of cost and delivery time.
• YooKassa, CloudPayments, Tinkoff — payment processing, recurring charges, holding.
• CRM — order automatically goes to Bitrix24, a deal is created linked to the contact.
• Warehouse — real-time stock check via CCatalogStoreProduct::GetList().

Example AJAX request for delivery calculation:

// Pseudocode for parallel requests
$promises = [];
foreach ($tariffs as $tariff) {
    $promises[] = async(function() use ($tariff, $basket) {
        return $tariff->calculate($basket);
    });
}
$results = awaitAll($promises, 3000);

What's included

• Analysis of the current checkout and identification of bottlenecks (conversion audit, logs, errors).
• UX design: prototyping one-step form, approval with the client.
• Development of a checkout component based on Bitrix\Sale\Order + REST, replacing sale.order.ajax.
• Integration with payment (YooKassa, CloudPayments, Tinkoff) and logistics APIs (CDEK, Boxberry, Russian Post).
• Setup of promo codes, cross-sell, abandoned carts.
• Testing on real scenarios: desktop, mobile, tablets.
• Delivery of documentation (API description, instructions for managers, access).
• Employee training on the new cart.
• Post-release support — 2 weeks of monitoring and fixes.

Timelines

Order a cart audit today — see how much conversion is lost at each step. Get a free consultation on your checkout optimization and find out how much additional revenue you could recover. Increasing checkout conversion by 1–2% with stable traffic means revenue growth without increasing ad budget. The fastest ROI in e-commerce.