How does ICEGATE filing work in India?

ICEGATE stands for Indian Customs Electronic Data Interchange Gateway.

Its own registration FAQ describes it as the Indian Customs National Trade Portal, developed as a single window for customs and import-export tax matters. Every page carries the same footer: Directorate General of Systems and Data management, Central Board of Indirect Taxes and Customs, New Delhi.

So ICEGATE is not a private service or a broker’s tool. It is the government’s own channel, and it groups what it does into four: registration, electronic filing, e-payment and enquiry.

That word channel matters. Assessment does not happen on ICEGATE. Customs officers work in the system behind it. What you send goes through ICEGATE, and so does everything that comes back: the acknowledgement, the query, the processed document, the release. ICEGATE counts 254 EDI locations, so the port decides where a file goes.

ICEGATE’s registration FAQ puts it plainly. Registration is a pre-requisite for filing all customs related documents online, bills of entry and shipping bills included.

The same FAQ lists sixteen kinds of business that can register. Freight forwarder is one of them, in its own right, separately from customs broker. The list also names:

• customs broker, which the manual still calls a customs house agent;
• non-vessel owning common carrier, console agent, shipping line, shipping agent and airlines;
• custodian, authorised terminal operator and container train operator; and
• importer, exporter, government agency, e-seal vendor, SEZ entity and courier service under ECCS.

Registering is paperless. ICEGATE says no paper application is accepted, and that a digital signature certificate and an Aadhaar card are both mandatory. Your email and mobile number have to be registered with GSTN, and with DGFT if you import or export. The name on the form has to match the PAN.

GSTIN and PAN are validated online, and a one time password goes to both the mobile number and the email address. A part-finished application can be saved for fifteen days. At the end you are issued a system generated ICEGATE ID.

What the ID buys is worth reading closely. ICEGATE lists four things, and three are about knowing where a document is. Documents can be filed. A filed job can be tracked. A positive or negative acknowledgement, carrying the bill of entry or shipping bill number, reaches the registered email address. Duty can be paid online.

An import consignment needs a bill of entry. An export consignment needs a shipping bill. Both are electronic messages, and both start a conversation rather than end one.

You do not have to wait for the goods. ICEGATE says a bill of entry may be filed before they arrive, and stays valid if the vessel or aircraft arrives within thirty days of the date it was presented.

There are five ways in. ICEGATE lists a RES package, a customs service centre, SMTP e-mail, web upload and a webform. The e-mail route is exactly what it sounds like: the message file is attached to an email and sent to that location’s address at icegate.gov.in. One warning about the service centre route, in ICEGATE’s own words. The centre is responsible for all tracking, and ICEGATE cannot give an update on a document filed that way.

Once the file is in, everything that follows is a named message, and ICEGATE publishes the list. These are the ones an operations desk sees.

Three of those ten rows are yours to send. The rest arrive, and each either moves the shipment or stops it.

There is a mandatory list, and there is everything else.

The mandatory list was notified by DGFT in notification 08/2015-2020 of 4 June 2015, and ICEGATE repeats it. Beyond that, it says the supporting documents depend on the commodity, the notification claimed and what the government agency requires.

Count the rows. One of the eight is yours. Every other row starts on somebody else’s desk and reaches you by email, if it reaches you.

eSANCHIT stands for e-Storage and Computerized Handling of Indirect Tax documents. CBIC launched it for paperless processing, and only a registered ICEGATE ID can use it.

The sequence is short. Log in, open eSANCHIT, upload the file, choose the document type, submit. Two reference numbers come back. A DRN identifies the batch, an IRN each document. ICEGATE is specific about which matters next: the group of IRNs goes into the bill of entry, not the DRN.

The order is not negotiable. ICEGATE says supporting documents have to be uploaded first, and only then can the bill of entry be submitted.

The rules on the file itself are strict, and they are where most first attempts fail:

