What does this error mean?
The next port of call in the vessel or Sea Manifest request is invalid or inconsistent with the voyage schedule.
SACHE01-15Sea Manifest Errors
Invalid next port of call
The next port of call in the vessel or Sea Manifest request is invalid or inconsistent with the voyage schedule.
Why does this happen?
- The port code is wrong.
- The next port was entered as the current or previous port.
- The vessel schedule changed but the request was not updated.
How to fix this error
- Verify the next port from the latest approved vessel schedule.
- Use the accepted port code and confirm voyage sequence.
- Update the source schedule and regenerate the request.
Who should resolve it?
Shipping Line / Shipping Agent / Vessel Operations 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-15 FAQ
Questions users ask after seeing this error
What does SACHE01-15 mean?
The next port of call in the vessel or Sea Manifest request is invalid or inconsistent with the voyage schedule.
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 / Vessel Operations 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.