1C EDI and Exchange of Legally Binding Documents

1C EDI must be built into the accounting process so documents do not get lost between the operator, accounting, warehouse, and sales.

The EDI module works inside standard 1C configurations, so there is no need to implement a separate system and employees stay in a familiar interface. The exception is the 1C web version and 1C:Fresh: the standard module is not supported there, so you need the EDI Client from 1C or integration via API. Pricing is receiver-friendly: incoming documents are free, and only outgoing sets are paid for (a set can include up to three documents, for example an invoice with a delivery note and an order).

What to check before setup:

• an active 1C:ITS subscription - the PROF and TECHNO tiers already include 100 and 50 outgoing sets per month;
• Personal qualified e-signature for each authorized employee and machine-readable power of attorney (POA)—as of September 1, 2024, employee certificates of legal entities are no longer valid; only the director can sign without a POA;
• the current configuration release (for example, Enterprise Accounting from 3.0.88, Trade Management from 11.4.13);
• roaming for counterparties on other operators - with Kontur.Diadoc, SBIS, and OFD.ru it connects automatically, without separate agreements;
• a pilot with 5-10 key counterparties and a test exchange before full rollout.

An employee signs organization documents with a personal qualified e-signature linked to a machine-readable power of attorney. For counterparty exchange, the POA is issued in unified format 003 and registered in the Federal Tax Service distributed registry—one POA works with any EDI provider. In 1C, POAs are managed in the 'Machine-readable Powers of Attorney' journal (EDI module from version 1.9.6): the 'Sign and Register' command sends the POA to the FTS registry, after which the employee's certificate is registered with the EDI provider.

As of February 1, 2026, new POAs must include SNILS, INN, date of birth of the representative, term of validity and description of powers (Ministry of Digital Development Order No. 1001 dated November 5, 2025); previously issued POAs remain valid until the end of their term.

EDI operators, exchange of UTDs, invoices, acts, delivery notes, signing statuses, approval workflows, and document storage linked to 1C. Setup is performed directly in 1C: in the Administration section -> Electronic Document Exchange, the registration is signed with an electronic signature, and the system assigns an EDI participant ID. Invitations to counterparties are sent directly from the Counterparties directory, and documents are stored in the 1C database by default.

• EDI operators and automatic roaming with counterparties on other operators.
• Exchange of UTDs, invoices, acceptance acts, and delivery notes with automatic generation of incoming document sets in 1C.
• Signing statuses and approval workflows within the accounting environment.
• Transfer of data from delivery notes into warehouse documents without re-entering it during receiving and shipping.
• For retail - a synchronization module with the fiscal data operator: loading fiscal documents from cash registers and matching receipt items with the 1C item master.
• Integration via API for custom configurations and third-party accounting systems.

We configure handling for rejections, duplicates, incorrect details, status mismatches, and cases where a document left the operator but did not appear in the accounting system. The goal is for every error to be caught before signing, not during reconciliation at the end of the quarter.

• A UTD with discrepancies (quantity, details, missing marking codes) is not signed - a discrepancy report is issued in EDI.
• Resending a document with the same number and date produces an error - instead of a duplicate, a corrective UCD is created.
• Incorrect details are filtered out by automatic validation when the document set is formed.
• Late signing of incoming documents is controlled through reminders and monitoring in 1C so documents do not get stuck with the operator.
• Status mismatches between the operator and 1C are visible in the exchange log, making it clear which document to resend and how to avoid creating duplicates.

Accounting and operations teams work with clear document statuses, with fewer manual reconciliations and less risk of missing a legally binding exchange. Electronic document flow cuts direct costs for paper, delivery, and storage by 40-60% and shortens document exchange from days to minutes. In our project for a metal trading company, integrating the EDI module into 1C:Trade Management took 3 months and delivered measurable results:

• shipment document set processing sped up from 3 days to 4 hours;
• 85% of document flow has been moved to electronic format, with more than 15,000 documents processed each month;
• more than 200 counterparties connected, including 40% that worked through other operators (roaming);
• errors in details dropped by 95% thanks to automatic validation;
• savings of 1.2 million rubles per year on paper, courier delivery, and manual processing.