What does this error mean?
The port code in the Sea Manifest or vessel-call request is invalid or does not match the filing context.
SACHE01-03Sea Manifest Errors
Invalid port in Sea Manifest request
The port code in the Sea Manifest or vessel-call request is invalid or does not match the filing context.
Why does this happen?
- The port code was typed incorrectly.
- The request uses another port of call or customs location.
- The filing entity is not mapped to the selected port.
How to fix this error
- Verify the port code from the vessel schedule and accepted port list.
- Check that the request, VCN, user authorisation, and intended call use the same port.
- Correct the source request before filing again.
Who should resolve it?
Shipping Line / Shipping Agent / Port Filing Team
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.
SACHE01-03 FAQ
Questions users ask after seeing this error
What does SACHE01-03 mean?
The port code in the Sea Manifest or vessel-call request is invalid or does not match the filing context.
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?
Shipping Line / Shipping Agent / Port Filing Team 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.