Resources  /  Playbooks

Shipping Bill Error Codes: ICEGATE, EGM and BE

Four different systems answer an exporter with a code, and they do not use the same alphabet. This is every code each one publishes, what it actually means, who has to move, and the fix, with the government document behind each family named.

What a customs error code is

A customs error code is the short response Indian Customs returns against a document that failed a validation, and the code you are holding belongs to one of four different systems: the SB series comes from the IGST refund matching that ICES runs against GST returns, single letters come from the export general manifest, plain numbers come from the shipping bill transmission to DGFT, and the three digit CACHI01 series comes from bill of entry filing. Reading the code correctly starts with knowing which of those four raised it, because the same number means different things in different families.

In one line: SB codes are about your refund, letters are about the manifest, plain numbers are about DGFT transmission, and the three digit series is about a bill of entry.

Where to read your own codes

Every family below is visible to the person who filed the document, not only to an officer. The IGST response code for each shipping bill appears in your ICEGATE login under the GST validation status view. The EGM position and the DGFT integration status both appear under the public enquiries on ICEGATE, by shipping bill number and date or by a date range for an IEC. Bill of entry filing errors come back on the acknowledgement for the job you filed.

Almost every enquiry asks for the same four things: shipping bill number, shipping bill date, port code and IEC. If you are working from a stack of paper and the port code is the field you always have to hunt for, the free shipping bill extractor reads those fields off the document so you can paste them into the enquiry instead of squinting at a scan.

Shipping bill error codes for IGST refund: SB000 to SB006

These are the response codes ICES returns when it matches your shipping bill against the invoice data GSTN transmits. They are published by the Directorate General of Systems in its guide on IGST refunds in ICES, and repeated in customs house public notices. The wording below follows the official tables.

CodeWhat it meansWho has to actThe fix
SB000Successfully validated. GSTIN, shipping bill number and invoice number match between the GST and Customs databases, so the bill is ready to be picked up in a refund scroll.Nobody, usuallyNo action. If the money still does not arrive, read the SB000 exceptions below, because a validated bill can still be held back.
SB001Invalid SB details. The combination of shipping bill number, date and port code in the invoice transmitted from the GST system does not match the shipping bill held at Customs.ExporterAmend the invoice in GSTR-1 through Table 9A with the correct shipping bill details. The usual cause is a typing error at the time of filing GSTR-1 or Table 6A.
SB002EGM not filed. The export general manifest that closes out the sailing has not reached the system for that shipping bill.Shipping line, airline or carrierAsk the carrier to file the EGM immediately. If the EGM was filed but rejected, it is sitting in the EGM error queue under one of the letter codes further down this page.
SB003GSTIN mismatch. The GSTIN declared in the shipping bill is not the GSTIN used to file the corresponding GST return.ExporterAmend GSTR-1 through Table 9A. Note that the shipping bill itself cannot be amended once the EGM has been filed, so the correction has to happen on the GST side.
SB004Record already received and validated. GSTN transmitted the same shipping bill and invoice record twice, and the earlier one was already validated by ICES.NobodyNo action required. This is a duplicate, not a rejection.
SB005Invalid invoice number. The invoice number in the invoice table of the shipping bill does not match the invoice number declared in GSTR-1 for the same supply. The common causes are a typing error, or an exporter running one invoice series for GST and another for export.ExporterIf the error is in GSTR-1, amend it through Table 9A. If the wrong number is in the shipping bill, no amendment is possible once the EGM is filed, and rectification runs through the customs house, which publishes its own document set for it.
SB006Gateway EGM not available. For cargo moving through an inland container depot, the gateway EGM was either not filed electronically or is stuck in an error of its own. A manually filed gateway EGM does not count.Shipping line and gateway port CustomsFile the train or truck summary as soon as the cargo leaves the depot, make sure the carrier lists the depot shipping bill in the EGM it files at the gateway port along with the transference copy, and get any mismatch amended at the service centre with the proper officer's approval.

Why a shipping bill can show SB000 and still not pay

SB000 means validated, not paid. Customs publishes six reasons a validated bill stays out of the money, and they account for most of the "my code is fine but there is no credit" cases:

  • The export went under bond or LUT, so no IGST was paid and there is nothing to refund.
  • The shipping bill carries several invoices and only some of them validated with SB000, while the others are stuck on another code.
  • A higher rate of drawback was claimed on that bill, which makes it ineligible for the IGST refund.
  • The claim is below one thousand rupees, in which case the scroll amount becomes zero automatically.
  • There is an alert or a suspension on the IEC in ICES. The bill appears in the temporary scroll and drops out of the final one.
  • The bank account is not validated in PFMS. Same symptom, different cause, and the PFMS codes are listed further down this page.

The last two are the ones exporters miss, because the response code stays green the whole time. If your incentive claims lean on these bills, the sequencing in eBRC for RoDTEP and drawback claims is worth reading alongside this, and the refund mechanics sit in eBRC for GST refund on exports.

SB105: invalid shipping bill number

