BERNEV / CUSTOMS LAW
Menu

China · EAEU · foreign counterparty

Shipping to Russia: documents, route and Russian FCS dispute risk

Start with the dispute point, not the country in general: what document arrived, which deadline is running, and what does not match in price, classification, origin, payment or route.

Initial review

  1. 1what arrived from the Russian FCS, a bank or a counterparty
  2. 2when the document was received and what has already been sent in reply
  3. 3which shipment, amount or payment is at risk

Routes and documents

Where shipments usually break down

At the first step, the country name matters less than the full chain: product, price, payment, route, supplier, marking, origin and the receipt date of the disputed document.

01

EAEU -> Russia

EAEU: import to Russia, SPOT, DOPP, QR and Russian FCS disputes

This page is not a translation of the general site. It is a working entry point for EAEU shipments: what happened, why it matters, which document to read first, which deadline cannot be missed and what the next route is.

DocumentDOPP, QR, RNPT, UPD, invoice, CMR, contract, payments, request or authority audit actDeadlinereceipt date and any reply already sentRiskprice, code, origin, payment or route
Open route
02

China -> Russia

China -> Russia: supplier, documents, payment and Russian FCS dispute

The China page should not be machine-translated. The Russian entry explains the commercial logic of the transaction; English and Chinese versions are prepared separately after language and PIPL/privacy review.

Documentcontract, specification, invoice, packing list, BL/CMR, payment trail, correspondence, product photosDeadlinereceipt date and any reply already sentRiskprice, code, origin, payment or route
Open route
03

Kazakhstan -> Russia

Kazakhstan -> Russia: EAEU shipment, documents and Russian FCS dispute

The Kazakhstan route is built around the shipment path and EAEU documents: what the supplier side declared, what the Russian authority sees and where the digital trace diverges.

Documentcontract, UPD/invoice, SNA/shipping documents, CMR, RNPT, QR, requestDeadlinereceipt date and any reply already sentRiskprice, code, origin, payment or route
Open route
04

Belarus -> Russia

Belarus -> Russia: transit, EAEU documents and Russian FCS dispute

The Belarus route often involves not only supply but also transit, seals, carriage and proof of goods status. This page brings those issues into one commercial route.

Documentcontract, UPD/invoice, CMR, carriage documents, seal data, RNPT, requestDeadlinereceipt date and any reply already sentRiskprice, code, origin, payment or route
Open route
05

Armenia -> Russia

Armenia -> Russia: EAEU documents, intermediaries and Russian FCS dispute

The Armenia route should not be buried inside a generic EAEU page. Intermediaries, origin, single-window processes, supplier documents and how the Russian authority sees the full chain often matter here.

Documentcontract, invoice/UPD, CMR, origin documents, payments, correspondence, request or authority audit actDeadlinereceipt date and any reply already sentRiskprice, code, origin, payment or route
Open route
06

Kyrgyzstan -> Russia

Kyrgyzstan -> Russia: route, advance data and Russian FCS dispute

The Kyrgyzstan route turns on transport, advance information, intermediaries and evidence that the Russian version of the transaction matches the shipment documents.

Documentcontract, invoice/UPD, CMR, route data, advance registration, payments, request or audit actDeadlinereceipt date and any reply already sentRiskprice, code, origin, payment or route
Open route

English intake

For foreign clients: Russian customs dispute

The English pages are not literal versions of the Russian site. They explain to foreign suppliers, counsel, CFOs and compliance teams which documents the Russian FCS, banks, importers and commercial courts compare in a Russian dispute.

01

China -> Russia

Russian customs dispute support for China-to-Russia trade

Written for Chinese exporters, trading companies, Hong Kong intermediaries and in-house counsel who need a clear route into a Russian customs dispute.

Documentcontract, specification, invoice, packing list, BL/CMR, payment records, correspondence, photographs, and customs request or decisionDeadlinereceipt date and any reply already sentRiskprice, code, origin, payment or route
Open English page
02

Hong Kong -> China -> Russia

Russian customs dispute support for Hong Kong trading chains

This page is for trading companies, intermediaries and in-house counsel when the seller, payer, manufacturer, shipper and Russian importer are not the same entity.

Documentcontracts across the trading chain, invoice, packing list, BL/CMR, payment records, manufacturer documents, correspondence, and Russian customs request or decisionDeadlinereceipt date and any reply already sentRiskprice, code, origin, payment or route
Open English page
03

China logistics -> Russia

Russian customs dispute support for China logistics routes

For freight forwarders, logistics directors and supply-chain teams where the transport file becomes evidence in a Russian customs or bank dispute.

DocumentBL/CMR, route records, Incoterms, carrier correspondence, invoice, packing list, and customs request or audit reportDeadlinereceipt date and any reply already sentRiskprice, code, origin, payment or route
Open English page
04

China equipment -> Russia

Russian customs dispute support for China equipment and electronics

For equipment, electronics and industrial-goods suppliers where product description, HS/TN VED classification, end use, origin or technical evidence is central to a Russian customs dispute.

Documenttechnical description, catalogue, photographs, specification, HS/TN VED code, invoice, origin records, end-use statement, and customs request or decisionDeadlinereceipt date and any reply already sentRiskprice, code, origin, payment or route
Open English page
05

United States -> Russia

Russian customs dispute support for US companies

This page is written for a US corporate visitor, not translated from the Russian site. The first step is to identify the Russian customs event, deadline, document set and evidence route before a Zoom call.

DocumentRussian customs request or decision, contract, invoice, product description, payment trail, route documents and correspondenceDeadlinereceipt date and any reply already sentRiskprice, code, origin, payment or route
Open English page
06

Europe -> Russia

Russian customs dispute support for European suppliers and counsel

This page is built for European corporate users who need a Russian customs-dispute route in English: what happened, why it is risky, which document matters first and what deadline controls the first move.

DocumentRussian customs decision or request, contract, invoice, export documents, route file, payment trail and correspondenceDeadlinereceipt date and any reply already sentRiskprice, code, origin, payment or route
Open English page

Initial contact

To start, one document, its date and a short description are enough

Documents are not uploaded through the website. In Telegram, state what arrived, who sent it, when it was received, and the amount or shipment at risk.