What does this error mean?
The transport or cargo details entered in the Bill of Entry do not match the Import General Manifest record expected by Customs.
BEBill of Entry Errors
Bill of Entry and IGM details mismatch
The transport or cargo details entered in the Bill of Entry do not match the Import General Manifest record expected by Customs.
Why does this happen?
- The IGM number, date, line number, or sub-line number is wrong.
- The carrier amended the manifest after the Bill of Entry was prepared.
- The cargo was manifested under a different bill of lading or package reference.
How to fix this error
- Compare the IGM number, date, line, sub-line, bill of lading, packages, and weight with the carrier record.
- Ask the shipping line or carrier to confirm whether an IGM amendment is pending.
- Correct the Bill of Entry only after identifying which source record is wrong.
Who should resolve it?
Importer / CHA / Shipping Line / Carrier
Send the exact error, filing reference, date, time, and supporting source document to the responsible team.
Related errors
Check these messages if the first fix does not match
Improve this guide
Was this solution helpful?
Your response helps EximSign prioritise unclear or incomplete error guides.
Practical guidance
These solutions are operational guidance, not a replacement for current ICEGATE instructions, customs orders, GST rules, bank requirements, or advice from the responsible authority.
BE FAQ
Questions users ask after seeing this error
What does BE mean?
The transport or cargo details entered in the Bill of Entry do not match the Import General Manifest record expected by Customs.
Can I refile after fixing this error?
Refiling depends on the transaction. First confirm whether the original submission failed, is pending, or already created an acknowledgement.
Who should resolve this issue?
Importer / CHA / Shipping Line / Carrier should review the relevant source record or system step.
Is this always an ICEGATE system problem?
No. The cause may be source data, a carrier filing, GST or bank validation, DSC setup, user access, Customs processing, or the ICEGATE service.
Should I contact Customs?
Contact Customs when the record is waiting for officer action, assessment, approval, or a customs query. Technical and source-data issues should go to the responsible team first.
How long does resolution usually take?
There is no fixed time. A local data or DSC issue may be corrected quickly, while carrier, bank, GST, or Customs processing depends on the responsible organisation.