SB105 is a separate response and it means "invalid shipping bill number". ICEGATE publishes the precise trigger: the port code given is not an SEZ port and the shipping bill number does not have a valid length of seven digits for an electronic shipping bill, six for a manual one, or five for a courier shipping bill. It is corrected the same way as SB001, by amending the details in GSTR-1 through Table 9A.

EGM error codes: the single letters

When an EGM is filed but fails a check against the shipping bill, it is submitted with an error flag and the bill moves into the EGM error queue carrying that letter. Two lists are published, and they differ because the failure happens in two different places. These are the letters behind an SB002 at a gateway port.

CodeWhat it meansWho has to actThe fix
CContainer number mentioned in the shipping bill and in the EGM do not match.Carrier or exporter, through CustomsIf the EGM is wrong, request an EGM amendment of the update type at the service centre for the proper officer to approve. If the shipping bill is wrong, the container number has to be amended in the bill.
NTotal number of containers in the shipping bill and in the EGM do not match.Carrier or exporter, through CustomsIf the EGM is wrong, a delete amendment removes the bill from the EGM and an add amendment puts it back with the correct details, each approved by the proper officer. If the shipping bill is wrong after stuffing, the longer correction route below applies.
PNumber of packages in the shipping bill and in the EGM do not match.Carrier or exporter, through CustomsAmendment of the package count. Chennai Customs assigns this one to its EGM cell.
RRotation number is not mentioned in the shipping bill and the EGM.Exporter or brokerThe rotation number is updated, through ICEGATE or the service centre.
QStuffing report has not been uploaded.Customs, preventive officer at stuffingThe stuffing report has to be uploaded before the bill can clear the queue.
TNature of cargo in the shipping bill and in the EGM do not match.Carrier or exporter, through CustomsAmendment of the nature of cargo, approved by the officers who handle EGM amendments at that port.
LThe let export order date in the shipping bill is later than the sailing date in the EGM. This happens when a let export order is cancelled for an amendment and granted again after the sailing report was already entered.CustomsThere is no amendment route. The bill is taken out of the queue by an officer using the forceful removal option, so this one goes to the EGM cell rather than to your broker.

For cargo that started at an inland container depot, the mismatch is between the truck or train summary and the gateway EGM, and the published list behind SB006 is shorter.

CodeWhat it meansWho has to actThe fix
MThe gateway port code given in the truck summary is different from the actual gateway port.Customs at the depotRectified in the transhipment details after verification of facts by the export officer at the depot.
NNumber of containers does not match.Gateway port CustomsVerification and updation at the gateway port, in cases where the mismatch is caused by cargo being consolidated into different containers.
CContainer number does not match.Gateway port CustomsSame route as N above.
TNature of cargo does not match.Gateway port CustomsSame route as N above.
LLet export order date is later than the sailing date.Customs at the depotRectified in the transhipment details after verification of facts.

Two things are worth saying plainly. There is no single consolidated EGM error code list published by CBIC in the way the bill of entry list is published, so these letters come from customs house notices and from the Directorate General of Systems guide rather than from one master file. And an EGM sitting in error is not the same thing as an EGM that was never filed: the first has a letter, the second is simply absent, and only the second is fixed by asking the carrier to file. Both stall the same downstream things, including drawback and the closure trail described in how shipping bills actually close in EDPMS.

DGFT shipping bill transmission codes: 0, 3, 9, 10, 16, 21 and 23

A shipping bill that is fine at Customs can still fail to land at DGFT, and when that happens the DGFT shipping bill integration status enquiry on ICEGATE returns a plain number rather than an SB code. This is the family that matters if your bill is invisible on the DGFT side.

CodeWhat it meansWho has to actThe fix
0The shipping bill integrated successfully at DGFT's end.NobodyNo action. This is the code you want to see.
3The table could not be added due to some error.Exporter, then CustomsUse the DGFT retransmission facility described below, and take it to the customs location if the retransmission does not clear it.
9The table could not be added due to a duplicate record.Exporter, then CustomsSame route. A duplicate usually means the bill was already sent once.
10Data error in some other related table.Exporter, then CustomsSame route.
16Parent record missing.Exporter, then CustomsSame route.
21Invalid let export order, or a let export order dated earlier than the shipping bill.CustomsA date problem in the bill itself, so it goes back to the customs location that granted the order.
23The FOB value in rupees is missing or invalid.CustomsA value problem in the bill, corrected at the customs location.

The retransmission route, and the six reasons it refuses

ICEGATE publishes a self service facility for exactly this. After logging in, the DGFT retransmission facility for shipping bills takes the shipping bill number, shipping bill date, port code and IEC, sends the request to ICES, and ICES passes it to DGFT. ICEGATE states the process takes roughly forty eight hours, and a separate status enquiry shows what happened.

The request does not always go through, and ICEGATE lists the six answers it can return instead: invalid shipping bill number or date; EGM not filed; the shipping bill is provisionally assessed; the EGM date must be earlier than today's date; the shipping bill was already recorded for DGFT transmission today; and the shipping bill does not contain a licence, DEPB, DFIA or RoSCTL claim, or the drawback scroll has not been generated. Four of those six are really telling you to fix something else first.

