FORM GST MOV-04 — Movement, interception and detention — prescribed form / control record MOV-04

Form in 2 Minutes

FORM GST MOV-04 is the physical verification report that the proper officer prepares on completion of the physical verification of a conveyance and the goods it is carrying, and serves on the person in charge of the goods and conveyance. It is issued after an order for physical verification in FORM GST MOV-02 (extended, if needed, by FORM GST MOV-03), and its outcome decides the next step: a discrepancy-free verification leads to a release order in FORM GST MOV-05, while a verification that supports detention under Section 129 leads to a detention order in FORM GST MOV-06 and notice in FORM GST MOV-07. Never select the form by filename alone: first identify the legal trigger, operative Rule, tax period and current portal version.

Legal trigger and mapped Rules

• Family rule framework: Section 129 (detention, seizure and release of goods/conveyances in transit) and Section 130 (confiscation), operationalised by Circular No. 41/15/2018-GST (the source that actually prescribes the MOV-01 to MOV-11 form series) and Rule 138B (verification of e-way bill/documents) and Rule 138C (inspection and verification of goods).
• Primary user/system owner: proper officer (issuer of the report) and the person in charge of the goods and conveyance (recipient of the served copy).
• MOV-04 is an officer-issued report served on the transporter/person in charge — it is not a taxpayer-filed return or a self-service portal filing.
• Check effective date and any amendment substituting the form or its instructions; the circular has been read together with subsequent clarificatory circulars on the same procedure.

Field-by-field control checklist

• GSTIN / legal identity and jurisdiction
• Correct tax period, financial year or proceeding reference
• Authorised signatory / verification
• Version-controlled attachments and supporting evidence

The list is a control checklist, not a reproduction of the official blank form. The current GST portal / notified appendix controls the exact field schema.

Portal and filing workflow

1. Identify the exact statutory trigger and current form version.
2. Prepare a reconciled offline working before portal entry.
3. Upload only prescribed and relevant evidence; cross-check names, periods and amounts.
4. Preview the generated form/PDF and obtain signatory approval.
5. Submit through the current portal channel; preserve ARN/acknowledgement and generated PDF.
6. Track deficiency, notice, order, payment or appeal consequence until closure.

Before you click Submit — 10 checks

1. Correct GSTIN/PAN/UIN and jurisdiction.
2. Correct tax period / financial year / order reference.
3. Correct legal form for the trigger.
4. Current version of the form and portal utility.
5. Amounts tie to books, returns, ledgers and notices/orders.
6. All statutory conditions tested separately from portal validation.
7. Attachments are legible, complete and relevant.
8. Signatory and authorisation are current.
9. Payment / pre-deposit / fee is correctly linked where applicable.
10. Final preview and evidence pack are archived before and after submission.

Practical case study

A user reaches FORM GST MOV-04 only after fixing the legal trigger. The preparer first reconciles the underlying books/return/order, checks the operative Rule and current version of the form, completes the portal submission from the approved working, then stores the generated form, ARN/acknowledgement, supporting documents and any later notice or order as one evidence pack.

Evidence and retention file

• Official form/version or portal-generated PDF used.
• Underlying statutory notice, order, invoice, ledger, return or registration evidence.
• Reconciliation/computation supporting each material figure.
• Attachments and approval/signatory record.
• ARN, acknowledgement, payment proof and subsequent communications.
• Snapshot/link to the controlling Rule/notification relied upon.

Common mistakes

• Using a legacy saved form after the Rule or portal schema changed.
• Entering portal values before reconciling the books and statutory trigger.
• Assuming portal acceptance proves legal eligibility.
• Missing limitation, response, payment or pre-deposit dates.
• Failing to retain the exact submitted version and attachments.

Finin2min Q&A