ICEGATE Error Codes: Complete List with Fixes (2026)
TL;DR - Summary
- What is an ICEGATE error code? - An ICEGATE error code is a system-generated response that flags a validation failure during customs filing. It acts as a hard block, stopping document processing until the error is fixed.
- What are the common reasons for ICEGATE errors? - Data mismatches are the most common reason. Other triggers include technical setup issues, the shipping carrier failing to file the EGM, using an incorrect IEC or AD code, and uploading oversized files.
- What are the most common ICEGATE error codes? - Error 101 (Type of BE Wrong), Error 103 (CHA No. Not Registered), Error 105 (IEC/Branch Invalid), SB001 (Invalid SB Details), SB002 (EGM Not Filed), and SB003 (GSTIN Mismatch).
- How do you fix ICEGATE IGST refund errors? - The fix depends on the error type. Most are resolved by amending Table 9A in GSTR-1, but for EGM-related errors, you must contact the shipping carrier directly.
- How do you track EGM and IGM error codes? - Log in to the ICEGATE portal, go to Services, click Enquiry, then Public Enquiries 2.0, and select the Document Status option.
What Is an ICEGATE Error Code?
An ICEGATE error code is a system-generated alphanumeric response from the Indian Customs Electronic Gateway (ICEGATE) that indicates a failure in data validation. These codes appear when the information you file, such as in a Shipping Bill, EGM, or Bill of Entry, conflicts with records held by the GSTN, DGFT, RBI, or the customs department.
These codes are not notifications; they represent hard blocks in the Indian Customs EDI System (ICES). For example, if you file a Bill of Entry but the currency code does not match the RBI standard, the system rejects the filing immediately. Processing resumes only after you fix the error.
What are the Common Reasons for ICEGATE Errors?
The following common reasons for ICEGATE errors will guide you to be more careful while filing documents on ICEGATE or help you understand why an error has come up.
- Data mismatches are the primary trigger for most filing failures on the platform. This occurs when a specific field in your Shipping Bill, GSTR-1, or Bill of Entry does not align with the record in a linked government database like the GSTN or RBI-IDPMS.
- Technical setup issues also cause frequent blocks. If your machine runs an outdated Java runtime or if the emSigner utility is not active, the portal cannot verify your Digital Signature Certificate (DSC).
- Shipping lines failing to file the Export General Manifest (EGM) or providing IGM details that do not align with the Bill of Entry.
- Using an IEC or branch code that is suspended or not registered at a specific port.
- Using an Authorized Dealer (AD) code that is mapped to a separate entity.
- Uploading oversized PDFs, unsupported file formats, or documents with digital signature mismatches in eSanchit.
- Technical transmission failures between ICEGATE and DGFT or between ICES and the RBI.
💡 QUICK INSIGHT
Most ICEGATE errors are data mismatches, not system bugs. The same filing submitted with corrected data clears instantly.
What Are the Most Common ICEGATE Error Codes in India?
The customs system categorizes errors based on whether they relate to your filing type, your technical environment, or the network sync between different government departments.
Filing & Customs Types Errors
These errors specifically target the accuracy of the trade documents submitted by the exporter or importer.
Bill of Entry (BE) Errors
- Error 101 (Type of BE Wrong): The declared BE type does not align with current customs regulations for your specific port.
- Error 103 (CHA No. Not Registered): The Customs House Agent code used in the filing is inactive at that port.
- Error 105 (IEC/Branch Invalid): There is a mismatch or suspension affecting the Importer-Exporter Code details.
- Error 146 (Ex-bond Bill of Entry Not Allowed): You attempted an ex-bond filing before completing the prior warehousing steps or obtaining procedural approval.
- Error 163: There is a mismatch in the branch serial number, often caused by using special characters in the importer name field.
- Error 170: The filing is missing mandatory container details or contains an incorrect port code.
- Error 110 (AD Code Registration Error): The system prevents re-registration because the IEC is already linked to a different location.
- Errors 181–190 (ICES Database SQL Faults): These are backend database timeouts on the customs side, not errors caused by you.
Shipping Bill (SB) & IGST Refund Errors
- SB001 (Invalid SB Details): The shipping bill number, date, or port code in the GST system does not match the customs record.
- SB002 (EGM Not Filed): The carrier has not filed the Export General Manifest.
- SB003 (GSTIN Mismatch): The GSTIN on the Shipping Bill differs from what was declared in GSTR-1 or GSTR-3B.
- SB004 (Duplicate Record): The IGST amount or taxable value has already been received and processed by the GSTN.
- SB005 (Invalid Invoice Number): The invoice date or number in the Shipping Bill does not match GSTR-1.
- SB006 (Gateway EGM Error): This happens in ICD shipments when the Gateway EGM is missing or has cargo mismatches.
Technical Portal & Setup Type Errors
These errors relate to the hardware and software configuration used to access the customs portal.
- DSC Errors (No PKI Applet Found): This indicates that your USB token driver is not installed or the emSigner service is not running.
- Java Security Warning: Your Java version is incompatible. ICEGATE requires a specific Java environment to run its security applets.
- e-Sanchit Upload Errors (ENCH01): The document you are trying to upload exceeds size limits or uses an unsupported format.
System & Inter-Agency Network Type Errors
These blocks occur when data cannot move correctly between different government systems.
- DGFT Transmission Errors (01, 02, 04): Structural control files failed to sync between ICEGATE and DGFT during automated nightly transfers.
- SCMTR Manifest Errors: These involve Sea Cargo Manifest filings, such as missing Date of Birth (DOB) in the profile or invalid carrier codes.
- IDPMS Errors: A mismatch between customs data and bank records, categorized as Fatal (requires document amendment) or Non-Fatal (requires bank reconciliation).
⚠️ WATCH OUT
Once the EGM is filed, you generally cannot amend the Shipping Bill, SB003 GSTIN mismatches must be caught and corrected in GSTR-1 before the EGM is submitted.
How Do You Fix ICEGATE IGST Refund Errors (SB001 to SB006)?
Compare your GST filings with your custom records to resolve IGST refund errors. Most of these fixes involve using the amendment tools provided on the GST portal or coordinating with your shipping line.
| Error Code | Error Name | Root Cause | Fix | Where to Act |
|---|---|---|---|---|
| SB001 | Invalid SB Details | Mismatch in port code, SB date, or SB number. | Amend invoice details via Table 9A of GSTR-1 | GST Portal |
| SB002 | EGM Not Filed | The carrier/shipping line has not filed the Export General Manifest. | Contact the carrier to file the EGM or a supplementary EGM. | Shipping Line |
| SB003 | GSTIN Mismatch | GSTIN on Shipping Bill differs from GSTR-1/3B. | If EGM not filed: Amend GSTR-1 Table 9A. If EGM filed: Approach Customs Officer for a manual systemic amendment. | GST Portal / Customs Port |
| SB004 | Duplicate Record / Value Mismatch | Record already transmitted by GSTN or data mismatch. | If a genuine duplicate, no action is needed; the system processes the original record. If the data is wrong, amend via GSTR-1 Table 9A. | GST Portal |
| SB005 | Invalid Invoice / Duplicate SB | Invoice number/date mismatch; or SB number already used. | Correct typos via Table 9A amendment. For duplicate claims, request an officer-assisted manual override. | GST Portal / Customs Port |
| SB006 | Gateway EGM Error | Missing or mismatched Gateway EGM (common for ICD shipments). | Coordinate with the carrier to file/rectify the Gateway EGM. | Shipping Line |
Additional notes:
- GSTR-1 Table 9A allows only one amendment per invoice.
- If a SB003 error persists after the EGM is filed, you must approach the Customs Officer at the port of export for a systemic amendment.
- After changing GSTR-1, wait 48 to 72 hours for the data to re-sync with ICEGATE
- Log in to the ICEGATE portal and use the Enquiry module to check the IGST Integration Status.
- Reach out to the ICEGATE helpdesk email is icegatehelpdesk@icegate.gov.in and toll-free number is 1800-3010-1000 for escalated or stuck cases.
💡 QUICK INSIGHT
SB002 and SB006 are not your filing errors, they are the shipping line's responsibility. Raise the issue with your carrier immediately; you cannot fix these from the GST Portal.
How Do You Fix AD Code Registration Error 110?
Error 110 occurs when the system detects that your Importer-Exporter Code (IEC) is already linked or registered at a different location.
To fix AD Code Registration Error 110, follow these five steps:
- Step 1: Ensure your IEC profile and all branch details are updated on the DGFT portal.
- Step 2: Confirm that your IEC and address data are correctly synced with the ICEGATE directory. This may require a data transfer authorization from DGFT.
- Step 3: Log in to ICEGATE using an Organization Class 3 DSC and navigate to the Bank Account Management tab.
- Step 4: Go to Foreign Remittance Account (AD Code), select Add New Bank Account, and submit the request from the primary registered site.
- Step 5: Use e-Sanchit to upload PDF scans of your AD Code letter, IEC certificate, PAN, and a cancelled cheque. Link the resulting Invoice Reference Number (IRN) to your submission.
If you encounter technical blocks during this process, raise a ticket with the ICEGATE Helpdesk.
How Do You Fix Bill of Entry (BOE) Submission Errors?
Fixing BOE errors occurs when physical shipping documents and the electronic data on ICEGATE do not match.
- For invoice or item mismatches, check that HS codes, quantities, and invoice numbers match the commercial invoice and bill of lading exactly.
- If you face Error 163 regarding an IEC or branch mismatch, update your data on the DGFT portal and remove any special characters from the importer's name. Then, request a data transfer to the ICES IEC Directory.
- For Error 170, re-verify the port codes and ensure all mandatory container numbers are included.
- In case of Error 146, refer to ICEGATE’s ex-bond advisory procedures to complete the warehousing steps before re-submitting.
Here’s how your workflow should look to fix a bill of entry error:
- Log in to the ICEGATE Dashboard and navigate to the Bill of Entry section.
- Review the error description in the response logs.
- You can then use the online web forms to file a BOE amendment.
- Once submitted, you must wait for the customs officer to assess and approve the changes.
For clerical errors in product classification, file an amendment under Section 149 of the Customs Act.
How Do You Fix Shipping Bill Submission Errors?
Exporters mostly face shipping bill errors because of typographical mistakes or technical failures during the digital signing process.
- For SB001, verify if the port code or date was entered incorrectly and amend the details via Table 9A on the GST portal.
- If the error is SB002, coordinate directly with the carrier to ensure the manifest is filed immediately.
- In case of SB003, where there is a GSTIN mismatch, amend GSTR-1 via Form 9A to match the shipping bill details
- For SB005, the issue is an invalid invoice number. Correct the errors in GSTR-1 or the shipping bill via Table 9A amendment.
Technical blocks at the signing stage, such as DSC upload failures, can be solved by using a compatible browser like Mozilla Firefox ESR or Edge in Internet Explorer Mode. Ensure you are using Java Runtime Environment 8 (JRE 1.8) and have added the portal to the Java Security Exception Site List.
If you face port registration or mapping failures, consult the official ICEGATE Port Code List to ensure accuracy. For clerical errors related to HSN codes, file an official amendment under Section 149 of the Customs Act using the ICEGATE Web Forms.
How Do You Fix EGM and IGM Error Codes?
Errors in manifests block the generation of IGST refunds and the creation of RoDTEP/RoSCTL scrolls. These issues must be handled through the carrier or a Customs House Agent(CHA).
EGM (Export General Manifest) Errors
- SB002: This shows the carrier hasn't filed the EGM. You must approach the shipping line and request a Supplementary EGM.
- Data Mismatches (SB003, SB004, SB005): These occur when Shipping Bill data does not match the GSTR-1 records. Amend GSTR-1 via Form 9A.
- Container Mismatches: If container numbers or seal numbers differ from the filing, the CHA must apply for an EGM Amendment via the ICEGATE Service Centre, which requires approval from the Customs Officer in the CRU section.
IGM (Import General Manifest) Errors
- IGM Not Found: This means the Bill of Lading number is misspelled or the filing has not yet been validated. Double-check the B/L number and port code, then wait 2–4 hours before escalating to the shipping line.
- Weight/Package Mismatch: If the declared Bill of Entry details do not match the Master or House IGM, the CHA must file an IGM Amendment on the portal.
How to Track and Amend
To check the status of your manifest:
- Navigate to the ICEGATE Portal
- Select Services
- Click on Enquiry from the drop-down menu
- Select Public Enquiries 2.0
- Tap on the Document Status option.
For any amendments, your Customs Broker must use the Bill of Entry Amendment webform or the specific SEA/AIR IGM webforms while logged in with a valid Class III DSC.
How Do You Fix SCMTR Error Codes?
The Sea Cargo Manifest and Transhipment Regulations (SCMTR) require precise profile data and document formatting.
- A common registration error is DOB is Required, which you can fix by updating the Date of Birth in the profile section of your dashboard before resubmitting the form.
- Ensure all site IDs and port codes match valid customs locations to avoid missing or invalid carrier errors.
- All uploaded documents must be in PDF format, under 1.5 MB in size, and digitally signed with a Class 3 DSC.
- If you receive a Duplicate/Mismatch Mapping (SDM message), check if one Shipping Bill is mapped to multiple Bills of Lading, as this triggers an error.
For rectification, make the data corrections and click Submit/Resubmit to re-validate the data against the ICES system. For specific payload-level errors like codes 264 or 284, refer to the official SCMTR Error Codes PDF provided by customs.
How Do You Fix IDPMS Error Codes?
The Import Data Processing and Monitoring System (IDPMS) flags mismatches between customs data and your Authorized Dealer (AD) bank records. These errors are split into two categories:
- Fatal Errors: These hard-block your filings and require an amendment to the Bill of Entry or Shipping Bill through a Customs Broker to fix incorrect data like invoice numbers or IEC codes.
- Non-Fatal Errors: These are data reconciliation failures between your bank records and foreign remittance records, which you can resolve directly with your AD Bank.
To find the exact reason for a rejection:
- Log in to ICEGATE using your account credentials
- Go to Services
- Select Quick Information
- Click on Public Enquiries 2.0
- Choose the Status of BE in RBI-IDPMS option
If the error relates to a PAN or registration mismatch, ensure your PAN, AD Code, and IEC details are identical across both the DGFT and ICEGATE databases. For incorrect port codes, log an amendment request using the BE Correction Role on the portal.
For any escalation, reach out to the ICEGATE helpdesk at 1800-3010-1000 or icegatehelpdesk@icegate.gov.in, for RBI-side issues, contact the designated regional RBI/EDPMS support desk.
How Do You Contact ICEGATE Helpdesk for Unresolved Errors?
If automated fixes and portal amendments do not resolve an error, you must contact the technical support team:
- The primary toll-free phone support is available 24/7 at 1800-3010-1000.
- You can also use the secondary outbound helpdesk lines at 0124-6725800 and 0124-6722900.
- When emailing icegatehelpdesk@icegate.gov.in, include the specific error code, screenshots of the block, and your document reference numbers.
- If you prefer in-person assistance, help is available at your nearest local Customs office on Monday, Wednesday, and Friday between 3:00 PM and 5:00 PM.
How Does Skydo Help?
IGST refunds (SB001–SB006) directly delay your export payments, and strains your business cash flow. An unplanned expense can set your production schedule back by weeks.
While customs compliance happens on the government portal, Skydo provides the financial infrastructure to ensure your international payments remain predictable.
Skydo helps Indian exporters receive international payments from clients in USD, EUR, GBP, and other major currencies with zero forex markup. This removes the hidden costs associated with traditional banking.
Our flat-fee pricing model is fully transparent:
- Under $2,000: $19 flat fee
- $2,000–$10,000: $29 flat fee
- Over $10,000: 0.3% fee
Every time you receive an international payment, an automated, free FIRC (Foreign Inward Remittance Certificate) is generated. An FIRC is crucial for customs compliance and to resolve data gaps in IDPMS or EDPMS records. By providing real-time payment tracking, Skydo gives you direct visibility into your finances.
What is the difference between a Fatal and Non-Fatal ICEGATE error?
Fatal errors are hard blocks that stop document processing and require a formal amendment to the Bill of Entry or Shipping Bill. Non-fatal errors flag data reconciliation issues that usually allow the document to pass but require later resolution with your bank.
Can I fix an ICEGATE error myself, or do I always need a CHA?
What happens to my IGST refund if I don't resolve SB errors?
How do I check the status of my IGST refund on ICEGATE?
What is the ICEGATE BE Filing Errors List and where do I find it?
What documents should I have ready before calling the ICEGATE Helpdesk?
Can an ICEGATE error delay my e-BRC generation?
Is SCMTR applicable to all exporters, or only shipping lines?
What should I do if my AD Code shows Error 110 at a new port?
