What Is 1C EDI and How It Helps Businesses Automate Document Flow, Speed Up Deals, and Avoid Errors

How 1C-EDO speeds up the exchange of legally binding documents, helps avoid errors and suits trade, logistics and manufacturing.

  • What is 1C-EDO
  • Which documents can be sent
  • How document exchange works
  • Comparing ways to use EDI in 1C

Main text

  1. 1C-EDI lets you receive, sign, and send electronic documents from a supported 1C application.

  2. The accountant works with the accounting document and its status in one interface; the operator delivers the legally significant electronic document to the counterparty.

  3. Getting started requires a compatible release, an EDI account, a signature, and configured exchange.

  4. Below: how the service differs from 1C:Document Management and operator modules, the cost of outgoing traffic, changes by September 2026, and how to test exchange before connecting all counterparties.

What is 1C-EDO

1C-EDI is an electronic document exchange technology and service built into supported 1C configurations.

Compatibility is checked by configuration name, edition, and release: having the 1C:Enterprise platform is not sufficient.

For a nonstandard program, determine the connection method and scope of custom development in advance.

For registration in 1C-EDI, the following were available as of the verification date

Kaluga Astral, Taxcom, Link-Service, and GPB ETP.

This is a list of registration operators, not all possible recipients: counterparties using

Diadoc or Saby can exchange documents through roaming. A dedicated module

Diadoc or Saby in 1C is another way to organize the workplace

1C:Document Management handles approvals, assignments, and internal processes. 1C-EDI provides external exchange with counterparties.

They can be linked: the document is approved first, then signed and sent.

An electronic signature does not verify the business substance of a transaction: the company checks the signer's authorization, required details, and consistency with the actual delivery.

Which documents can be sent

  1. EDI is used to transmit structured documents with a prescribed format and unstructured files: contracts, addenda, letters, and reconciliation statements.

  2. The ability to create an accounting document automatically depends on the format, mapping settings, and features of your configuration. As of January 1, 2026, the previous XML formats for electronic waybills and acts under Federal Tax Service Orders No. 551 and No. 552 have been discontinued.

  3. For the formalized transfer of goods, work, and services, use UPD 5.03 under Order No. ED-7-26/970@.

  4. Cancelling these formats does not by itself prohibit paper or informal primary documents; special labeling and transportation requirements are checked separately. A universal transfer document may serve as a primary document or combine this function with an invoice. Test exchange verifies the document function, VAT, party details, and the ability to make corrections.

  5. For labeled goods, they also verify the information required specifically for the relevant product group.

How document exchange works

StepActionResults control
PreparationCreate an accounting document and an electronic documentThe counterparty, contract, items, and amounts have been matched
SigningCheck and sign the documentCertificate valid, authorization confirmed
SendingSend the document to the operatorIdentifier and sending status received
AcceptanceThe counterparty verifies the delivery and signs or rejects the documentDiscrepancies resolved before being recorded in accounting
PostingLink the electronic document to a 1C objectNo duplicate document was created; signatures and statuses were preserved

For an employee signing for an organization under a power of attorney, verify their personal QES and MChD. A manager acting without a power of attorney is a separate scenario: not every signatory needs an MChD. Check the validity period, revocation, and scope of authority; they must not be ignored to speed up exchange. The statuses "sent," "delivered," "signed," and "recorded in accounting" represent different events. Period closing should rely on the required business status, not merely successful transmission to the operator.

Comparing ways to use EDI in 1C

Criterion1C EDIDiadoc moduleSaby / SBIS module
ConnectionBuilt-in service in a supported configurationA module or extension with its own compatibility matrixProcessing or extension for a supported configuration
AutomationCreating, signing, and recording documents according to 1C settingsDocument exchange and processing from 1C within the module versionDocument exchange and processing from 1C within the selected solution
Counterparties using another operatorExchange through a supported roaming pairExchange through a supported roaming pairExchange through a supported roaming pair
What is included in the budgetOutgoing document packages, signing, configuration, and supportDocument packages, module or API license, and configurationService plan, packages, and integration terms
What to check before choosing1C release, registration operator, actual document typesModule version and cloud or on-premises 1C modeProcessing type, permissions, and specialized environments

All three options provide automation. The choice depends on your document workflow: document types, 1C configurations, counterparties, and approval processes. Detailed API and specialized environment terms are collected in comparison of Diadoc, SBIS, Taxcom, and Astral; module versions are listed in review of Diadoc for 1C.

Map out your integration landscape

1C EDI costs and plans

Under 1C rates as of September 12, 2026, outgoing traffic costs 2 to 10 rubles per package, depending on volume and payment method. Registration, incoming documents, invitations, and roaming itself are free.