• only PDF is accepted, and the size limit depends on the document type, which ICEGATE puts at 1 MB to 20 MB;
• five documents can go up at a time for a trade filer, ten for a government agency;
• every file needs its own name, and ICEGATE asks for meaningful ones rather than scan001;
• the file is signed with the certificate that signs the bill of entry;
• once a document has an IRN it cannot be deleted, so ICEGATE’s advice is to keep that IRN out of any filing; and
• documents older than thirty days come back from archival, and stay online for seven days.

The instruction that saves the most time is the one people skip. CBIC’s process guide says to ask the issuer, the seller, the shipping line, the airline or the regulator, to render the document as a PDF at source rather than fax or scan it. Where you must scan, CBIC sets a standard: at least 200 dpi, no more than 75 kb per A4 page, one document to one PDF, no staple marks and no folds.

That is a standard aimed at your supplier, not at you. Getting it met is a conversation, and it happens by email.

These are two different failures and they need two different reactions.

The first happens before customs ever see the document. ICEGATE runs its own checks at the gate, and publishes them. The format has to match the published advisory. The ID has to be registered and active, and registered for that customs location and that document type. The file has to be digitally signed.

Fail any of those and, in ICEGATE’s words, the document gets rejected as soon as it reaches ICEGATE for processing. What comes back is a negative acknowledgement. CBIC publishes an advisory of the bill of entry fresh filing error codes, dated 25 March 2026.

If nothing comes back at all, ICEGATE says to contact its helpdesk after two hours.

The second failure happens after the document is with customs, and it is the ordinary one. An officer raises a query. ICEGATE describes it again at examination, where the officer may revise the assessment or query before giving out of charge. A query stops the clock until it is answered.

Now look at what a query asks for. A document. A clarification from the shipper. A certificate the agency has not uploaded. A value the seller has to confirm. Almost none of it is a decision your team can take alone, so the query clock runs inside somebody else’s inbox.

You can at least see where you stand. ICEGATE’s document status enquiry shows where a bill of entry or shipping bill has got to, including the no objection certificate from other agencies. Where an agency’s release order is missing, ICEGATE’s advice is to contact that agency, not customs.

The export side has an after-the-event version of the same story. ICEGATE publishes the response codes that decide whether an IGST refund goes through. They run from SB000 to SB006.

• SB000, successfully validated.
• SB002, manifest not filed. ICEGATE’s instruction is to approach the shipping line, airline or carrier to file the manifest.
• SB006, gateway export general manifest not available. ICEGATE’s answer is that exporters can also approach their shipping line.

Read that again. A common reason an exporter’s money is stuck is that a third party has not filed something. That is not a customs problem. It is a chase.

Go back through the documents table and count the rows you produce yourself. One.

The filing itself is a transmission. Once the pack is complete and the IRNs are in hand, it takes minutes. Completing the pack is the job, and it runs across shippers, agents, carriers and agencies in other time zones. It is usually held together by one coordinator remembering who has not replied.

FreighAI does not file a bill of entry, a shipping bill or anything else on ICEGATE. Direct customs filing stays in the system you already use, with the people licensed to do it. FreighAI works on the chase around it. Spots what is missing in an enquiry and drafts the email asking for it. Follow-ups, chasers and reminders happen on their own, on the same conversation.

The documents are still checked by the person accountable, and the filing still goes out through your broker or your own ICEGATE ID. Two questions worth putting to any supplier who says it helps here:

• 01Here is a booking where the packing list never came and the agency certificate is pending. What does your system send, who to, and when does it send again?
• 02The shipper replies on the fourth day with one of the two. Who is told, what gets updated, and what does a person still retype?

Take one import file where a query came back and one that went straight through, and put the documents next to the dates:

• the date each mandatory document arrived, and who sent it;
• the eSANCHIT upload, the IRNs and anything that went up twice;
• the acknowledgement, positive or negative, and how long it took;
• the query, the reply, and everything in between; and
• the emails asking a shipper or an agency for a document, and how often they went.

The useful question at the end is not who was slow. It is what asked for the document, when it asked again, and what your coordinator was doing while it waited.