#1c

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

What changed in the Diadoc module for 1C by 2026: version 4.59+, 22% VAT, transition to UPD 5.03, mandatory MChD, and end of 1C 7.7 support. Requirements and setup.

  • EDI regulatory deadlines in 2026
  • What is the Diadoc module for 1C
  • Two module versions: Starter and Universal
  • Integration format and 1C versions

EDI regulatory deadlines in 2026

Diadoc for 1C in 2026: Versions, UPD 5.03, MChDThree dates in 2026 on one timeline: on January 1, the XML formats for TORG-12 and the act are canceled and exchange moves to electronic UPD format 5.03; on April 1, mandatory line 5b appears in the invoice and UPD; on September 1, support ends for the module for 1C 7.7 and the COM SDK external component. Version 4.59 or later is required for all three dates.01.01.202601.04.202601.09.2026XML TORG-12 cancellationand act -> UTD 5.03Mandatory line 5bin the invoice and UTDEnd of module supportfor 1C 7.7 and COM SDKFor all three dates, you need module version 4.59 or later
Three 2026 dates that require module version 4.59 or later.
4.59+minimum module version in 2026: VAT 22%, simplified taxation system, UPD cancellation
22%higher VAT rate from 2026 - supported only in 4.59 and later
5.03UPD and invoice format instead of the canceled XML TORG-12 and act
01.09.2026end of module support for 1C 7.7 and COM SDK

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

Prices below are a market reference from resellers; check the current price list with SKB Kontur before buying.

ParameterStarter (approx. 6,000 RUB/year)Universal (approx. 17,500 RUB/year)
1C configurationslimited setmore than 20 standard
Usersup to 2multi-user mode
Batch processingnoyes
Web client and 1C:Freshnot supportednot supported
Process-specific customizationsnoyes

Integration format and 1C versions

Integration formMinimum 1C platformStatus
External processing8.2.19 or 8.3.4.465 and latercurrent
Configuration extension8.3.14 and latercurrent, newer
Module for 1C 7.77.7support discontinued as of 01.09.2026
Diadoc for 1C in 2026: Versions, UPD 5.03, MChD
A working conversation

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

From January 1, 2026, FNS Order No. ED-7-26/28@ dated 20.01.2025 cancels the XML formats for electronic TORG-12 (No. 551) and the act (No. 552): structured exchange moves to electronic UPD format 5.03 (UPD - FNS Order No. ED-7-26/970@ dated 19.12.2023, invoice - Order No. ED-7-26/1032@ dated 15.11.2024). The previous format under Order No. MMV-7-15/820@ dated 19.12.2018 is obsolete.

From April 1, 2026, the invoice and UPD are supplemented with mandatory line 5b (advance invoice details); the configuration and module must support this, which is why build 4.59 or later is required.

Signing in 2026: individual QES and MChD

Legally binding signing on behalf of an organization in 2026

Who signs

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

What confirms authority

MChD from the FNS registrymachine-readable power of attorney in unified format 003, mandatory since September 1, 2024

What you get

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

EMCHD in 2026: format 003 and new required fields from February 1

  1. For counterparty exchange, EMCHD is issued in unified format 003—both government bodies and EDI operators accept it.

  2. Format 5.03 remains only for tax reporting to the Federal Tax Service, while registration of previous formats has been discontinued: 5.02—since January 10, 2025; 5.01—since March 1, 2025; previously issued powers of attorney remain valid until expiration.

  3. Registered EMCHD is stored in the Federal Tax Service's distributed registry, so you don't need a separate power of attorney for each operator—counterparties verify it in the registry. As of February 1, 2026, an order takes effect

  4. Ministry of Digital Development Order No. 1001 (November 5, 2025): new EMCHDs must include the representative's SNILS, INN, date of birth, power of attorney validity period, and authority name; passport data are no longer required. Powers of attorney issued before this date do not need to be reissued. In the bundle

  5. Diadoc and 1C workflow: an employee logs into the module with a personal certificate; EMCHD is issued via Kontur.Doverennost service or uploaded as a signed XML file; the manager signs the power of attorney with their certificate—then the module signs documents with the employee's enhanced qualified signature linked to the EMCHD.

Module capabilities

Send and receive

Create and send documents directly from 1C; incoming documents automatically create an accounting document (for example, "Goods Receipt" from an UPD) and fill in the details.

