Electronic Waybills for Shipments to Russia: The Carriage UID, Codes 02015 and 02016, and What Your Buyer Will Ask You For

What goes into Box 44 when the carriage runs on an electronic waybill

The mechanism is simple. The declarant in Russia — your buyer or the customs broker acting for them — enters the document type code 02015 or 02016 into Box 44 together with the carriage UID itself. The customs authority can then request the details of that carriage from GIS EPD, the system operated by the Russian Ministry of Transport. The system stores electronic transport documents and makes the data they contain available to state authorities, which means the content of your waybill reaches customs control without anyone submitting a separate set of files.

For you as the shipper this is a change in the status of a document you issue. The electronic transport document stops being an internal matter between consignor and carrier and becomes part of a digital loop that Russian customs reads directly. The practical consequence: the carriage data in the declaration and the carriage data in GIS EPD have to match, because they are no longer compared by eye against a paper copy — they are matched by identifier.

The identifier is generated on your side of the shipment, but it is checked on the Russian side, at the moment the declaration is filed. If the UID reaches your buyer late, in the wrong format or with a single character wrong, customs simply will not find the carriage in GIS EPD — and the request for documents arrives exactly when the truck is already standing in the customs control zone.

When the transport document may still be issued on paper

The move to electronic documents has not abolished paper entirely. The Russian Ministry of Transport has approved, by separate orders, the lists of cases in which a transport document may still be drawn up on paper: for the rail waybill — order No. 407 of 21.11.2025; for the air waybill — No. 102 of 18.03.2026; for freight-forwarding documents — No. 115 of 03.04.2026; for the road consignment note, the order and the request — No. 262 of 01.06.2026.

The typical ground is the absence of technical capability: the consignor cannot generate an electronic document, or the carrier cannot accept one. Additional grounds exist for particular types of carriage. Hence an important point for the exporter: the absence of a UID is not in itself a sign of a problem. What has to be established first is which transport document applies to your particular movement and whether your situation falls within the exception list for that document. Only then does it become clear whether codes 02015 or 02016 appear in Box 44 at all, or whether the transport document is declared in the ordinary way.

The distinction matters most when your buyer starts asking for «the UID» as if every shipment had one. If your carrier issues a paper document on a valid ground, there is nothing to send — what your buyer needs from you instead is a clear written statement of which document was issued and on what basis, so that the declaration can be prepared without waiting for an identifier that will never arrive.

Situations on the shipper’s side and what to do about them

Discrepancies almost always appear at the handover points: the carriage is arranged by one party, the electronic document is transmitted to GIS EPD by an information system operator, and the declaration is filed by a third party in Russia — and nobody compares the identifier until filing. Below are the main situations and the action each one calls for.

Multimodal routings deserve separate attention. Where a consignment travels to a Russian station and is then trucked onward, the documents for the two legs are created under different rules, and the lists of grounds for paper differ between the rail waybill and the road consignment note. If your cargo moves by rail, clarify in advance with your forwarder which document covers each leg and who transmits the data to the system — on rail this is usually handled by the carriage operator rather than by the consignor. The same question applies to a combination of an air leg and an onward road delivery.

It also helps to know who is looking at your data on the other side. Import declarations in Russia are filed with electronic declaration centres, which work remotely: the inspector sees neither the vehicle nor any originals, only data. The customs post where the cargo physically stands handles the operations on the spot. The more precise the identifier in Box 44, the fewer reasons the electronic declaration centre has to ask for anything extra — and the less time your consignment spends waiting for an answer.

What the exporter should do

1. Establish which transport document applies to your shipment: a road consignment note, a rail waybill, an air waybill or a forwarding document.
2. Check with your carrier or forwarder whether the movement falls within the paper cases under the relevant Ministry of Transport order — above all on the ground of no technical capability at the consignor or the carrier.
3. Obtain the carriage UID and make sure it belongs to your consignment and not to the same carrier’s previous run.
4. Get confirmation from the information system operator that the electronic document has been transmitted to GIS EPD and the data is available.
5. Send the UID to your Russian buyer in writing, in the exact character string, before the declaration is filed — not after loading is complete.
6. Reconcile the core carriage data across your document set and the electronic waybill: carrier, vehicle, number of packages, weight, route.
7. Write the obligation to hand over the UID into your contract with the carrier and the forwarder, with a deadline tied to the filing of the declaration — it costs far less than correcting Box 44 after the fact.

If you would rather not carry this coordination between your carrier, your buyer and Russian customs inside your own team, that part is covered by turnkey customs clearance: the document set is checked before filing rather than after an inspector’s request arrives. The same applies to the full delivery chain, where transport documents and declaration data are prepared by one party.

Frequently asked questions

What is the difference between codes 02015 and 02016 in Box 44?
These are document type codes under which the unique carriage identifier may be declared in Box 44 where an electronic transport document is used. Which one applies to your shipment depends on the type of transport document, so the code is selected for the specific carriage rather than reused out of habit.

Our shipment has no UID. Will the declaration be refused?
The absence of a UID does not in itself mean a breach. The law provides for cases in which transport documents are issued on paper, and if your situation is on the list approved by the Ministry of Transport, the transport document is declared without an identifier.

Does the UID actually speed up release?
The identifier does not change the statutory time limits by itself, but it does change the course of the check: once the customs authority receives the carriage data from GIS EPD, there is no need to submit separate documents, and the requests that push the release date back arise less often.

Who is responsible for transmitting the electronic document to the system?
Transport documents are transmitted to GIS EPD through operators of electronic transport document information systems. The declarant remains responsible for the accuracy of the identifier in Box 44 — which is why confirmation of transmission is worth obtaining before the declaration is filed, and why the exporter is the one who has to supply the identifier in time.

Summary

Where a carriage runs on an electronic transport document, the carriage UID is declared in Box 44 of the Russian import declaration under codes 02015 or 02016, which lets customs take the carriage data straight from GIS EPD. Paper transport documents survive for the cases listed in the Ministry of Transport orders, so a missing identifier is not a breach — but the ground has to be confirmed. The real risk for your shipment is not the code itself: it is mismatched data and a wrong identifier, which leave the carriage impossible to match to the declaration. Request a consultation and we will go through your specific consignment.

Send us your shipment details and we will check the transport document set and the Box 44 data before your buyer files the declaration in Russia.

Request a consultation