Implementation of 1C-EPD for electronic transportation documents
We will connect and configure 1C-EPD for working with electronic waybills, orders, requests, and other transportation documents within 1C software. We will verify the current configuration, participant roles, electronic signatures, the exchange operator, and counterparty readiness.
What is 1C-EPD
For companies in Uzbekistan, the service is relevant if the company participates in transportation within the Russian legal framework, operates through a Russian legal entity, or needs to integrate Russian EPDs into an international logistics chain. Russian requirements do not automatically apply to all organizations in Uzbekistan.
1C-EPD is a service for generating, signing, and exchanging electronic transportation documents within 1C software. The exchange takes place through an accredited EPD information system operator, which transfers data between transportation participants and to the Russian GIS EPD. The capabilities and terms of the service are published on the official 1C portal.
The user works with documents in the familiar 1C interface: creates a document, fills in the data, signs the required title, and tracks statuses. A mobile application can be used by drivers and other participants who need to sign the document outside the office.
Important. 1C-EPD is not a GIS EPD operator and does not replace legal preparation. Exchange requires connection through a supported accredited operator and the correct distribution of authorities.
What documents can be processed in 1C-EPD
The official 1C portal indicates support for approved electronic transportation document formats for road transport:
- electronic waybill (ETRN);
- electronic order or request;
- electronic waybill (EPL);
- electronic accompanying document;
- electronic work order;
- electronic charter agreement.
The availability of a specific document and scenario depends on the 1C configuration, its release, the organization's role, and the configured operator. A compatibility check is conducted prior to the project.
Who needs 1C-EPD configuration
The service is used by logistics chain participants and employees who create, fill in, sign, or monitor transportation documents.
To shippers
To prepare cargo data, hand it over to the carrier, and sign their titles.
For Carriers
For assigning drivers and vehicles, managing transport stages, and confirming operations.
For Consignees
For cargo acceptance, logging remarks, and finalizing documents.
For Freight Forwarders
For managing transport and freight forwarding processes based on the contractual role.
For drivers and responsible personnel
For mobile signing and entering information based on assigned authorities.
For IT, Accounting, and Logistics
For managing data exchange, tracking statuses, reconciliation, and user support.
For international groups, it is crucial to determine in advance which legal entity is participating in the transportation and within which jurisdiction the document is generated. This directly determines the applicability of Russian regulations, signatures, and the system operator.
What changes on September 1, 2026
Starting September 1, 2026, in Russia, the bill of lading and the transport order (request) must be issued in electronic form in cases provided by law. The changes also cover a number of freight forwarding, rail, and air documents. A detailed analysis and checklist are compiled on the page. "Transition to EPD from September 1, 2026".
What to prepare before connecting
The current 1C configuration and release version
We check whether 1C-EPD is supported by standard functionality and whether an update or integration is required.
1C-EDI and the EPD operator
The organization must be connected to a supported data exchange loop through an accredited operator.
Qualified electronic signatures
A QES is used for the executive; for employees, it is necessary to define authorities and issue a machine-readable power of attorney (MRPOA) when required.
Roles and responsibilities
An administrator, logistics staff, accounting staff, drivers, and other participants are assigned.
Counterparties
Readiness for exchange, the operator, the test route, and contact persons are coordinated with key partners.
Mobile devices and internet
Participants working on the road need access to the mobile app and stable internet.
High-quality master data
Organizations, counterparties, vehicles, drivers, addresses, cargo, and contracts are verified.
How the 1C-EPD implementation process works
Process audit
We define transport types, documents, legal entities, roles, and configuration versions in use.
Compatibility check
We analyze the 1C release, the availability of 1C-EDI, the operator, custom modifications, and integrations.
Scenario design
We map out who creates the document, who signs each title, what data is populated automatically, and how exceptions are handled.
Service configuration
We set up data exchange, users, certificates, MRPOAs, routes, and mobile access within the agreed loop.
Test exchange
We route the document through the entire chain with the selected counterparty and check statuses, signatures, corrections, and refusal scenarios.
Training
We analyze work operations separately for logisticians, accounting, administrators, drivers, and executives.
Launch and support
We monitor the initial documents, eliminate errors, and connect subsequent counterparties according to the plan.
Integration with 1C-EDI, QES, MRPOA, and counterparties
Technical configuration only works in conjunction with legally correct authorities. For each employee, it is determined which actions they perform and on what basis they sign the document. If the document is signed by a representative, the necessity of a machine-readable power of attorney is verified.
Key counterparties are connected before the mass launch. It is necessary to align on the test scenario, verify routing between operators, and ensure that each party sees the document and can sign their respective section. If the company uses multiple information systems, the data source and discrepancy handling are designed separately.
The Federal Tax Service of Russia recommends obtaining a QES, choosing an accredited operator, and granting access to responsible employees. The official sequence is published in the FTS clarification.
1C-EPD for logistics, transport, and international shipping
In a logistics company, EPD affects more than just one department. Sales establishes the order terms, the logician assigns the shipment, the dispatcher works with the driver, accounting controls the closing documents, and IT is responsible for data exchange and access.
For a company from Uzbekistan, the issue of jurisdictional boundaries arises. Russian EPD should be implemented within the environment where the respective document actually originates and where a Russian legal entity participates or Russian regulation applies. The remaining processes can continue to operate under the rules of their own jurisdiction and connect with EPD through a coordinated integration.
If a telematics system is available, part of the master and actual data about the transport can be used in related 1C processes. The possibility of automatically filling in specific EPD attributes is evaluated separately: it depends on the format, API, data quality, and access rights.
Timeline and cost of implementation
The cost depends on the number of legal entities, document types, roles, 1C configurations, EDI status, the number of counterparties, mobile users, and integrations. Database updates, custom modifications, and complex scenarios are evaluated separately.
After the audit, we form a plan: the mandatory minimum for launch, the test environment, training, and the sequence of connecting counterparties. This allows us not to mix the basic configuration with tasks that can be safely postponed to the next stage.
FAQ
How does 1C-EPD differ from 1C-EDI?
1C-EDI provides electronic document exchange, while 1C-EPD is designed for transport documents and interaction via an operator with the GIS EPD. For 1C-EPD to function, a configured electronic exchange environment is required.
Which documents does 1C-EPD support?
The official 1C portal lists the electronic bill of lading, electronic transport order or request, electronic waybill, accompanying sheet, work order, and charter agreement. Specific availability depends on the configuration and release version.
Is a QES required for a driver?
The signing scheme depends on the document, the role, and the current requirements. Before launch, it is necessary to determine the participants, types of signatures, and grounds for authority. For employees, the necessity of an MRPOA is also verified.
Is it possible to connect only one counterparty for testing?
Yes. A pilot project with a key counterparty helps to verify the entire document route, statuses, signatures, and exceptions before the mass connection of partners.
Does 1C-EPD work in any 1C configuration?
No, compatibility must be checked. 1C publishes a list of supported programs and indicates the possibility of embedding it into other applications on the 1C:Enterprise 8 platform, but such a scenario requires a separate evaluation.
Does a Uzbek company need to transition to EPD from September 1, 2026?
Not automatically. This is a requirement of Russian legislation. Applicability depends on the company's role, the legal entity, the route, the contract, and the legal jurisdiction within which the transportation is issued.
Is a PDF considered an electronic bill of lading?
No. An EPD is a structured electronic document of a specified format, signed and transmitted via an operator in accordance with the established procedure. A scan or PDF on its own does not replace this.
We will prepare a 1C-EPD connection plan
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