Signing and statuses

The QES signature with MChD gives the document legal force; statuses (waiting for signature, signed, rejected) are visible directly in 1C.

Invitation and auto-roaming

Counterparty search by TIN and invitation from 1C; roaming is set up automatically between major operators, without a roaming request.

Approval and BPM

Before sending, the document can be approved in 1C:Document Management: workflows, assignees, deadlines, and approval marks.

Map out your integration landscape

clients@kt.team Telegram @kt_team_it

Implementation Scenarios

  1. 01

    Accounting and Trade

    1C:Accounting Enterprise and Trade Management: exchange of UTDs, invoices, and acts on a standard out-of-the-box configuration.

  2. 02

    Integration with 1C:Document Management

    Internal approval of contracts and orders plus external exchange in one environment, without switching between programs.

  3. 03

    Custom and ESB

    Non-standard configurations, custom workflows, and integration with ESB: implemented with add-on modules and plugins KT.Team turnkey.

Diadoc for 1C in 2026: Versions, UPD 5.03, MChD
The team's workstations

Infrastructure requirements

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

Printing, paper, courier delivery, and archive storage are eliminated; savings depend on document volume.

Transparency

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

Exchange discipline

Fast exchange without errors in details simplifies work with the Federal Tax Service and counterparties, and helps close periods on time.

Comparison with alternatives and roaming

  1. Kontur.Diadoc is not the only EDI operator: there are SBIS/Tensor, Takscom, Kaluga Astral, and others.

  2. The choice depends on the industry, document volume, and accounting systems.

  3. Key for 1C: auto-roaming works between major operators - exchange is set up by automatically sending an invitation, with no roaming request or paperwork (ROSEU association), meaning 0 requests.

  4. If your counterparties use another operator, see 1C and SBIS integration or 1C and Taxcom.

  5. How to choose between them for your specific landscape—configurations, product marking, transportation, and roaming—we covered in comparison of Diadoc, SBIS, and Taxcom.

  6. A separate workflow starts on September 1, 2026 for mandatory transport documents: transport consignment notes move into GIS EPD through accredited EPD IS operators, and a standard EDI connection is not enough.

  7. A breakdown of the transition is in the article about ETrN and GIS EPD in 1C.

Diadoc for 1C in 2026: Versions, UPD 5.03, MChD
Open office among plants

Steps to a successful integration

  1. 01

    Check module version

    Make sure build 4.59 or later is installed; otherwise, 22% VAT, simplified taxation, and UPD 5.03 will not work.

  2. 02

    Choose version and platform

    Define the document volume, choose the Starter or Universal edition, and the supported 1C platform.

  3. 03

    Prepare signature

    Obtain an individual QES, issue an MChD in the FNS registry, and install CryptoPro.

  4. 04

    Set up documents and counterparties

    Map document types and directories; for complex processes, use add-on modules or plugins.

  5. 05

    Train and support

    Train employees, assign EDI owners, and regularly install FNS format updates.

News

What’s new in EDI

All news

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

Not just Diadoc and 1C

Turnkey integrations on any EDI transport and in any accounting system

KT.Team has been building enterprise integrations for 13 years and delivers turnkey solutions with any tools, not just Diadoc and 1C. For system landscapes, we use ESB/iPaaS: a service bus, queues, and monitoring with guaranteed delivery on top of any EDI operator (Diadoc, SBIS, Takscom, and others) and any accounting system. For teams building AI agents, we provide ready-made skills for working with the EDI environment out of the box: the agent sends, receives, and reconciles documents through EDI transports without a separate manual integration. Any transport, any system, guaranteed delivery.

Discuss a turnkey integration

Sources

Review date: 08.07.2026

Discuss the article: Diadoc for 1C in 2026: what...

Send via:

By clicking the button, you accept the offer and grant consent to the processing of personal data.

Related Cases

All cases

Related solutions

All solutions
1C Integration with Chestny Znak and TS PIoT1C and Diadoc integration — electronic document exchange1C Marketplace Integration — Orders, Inventory, Pricing1C integration with SBIS: EDI and regulated reporting

Articles on the topic

All articles

Related videos

All videos
4:40 The Diadoc Module for 1C | Making Document Work Easier 4:46 Chestny Znak and 1C integration | Automatic product labeling 4:19 Cloud Native ESB / Flexibility and Speed for Your Business

News on the topic

All news