Lawyer's answers
Questions and answers on post-release customs checks
Questions on desk audits under Article 332 of the EAEU Customs Code, assembling the file, response strategy and the risk of additional assessments or administrative-offence proceedings.
Why does customs release not mean that all risk has ended?
Release of the goods does not end customs control. The applicable post-release control period must be checked under the EAEU Customs Code and Russian implementing rules for the particular form of control; it should not be reduced to a blanket statement that Article 332 gives customs three years for every desk customs inspection. During the relevant period, declarations, responses and correspondence may remain material evidence.
In post-release control, customs may compare the contract with bank payments, invoices with transport records, product descriptions with the declared EAEU CN code, the declared value with other information available to customs, and patterns across repeated shipments. By the time a request arrives, the business may have moved on, documents may be spread across departments and key employees may have left, so reconstruction of an older shipment can itself be a substantial task.
A desk customs inspection is governed by the EAEU Customs Code and national implementing rules. The procedure, any inspection report, the period for objections and the route for challenging a resulting decision must be checked from the actual documents and the rules in force. Article 358 of the EAEU Customs Code concerns appeals, while an application to a Russian commercial court is subject to Article 198 of the Arbitrazh Procedure Code; the two routes do not create identical time calculations.
A shipment therefore remains exposed to post-release questions after release. The relevant control, record-retention and challenge periods should be recorded for the transaction rather than treated as a single universal three-year cut-off.
How should a business respond to the first post-release customs request?
Do not send a substantive response merely because the request has just arrived. First fix the receipt date, read what is actually being requested, reconcile the documents and decide what the response must establish. Once submitted, the first explanation becomes part of the record and later changes may require explanation.
First identify what customs is actually examining—value, classification, origin or the transaction structure—by reading the request and the legal basis behind it. Then collect the relevant records across trade, finance, logistics, procurement and legal; reconcile contradictions; decide what factual explanations are supported; and submit one coordinated response. A bundle of files sent independently by different departments is not a substitute for that work.
Three departments sending disconnected answers can create avoidable inconsistencies. A difference between a document and an explanation may lead to further questions or a broader review, so the response should be coordinated before it leaves the company.
Accuracy matters more than speed, but the company must work within the actual deadline stated by law or the request. Article 313 of the EAEU Customs Code does not create one universal ten-working-day response period for every customs document request. Check whether an extension is available in the particular procedure and request it promptly if additional time is genuinely needed.
Who inside the company should coordinate a post-release customs review?
Use one coordinator with access to management who can reconcile documents and explanations from trade, finance, logistics and procurement. Without coordination, inconsistent versions of the same transaction can emerge.
A common problem is departmental fragmentation: trade supplies declarations and certificates, finance sends bank statements, logistics sends transport documents and procurement sends supplier correspondence. The resulting file may reveal unexplained differences in parties, dates, prices or discounts. Those differences need to be reconciled before the response is finalised.
The coordinator should collect and reconcile the file, approve one explanatory note, control outbound communications and maintain the procedural calendar. If the company lacks the internal capacity to do this, external counsel can take the coordinating role.
From customs' perspective, the company is one respondent even when different departments prepare the underlying material. Contradictory explanations can therefore damage the company's own evidential position.
Should we send only the documents expressly listed in the customs request?
Sometimes the listed documents are enough; sometimes they are not. What should be supplied depends on the request, the legal duty to produce material and what is needed to explain the transaction accurately. The document list should not be treated as a substitute for legal analysis.
If the requested documents do not explain a material point—such as the price structure, a payment difference or an apparent inconsistency—an explanatory note, calculation or relevant translation may be useful. Additional material should be relevant and accurate; it should not be added simply to make the response look larger.
Excess material can also create problems. Unrelated internal correspondence, calculations prepared for a different purpose or documents from other transactions may raise issues outside the request. Before submission, identify what the company is legally required to provide and what additional material is genuinely needed to make the response complete and accurate.
Select documents by relevance, legal production duties and evidential purpose—not by whether they appear favourable. Required material must not be withheld because it may hurt the position. If a document needs context, provide that context accurately; if it is outside the request and there is no duty or strategic reason to submit it, keep it out of the response.
What most often weakens a company's position in post-release customs control?
Three recurring problems reinforce one another: rushed responses without internal review, inconsistent explanations from different departments, and careless wording in written communications.
The first problem is rushing. Customs deadlines can be short, but the applicable period and any right to seek more time depend on the procedure. Use the available time to reconcile documents and approve one position rather than assuming there is always a ten-working-day period or an automatic extension.
The second problem is departmental inconsistency. Customs can compare what trade, finance, logistics and procurement have each supplied. Once conflicting versions are on the record, later explanations have to account for the discrepancy rather than simply replace the earlier version.
The third problem is language that unnecessarily concedes a fact before the legal position is understood—for example, saying that an element of value was never checked or that another party alone chose the code. Such statements may become evidence in a valuation, classification or administrative case. State verified facts; do not speculate about fault.
The common safeguard is a coordinated response reviewed before submission.
Can post-release control develop into a valuation, classification or administrative case?
Yes. A post-release review can identify issues concerning customs value, classification, origin and possible administrative liability. Different consequences require their own procedural acts and legal grounds; a desk inspection does not automatically produce all of them.
For example, a review of repeated shipments may uncover a valuation issue, a classification issue or information relevant to an administrative-offence case. Customs must follow the applicable procedure for each resulting decision or proceeding, and each has its own challenge route and deadlines.
Article 16.2 of the Russian Administrative Offences Code contains several offences and sanctions, some of which are linked to unpaid customs duties and taxes and may include confiscation. Related provisions such as Articles 16.1 and 16.7 have different elements and sanctions. The exact part of the article, date of the conduct and applicable wording must be checked before calculating exposure.
A response to post-release control should therefore be tested against all issues the facts may raise: customs value, classification, the actual transaction structure and possible administrative liability. Under Article 2.1 of the Administrative Offences Code, a legal entity's fault is assessed by the statutory test; it should not be reduced to a generic assertion that the company did not know and could not have known.
What if documents from an older shipment are scattered across departments and archives?
Rebuild the file as one transaction history. An incomplete but transparent and coherent file, with identified gaps and an explanatory chronology, is more useful than an unexplained collection of files from multiple folders.
Start with the key transaction dates—contract, invoice, payment, shipment and release—and locate the evidence for each event. Reconcile the records, identify contradictions and prepare a chronology that explains them. Where a genuine gap cannot be filled, explain the reason and the steps taken to locate the missing material.
If a document has genuinely been lost, say so rather than creating a document retrospectively or presenting a reconstructed record as an original. Keep evidence of attempts to recover the missing material and distinguish clearly between contemporaneous documents and later reconstructions.
Do not send whichever files happen to be found first. Build the transaction picture first, then decide what the response must contain by reference to the request, production duties and evidential purpose.
When should an external specialist be brought into a post-release review?
Earlier is usually better—ideally before the first substantive response. At the latest, external advice should be considered before formal objections if the review is material or the internal team lacks customs-dispute experience.
Early external involvement is particularly useful where the request focuses on value, classification or transaction structure; covers a series of declarations; exposes a material amount; reveals contradictions in the underlying documents; or suggests that administrative liability may be under consideration.
An early review can prevent avoidable inconsistencies, align the departments on verified facts, structure the first response with later challenge stages in mind and create a reliable deadline calendar. It should not manufacture a single 'version'; it should make the company's actual evidence coherent and accurately explained.
Advice obtained only after an inspection report or final decision often has to address statements and documents already placed on the record. The position can still be defended, but options may be narrower than they were before the first response.
Which post-release deadlines require the closest control?
Post-release control involves several distinct procedural deadlines. Missing one can limit a particular objection or challenge route, so each deadline should be calculated from the actual procedural document.
Do not use one generic timetable for post-release customs work. The response period for a document request depends on the legal basis of that request; the period for objections depends on the form of control and the resulting act; Article 358 of the EAEU Customs Code governs customs appeals; Article 198 of the Arbitrazh Procedure Code generally provides a three-month court-filing period, subject to its own calculation rules; and Federal Law No. 289-FZ Article 67 concerns refunds and setoff. Record each deadline separately from the document that triggers it.
For customs-law administrative offences, Article 4.5(1) of the Russian Administrative Offences Code generally sets a two-year limitation period, not a blanket one-year period. A ruling in an administrative-offence case is normally challenged within the period prescribed by Article 30.3, subject to the applicable version and service date.
Missing an objection or appeal deadline can materially weaken or close a particular procedural route. On receipt of every customs document, record the actual receipt date, identify the legal nature of the document and calculate the relevant response or challenge period from the rule that applies to it.
How can a company reduce post-release risk across repeated shipments?
For repeated shipments, use one documentary standard, periodic internal review and repeatable support for classification and customs value rather than rebuilding the file after every request.
Useful tools may include an advance classification decision for a recurring product where appropriate, a contract structure that records how price changes and discounts work, Incoterms terms that match the actual logistics, a document-retention policy and periodic review of recurring customs risks. The validity period, fee and procedural requirements for an advance classification decision should be checked against the rules in force when the application is made.
Larger importers may also assess whether Authorised Economic Operator status under the EAEU Customs Code is commercially appropriate and maintain internal controls consistent with a lower-risk customs profile. If the company discovers an error, the legal consequences of voluntary disclosure or correction depend on the specific offence and procedure; Article 16.4 of the Administrative Offences Code is not a general amnesty for customs offences.
A periodic review of recurring imports can be cheaper than reconstructing multiple transactions during a live customs review. The business case depends on shipment volume, recurring exposure and the complexity of the goods.