Once the bill is at DGFT, the realisation side of the file becomes the live question rather than the transmission. That is the ground covered in why an IRM does not show on DGFT and how to fix it, and it is the point at which the eBRC exporter app takes over the chore, because a certificate is filed against the shipping bill that made it across.

Bill of entry error codes: the full ICEGATE filing list

This is the longest list of the four and the only one Customs publishes as a single file. It is the acknowledgement error list for a bill of entry filing, carried in the CACHI01 message, and every code is a three digit number in a band that tells you which part of the declaration failed. The bands are worth learning on their own: a 1 in front is the header, a 2 is the invoice, a 3 is the item, a 4 is a licence or a single window declaration, a 5 is a bond or a GST notification, a 6 is the manifest, a 7 is the container, and an 8 is a duty notification.

The wording below is reproduced exactly as it is published, including the spelling. That is deliberate: if you paste the message your broker sent you into a search box, the string has to match. Code 000 is not an error at all, it is the acknowledgement that the bill was submitted.

Reading the bands: 100s header, 200s invoice, 300s item, 400s licence and single window, 500s bond and GST, 600s manifest, 700s container, 800s duty notifications.

Codes 000 to 199: header, importer and broker

CodeError, worded exactly as it is published
000BE Submitted
100Submission Stopped by System Manager
101Type of BE wrong
102DIP_DEF Flag wrong
103CHA No. not registered
104Port of Origin invalid
105IEC/BRANCH INVALID/ invalid
106Port of Shipment invalid
107Country of Origin invalid
108Country of Consignment invalid
109Importer Type wrong
110Green Channel Flag wrong
111Section 48 Flag wrong
112Mode of Transport Flag wrong
113Prior BE Flag wrong
114First Check Flag wrong
115Kachcha BE Flag wrong
116High Sea Sale Flag wrong
117Orignal Buyer details missing
118Orignal Buyer details not required but present
119Warehouse BE details not required for type
120problem in Sec 48 (Container Details)
121Container Details Cannot be there for Air consigments
122Container Details Missing
123BE is already in AC's queue for Section 48 Approval
124IEC Blackliksted
125IEC Suspended
126IEC Cancelled
127IEC Not Registered
128IEC Branch Slno Should not be Blanck or Negative
129Importer Name/Address/City/Pin is must for Non standard IEC
130Branch Slno should be zero for Non standard IEC
131Branch Slno Does Not exists
132CHA Licence Expired
133WBE Details Missing for Ex-bond BE
134WBE Details not matching for Ex-Bond
135Package Code/UQC Cannot be Null for Ex-Bond
136Package Code/UQC Wrong for Ex-Bond
137Declared quantity exceeds available no. of units ins WBE
138WBE not Out of Charged
139Warehousing Date Not updated for the WBE
140BE Already Submitted
141CHA Licence has been suspended
142CHA Licence has been cancelled
143Invalid Payment Method Code
144Invalid AD Code
150Job Submitted for Section 48 Approval
151Currency Code invalid (in Exchange Details)
152Standard Currency Flag wrong (in Exchange Details)
153Currency is NOT a notified Currency (in Exchange Details)
154Exchange Rate/Unit in Rs./Effective Date should not be NULL for Non Notified Currencies (in Exchange Details)
155Bank Name/Certificate Number/Date should not be NULL for Non Notified Currencies (in Exchange Details)
156Exchange rates not available
157Exchange Rates not Updated in System
161IEC not registered - HSS
162IEC Branch Slno Should not be NULL or Negative- HSS
163IEC Branch Slno Not registered - HSS
164Importer Name/Address/City/Pin is must for Non standard IEC - HSS
170Container Details not Present
171Invalid Commissionerate Code
175Duplicate Record found
176Duplicate Record found in Exchange
177Duplicate Record found in Permission
178Duplicate Record found in High Sea Sale
179Data Error
180Problem in Duty related parameters. Check CTH/CETH/Notn. etc.
181SQL Error
182SQL Error
183SQL Error
184SQL Error
185SQL Error
186SQL Error
187SQL Error
188SQL Error
189SQL Error
190SQL Error
195Central Excise Certificate Required
196Permission Code wrong
197Reasons for Request (permission)
199X Bond BE not allowed through EDI Submission

Codes 201 to 290: invoice, freight, insurance and valuation

