Initial assessment
whether the file contains procedural defects or weaknesses in the legal characterisation or evidence
Customs administrative proceedings / offence report and defence
A customs administrative-offence case can involve an offence report, additional assessment and a risk of confiscation. Early explanations become part of the case record, so the alleged offence and evidence should be understood before substantive explanations are signed.
Customs administrative-offence cases under Chapter 16 of the Russian Code of Administrative Offences include proceedings against importers under Article 16.2 of the Russian Code of Administrative Offences (inaccurate declaration of information), Article 16.3 of the Russian Code of Administrative Offences (failure to comply with prohibitions and restrictions), Article 16.7 of the Russian Code of Administrative Offences (submission of invalid documents), Article 16.21 of the Russian Code of Administrative Offences (unlawful use of goods). Work may include challenging a customs penalty by examining procedural defects (Article 28.2 of the Russian Code of Administrative Offences), challenging the legal characterisation of the alleged offence and testing the evidence.
Initial assessment
Tools
whether the file contains procedural defects or weaknesses in the legal characterisation or evidence
that become part of the case record
Common questions
Start with the exact document you received. Identify what it says happened, how the alleged conduct is described, which facts or evidence are already referred to, and when and how the document was received.
Then collect the records for the same episode: the customs declaration, contract, invoice, transport documents, relevant correspondence and any explanations already given. Before providing a detailed factual account, check who is being asked to respond, in what procedural capacity, and whether the proposed explanation is consistent with the existing documents.
A written review can map the allegation against the available evidence, identify factual gaps or inconsistencies, and separate points that can be confirmed from records from points that still require legal verification.
They can. A rushed explanation may create a factual record that does not match the documents or that is broader than the person actually knows. Statements made by an employee or representative should therefore be separated from assumptions about the company's conduct or legal responsibility.
Before responding, compare the proposed explanation with the declaration, transaction documents, correspondence and other evidence. Also identify who is giving the explanation and in what capacity, because personal knowledge, company records and legal conclusions are different things.
The review should show which facts are supported, which statements need qualification, and which procedural rights or consequences require separate verification before a final response is given.
Do not start from a generic label such as "customs dispute" or "administrative case." Identify the exact document, the procedure it belongs to, the date and method of service, and any steps already taken in response.
Keep the envelope, electronic delivery record, acknowledgement or other evidence showing how the document was received. Different requests, decisions, demands and administrative-offence documents may involve different procedural routes, so the relevant deadline has to be checked for the specific document rather than assumed from memory.
A written review can reconstruct the chronology, identify which date or event needs legal verification, and show which next filing or response must be assessed for the current stage.
Describe the matter on Telegram: the document received, its date, the amount at risk and what has already been sent to the other party or authority.
Initial contact
Describe what you received, the date, the amount at risk and what has already been submitted. The first practical step will be clear after review.
Materials on this issue