1C Accounting Integration with Website

Our company is engaged in the development, support and maintenance of sites of any complexity. From simple one-page sites to large-scale cluster systems built on micro services. Experience of developers is confirmed by certificates from vendors.
Development and maintenance of all types of websites:
Informational websites or web applications
Business card websites, landing pages, corporate websites, online catalogs, quizzes, promo websites, blogs, news resources, informational portals, forums, aggregators
E-commerce websites or web applications
Online stores, B2B portals, marketplaces, online exchanges, cashback websites, exchanges, dropshipping platforms, product parsers
Business process management web applications
CRM systems, ERP systems, corporate portals, production management systems, information parsers
Electronic service websites or web applications
Classified ads platforms, online schools, online cinemas, website builders, portals for electronic services, video hosting platforms, thematic portals

These are just some of the technical types of websites we work with, and each of them can have its own specific features and functionality, as well as be customized to meet the specific needs and goals of the client.

Our competencies:
Development stages
Latest works
  • image_web-applications_feedme_466_0.webp
    Development of a web application for FEEDME
    1161
  • image_ecommerce_furnoro_435_0.webp
    Development of an online store for the company FURNORO
    1041
  • image_crm_enviok_479_0.webp
    Development of a web application for Enviok
    822
  • image_crm_chasseurs_493_0.webp
    CRM development for Chasseurs
    847
  • image_website-sbh_0.png
    Website development for SBH Partners
    999
  • image_website-_0.png
    Website development for Red Pear
    451

1C:Accounting Integration with Website

1C:Accounting is an accounting system for maintaining accounting and tax records. Integration with a website allows automatic generation of primary documents (invoices, shipping bills, acts) from online store orders and transmission of payment data.

Key Integration Tasks

  • Order transmission → creation of sales and invoices in 1C
  • Payment synchronization: money received on website → cash receipt in 1C
  • Nomenclature export: product directory from 1C → website catalog
  • Counterparty synchronization: website buyers → 1C clients

Technical Connection Options

HTTP Service in 1C:Accounting — an HTTP request handler is created in the configuration. A REST endpoint is published through the 1C web server. The website accesses it with JWT authorization.

External Handlers and COM Connection — a 1C agent on the same server as 1C interacts through COM object COMConnector. More performant but requires Windows server.

Creating Product Sales

// Structure of a request to 1C HTTP service
$payload = [
    'OperationType' => 'SalesCreation',
    'OrderNumber'   => $order->id,
    'Date'          => $order->created_at->format('d.m.Y'),
    'Organization'  => 'OOO "Shop"',
    'Counterparty'  => [
        'Name'  => $order->customer_name,
        'TIN'   => $order->customer_inn,
        'Email' => $order->customer_email
    ],
    'Goods' => $order->items->map(fn($item) => [
        'Article'   => $item->sku,
        'Quantity'  => $item->quantity,
        'Price'     => $item->unit_price / 100,
        'VATRate'   => '20%'
    ])->toArray()
];

Invoice for Legal Entities

Legal entities often request an invoice before payment. The website requests a PDF invoice from 1C:

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

$pdfUrl = $invoice['pdf_url'];
// Save link, send to buyer

Nomenclature Directory Synchronization

Nomenclature from 1C:Accounting is a basic product directory. Exported via XML exchange or direct HTTP service request. Frequency: every hour for prices, daily for names and characteristics.

Configuration Features

1C:Accounting exists in several editions (2.0, 3.0) and can be significantly customized. Before starting integration, you must obtain from the client:

  • 1C platform version and configuration edition
  • Schema of used objects (which directories and documents are involved)
  • API user rights for reading/writing needed objects

Development Timeline: 4–7 weeks depending on 1C configuration complexity and data volume.