CodeError, worded exactly as it is published
201Invoice Serial Number Cannot be Null or Negative or Zero
202Actual Invoice Number Cannot be Null
203Invoice Date is wrong
204Supplier Name cannot be Null
205Invoice Value Cannot be Null or Negative or Zero
206Invoice Currency Cannot be Null
207Terms of Invoice wrong
208Invoice Currency invalid
209Exchange details missing for Invoice Currency
210Freight Rate Or Amount Cannot be Null for invoice term FOB
211Insurance Rate Or Amount Cannot be Null for invoice term FOB
212Insurance Rate Or Amount Cannot be Null for invoice term CF
213Freight Rate Or Amount Cannot be Null for invoice term CI
214Both Freight Rate and Amount Cannot be Present
215Freight Rate Cannot be Zero or Negative
216Freight Value Cannot be Zero or Negative
217Freight Currency is Must for Freight Value
218Freight Currency Cannot be Present when Freight Value is null
219Freight Currency invalid
220Exchange details missing for Freight Currency
221Both Insurance Rate and Amount Cannot be Present
222Insurance Rate Cannot be Zero or Negative
223Insurance Value Cannot be Zero or Negative
224Insurance Currency is Must for Insurance Value
225Insurance Currency Cannot be Present when Insurance Value is null
226Insurance Currency invalid
227Exchange details missing for Insurance Currency
228Both Miscellaneous Rate and Charges Cannot be Present
229Misc. Rate Cannot be Zero or Negative
230Misc. Charges Cannot be Zero or Negative
231Misc. Currency is Must for Misc. Charges
232Misc. Currency Cannot be Present when Misc. Charges is null
233Misc. Currency invalid
234Exchange details missing for Misc. Currency
235Both Loading Rate and Charges Cannot be Present
236Loading Rate Cannot be Zero or Negative
237Loading Charges Cannot be Zero or Negative
238Loading Currency is Must for Loading Charges
239Loading Currency Cannot be Present when Loading Charges is null
240Loading Currency invalid
241Exchange details missing for Loading Currency
242Both Agency Commission Charges and Rate Cannot be Present
243Agency Commission Rate Cannot be Zero or Negative
244Agency Commission Charges Cannot be Zero or Negative
245Agency Commission Currency is Must for Agency Commission Charges
246Agency Commission Currency Cannot be Present when Agency Commission Charges is null
247Agency Commission Currency invalid
248Exchange details missing for Agency Commission Currency
249Landing Rate cannot be Zero or Negative
250High Sea Sale Load rate/Amount is must for Hea Sea Sale
251High Sea Sale Load Rate cannot be Zero or Negative
252High Sea Sale Load Amount cannot be Zero or Negative
253High Sea Sale rate/Amount should be null for non HSS
254Discount Rate cannot be Zero or Negative
255Discount Amount cannot be Zero or Negative
256Nature of Transaction wrong
257Terms of Payment wrong
258Item Details not found for this invoice
259Invoice Details not entered
260Invoice value is not tallying with item value
261SVB Number/Date blank
262SVB Details Wrong
263SVB Flag Wrong
264SVB Load on Assessable Value is Wrong
265SVB Load on Duty should be blank for SVB Flag - A
266SVB Load on Duty is Wrong
267SVB Load on Assessable Value should be blank for SVB Flag - D
268Both SVB Load on Assessable Value and Duty are required for SVB Flag - B
269SVB Provisional/Final Flag Wrong for SVB Flag -A
270SVB Provisional/Final Flag Wrong for SVB Flag -D
271SVB Provisional/Final Flag Wrong for SVB Flag-B
276Ex-Bond Invoice Serial Number Wrong /Not available in WBE
277Ex-Bond Invoice Serial Number Wrong / Not available in WBE
278Invoice Slno and Actual Invoice number not matchin in Ex-bond
281Invalid Third Party Country Code
282Check Third Party Name and Address
283Third Party Country is missing bud Name/Address is available
284Invalid Authorised Economic Operator Country Code
285Authorised Economic Operator is missing but Country Available
286Authorised Economic Operator country is missing but Operator available
287Invalid Buyer Seller Relationship Flag
288Invalid OBIN/AEO
289OBIN and IEC not linked
290Invalid AEO Role

Codes 301 to 399: item, classification, quantity and scheme

