Diadoc Module for 1C in 2026: Versions, UPD 5.03, MChD

Key point

In brief: what to check in the integration for September 2026

Update the module together with the 1C configuration. The 4.59+ recommendation refers to Kontur’s November 2025 announcement; it does not promise support for all September 2026 requirements in every higher-numbered build.
As of January 1, 2026, the previous XML formats for electronic TORG-12 and acts have been cancelled. Use UTD 5.03 for formalized data exchange; cancelling the formats does not by itself prohibit paper acts and waybills.
An employee signing under a power of attorney needs a personal qualified electronic signature and an MChD with appropriate authority. A manager acting without a power of attorney signs under a separate workflow.
For a shipment against an advance payment, verify the transfer of the advance invoice details and line 5b: the XML, printed form, and source data in 1C all matter.
As of September 1, 2026, support for the Diadoc module for 1C 7.7 has ended, including renewals, updates, fixes, and consultations. This is a change to a specific Diadoc product, not an announcement ending support for the entire 1C 7.7 platform.

Key EDI changes in 2026

Updated 13.09.2026. Advance invoice details have been required since January; the new approved form has been in effect since April.

5.03UPD format for formalized exchange instead of the discontinued XML TORG-12 and act formats

01.04.2026new invoice form with line 5b for the details of an advance applied

01.09.2026Support for the Diadoc module for 1C 7.7 has ended

What is the Diadoc module for 1C

The Diadoc module for 1C is an external processing tool or configuration extension from SKB Kontur that brings Kontur.Diadoc electronic document exchange (EDI) directly into the 1C interface. From your familiar accounting system, you can create, send, receive, and sign FNS-formatted documents (invoices, UPD, acts, and delivery notes) as well as arbitrary files, without duplicate data entry or working in a separate web portal.

The shared EDI setup in 1C is covered in in the EDI solution in 1C; handles non-standard scenarios Diadoc integration via API.

Two module versions: Starter and Universal

Choose a license based on workflows, number of users, document volume, and need for customization. The module, outgoing-document package, and implementation are separate budget items; have the license scope specified in the supplier's proposal.

Parameter	Starter	Universal
Main scenario	Standard exchange for a small volume	Work involving multiple employees and more complex processes
Document processing	Sequentially, one at a time	Batch processing
Users	Up to two simultaneously under the tariff terms	Multi-user mode
Customizations	Standard functionality	Adaptation is possible; the scope of work is agreed separately
Configurations	Check that the exact release appears on the support list	Check the configuration, release, and required enhancements
1C:Fresh and the web client	The built-in module is not supported	The built-in module is not supported

For your own API integration in Kontur's price list dated May 29, 2026 A license priced at $320 per year is listed. This is the cost of API access, not a ready-made integration: development, support, and outgoing documents are charged separately. Before purchasing, verify the current offer and scope of permissions.

Integration format and 1C versions

Compare the platform, configuration, client mode, and delivery format against Kontur compatibility table. The minimum platform version alone does not guarantee operation with a modified or outdated configuration.

Integration form	What to check	Solution
External processing module for 1C 8	Supported platform releases and configurations, client, and cryptography	Update and test exchange on a copy of the database
Configuration extension	Support for the selected configuration and operating mode	Choose a compatible distribution; check third-party extensions
Diadoc module for 1C 7.7	Support ended on September 1, 2026	Plan a transition to a supported 1C version or a separate integration

In announcement dated 14.11.2025 Kontur announced that versions 4.47.23, 4.48, and 4.50 would be disabled from December 10, and 4.49 from December 15, 2025, recommending 4.59+. That version added support for 22% VAT, universal messages, and annulment changes. When updating in 2026, choose the currently supported build for your configuration and check its change log.

Compatibility with line 5b or a specific UPD scenario cannot be determined solely by the condition “version 4.59 or higher.” According to the announcement of support ending for 7.7 License renewals, fixes, updates, and consultations for the module have ended. This does not mean that all data exchange in 1C 7.7 has been technically stopped at the same time. An independent API integration requires separate assessment and support.

EDI in 1C:Fresh: why the module will not install and what to do

The built-in Diadoc module is not designed for 1C:Fresh or the web client.

At the same time, the 1C:Fresh platform itself allows extensions and additional processing tools, which undergo provider auditing before use.

Therefore, a limitation of a specific module must not be presented as a claim that in

There are no customizations in 1C:Fresh at all

1C:Fresh audit procedure. This leads to a typical choice.

The company already operates in Fresh, while its counterparties use Diadoc.

Alternatively, the organization has historically used Diadoc, is moving accounting to the cloud, and wants to preserve exchange from 1C.

Exchange between different operators is handled through roaming: in

In 1C:Fresh, the built-in 1C-EDI can be used when the required combination is available.

Another question is transferring Diadoc workflows to the accounting system:

document matching
batch processing
approval
statuses

The capabilities of such a workstation depend on the integration; roaming alone does not add them.

Four EDI approaches in Fresh, and what each one actually covers

Check the availability of a specific connection and roaming setup with your operator: the list of supported operators and exchange terms changes.

