ETRN and GIS EPD in 1C: mandatory transition by September 1, 2026

From September 1, 2026, the transport waybill, carriage order (request), forwarding documents, air cargo waybill, and rail waybill are issued only as electronic documents and sent to the GIS EPD state system. This is required by Federal Law No. 140-FZ of June 7, 2025, which amended four laws at once: the Road Transport Charter (259-FZ), the law on forwarding activity (87-FZ), the Air Code, and the Rail Transport Charter. The law applies to domestic CIS transport; the obligation covers shippers, carriers, forwarders, and consignees.

There is no transition period in the law: the September 1, 2026 deadline has not been moved. The only easing was announced on June 23, 2026: the Ministry of Transport proposed limiting enforcement to an oral warning until March 1, 2027 if a driver presents a paper waybill instead of an electronic one, and the president supported the initiative. This does not remove the obligation to issue documents electronically - only roadside enforcement practice changes during the first six months.

For a company with freight logistics, the question quickly comes down to the accounting system: does the 1C configuration support electronic transport documents, who will process incoming ETRNs, and who will see that the shipment is not closed until the acceptance title is signed. Below is how the exchange works, which documents go electronic, and what to check in 1C before the deadline. How the full transport framework is built is covered in the section digitalization of logistics.

ETRN is the electronic transport waybill, a legally binding equivalent of the paper waybill for road transport. The key difference from standard invoice EDI is that this is not one file with two signatures, but a document made up of several titles signed by different participants at different stages of the shipment. The shipper signs the loading title, the driver or carrier signs cargo acceptance for transport and then handover, and the consignee signs the acceptance. Until the titles are signed, the shipment is not closed in the system.

GIS EPD is the state information system for electronic transport documents, operated by the Ministry of Transport. The system has operated in voluntary mode since September 1, 2022; the exchange rules were approved by CIS Government Resolution No. 931 of May 21, 2022. From September 1, 2026, sending transport documents to GIS EPD becomes mandatory, not optional.

The exchange is a three-step chain. The company creates the document in its accounting system, for most this is 1C, and sends it to the EPD IS operator, a commercial organization accredited by the Ministry of Transport. The operator validates the document and sends it to GIS EPD, where statuses and signed titles become available to all parties involved in the shipment and to regulators. The driver does not need paper: during a roadside inspection, the officer receives the waybill data from GIS EPD.

The EPD IS operator register is maintained by the Ministry of Transport; as of July 2026 it includes 11 connected operators, including Kaluga Astral, SKB Kontur, Taxcom, Tensor, and SberKorus. If you and your counterparty use different operators, ETRN exchange goes through GIS EPD, but you should verify the chain in a pilot: operators are integrated with accounting systems at different depths, and inter-operator roaming is not supported for electronic route sheets, so all parties involved in issuing the EPL must be with the same operator.

The first question is whether your configuration supports electronic transport documents. The standard mechanism is the 1C-EPD service: according to the 1C portal, it is supported in 1C:Accounting, 1C:ERP 2.5, 1C:Integrated Automation, 1C:Trade Management, 1C:UNF, 1C:Retail 3.0, 1C:Holding Management, 1C:UPP 1.3, 1C:EDI Client ed. 2, as well as in the transport configurations 1C:Vehicle Management (Standard/PRO and the module for 1C:ERP) and 1C:TLE CORP. Drivers have the 1C-EPD mobile app for Android and iOS. The service works through Kaluga Astral and Taxcom operators; if you use another operator, you will need its 1C module or API integration. An outdated release or heavily customized configuration is a separate upgrade project, and it is better to assess it now rather than at the end of August.

EPD IS operator. Check that the operator is listed in the Ministry of Transport register and is actually connected to GIS EPD, not just accredited. If most of your documents already go through your usual EDI operator, it makes sense to start there: Taxcom's transport document framework integrates with 1C - see 1C integration with Taxcom; how the exchange with Diadoc works is explained in the breakdown Diadoc integration with 1C.

Signatures and Powers of Attorney. Document titles are signed with an advanced qualified signature. Employees who sign documents on behalf of the company—logistics specialists, dispatchers, warehouse managers—require machine-readable powers of attorney (MChD). MChD is issued in unified format 003 and registered in the Federal Tax Service's distributed registry: a single power of attorney works with any operator. Starting February 1, 2026, new MChD must include the representative's SNILS, INN, date of birth, and power of attorney expiration date (Ministry of Digital Development Order dated 05.11.2025 No. 1001); powers of attorney issued previously remain valid through their expiration. Issue and renew signatures and MChD in advance: this is the most bureaucratic step of the transition. Drivers do not need a legal entity signature—they work through the operator's mobile app.

Incoming handling. The consignee is a full participant in the exchange: until they sign the acceptance title, the shipment is not closed in GIS EPD. You need a workstation where incoming ETRNs are visible and processed daily, rather than piling up in the operator's personal account that nobody checks.

Status control. ETRN has more statuses and signers than standard invoice document exchange, and a title stuck in limbo is not a cosmetic issue but an unconfirmed shipment. Assign an owner and set up a report on open documents in 1C. If transport is your operational core, status control should live in the transport framework, just as TMS connects with ERP, explained in the article on TMS and ERP integration.