CodeError, worded exactly as it is published
301Invoice serial number cannot be null in item details
302Item Serial Number cannot be null
303Invoice serial Number cannot be negative or zero
304Item Serial Number cannot be negative or zero
305Invoice Details Not exists for invoice number but items present
306Item Description must be entered
307Quantity cannot be null
308Quantity cannot be Negative or Zero
309Unit Price cannot be null for inv / item no
310Unit Price cannot be Negative or Zero
311UQC wrong
312Brand name should not be null
313Model should not be null
314Country of Origin wrong
315Invalid RITC/RITC cannot be null
316Invalid CTH/CTH cannot be null
317Invalid CETH/CETH cannot be null
318Preferential/Standard duty code Wrong
319RSP Flag Wrong
320Re-Import Flag Wrong
321Re-Import details missing
322Re-Import Details not required
323Quantity as per CTH cannot be Negative or Zero
324Quantity as per CTH(2nd spec.) cannot be Negative or Zero
325Quantity as per antidumping cannot be Negative or Zero
326Quantity as per tariff value cannot be Negative or Zero
327RSP details missing
328RSP Details not required
329Wrong Licence Code
330Scheme Code Notn details missing
331Scheme Code Notn details not required
332Item Details not entered
333Quantity as per CTH wrongly entered
334Quantity as per CTH not entered
335Licence Details not available for this item
336First Four Chars. of CTH and CETH not Matching
340Problem in Licence Details
341SVB Number/Date Blank
342SVB Details Wrong
343SVB Flag Wrong
344SVB Load on Assessable Value is Wrong
345SVB Load on Duty should be blank for SVB Flag - A
346SVB Load on Duty is Wrong
347SVB Load on Assessable Value should be blank for SVB Flag - D
348SVB Provision/Final Flag Wrong
350CTH and RITC_CD not matching
351Debit Value less than Actual Cif value for Licence
352Invalid Reimport Notification/Slno
353Export Freight/Export Insurance should be null in Reimport Details
354BCD Amount/CVD Amount should not be null in reimport details
355Export Freight/Export Insurance should not be null in reimport details
356BCD Amount/CVD Amount should be null in reimport details
357BCD Amount/CVD Amount should be Zero in reimport details
358Invalid Manufacturer Country Code
359Invalid Source Country Code
360Invalid Transit Country Code
361Invoice Serial Number Cannot be Null or Zero or Negative in RSP Details
362Item Serial Number Cannot be Null or Zero or Negative in RSP Details
363Serial Number of RSP Cannot be Null or Zero or Negative in RSP Details
364Retail Sale Price Cannot be Null or Zero or Negative in RSP Details
365Quantity cannot be Null or Zero or Negative in RSP Details
366Item Details missing for the rsp
367Item not Declared as RSP item but rsp details present
371Invoice Serial Number Cannot be Null or Zero or Negative in Re_Import Details
372Item Serial Number Cannot be Null or Zero or Negative in Re_Import Details
373Notification Number Cannot be Null in Re_Import Details
374Notification Serial Number Cannot be Null in Re_Import Details
375Shipping Bill Number Cannot be Null or Zero or Negative in Re_Import Details
376Shipping Bill Date Cannot be Null in Re_Import Details
377Shipping Bill Invoice Serial Number Cannot be Null or zero or negative in Re_Import Details
378Shipping Bill Item Number Cannot be Null or Zero or Negative in Re_Import Details
379Shipping Bill Port Cannot be Null in Re_Import Details
381Invoice Serial Number Cannot be Null or Zero or Negative in Licence Notification Details
382Item Serial Number Cannot be Null or Zero or Negative in Licence Notification Details
383Notification/Slno cannot be null in Licence notification details
384Licence Notification 034/97 not valid with the licence
385IEC Not Registered as EOU
386Invalid Scheme Notification
387Item Details missing for the reimport
388Item Not declared as reimport but reimport details present
389Item details missing but scheme details present
390Additional Duty Exemption Requied Flag Wrong in Licence Notification Details
391Ex-Bond Item Serial Number Wrong / Not available in WBE
392Ex-Bond Item Serial Number Wrong / Not available in WBE
393Invalid CUS_CEX_NOTN Flag
394Invalid End Use Code
396Invoice Number Cannot be Null or Zero or Negative in sbe Duty Details
397Item Number Cannot be Null or Zero or Negative in sbe Duty Details
398Item Details missing for the sbeduty
399GST Levy Notn. Not Declared

Codes 401 to 450: licence and authorisation debit

CodeError, worded exactly as it is published
401Invoice Serial Number Cannot be Null or Zero or Negative in LIC Details
402Item Serial Number Cannot be Null or Zero or Negative in LIC Details
403Registration Number in LIC details Cannot be Null
404Registration Date in LIC details cannot be Null
405Licence Code in LIC details cannot be Null
406Wrong Licence Code in LIC Details
407Invalid Licence Registration Number
408No Such Licence
409Licence Fully Debitted - No Balance Available
410Licence Agency Mismatch
411Licence Mismatch
412Licence - Less Value in Export FOB
413Invalid / Expired Licence
414Licence -Invalid Doc Type
415Licence - Less Value (Duty)
416Licence - Less Value(Quantity)
417Licence Rejected
418Licence - Invalid Notification
419Bond Required for this Licence
420Licence - Less FC Value
421Amendment Pending for this Licence
422Licence Cancelled
423Item Details Missing but Licence Details present
424Item Slno in licence cannot be null
425Bond No. Required for this licence
426Scheme Code Mismatch in Licence and item
427Slno in Lic is not matching/not available in Actual Licence
450Problem in Debitting of Licence

Codes 451 to 492: single window and participating agency data

CodeError, worded exactly as it is published
451Inv. No. Cannot be Null or Negative or Zero in SW info type details
452Item No. Cannot be Null or Negative or Zero in SW info type details
453Invalid Info Type Code
454Invalid Info Qualifier Code
455Invalid Info Code
456Info Text/Info Mesurment/UQC is/are not required for Info Qualifier
457Info Text is null
458Info Code/Info Measurement/UQC is/are not required for Info Qfr
459Info Measurement/UQC is null
460Info code/Info text is not required for the info qfr
461Item table Details are not available for SW info type
462Inv. No. Cannot be null or negative or zero in SW Const Details
463Item No. Cannot be null or negative or zero in Sw Const Details
464SW Info Type Table details are not available for SW Const.
465Inv. No. Cannot be null or Negative or Zero in SW control Details
466Item No. Cannot be null or Negative or Zero in Sw control Details
467Invalid Control Code
468Invalid Control Result Code
469SW info type details not avilable for this SW Control
470Inv. No. Cannot be Null or Negative or Zero in SW Product Details
471Item No. Cannot be Null or Negative or Zero in SW Product Details
472SW Info type Table Details are not available for this SW product
473Inv. No. Cannot be Null or Negative in Statement Details
474Item No. Cannot be Null or Negative in Statement Details
475Invalid Statement Type/Code
476Item Details are not available for Declaration Statement
477Inv. No. Cannot be null or negative in Supp Docs Details
478Item No. cannot be null or negative in Supp Docs Details
479Invalid Document Code/Type
480Item Details are not available for Supp Doc Details
481Mandatory Declaration/Undertaking Missing
482Manufacturer Name/Add/Country/src Cntry/transi cntry is blank for FS
483Product Details are required but not declared for Agency DC
484Mandatory Info Type Details are missing for this item
485Mandatory Info Qualifier Details are missing for this item
486Single Window Details Missing
487Invalid PGA Except Category code and Slno
488Info Measurement /UQC is null or Invalid UQC
489Info Text is not required for this info qualifier
490Mandatory Control Information Missing
491Wrong Control Information
492Duplicate Control Information at BE Level

