Post-release control: review the response before sending

Because Article 332 of the EAEU Customs Code post-release customs control can reach transactions long after release, declarations, responses and correspondence may remain relevant evidence. Customs may compare the contract with payments, invoices with transport records, product descriptions with the declared classification, value evidence with available comparison data, and a company's treatment of related shipments. Older transactions are harder to reconstruct when documents are dispersed across departments or staff have changed. The exact period, form of customs inspection and response deadlines depend on the applicable provisions of the EAEU Customs Code and the particular control measure. A desk customs inspection is conducted under the rules governing that form of post-release control Article 332 of the EAEU Customs Code. If an audit report is issued, the period and procedure for objections must be taken from the applicable rule and the document itself. Any subsequent decision on value, classification, origin or additional payments must likewise be checked for its own appeal route and deadline under the relevant law Article 358 of the EAEU Customs Code or Article 198 of the Russian Commercial Procedure Code. The practical point is not to treat a fixed period as universally applicable to every post-release measure. The transaction file should be retained and reviewed for as long as the relevant customs-control and record-retention rules may apply.

Do not answer reflexively on the day the request arrives. The first response becomes part of the inspection record and may shape later questions. First identify what customs is examining: value, classification, origin, transaction structure or another issue. Then collect the relevant materials across foreign-trade, finance, logistics, procurement and legal teams; compare them for inconsistencies; and prepare one coherent response. A bundle of unrelated files from different departments is not a substitute for a legal explanation. The response deadline must be taken from the specific request and the applicable provision. Where the law permits an extension, any request for extra time should be made on the statutory grounds rather than assuming a standard extension under Article 313 of the EAEU Customs Code). The cited provision and the specific request should be checked before relying on it for an extension.

A coherent evidential record matters: each document should serve a defined purpose. A collection of disconnected papers usually does not provide that coherence. One strong document unsupported by the rest may be weaker than an ordinary document within a consistent chain. Each document should answer a specific question. Transaction records should show how the price is formed (the price structure under Article 40 of the EAEU Customs Code — base price, additional charges, exclusions, additions and deductions); why this supplier was chosen (alternative quotations and the basis for the choice); how logistics are structured (route, carriers, insurance and transshipment consistent with the Incoterms terms); why a discount was granted (for example volume, seasonality, defect or a long-term relationship, supported by documents); and how the tariff code follows from the product’s characteristics through the GRI and technical documentation. A document that cannot be placed in the evidential chain under Articles 39–45 of the EAEU Customs Code (for value) or the GRI (for classification) does not necessarily strengthen the position; it may simply add volume and create more questions. A practical test for the file is whether the transaction can be reconstructed from contract conclusion through release in about 30 minutes. If not, the file may need further work before the declaration is filed rather than after the first customs request.

Identify and explain inconsistencies before customs does. An internal audit has value only if its findings lead to corrections or documented explanations. Typical inconsistencies include a payment that does not match the invoice; Incoterms terms that do not match the actual freight arrangement; a specification that differs from the declaration; document dates that do not form a logical chronology; a payment currency that differs from the contract currency; or payment from a third-party account. Each can prompt questions about the transaction, valuation or parties involved. Do not conceal a discrepancy. Prepare an explanation supported by documents and make sure it is consistent with the rest of the transaction record. Before filing the declaration, the file can be reviewed from the perspective of a customs inspector so that discrepancies are either corrected or properly documented.