Path	What it covers	Constraint
Built-in 1C-EDI in Fresh	Exchange with counterparties whose operators are connected to the service; work directly in 1C	The set of operators is limited by the service; it does not reproduce Diadoc workflows
Roaming with the counterparty's operator	Legally significant exchange when the parties use different operators	Configured through the operator; it is a transport layer, not a workspace in 1C
Diadoc web portal separate from 1C	Working with documents in the Diadoc web interface	File export and reconciliation with accounting remain separate operations
Integration via the operator API	Documents, statuses, and accounting reconciliation within your process; available when permitted exchange interfaces are provided	Development and maintenance of the integration layer, verification of available Fresh interfaces, and enhancement auditing

How we connect EDI to 1C:Fresh when there is no standard module

For a non-standard scenario, we design an integration layer between the EDI operator's API and the application's permitted interfaces in 1C:Fresh.
First, we check the available exchange methods, permissions, and limitations of the specific application.
If an extension is required, it must pass the provider’s audit.
The accounting system remains in the cloud; the external integration service requires hosting and support.
The operator having an API is only one of the requirements.
Before estimating development, confirm that the application in
1C:Fresh allows the required documents to be read and written, and the selected signing method is available in this architecture.
Otherwise, file transmission may be automated while manual entry and reconciliation of incoming documents remain. The agreed scope may include receiving and sending documents, matching counterparties and contracts, transferring statuses, processing UPD 5.03, and verifying MChD.
For each document, we retain the identifier, link to the accounting object, processing log, and error reason.
A retry must not create a duplicate.
Integration does not remove signature and inter-operator exchange requirements.
Its feasibility depends on volume and effort: for a few documents per month, compare development costs with a web account or built-in 1C EDI.
Enhancement rules are set out in the 1C:Fresh documentation.

Document format in 2026: UPD 5.03 instead of TORG-12 and the act

As of January 1, 2026, Federal Tax Service Order No. ED-7-26/28@ cancelled the electronic goods waybill and act formats established by Orders No. 551 and No. 552.
Formalized exchange uses UTD 5.03 under Order No. ED-7-26/970@; select the required function based on the document content: invoice, transfer document, or a combination of both.
The cancellation of previous XML formats does not affect paper acts and waybills and, by itself, does not require all businesses to switch to EDI. Federal Tax Service clarification.
For a shipment against an advance payment received earlier, advance invoice details have been required since January 1, 2026. An updated form with line 5b has been in effect since April 1.
It is completed for the relevant application of the advance, rather than with the same value in all documents.
For electronic transmission, the Federal Tax Service has described how to complete additional information fields; the XML structure and agreed visualization method are important. Form effective April 1, Federal Tax Service letter dated March 23, 2026.
After the update, test three scenarios: shipment without an advance payment, settlement of one advance payment, and settlement of multiple advance payments.
The accountant compares the original invoices in 1C with the generated XML and printable form.
If a customized module or proprietary API adapter is used, the changes must be checked there as well.

Map out your integration landscape

clients@kt.team Telegram @kt_team_it

Employee signing: personal qualified electronic signature and MChD

Scenario for a representative acting under a power of attorney

Who signs

Personal qualified electronic signaturean employee's qualified signature, not a certificate issued to a legal entity

What confirms authority

Valid MChDThe authority is appropriate for the document; the power of attorney is available for verification

What you get

Legally binding document in 1Csigned and sent through Diadoc from the accounting system

A manager acting without a power of attorney uses the organization's manager's qualified electronic signature; an MChD issued to the manager personally is not required in this scenario.

MChD: format, authorizations, and verification

Document exchange between organizations uses a unified MChD in the format

Do not confuse it with UPD 5.03: the same word “format” refers to different documents. For tax reporting and certain information systems, the recipient’s requirements must be checked specifically; having an XML file alone does not confirm that the power of attorney is suitable for every exchange. In 2026, unified requirements for MChD content were updated by the Ministry of Digital Development order dated 05.11.2025 No.

Check the representative's details, validity period, and scope of authority in the current power-of-attorney service. Federal Tax Service clarification on the requirements. For an employee signing on behalf of an organization under a power of attorney, a personal qualified electronic signature and MChD are configured. A manager acting without a power of attorney signs with the manager's qualified electronic signature; issuing a power of attorney to themselves is unnecessary.

An employee’s MChD is created in the power-of-attorney service or uploaded as signed XML, then registered and linked to the user. The Federal Tax Service service and procedure for creating MChD. Before launch, verify the certificate's validity, the MChD term and status, authority for the specific document, and whether the counterparty can perform the verification. Procedures should include revoking the power of attorney and blocking access when a role changes or an employee leaves. A new certificate does not replace an authority check.

Module capabilities

Send and receive

Creating and sending documents from 1C; based on a supported incoming UPD, an accounting document can be created after matching reference data and validating fields.

Signing and statuses

Signing must match the signatory's role; statuses are visible in 1C. For a representative, verify their personal qualified electronic signature, MChD, and authority for the document.