Codes 501 to 507: bond

CodeError, worded exactly as it is published
501Bond Code Invalid
502Bond Number Cannot be Null
503Invalid Bond Number
504Bond Not Yet Credited
505Bond Already Expired
506Bond Already Closed
507Bond Not Available

Codes 521 to 552: GST notifications and certificates

CodeError, worded exactly as it is published
521Invalid GST Addl. Flag
522Invalid GST Notn Type
523Invalid GST Levy Notn/Slno
524Invalid GST Exemption Notn/Slno
525Duplicate records found for IGST/GST Cess notn/slno
551Certificate Type Invalid
552Certificate Number/Date Cannot be Null

Codes 601 to 665: manifest, arrival and bill of lading

CodeError, worded exactly as it is published
601UQC wrong in IGM/IR Details
602PACKAGE CODE wrong in IGM/IR Details
603Prior/Advance BE Inward Date should be NULL
604In Advance BE IGM Rotation Number/Year should be NULL
605IGM Rotation Number/Year is must for Prior BE
606In Prior BE IGM/IR Number/Year should be NULL
607Inward Date should NOT be NULL
608IGM/IR Number should NOT be NULL
609Gateway IGM Rotation Number/Year is Must
610Gateway Inward Date is Must
611Total Packages Should NOT be Negative/Zero or Null
612Gross Weight Should NOT be Negative/Zero or Null
613MAWB/BL Number Should NOT be Null
614MAWB/BL Date Should NOT be Null
615HAWB/HBL Date is must when HAWB/HBL Number is present
616HAWB/HBL Date cannot be present when HAWB/HBL Number is not present
617IGM/IR Details not entered
618BL No. can not be less than 2 characters
619Special Charters not allowed in BL Number. Only Alphabets and Numerals are allowed
620MAWB Number cannot be less than 11 characters long
621Special Charters not allowed in HAWB/House BL Number. Only Alphabets and Numerals are allowed
622Master BL/House BL Already Exists. Prior BE cannot be filed
623Master BL/House BL Already Exists. Advance BE cannot be filed
624IGM/IR is not Prior IGM. Prior BE cannot be filed
625Master already exist, Prior BE can not be filed
626IGM/IR DT wrong
627Gateway IGM Date Wrong
628Reporting Port Wrong
629IGM/IR Waiting for Inward Entry
630Cargo is a transhipment Cargo. BE cannot be filed against this line
631Flight Arrival Date Not Updated/Flight Not Arrived yet
632Total Pacakges not Matching with the IGM/IR Line
633UQC Not Matching with the IGM/IR Line
634Gross Weight Not Matching with IGM/IR Line
635IGM/IR Not Submitted OR BL/HBL Not Available in IGM/IR
636IGM/IR Not Submitted OR MAWB/HAWB Not Available in IGM/IR
637Invalid MAWB Number
638IGM/IR Not Submitted
639Wrong BL No./BL Date or matching BL No./BL Date Not available in IGM/IR
640Wrong MAWB No. or matching MAWB No. Not available in IGM/IR
641Wrong HBL No./HBL Date or matching HBL No./HBL Date Not available in IGM/IR
642Wrong HAWB No. or matching HAWB No. not available in IGM/IR
643Transhipment Permit Filed against this Line. BE not allowed
644Wrong/ Invalid Gateway Port code
645IGM Line belongs to some other Port. BE cannot be filed in this port
646Transhipment Permit not given. Cannot File BE
661IGM details not required for X-bond BE
662Exchange Details not required for X-bond BE
663Permission Code not required for X-bond BE
664HSS details not required for X-bond BE
665Container Details not required for X-bond BE

Codes 701 to 708: container

CodeError, worded exactly as it is published
701LCL/FCL Flag wrong
702Container Number Cannot be Null
703Seal Number Cannot be Null
704IGM/IR Number not exists in IGM/IR Details
705In Advance BE IGM Rotation Number/Year should be NULL in container details
706IGM Rotation Number/Year is must for Prior BE in container details
707In Prior BE IGM/IR Number/Year should be NULL in Container Details
708Container Numbers Not Matching With IGM/IR

Codes 801 to 999: duty notifications and GST declaration

