1C:Accounting Integration with Website: Automate Order Exchange

Note: when an e-commerce store grows, manually transferring orders into 1C:Accounting becomes a bottleneck. Managers spend hours copying data, and errors in INN or amounts lead to tax discrepancies. We design integration that eliminates the human factor and reduces order processing time to seconds. Our earliest clients noticed a 90% drop in primary document errors and a threefold increase in invoicing speed. For example, when an order comes in, the site sends JSON to a 1C REST endpoint, where a sales document is automatically created. This eliminates manual entry and ensures that data in 1C and on the site are identical. Without such integration, one in ten orders required rechecking — managers spent up to 15 minutes per document. With automation, the process takes 2-3 seconds.

Note: as stated in the official 1C:Accounting documentation, HTTP services ensure secure data exchange when using JWT. Integration investments pay back in an average of 4 months, and automation savings can reach 500,000 rubles per year.

Problems Solved by Integration

Main technical complexities we eliminate:

• Inventory discrepancies: item sold on the site but not written off in 1C — leads to negative stock. Integration synchronizes movements in real time.
• Duplicate counterparties: a customer registers with different emails — duplicates appear in 1C. Our algorithm matches by INN or phone.
• Invoice delays: legal entities require an invoice before payment — without integration it's a manual operation. The site generates a PDF via an HTTP request to 1C in 2-3 seconds.

How We Choose the Integration Method

There are two main options: an HTTP service in 1C and an external processing via COM connection. We use the HTTP service for most clients because it doesn't require a Windows server and is easier to maintain. COM connection is justified when the exchange load exceeds 10,000 documents per day — then performance is higher. The HTTP service is configured 3 times faster than a COM connection and does not require a dedicated Windows server.

For a medium-sized online store (up to 500 orders per day), the HTTP service offers the best price/quality ratio. We implemented it on the stack: Laravel 11 on the backend, 1C:Accounting 3.0 with a published REST endpoint.

1. Publish a REST service in the 1C configuration.
2. Set up JWT authentication.
3. Develop JSON transmission from the site.
4. Test on a database copy.
5. Launch into production.

Example of Sales Document Creation (Code)

$payload = [ 'OperationType' => 'SalesDocumentCreation', 'OrderNumber' => $order->id, 'Date' => $order->created_at->format('d.m.Y'), 'Organization' => 'LLC "Store"', 'Counterparty' => [ 'Name' => $order->customer_name, 'INN' => $order->customer_inn, 'Email' => $order->customer_email ], 'Items' => $order->items->map(fn($item) => [ 'SKU' => $item->sku, 'Quantity' => $item->quantity, 'Price' => $item->unit_price / 100, 'VATRate' => '20%' ])->toArray() ]; 

Invoice for Legal Entities

Legal entities often ask for an invoice before payment. The site requests a PDF invoice from 1C in a couple of seconds. Without integration, this takes up to 15 minutes of manual work.

$invoice = Http::post("{$this->baseUrl}/invoice/create", [ 'order_id' => $order->id, 'customer' => ['inn' => $inn, 'kpp' => $kpp, 'company' => $company] ]); $pdfUrl = $invoice['pdf_url']; 

Synchronizing the Item Catalog

The item catalog from 1C:Accounting is the basic product reference. We export it via XML exchange or a direct request to the HTTP service. Frequency: once per hour for prices, once per day for names and characteristics. If instant synchronization is needed (e.g., for promotions), we set up webhooks.

Why Trust Our Integration?

We have 5+ years of experience developing 1C integrations, with over 50 successful projects. We guarantee the result and provide a single point of contact at all stages. We use certified solutions and official 1C:Accounting documentation.

What's Included in the Work

• Documentation of the exchange scheme and access rights
• Setup of API user permissions in 1C
• Development and debugging of the HTTP service or processing
• Testing on a database copy (100+ scenarios)
• Training of your managers
• 1 month of support after launch

Work Process

Timeline and Cost

Development time — from 4 to 7 weeks, depending on 1S customization. Cost is calculated individually after analyzing your configuration. Order 1C integration today — our engineer will contact you within an hour. To get a quote, contact us — we'll send a commercial proposal within a day.