Section 55 — Duty liability on transit/transhipment

2-minute view

Provides that goods allowed to transit or tranship to another customs station become liable to duty if they do not reach the destination as required. It protects revenue by linking duty relief to proof of due arrival.

Statutory position and legal effect

Section 55 must be applied to the transaction event it actually regulates. It should not be stretched to decide classification, valuation, exemption, assessment or confiscation questions that belong to other provisions. The legal note should therefore identify the statutory actor, the event that activates the section, the consequence of compliance or default, and every connected provision needed to complete the transaction chain.

For this provision, the material compliance question is whether the statutory event has occurred in the manner Parliament and the delegated legislation require. The answer should be supported by contemporaneous system records rather than reconstructed from memory. Where a carrier, custodian, importer, exporter or transhipper is the statutory actor, the SOP should name that actor and assign responsibility for the filing, amendment, permission or closure event.

When a system message is rejected or amended, preserve both the original transmission and the accepted correction. Customs disputes often turn on sequence: whether manifest data preceded unloading, whether entry inward/outward existed at the relevant time, whether OOC/LEO preceded removal/loading, and whether destination arrival closed a duty-free transit movement. A screenshot alone is weaker than a downloadable acknowledgement, message ID, officer order or system log tied to the customs document number.

Allied-law controls must be checked separately. Customs permission cannot legalise goods prohibited by another statute, and a port/airport operational clearance cannot replace the Customs Act event. Conversely, a customs hold may coexist with separate custodian, port, carrier or regulatory charges. The file should therefore identify which legal relationship each payment, detention or release document belongs to.

Official-text rule: Use the current India Code/Gazette wording in opinions, pleadings and statutory filings. This page is an explanatory compliance guide.

Applicability, rights, obligations and decision workflow

1. Track destination arrival acknowledgement.
2. Investigate shortages/non-arrival immediately.
3. Quantify duty exposure where due arrival cannot be proved.

Chapter VIII allows customs-controlled movement without immediate duty payment where goods are genuinely in transit or transhipment. The relief depends on manifest declaration, prescribed documents/messages, security and proof that the goods reached the authorised destination. The gateway customs station therefore needs a closed chain of evidence: arrival manifest, transhipment/transit permission, container/seal identity, carrier movement and destination acknowledgement.

SCMTR is central for sea movements and has been rolled out in phases. As of 5 October 2026, the current 2026 amendment extends the relevant transitional table date to 31 October 2026. Practitioners should check the exact message implementation at the originating and destination customs stations rather than relying on an old EGM/IGM SOP.

Section 56A, inserted in 2026, is conceptually different from ordinary transit/transhipment. It creates a special statutory basis for fishing and fishing-related activities beyond territorial waters. The headline relief is expressly subject to rules and the Board’s procedural regulations. Until the operative customs procedure for the specific transaction is verified, the prudent position is to treat section 56A as an enabling provision rather than assume that every offshore catch is automatically entitled to customs treatment without documentary conditions.

For transit and transhipment, the critical audit question is closure. The original customs station grants movement without immediate duty because the goods are expected to remain under customs control and arrive at an authorised destination. Accordingly, the professional file should reconcile manifest identity, container or package number, seal, transhipment/transit document, carrier, route, bond or security, and the destination acknowledgement. A missing destination event is not just a logistics exception; it can crystallise a customs duty exposure under section 55.

Practitioners should distinguish foreign transit, domestic transhipment to another customs station, international transhipment and special treaty/bilateral arrangements. The prescribed document and security can differ. SCMTR has also replaced or re-engineered several sea-cargo messages, so old manual references to transhipment permits should be checked against the current electronic workflow at both ports.

Section 56A adds a fisheries-specific policy layer to this chapter. Vessel flag status, catch location, traceability, landing port, catch/health records and customs entry will all be material to a defensible claim. Because the statutory relief is conditional on rules and regulations, the chapter hub deliberately separates the enacted entitlement from the still-to-be-verified operational instrument for a particular voyage.

For sign-off, record the responsible person, customs station, document/message number, statutory deadline, acknowledgement/order and exception relied on, if any. If the system route and the statutory wording appear inconsistent, preserve the evidence and escalate through the proper customs channel rather than bypassing the statutory condition.

Provisos, thresholds, timelines and safeguards

The headline rule must be read with the provisos, prescribed forms and delegated instruments applicable on the material date. Where the Act allows relaxation, amendment or sufficient-cause relief, it should be treated as an exception requiring reasons/evidence, not the routine filing path. Penalty ceilings, filing times, payment times and permission requirements are provision-specific; do not borrow a deadline from a neighbouring section.

For 2026 transactions, particular attention is required to SCMTR transition dates, passenger-data regulations, ECL implementation and the newly inserted section 56A. Historical consignments must instead be tested under the law and system regime that applied when the relevant event occurred.

Rules, notifications, circulars and operational instruments

For a live transaction, re-check amendments, implementation dates and customs-station specific notices on the official source before execution.

Case law — provision-specific research matrix

Worked example

A customs transaction triggers section 55 because of duty liability on transit/transhipment. The professional file identifies the statutory actor, material event, system/document evidence, linked delegated law and the consequence if the condition is not met before the goods or conveyance move.

The working paper should separately record the assumed facts, statutory step, evidence, delegated instrument and operational result. If one fact changes—such as customs station, mode of transport, manifest status, prohibition, assessment status, destination or system implementation—the conclusion should be recomputed rather than copied.

Evidence and compliance checklist

• Manifest/report, bill of entry, shipping bill or transit/transhipment document as relevant
• Carrier bill/airway bill, invoice, packing list and container/ULD/seal identifiers
• Customs automated-system acknowledgements, message IDs and amendment trail
• Permissions/orders for entry inward/outward, OOC, LEO, transit/transhipment or departure as applicable
• Custodian/terminal gate, inventory, loading/unloading and movement records
• Exact rule/regulation/notification and port/system implementation notice in force on the event date

For controlled movement, reconcile quantities and identifiers from origin to destination. For delayed or amended filings, retain the explanation and approval because later audit may otherwise see only the final accepted record without the chronology.

Common mistakes and professional traps

• Confusing a commercial logistics event with the separate Customs Act permission/order.
• Using legacy IGM/EGM instructions without checking the current SCMTR implementation status.
• Treating portal acceptance as proof that allied-law restrictions were satisfied.
• Failing to preserve amendment, sufficient-cause or exception evidence.
• Copying a deadline or penalty rule from a neighbouring provision.

Related provisions

• Section 54 — Transhipment of certain goods without payment of duty
• Section 56 — Transport subject to prescribed conditions

Read the connected provisions together while keeping their functions separate: carrier reporting, cargo custody, importer/exporter entry, assessment, physical clearance, manifest closure and transit security are distinct legal events.

Finin2min Q&A

What does section 55 practically control?

What should be checked first?

Identify the statutory actor, customs station, mode of transport, event date, accepted customs message/order and the delegated law in force on that date.

Can a customs-system status override the Act?

No. System status is important operational evidence, but legal entitlement and obligations remain governed by the Act, valid delegated legislation and binding judgments.

What is the safest audit file?

Keep the statutory source, accepted electronic filing, amendment history, transport/commercial documents, permissions/orders and a chronology showing when each customs event occurred.

Primary-source trail

India CodeCBIC Tax InformationGazette / official customs noticesCourt record where relevant

Source review date: 2026-10-05. Historical matters require the law and implementation regime applicable to the material date.

Previous / next