CodeError, worded exactly as it is published
801Invalid Basic Customs Notification(BCD)/Slno
802Invalid Excise Notification(CVD)/Slno
803Invalid GSIA Notification/Slno
804Invalid SED(CVD Sch II) Notification/Slno
805Invalid TTA Notification/Slno
806Invalid Educational Cess Notification
807Invalid Health Cess Notification
808Invalid Special CVD Notification
809Invalid SAPTA Notification
810Invalid Safeguard Notification
811Invalid Aggregate Notification
812Invalid Antidumping Notification
813Invalid Tariff Value Notification
814Check Commercial Tax Details
815Invalid GST type/State Code
816GST Details not declared
817Invalid GST id/Aadhar No./PAN/TAN/Passport No.
818State Code mismatch in GST id and GST declaration
819Mismatch of PAN in IEC and GSTIN
999Check Data/Duty Related Parameters like CTH/CETH/RSP/NOTN etc.

PFMS bank validation errors: TBE0001 to TBE0025

A shipping bill can pass every customs check and still not pay, because the last step is a bank account validation in the Public Financial Management System. When that fails, the shipping bill appears in the temporary scroll and not in the final one, and the reason is a TBE code rather than an SB code. Several of these are structural errors in the file itself, which is why the published rectification against them reads "not applicable": they never reach an exporter's report.

CodeWhat it meansWhat to do
TBE0001Error in reading file, file is malformed or failed during schema validation.Not applicable, a structural error.
TBE0002Mandatory tag values are missing in the header part.Not applicable, a structural error.
TBE0003Invalid batch format.Not applicable, a structural error.
TBE0004Duplicate batch or message id not allowed.Not applicable, a structural error.
TBE0005Invalid assessee type.Not applicable, a structural error.
TBE0006The same assessee code, location code, assessee type and source already exist in PFMS.Submit again.
TBE0007The assessee code, location code, assessee type and source do not exist in PFMS, on an update or delete request.Submit again.
TBE0008Rejected by the bank, the account number is invalid.Check the account number and submit correct details.
TBE0009Bank name is not as per the PFMS bank master.Not applicable on its own, it appears only alongside other errors.
TBE0010Bank account details have not been provided.Check the account number and submit correct details.
TBE0011Mobile number should be ten digits only.Not applicable, a structural error.
TBE0012Invalid value for location code.Inform the Directorate General of Systems for rectification.
TBE0013Invalid value for division code.Inform the Directorate General of Systems for rectification.
TBE0014Invalid value for purpose, it should be A, U or D.Not applicable, a structural error.
TBE0015Invalid IFSC code.Check the IFSC code and submit correct details.
TBE0016Rejected by the bank, the account number does not exist at the bank.Check the account number and submit correct details.
TBE0017Rejected by the bank, the account status is closed.Check the account is still valid and submit correct details.
TBE0018Duplicate assessee details found in the file.Submit again.
TBE0019Blocked account.Submit another valid account.
TBE0020One or more mandatory tag values are missing in the detail section.Not applicable, a structural error.
TBE0021The IFSC code does not exist in PFMS.Inform the Directorate General of Systems for rectification.
TBE0022The actual record count and the number of records in the detail section are not the same.Not applicable, a structural error.
TBE0023Assessee already exists.Submit again.
TBE0024Assessee code does not exist during update.Submit again.
TBE0025More than one record found during update.Submit again.

The practical version of this table is short. If the money has not arrived and the response code is SB000, ask your customs house whether your account is validated in PFMS, and give them the account number, bank name and IFSC in writing. Bank details that move, after a merger or a branch change, are a common way for a clean shipping bill to go quiet.

Other codes you will meet on an ICEGATE enquiry

Four smaller families answer questions that get mistaken for shipping bill errors.

IEC status codes

The IEC enquiry returns a status digit rather than an error, and it decides whether anything else can proceed at all.

CodeWhat it meansWhat to do
0Normal. The IEC can be used.Nothing.
1Blacklisted.Contact DGFT.
2Suspended.Contact DGFT.
3Cancelled.Contact DGFT.
4Cleared from the blacklist.The IEC is transmitted afresh from DGFT with a 00 error code.
7Suspension revoked.Nothing. The IEC is out of suspended status.
8Cancellation revoked.Nothing. The IEC can be used.
9Amended. A change has been made to the IEC.Nothing, but check that the amended details reached Customs.

Challan and duty payment codes

CodeWhat it meansWhat to do
00Payment has been done successfully.Nothing.
02One of the payments made has already been updated.Nothing. It is a duplicate update, not a failure.
03, 04 and 11Published only as codes that need help rather than as descriptions.ICEGATE directs these to its helpdesk.

SEZ acknowledgement codes

CodeWhat it meansWhat to do
00The acknowledgement, for a SEZ bill of entry or a SEZ shipping bill, has been processed successfully.Nothing.
01The acknowledgement has failed.Contact the SEZ location for the failure reason. ICEGATE does not carry it.

Inland depot bill of lading status codes

These come back on the ICD bill of lading status enquiry and are almost all about the train or truck summary, which is the document that later decides whether your gateway EGM works.

