1C-Bitrix with Taxcom EDO: Streamline Your Document Workflow

Integrate 1C-Bitrix with Taxcom EDO System

Imagine: 150 orders per day, each requiring its own UPD. A manager prepares the document in 1C, then manually uploads it to the Taxcom personal account — spending 15–20 minutes. Result: 40 hours per week on routine. Errors in details lead to rejections in 12% of cases, and counterparties delay signing by an average of 4 days. The situation worsens if the client has specific document requirements (medical goods with serials and expiration dates).

We have specialized in Bitrix for over 10 years and have completed 30+ EDO integration projects. Our standard implementation is automatic UPD sending from Bitrix via the Taxcom operator without manager involvement: signing status is tracked in the admin panel. This approach reduces order processing time by 80% and eliminates manual entry errors. At 100 orders per month, savings reach 350,000 rubles per year. For a B2B construction materials supplier, the implementation reduced document processing costs by 1.2 million rubles annually.

Common Problems Companies Face

• Manual document export. The manager creates a UPD in 1C, then uploads it to the Taxcom personal account — 15–20 minutes per order. At 50 orders per day, that's 12–17 hours of pure routine.
• No link to order statuses. The document is not sent automatically upon shipment — it may be forgotten or delayed.
• Difficulties with counterparties. Finding a new counterparty's BoxId takes time, and errors in details lead to document rejection.
• Incomplete document package. For medical goods, acts with serials and expiration dates are needed — the standard UPD does not contain them.

Our experience shows that 90% of these problems are solved by a proper integration of Bitrix with Taxcom via REST API. Get a consultation on your project.

How Taxcom Integration with Bitrix Works

Authentication is done via OAuth 2.0 Client Credentials. We cache the token for 3500 seconds (slightly less than its lifetime) to avoid hitting the API on every request:

class TaxcomClient
{
    private string $baseUrl = 'https://edo.taxcom.ru/api/v1';
    private string $accessToken;

    public function __construct(
        private string $clientId,
        private string $clientSecret
    ) {
        $this->accessToken = $this->getAccessToken();
    }

    private function getAccessToken(): string
    {
        $cached = \Bitrix\Main\Data\Cache::createInstance();
        if ($cached->startDataCache(3500, 'taxcom_token', '/taxcom/')) {
            $response = $this->httpPost('https://auth.taxcom.ru/oauth/token', [
                'grant_type'    => 'client_credentials',
                'client_id'     => $this->clientId,
                'client_secret' => $this->clientSecret,
                'scope'         => 'edo',
            ]);
            $cached->endDataCache(['token' => $response['access_token']]);
            return $response['access_token'];
        }
        $data = $cached->getVars();
        return $data['token'];
    }
}

Creating and Sending a Document

After obtaining the token, we generate the document XML and send it in three steps: file upload, signing, message sending:

public function sendDocument(\Bitrix\Sale\Order $order): array
{
    $xmlContent = $this->generateUPDXml($order);

    // Step 1: upload file
    $uploadResponse = $this->apiPost('/documents/upload', [
        'FileName'    => "UPD_{$order->getId()}.xml",
        'Content'     => base64_encode($xmlContent),
        'ContentType' => 'application/xml',
    ]);

    $fileId = $uploadResponse['FileId'];

    // Step 2: signing (CryptoPro or Taxcom cloud signature)
    $signature = $this->signFile($xmlContent);

    // Step 3: send document
    return $this->apiPost('/messages/send', [
        'RecipientBoxId' => $this->getRecipientBoxId($order),
        'Documents' => [[
            'FileId'    => $fileId,
            'Signature' => base64_encode($signature),
            'DocType'   => 'UniversalTransferDocument',
            'Function'  => 'ДОП',
        ]],
    ]);
}

Taxcom supports a cloud signature via the "Taxcom-Crypto" service — the certificate is stored on Taxcom's side, and signing is done through the API without requiring CryptoPro on the server. This simplifies infrastructure and reduces costs compared to purchasing a separate license key.

Finding a Counterparty's BoxId

On first contact with a new counterparty, the system searches for their BoxId by INN/KPP:

public function findRecipientBoxId(string $inn, string $kpp = ''): ?string
{
    $response = $this->apiGet('/organizations/search', [
        'inn' => $inn,
        'kpp' => $kpp,
    ]);

    foreach ($response['Organizations'] as $org) {
        if ($org['Inn'] === $inn && ($kpp === '' || $org['Kpp'] === $kpp)) {
            return $org['BoxId'];
        }
    }
    return null;
}

The found identifier is saved in the buyer's user field (UF_TAXCOM_BOX_ID) — subsequent sends proceed without further queries.

Why Choose Cloud Signature?