Invitation and auto-roaming

Search for and invite a counterparty from 1C. For another EDI system, verify whether auto-roaming is available or how to connect through the operator's support service.

Approval and BPM

The integration with 1C:Document Management workflows, assignees, and deadlines is designed for the company's processes; it should not be considered an automatic part of every module delivery.

Implementation Scenarios

01
Accounting and Trade
1C:Accounting Enterprise and Trade Management: exchange of UTDs, invoices, and acts on a standard out-of-the-box configuration.
02
Integration with 1C:Document Management
Internal approval of contracts and orders plus external exchange in one environment, without switching between programs.
03
Custom and ESB
Non-standard configurations, custom workflows, and integration with ESB: implemented with add-on modules and plugins KT.Team turnkey.

Infrastructure requirements

The currently supported module build and compatible 1C configuration release; review of change logs before updating.
The platform, delivery format, client mode, and operating system are compatible Kontur compatibility matrix; support for the Diadoc module for 1C 7.7 has ended.
The cryptography and certificate suit the selected scenario; for an employee acting under a power of attorney, the MChD and authorizations have also been verified.
The workstation and, if necessary, the server can access Diadoc API addresses over HTTPS; proxies and security tools do not block data exchange.
For 1C:Fresh, a supported exchange method has been selected; the required customizations have passed the provider's audit.
There is a backup, a test database, and a rollback plan. Acceptance testing covers sending, receiving, signing, correcting, and retrying after an error.

What changes after implementation

Speed

Creation, approval, and signing happen in one flow; the more incoming and outgoing documents there are, the more noticeable the benefit.

Costs

Costs for the paper-based part of the exchange are reduced. The calculation includes licenses, outgoing documents, implementation, support, and retention of the available electronic archive.

Transparency

Managers can see statuses, approval stages, and comments online, so delays are visible immediately.

Exchange discipline

Reference-data matching and field validation help reduce manual errors; disputed documents remain subject to review by the responsible employee.

Comparison with alternatives and roaming

Diadoc is one EDI option alongside Saby/SBIS, Taxcom, Kaluga Astral, and other operators.
The choice depends on the industry, document volume, and accounting systems.
Automatic roaming is available for supported combinations; for a specific counterparty, check the invitation, exchange direction, and supported documents.
If automatic connection is unavailable, agree on the procedure with the operator.
For other systems, see 1C and SBIS integration or 1C and Taxcom.
Selection scenarios are explained in the comparison of Diadoc, SBIS, and Taxcom. From September 1, 2026, electronic transportation documents will be mandatory where required by law.
Transmitting data to GIS EPD requires an EPD information-system operator and separate transport-process configuration: a standard EDI connection does not confirm readiness for electronic waybills.
Exceptions are provided, in particular, for military and special cargo, transactions with foreign counterparties, and transportation for individuals’ personal needs. According to the announcement
The Ministry of Transport’s penalty-free period for using paper documents instead of electronic ones runs until March 1, 2027; it does not remove the obligation to transition. Ministry of Transport clarification.
Configuration setup - ETrN and GIS EPD in 1C.

Steps to a successful integration

01
Check module version
Compare the installed build with the currently supported release, review the changes, and test the update on a copy of the database.
02
Choose version and platform
Define the document volume, choose the Starter or Universal edition, and the supported 1C platform.
03
Prepare signature
Identify the signatories: a manager without a power of attorney or an employee with a personal qualified electronic signature and MChD. Check the certificates, cryptography, and authorizations.
04
Set up documents and counterparties
Map document types and directories; for complex processes, use add-on modules or plugins.
05
Train and support
Conduct acceptance testing with real document types, train users, assign responsibility for errors and updates, and measure the share of manual processing and document completion time.

News

What’s new in EDI

All news

2026-04-09
The FNS extended Taxcom’s status as an EDI operator until 2028
The FNS Commission (Decision No. 936-039 dated April 3, 2026) confirmed Taxcom’s compliance with requirements for EDI operators and extended its status until April 3, 2028; the service supports roaming with 33 operators.

Turnkey implementation

Need integration tailored to your processes?

Non-standard 1C configurations, custom approval workflows, or integration with 1C:Document Management or ESB - KT.Team delivers end-to-end 1C and Diadoc integration: setup, process-specific configuration, and a transferable solution that stays with you.

Order turnkey implementation

Sources

Verification date: 13.09.2026

Kontur: build support ended in December 2025
Diadoc: support ending for the 1C 7.7 module
Kontur: module compatibility with the platform and configurations
Kontur: API pricing as of 29 May 2026
1C:Fresh: auditing extensions and processing modules
Federal Tax Service: discontinuation of TORG-12 and act formats; the transition to UPD
Federal Tax Service: new VAT forms from April 1, 2026
Federal Tax Service: advance invoice details in an electronic document
Federal Tax Service: MChD content requirements in 2026
Federal Tax Service: creating and verifying MChD
Diadoc: inter-operator roaming
Ministry of Transport: mandatory electronic transport documents and penalty-free period

Diadoc module for 1C in 2026: what changed and what to update