CodeWhat it means
31SMTP number is null.
32SMTP date is null.
33Train number is null.
34Arrival date is null.
35Container number is null.
36Shipping line code is null.
37Invalid gateway port.
38Arrival date is later than today's date.
39Invalid container condition.
40Invalid combination of SMTP number, SMTP date and gateway port code.
41Invalid combination of SMTP number, SMTP date, gateway port code and container number.
42Invalid shipping line code.
43, 44, 45 and 46Error in file.
100Container record transfer failed.
101Container validation failed.
102Container already exists.

What Customs does not publish, stated plainly

A page like this is only useful if it is honest about its edges, so here are three.

  • There is no consolidated shipping bill filing error list to match the bill of entry one. The import side gets a single published file. On the export side the codes are scattered across the IGST response set, the EGM letters and the DGFT transmission numbers, which is why so many lists on the open web are stitched together from guesswork.
  • The EGM letters are not a master list either. They are published in customs house notices and in the Directorate General of Systems guide, and a letter that appears on your report but not on this page is best read by the EGM cell at the port that raised it. That is not a fob off, it is the only place that can see the flag against your bill.
  • Rectification procedure is port specific. The response codes are national and the remedies are not. What a customs house asks for, the letter, the concordance table, the challan, is set by that customs house in its own public notice, so check the notice for the port on your bill rather than assuming the procedure you used last year at another port.

When a code turns out to be about the money rather than the document, the trail runs into the realisation side of the file, which is where EDPMS closure and the certificate that evidences realisation take over.

Where these codes are published

Every table on this page comes out of one of five government documents, and each one is worth keeping a link to, because the remedies change more often than the codes do.

  • The IGST response codes, in depth. The Directorate General of Systems guide on IGST refunds in ICES carries SB000 to SB006 with the discussion behind each one, the PFMS error annexure and the EGM error annexure: the guide on IGST refunds in ICES.
  • The same codes, restated recently. Chennai Customs published a response and rectification note in August 2025: IGST refund response codes and rectification procedure.
  • The EGM error letters. Chennai Customs Facility Circular 19 of 2025 carries the error type table as an annexure, with the rectification action and the desk that performs it: EGM error rectification.
  • The bill of entry filing list. Published by ICEGATE as a single file: the bill of entry filing error list.
  • The enquiry codes and the retransmission route. The IEC status digits, challan codes, SEZ acknowledgements, depot bill of lading codes and DGFT integration codes are all in the ICEGATE FAQ, and the retransmission facility has its own user manual.

Common questions

What does bill of entry error code 496 mean?

Nothing, as far as the published list goes. The ICEGATE bill of entry filing error list runs 451 to 492 in the single window band and then jumps to 501 for the bond band, so 493 to 500 are not assigned. If your acknowledgement shows 496, it is worth checking the code against the message it came in, because a number that is not on this page usually belongs to a different message type rather than to the bill of entry filing acknowledgement.

What does EGM error code S mean?

S is not one of the EGM error letters Customs publishes. The published flags are C for a container number mismatch, N for a container count mismatch, P for a package count mismatch, R for a missing rotation number, Q for a stuffing report that was not uploaded, T for a nature of cargo mismatch, L for a let export order dated after sailing, and M for a gateway port mismatch on depot cargo. If your report shows a letter that is not in that set, the EGM cell at the port holding the bill is the place to have it read.

What is SB005 and how do I fix it?

SB005 means invalid invoice number: the invoice number in the shipping bill does not match the one in GSTR-1 for the same supply. If the mistake is in GSTR-1, amend it through Table 9A. If the mistake is in the shipping bill, it cannot be amended once the EGM has been filed, and rectification goes through the customs house, which typically wants a request letter to the officer handling IGST refunds, a shipping bill wise concordance table, and the fee challan set out in its own public notice. The durable fix is to stop running two invoice series, one for GST and one for export, because that is what produces the mismatch in the first place.

Why has my refund not arrived when the code is SB000?

Because SB000 means validated, not paid. Customs lists six reasons a validated bill stays unpaid: the export went under bond or LUT, only some invoices on the bill validated, a higher rate of drawback was claimed, the claim is under one thousand rupees, there is an alert or suspension on the IEC, or the bank account is not validated in PFMS. The last two are the ones that catch people out, because nothing on the response code changes.

Where do I see the error code for my own shipping bill?

In your ICEGATE login, the GST validation status view shows the response code for every shipping bill for which GSTN has sent data. The DGFT integration status and the EGM position are available through the public enquiries, by shipping bill number and date with the port code, or across a date range for an IEC. All of them want the same identifiers off the bill, so having the number, date, port code and IEC to hand turns a long afternoon into a few minutes.

My shipping bill is not visible at DGFT. Is that an error code?

It is, and it is a plain number rather than an SB code. The DGFT shipping bill integration status enquiry returns 0 when the bill integrated successfully, and 3, 9, 10, 16, 21 or 23 when it did not. ICEGATE also publishes a self service retransmission facility that takes the shipping bill number, date, port code and IEC and pushes the bill to DGFT again, which it states takes roughly forty eight hours.

Get started

Codes cleared. Now close the file.

The eBRC exporter app is free at any volume. No certificate limit, no card required.