Taxcom cloud signature is an alternative to purchasing and setting up CryptoPro. Key differences:

Cloud signature is 40–60% cheaper than the classic one due to no licenses and maintenance.

Case Study: EDO for a Medical Distributor (from our practice)

A medical consumables distributor, ~400 B2B clients, working with government hospitals and private clinics. Government institutions often have their own EDO operators with roaming, some work directly with Taxcom.

Peculiarity: besides UPD, medical goods require acceptance acts with extended requisites (serial, expiration date, registration certificate). The standard UPD format does not cover all fields.

Solution:

We developed a composite document: UPD + annex with extended medical requisites as an additional XML file in the same Taxcom message. Both files are signed with one signature.

$documents = [
    [
        'FileId'    => $updFileId,
        'Signature' => base64_encode($updSignature),
        'DocType'   => 'UniversalTransferDocument',
    ],
    [
        'FileId'    => $annexFileId,
        'Signature' => base64_encode($annexSignature),
        'DocType'   => 'Attachment',  // supplement to main document
        'Comment'   => 'Medical product requisites',
    ],
];

In Bitrix, product requisites (serial, expiration date) are stored as order item properties. When generating XML, they are extracted from \Bitrix\Sale\BasketItem::getPropertyCollection().

Savings for the client amounted to 1.2 million rubles per year due to reduced manual labor and late document penalties.

Monitoring Document Queue

For document flow control — an admin section in Bitrix with a table of sent documents:

• Order → Taxcom Document → Status → Signing Date

Data is taken from the local_taxcom_documents table + periodic polling of the Taxcom API to update statuses (cron every 10 minutes).

What's Included in the Work

1. Taxcom account setup — obtaining Client ID/Secret, cloud signature (if required).
2. PHP client development — class for REST API interaction, token caching, error handling.
3. XML generation — creating UPD, acts, composite documents based on order data.
4. Counterparty directory — loading BoxId, saving in Bitrix user field.
5. Event-driven sending — binding to order statuses: shipment → automatic sending.
6. Status monitoring — admin panel with table, error notifications, auto-update.
7. Documentation and training — code handover, manager instructions, launch consultation.

Timelines and How to Start

Basic integration (UPD, cloud signature, monitoring) takes 3 to 5 weeks. Extended integration with composite documents and specific formats takes 6 to 9 weeks. Cost is calculated individually after analyzing your document flow. We will assess your project within 2 business days — contact us for a consultation and accurate estimate. Order a test run on one document type.

CommerceML: Why Standard Exchange Is Both a Lifesaver and a Trap

Standard exchange via CommerceML 2.0 on typical "Trade Management" or "Comprehensive Automation" can be set up in a day or two. Products, prices, stock, orders—all via XML files on a schedule. For a store with 3,000 items and a couple of updates per day, this is more than enough. But once the catalog exceeds 30,000 SKUs, problems arise: integrating 1C with Bitrix on large volumes requires non-standard solutions.

Why does CommerceML slow down with catalogs over 100,000 items?

bitrix_1c_exchange.php generates XML on the Bitrix side, and 1C retrieves and parses it. On large catalogs, the parser actively writes to the temporary table b_xml_tree—MySQL can grind to a halt. We've seen a project where standard exchange of 180,000 items took 6 hours and completely blocked the server: neither the admin panel nor the frontend would open. The solution is incremental exchange. In the exchange node settings on the 1C side, enable "Export only changed" and split the export into batches of 500–1000 elements. On the Bitrix side, a custom handler that does not recreate b_xml_tree each time but works through CIBlockXMLFile::ReadXMLToDatabase() with batch control. A catalog of 200,000 SKUs updates in 8–12 minutes.

Another pitfall is EXTERNAL_ID. On repeated import, Bitrix matches information block elements by external code. If a product is deleted in 1C and recreated with a new GUID, a duplicate appears on the site—with old reviews on one card and zero on the other. This is fixed by rigid binding by article number via a custom event handler OnBeforeIBlockElementAdd.

How to avoid duplicates during repeated import?

We bind products not by GUID but by article number. Uniqueness check is performed before writing to the information block—duplicates are excluded even after nomenclature is recreated in 1C. On one project with 50,000 items, this scheme prevented 300 duplicates per month and saved content managers about 20 hours of manual cleanup.

Custom 1C Configurations: When CommerceML Falls Short

"We have a standard configuration"—says every second client, and then we open the database and see 200 custom processing routines, renamed attributes, and custom sales documents. CommerceML works with a fixed XML structure. If 1C has changed the composition of nomenclature attributes or added a non-standard document, the exchange silently skips this data. Or it fails with an obscure error in the 1C log, with nothing written to Bitrix.

