What does this error mean?
The total number of cargo lines declared in the message does not match the actual cargo detail lines.
SACHM090SCMTR Errors
SCMTR cargo line count mismatch
The total number of cargo lines declared in the message does not match the actual cargo detail lines.
Why does this happen?
- The header line count is stale.
- A cargo line was omitted or duplicated.
- The source system grouped or split bills without recalculating the total.
How to fix this error
- Count the final cargo detail lines in the generated message.
- Check for missing and duplicate master or house bill rows.
- Correct the header count, regenerate the file, and validate it before submission.
Who should resolve it?
Shipping Line / Shipping Agent / Freight Forwarder / Software 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.
SACHM090 FAQ
Questions users ask after seeing this error
What does SACHM090 mean?
The total number of cargo lines declared in the message does not match the actual cargo detail lines.
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 / Freight Forwarder / Software 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.