EPD from September 1, 2026: how to prepare 1C
Starting September 1, 2026, in Russia, a portion of transport documents must be issued electronically in cases provided by law. Check the readiness of your 1C, EPD operator, QES, MRPOA, and counterparties.
Important for Uzbek companies: the requirements are relevant when operating within the Russian legal framework. Official Section of the Federal Tax Service of Russia
What changes on September 1, 2026
Federal Law of Russia No. 140-FZ dated June 7, 2025, transfers a number of transport documents into a mandatory electronic format starting September 1, 2026. According to the clarification of the FTS of Russia, the new procedure affects participants in the transport chain: shippers, carriers, consignees, and freight forwarders.
An electronic document is generated in an approved format, signed with the established electronic signature, and transmitted through an accredited EPD information system operator to the GIS EPD. A regular PDF, scan, or file sent by email does not replace such an exchange.
For certain cases, exceptions and special rules provided by law may apply. Before changing the process, the current regulatory acts and the applicability of the requirements to a specific shipment should be checked.
Who needs to switch to EPD?
Organizations and entrepreneurs who create, sign, or receive documents transferred by Russian legislation into a mandatory electronic format must check the applicability.
Shippers
They transmit cargo data and participate in issuing the bill of lading.
Carriers
They organize transportation, assign vehicles and drivers, and sign the required document sections.
Consignees
They confirm receipt and enter delivery result details.
Freight Forwarders
They issue documents within the scope of freight forwarding activities.
Employees and representatives
Logistics managers, drivers, dispatchers, accounting, and other individuals act within the limits of assigned authorities.
For a Uzbek company: The key issue is not the location of the website or office, but the role of the specific legal entity and the legal framework of the transportation. Applicability must be checked based on contracts, the route, and the participants, involving a specialized lawyer or an EPD operator if necessary.
Which documents need to be converted to electronic format
The FTS lists the following groups of documents transitioning to mandatory electronic document management starting September 1, 2026:
- bills of lading;
- transport orders or requests;
- forwarding instructions;
- forwarder's receipts and warehouse receipts;
- rail waybills;
- air waybills.
This list is broader than the capabilities of a single software service. On its official page, 1C-EPD separately outlines the supported formats for road transport: the electronic bill of lading, transport order or request, electronic waybill, accompanying sheet, work order, and charter agreement. Therefore, the document type and the company's role are determined first, and then the technical scenario is selected.
What needs to be checked in 1C in advance
Configuration and release version
Ensure that the software in use supports the required EPD type or allows for a coordinated integration.
1C-EDI and the operator
Check the connection to an operator accredited to work with the GIS EPD and verify the exchange routing.
Organization and counterparty profiles
The details must be complete and uniform, with no duplicates.
Vehicles, drivers, and addresses
Directories must contain the data required for documents and operational scenarios.
QES and MRPOA
Determine who signs each section, with which certificate, and on what legal basis.
User permissions
Restrict access by roles and assign a process administrator.
Mobile operations
Prepare devices, user accounts, and internet access for drivers and other mobile participants.
Integrations
Verify where the order, route, cargo data, and vehicle details originate, and how errors are handled.
Document archive and status tracking
Determine where employees look up documents, who monitors unsigned sections, and how discrepancies are resolved.
Company readiness checklist
Define the scope
Compile a list of legal entities, routes, transport types, and documents to which the new procedure may apply.
Assign a project owner
A single responsible person coordinates logistics, accounting, IT, lawyers, drivers, and counterparties.
Select an operator and a technical environment
Verify accreditation, compatibility with 1C, and data exchange with your partners' operators.
Conduct a signature audit
Obtain a QES, issue an MRPOA, and create a clear authority matrix.
Update 1C
Install the supported release version in the test environment first and verify the impact of custom modifications.
Clean up 1C catalogs
Correct the details of organizations, counterparties, vehicles, drivers, and addresses.
Run a pilot project
Select a typical route and a ready counterparty, process the document through the entire chain, and test the adjustments.
Train the participants
Divide instructions by roles and practice actions in case of errors, loss of connectivity, or data changes.
Connect counterparties in waves
Start with key partners, then expand the scope and monitor problematic statuses.
Prepare support
Determine the request channel, responsible persons, and the escalation procedure after launch.
The FTS notes that the transition, including connecting counterparties and testing processes in practice, can take from two to six months. Official FTS Checklist recommends starting in advance. If the deadline has already arrived, the priorities become the legal verification of applicability, a minimum viable environment, and the phased connection of partners.
How the 1C-EPD implementation process works
The technical project begins after the legal and process scope is defined. Then, the 1C configuration, 1C-EDI, the operator, signatures, MRPOA, and participants are verified. Documents and roles are configured in a test environment, followed by an end-to-end exchange with a selected counterparty.
The commercial service, scope of work, and source data requirements are detailed on the page of 1C-EPD implementation.
Audit result
It is clear which documents and legal entities are included in the project.
Configuration result
Users, roles, signatures, and exchange routes are functioning in the test environment.
Pilot Project Deliverables
The document goes through the entire chain, and the team knows how to handle typical exceptions.
Launch result
Key counterparties are connected, statuses are monitored, and requests are handled according to the agreed procedure.
Common mistakes during transition
Treating EPD as a regular PDF
A legally binding document must have a specified format, signatures, and a routing path through the operator.
Leaving the project solely to the IT department
Without logistics, accounting, lawyers, and a process owner, technical configuration does not resolve organizational issues.
Inapplicability cannot be verified
It is essential for an international company to identify the correct legal entity and regulatory framework, rather than extending Russian requirements across the entire corporate group.
Update the production database without testing
Customizations and integrations may conflict with the new release; a backup plan and testing in a sandbox environment are required first.
Disregard counterparties
The document will fail the workflow if the partner is not ready, uses a different routing path, or has not assigned responsible personnel.
Failure to issue authorizations
Possession of a certificate does not automatically mean the employee is authorized to sign a specific document title.
Test only the happy path
It is necessary to verify corrections, driver or vehicle changes, cancellations, discrepancies, and temporary loss of connectivity.
How Transport Telematics helps you prepare
We view Electronic Transport Documents (ETD) as an end-to-end process connecting 1C, transport participants, and external systems. This is especially critical for companies with their own fleets, international routes, and multiple business units.
- We conduct an audit of your current workflow and 1C configuration;
- We help define the technical scope after verifying the applicability of the requirements;
- We configure 1C-ETD, roles, access permissions, signatures, and test exchange;
- We prepare scenarios and instructions for different user groups;
- We support the pilot launch and the phased onboarding of counterparties;
- We evaluate integrations with logistics and transport management systems.
FAQ
Is the electronic consignment note mandatory from September 1, 2026?
In Russia, the consignment note and the transport order or request must be issued in electronic form in cases provided by law. Official exceptions and the specific details of each transport operation must be taken into account.
Does the transition apply to all companies in Uzbekistan?
No. This is a change in Russian legislation. For a company from Uzbekistan, the applicability depends on the role of the legal entity, the contracts, the route, and the specific regulatory framework in which the documents are issued.
Which documents are being converted to electronic format?
The Federal Tax Service lists consignment notes, transport orders or requests, freight forwarder instructions, forwarder and warehouse receipts, railway consignment notes, and air waybills.
Is it enough to connect 1C-EDI?
No. It is necessary to verify the support for the specific electronic transport document in the configuration, select an accredited operator, set up roles, qualified electronic signatures, and machine-readable powers of attorney, onboard counterparties, and conduct a test exchange.
Is a machine-readable power of attorney (MRPA) required?
For employees signing documents on behalf of the organization, the requirement and content of the machine-readable power of attorney (MRPA) are determined by their authorities and current regulations. The signing matrix should be prepared prior to the pilot launch.
When should preparation begin?
The Federal Tax Service indicates that the transition, along with counterparty onboarding and testing, can take from two to six months. Preparation should start as early as possible; once the deadline passes, a priority launch and risk mitigation plan will be required.
Can we continue to use paper documents?
Only if the specific case falls under a statutory exception or if the document is not included in the mandatory list. This must be verified against the current official guidelines.
Verify readiness prior to launch
Describe your current configuration, the number of users, the processes, and the systems that require data exchange. We will clarify the task and propose the next step for the project.
Calculate the cost of 1C implementation and configuration
