Mandatory in Russia since 1 September 2026

The electronic forwarder order is mandatory. Your system cannot issue one.

The law is already in force, yet most forwarders have no built-in mechanism in their transport systems: rewriting a TMS is slow and expensive, and operating without the document is not an option. We close that gap with a separate service that stands next to your system and takes the document flow on itself.

01.09.2026from this date the forwarder order, the forwarding receipt and the warehouse receipt exist only in electronic form
State systemevery electronic forwarding document is routed into the state information system
3 partsthe order is signed in parts: the client, the forwarder and, if needed, a withdrawal
Qualified signaturean enhanced qualified electronic signature; individuals may use the state signature app
01The law

What exactly changed

Short and to the point, without ten pages of regulatory retelling.

The documents became electronic by default

Since 1 September 2026 the electronic forwarder order, the electronic forwarding receipt and the electronic warehouse receipt are drawn up electronically. There is no paper alternative, and the rule also covers shipments that previously had no documents at all.

There is now an approved format

The format of the electronic forwarder order was approved by Federal Tax Service Order No. ЕД-1-26/277@ of 28 April 2026, and the exchange procedure by Government Resolution No. 469 of 27 April 2026. You cannot invent your own format: the structure is fixed and validated.

Exchange goes through an operator and the state system

The document is created and signed in an EDI operator's service, from where it is routed to the counterparty and simultaneously lands in the state information system for electronic transport documents.

In a chain of forwarders every link needs its own document

If a forwarder engages another forwarder, an order is issued for every leg of the chain, with the next participant acting as the client. A manual process breaks here first.

02The documents

Which documents, and how they differ

These are the most commonly confused, yet they differ in purpose and timing.

Forwarder orderElectronic forwarder order

Defines the terms of work: what is carried, where and on what conditions. Issued before transport. It consists of parts: the client creates and signs theirs, the forwarder signs theirs to confirm agreement, and the client may withdraw the order with a separate part.

Forwarding receiptElectronic forwarding receipt

Records a fact: the forwarder has taken the cargo. Unlike the order, it is issued at the moment the cargo is actually accepted, not in advance.

Electronic waybillElectronic consignment note

Accompanies the cargo in transit and evidences the carriage contract. The order defines the terms of work; the waybill is used in the transport itself.

Order requestElectronic order request

Used when the forwarder never physically takes the cargo: an order request and a waybill are issued instead, signed with the carrier and the consignee by the client themselves.

03The process

How a document travels

Six steps from a request to a mark in the state system. In our service a human is involved only where the law requires a signature.

The request

The request arrives from your source: a transport system, an accounting system, a spreadsheet, a file or an API call.

Assembling the document

The service fills the approved structure: parties, cargo, route, addresses and signatory details.

Validation before sending

Mandatory fields, reference data and internal consistency are checked. An error is caught before sending rather than in a rejection from the state system.

Signing

The document is signed with an enhanced qualified electronic signature. This is the step that stays with a human — and the only one where a human is genuinely needed.

Sending via the operator

The signed document goes to the counterparty through an EDI operator and lands in the state system at the same time.

Statuses and storage

The service tracks counter-signature, withdrawals and rejections, keeps the history and returns the status to your system.

04The problem

Why this hurts almost everyone

The transport system simply has no mechanism

Most transport systems were designed before the requirement existed. A modification depends on the vendor, the timeline and the budget — while the documents are needed now.

Requests arrive in different shapes

One client sends a spreadsheet, another an email, a third is integrated through an API. Normalising that by hand is separate work on every single shipment.

Manual assembly does not survive the volume

With dozens of shipments you can do the documents by hand. At hundreds it turns into a queue, errors and rejections from the state system.

A forwarder chain multiplies the work

Every link needs its own document. Where there used to be one paper set, there is now a set of electronic documents for each leg.

05The solution

What our service does

It does not replace your transport system and does not require rewriting it. It takes the request in whatever shape you have it and carries the document through to the state system.

01

Accepts a request from any source

A spreadsheet, a file in a folder, an API, an accounting or a transport system — the service assumes sources differ and change over time.

02

Assembles the document in the approved format

The structure follows the format approved by the tax authority, not somebody's interpretation of the document.

03

Validates before sending

Mandatory fields, reference data and consistency. A rejection from the state system costs more than a check on the way in.

04

Signs and sends through EDI

Works with an EDI operator through which the document reaches the counterparty and the state system.

05

Tracks statuses and history

You can see what is signed, what awaits the counterparty, what was withdrawn and what was rejected — per document and across the whole flow.

06

Returns the result to your system

The status and a link to the document go back, so nobody has to watch two interfaces.

Our driver by a branded truck: request, documents and statuses in one app
Last mileOur driver by a branded truck: request, documents and statuses in one app
06Rollout

How we connect

We look at your requests

A handful of real requests in their existing shape is enough. We show the service working on them, before any commitments.

We connect the source

We set up intake from your system, folder or API. Your transport system stays untouched.

We agree the operator and the signature

We work with your EDI operator and your electronic signature — there is no need to change either.

A parallel run

For a while documents are produced in parallel with your current process. We switch over when there are no discrepancies.

07FAQ

Frequently asked

Do we need to change our TMS?

No. The service installs alongside and pulls requests from it or from any other source. That is precisely why it can go live quickly — rewriting a transport system would take months.

We already have an EDI operator. Will it work?

Yes, we work through your operator. There is no need to change the operator or your electronic signature.

Who signs the document?

The parties sign with their own enhanced qualified signatures: the client signs their part, the forwarder theirs. The service prepares the document and brings it to the signature stage but never signs on a person's behalf.

What about a chain of several forwarders?

An order is issued for every link, with the next participant acting as the client. The service produces documents across the whole chain, not just the first leg.

What if requests arrive in Excel?

That is a standard scenario. A spreadsheet is as valid a source as an API: the service parses it and assembles the document.

How long does it take to go live?

A demo is immediate, on your own requests. A pilot usually takes weeks, because the service already exists and runs; the time goes into connecting the source and agreeing things with the operator.

Note. This material is for information only and is not legal advice. Confirm the document procedure with your own EDI operator and legal counsel.

Let us show it on your own requests

Send two or three real requests in any format — we will show how the document is assembled from them and tell you how long connecting will take.

All products →