In such cases, we implement custom export. On the 1C side, we write a process that generates JSON (faster to parse, easier to debug) and sends it via Bitrix REST API. Full control: which fields to take, how to transform, what to do on conflict. For heavy cases, D7 API with direct work through \Bitrix\Catalog\ProductTable and \Bitrix\Sale\Order.

What are the key steps to set up 1C integration?

Custom REST is justified when:

• Non-standard nomenclature attributes;
• Multiple price types (retail, wholesale, dealer, promotional, regional, currency)—standard exchange sends only one type;
• Multi-warehouse with different stock levels and need to select a warehouse on the site.

Prices, Stock, and Multi-Warehouse

Standard exchange can transfer one price type. In reality, there may be 15: each with its own buyer group and priority. Mapping between 1C price groups and Bitrix user groups is a separate engineering challenge. Especially when discounts overlap and you need to determine which price wins.

Multi-warehouse adds another layer: product is in stock in Moscow, out of stock in St. Petersburg, and "on order" in Novosibirsk. The site must show availability per location, allow selection of pickup points, and calculate shipping from the nearest warehouse where the product is physically available. The standard Bitrix warehouse module (catalog.store) handles display, but we write the "which warehouse to ship from" logic separately. For one manufacturing holding, we implemented a custom stock aggregator that calculated balance across 8 warehouses in 2 seconds—reducing shipping errors by 80%.

Orders and Document Flow

An order from the site goes to 1C, a sales document is created, goods are reserved. Statuses come back. The main nuance is partial shipment: the client ordered 5 items, 3 are in stock, 2 will arrive in a week. 1C creates two sales documents. Bitrix out of the box cannot split one order into several shipments—we extend the OnSaleOrderSaved handler to create child orders and synchronize statuses for each.

Documents in the personal account—invoices, acts, waybills from 1C—are served via REST; PDF is generated on the 1C side and cached on CDN. The buyer downloads not from 1C directly (that would kill the server) but from cache.

Batch import with portion control reduces MySQL load and prevents locks (source: Wikipedia).

Monitoring: Not "Set and Forget"

Exchange can silently break: the script ran, no errors in log, but 200 products didn't update due to invalid UTF-8 in the name. Or 1C changed the date format in an update—all prices came in as zero.

Minimum set we install on every project:

• Telegram alert if exchange time increases 3+ times from average.
• Stock discrepancy check: script compares b_catalog_product.QUANTITY with what 1C provides, and alerts when delta exceeds 5%.
• Dashboard: last sync, number of processed items, queue, errors.

For high-load projects, we add async queues on Redis or RabbitMQ. Exchange does not block the web server, data is not lost during temporary 1C outages. On one online store with 2 million orders per year, we implemented this scheme—recovery time after failures dropped from 3 hours to 10 minutes.

Linking with Bitrix24 for Document Flow Automation

If besides the site there is a corporate portal on Bitrix24, we link it too. Counterparties from CRM go to 1C, invoices from 1C appear in deal cards. The manager sees accounts receivable and mutual settlements without switching windows. Deal closed—documents generated automatically.

Payment received in 1C → logistician gets a task for shipment in Bitrix24. Goods shipped → manager sees notification. Automatic tasks based on events from 1C—via Bitrix24 REST API webhooks. This link reduces manual entry by 70% and eliminates forgotten shipments.

How We Set Up Integration: Step-by-Step Process

1. Audit of 1C Configuration. Review the structure of directories, documents, attributes. Identify custom modifications. Assess data volume (number of SKUs, orders, warehouses).
2. Design Exchange Schema. Agree on data set: products, prices, stock, orders, documents. Determine sync interval and mechanism—CommerceML or custom REST.
3. Configure Standard Exchange. Set up CommerceML, batch mode, binding by article. Verify data transfer correctness on a test catalog.
4. Extended Integration. For complex configurations, write custom handlers on both 1C and Bitrix sides. Incorporate multi-warehouse, multiple prices, partial shipment.
5. Monitoring and Warranty. Set up alerts, dashboard, documentation. Train operators. After launch, warranty support.

Timelines and What's Included

Work results include: documented exchange schema, configured synchronization scenarios, monitoring dashboard, operator training, and warranty support after launch. Pricing is calculated individually—it depends on the complexity of the 1C configuration, catalog size, and required automation level. We'll evaluate your project in 1 day—write to us, let's discuss. Order integration and get stable exchange in 1–2 weeks.

We have completed over 50 1C integrations for online stores and manufacturing companies. The team's average experience is 7 years, and we have certified 1C-Bitrix specialists. Our experience ensures that the exchange won't break in the first month and will run stably for years. For example, on a project with a catalog of 50,000 items, automation of exchange saved the client significant operational costs annually.

Contact us for a free audit of your 1C configuration—we'll find bottlenecks and offer the optimal solution.