Free roaming does not mean that sending documents beyond the included limit is free.

Without benefits, up to 5 outgoing document packages are available monthly.

1C ITS PROF, ITS TECHNO, and StartEDI include 100, 50, and 20 document packages respectively.

An ITS contract is not a mandatory requirement for using 1C EDI.

A package is calculated according to the service rules and is not an arbitrary set of files: use the 1C pricing calculator before selecting a plan.

The implementation budget is calculated separately from document traffic

It includes 1C preparation and updates, signature issuance and setup, counterparty onboarding, item master mapping, approval workflows, and exception handling.

There is no universal price or launch timeline for a standard database and a customized holding environment.

How to connect the service: a step-by-step guide

Confirm the 1C configuration, edition, and release; check support for EDI and your document formats. First update the test database and verify customizations.

Choose a registration operator and prepare the organization's account

Confirm department details and the identifiers of existing mailboxes to avoid creating unnecessary ones.

Configure the electronic signature, cryptographic provider, and user permissions. For representatives, prepare a machine-readable power of attorney and verify authority for the required operations.

Invite several actual counterparties

Include your operator's recipient and the counterparty in roaming in the pilot if this type of exchange is needed.

Configure counterparty and item master matching, incoming document retrieval, and accounting posting rules. An incoming document may be signed automatically only after the checks required by the company.

Run through the full cycle: sending, receipt, discrepancy, correction or cancellation, and retry after a failure. Compare the electronic document with the accounting record and actual delivery.

Assign an owner for unsigned and rejected documents

Document the escalation procedure for the operator and the person responsible for 1C; response times are defined by your support agreement. KT.Team configures EDI in 1C to the company's workflows: documents and statuses remain linked to accounting objects, while errors are visible to responsible employees in one log.

Industry scenarios and requirements for 2026

WorkflowWhat to check in the exchangeWhere separate configuration is required
Retail and distributionUniversal transfer document, actual receipt, codes or GTIN, and quantityProduct group and labeling stage, cash register, and GIS MT
ManufacturingMaterials, services, contracts, and departmentsItem master matching, approval, and rejections
ConstructionCompletion documents, volumes, contract, and work stageDocument forms, completeness, and receipt workflow
LogisticsTransport document and participant statusesSeparate electronic transport document environment and information-system operator

For labeling, the information set to be transmitted depends on the product group and the start date of the relevant stage. UPD acceptance and retail withdrawal through the cash register are different operations. Their relationship is explained in Chestny Znak and 1C instructions. From September 1, 2026, electronic transport documents become mandatory in cases specified by law. The Ministry of Transport separately lists exceptions allowing paper documents and announces a penalty-free period until March 1, 2027.

This period does not remove the obligation to switch. A standard EDI account for UPDs does not replace connecting to GIS EPD through an EPD information system operator.

How to evaluate the results of the integration

  1. Before the pilot, select the same set of documents and measure processing time, the share of manual entry, the number of discrepancies, and the delay before signing.

  2. After launch, repeat the measurement on a comparable workflow.

  3. Account separately for verification and correction time: automatic file upload does not yet mean that the operation is complete.

  4. The management outcome is documents signed and recorded in accounting on time. The log should show unsigned incoming documents, rejected outgoing documents, matching errors, and expired authorizations.

  5. Each queue needs an owner and a review deadline agreed with accounting and operations.

FAQ

Frequently asked questions about 1C EDI

### Does the service work with any 1C version?

Support depends on the configuration, edition, and release. For a customized database, the connection method must be checked separately; having the 1C platform alone does not guarantee compatibility.

### Can I exchange documents with a counterparty using Diadoc or Saby?

Yes, if the corresponding roaming pair is supported. Set up the invitation and test the exchange of your document types. The counterparty does not always need to change operators.

### Is an electronic signature enough to get started?

You also need compatible software, registration, cryptographic settings, permissions, and exchange with counterparties. A representative additionally requires verification of the machine-readable power of attorney.

### Do I need to purchase 1C ITS for EDI?

No. ITS and StartEDI provide preferential limits; the current package terms and outgoing volume determine the payment calculation.

### Can manual review of all documents be disabled?

Checks are defined by the process. First agree on permitted operations and exceptions: delivery, details, or authorization discrepancies must reach the responsible employee before signing.

### How can documents be preserved when changing operators?

Before switching, verify the export of originals, signatures, and service confirmations, their links to accounting documents, and subsequent signature validation. A PDF export does not replace a complete electronic archive.

Sources

Verification date: 12 September 2026

Discuss the article: What is 1C-EDO and how it helps…

Enter your email or phone number so we can get back to you.

Send via: