SAM, SDM and SAA filing software for shipping lines and steamer agents
Updated
The line files the SAM on arrival and the SDM on departure — the line’s IGM / EGM filing under SCMTR — then amends them, files entry inward and the departure notification. On SCMTR.io the whole manifest opens as lines you can search, each line is checked against the CSN it quotes, the SAA is built from what customs accepted, and the line’s team, its branches and the forwarders on the vessel work from the same copy.
Opened from a file or built from nothing, each line checked against the CSN it quotes, signed and sent
SDM
Departure manifest (the line’s EGM filing)
Its lines added from the export CSNs, checked, signed and sent
SAA
Arrival manifest amendment
Built from the manifest customs accepted — only what changed, numbered the way customs holds your lines
SDA
Departure manifest amendment
Built the same way as an SAA, from the accepted SDM
SEI
Entry inward
Checked against the call’s SAM before it goes
SDN
Departure notification
Checked against the call’s SDM, with customs’ EGM reply read after it
Each one prepared, checked, signed with your own DSC and sent to ICEGATE from one place.
scmtr.io
A SAM checked before it goes to ICEGATE: each error with how to fix it. · Invented data.
The whole manifest, readable
A SAM of a thousand lines opens as lines, not as code.
Find any line by BL, container or consignee
Build a manifest from nothing for bulk, tanker and tramp calls, or add a line from a forwarder’s CSN
The vessel list and totals worked out from the lines
Entry inward checked against the SAM, the departure notification against the SDM
Checked against the CSNs and customs’ record
Problems to fix, found before the DSC comes out.
Each manifest line compared with the CSN it quotes
See the manifest customs holds for your call, line by line
Every error with how to fix it — many in one press — and the verdict shareable on WhatsApp
The SAA, built for you
An amendment addressed the way customs holds your lines.
Built from the manifest customs accepted: only what changed goes
Drop-and-re-add when a straight line becomes consolidated, as customs’ advisory asks
Customs’ reply read as one story — which lines, why, and the next step
A complex SAA prepared for you — quoted before any work starts — opened and signed only with your own DSC
The line’s whole organisation, and its forwarders
One organisation for the line’s Indian agency.
Branches, view-only members and sub-agents the line confirms by name
Several people on one manifest at once, one on each line, with change requests from forwarders
Share the SAM before filing; forwarders’ CSNs compared with it before they send
Forwarders ask the line to amend from their own check; the line approves and sends
Every call of the line in one view, once the line’s organisation is verified; CSN cut-offs published to the public board
Line desk — eHBL, invoices, ePayment, the eDO and Form 13
The line and its customers on one master bill. Lines are being switched on with SCMTR.io support as the payment terms are finalised. A shipping line whose organisation SCMTR.io has verified writes to support@scmtr.io; the line opens its bills from its SAM and invites its customers, and a customer can also open a bill itself by naming the line and the master bill, or straight from its own CSN.
House bills (eHBL) or the CSN, with each container’s destination
Bills opened from the line’s SAM in one press, one per master BL; the consignee, notify party or broker invited by PAN, GSTIN or e-mail with the arrival notice — the vessel, the expected arrival, the free days and what to send next; and accepted house bills written into the line’s saved SAM, every change shown first — the line still checks, signs and sends its SAM
Export bills too: the exporter, its customs broker or its forwarder invited with the sailing notice — the vessel, its call and the cut-offs in India time — and either notice sent now or at a day and time the line schedules
The line’s own customer list brought in from a CSV or Excel workbook — each row’s numbers checked as typed and its verdict said — its customers on SCMTR.io invited in the app and the rest by e-mail in one press, reminded once after three days, and, where the line chooses, kept as its own record of each customer’s KYC until the customer shares its own
Invoices posted as the line’s own system raised them, credit notes and statements
The line drops its GST e-invoice PDF and the IRN, number, date and value fill in from its QR code — anything that differs from what the line typed is shown, and its customer sees the IRN marked as checked
Payment (ePayment) into the line’s own account: by bank transfer, and online by UPI, card or net banking once the line connects its payment provider
Several bills paid at once, up to 1,000 invoices to a line — each invoice’s amount shown before paying, one payment or one transfer for all of them, and bills with several lines in one checkout, a payment into each line’s own account — and, where an organisation asks, an approver (maker-checker) at or above a limit it may set: one person prepares a payment, or the release of a DO or an export BL, and another pays or releases it; and a line’s own invoices and the payments it records, prepared by one of its people and posted by another, and the refunds a line records
Paying a line before its invoice — an advance on account, a deposit before it is posted or a DO revalidation charge, used first on the next invoices and paid back by the line on request; invoices paid net of TDS, the customer choosing the section and rate and giving the line its certificate; and a customer questioning an invoice, answered by the line or settled with a credit note, with the line’s rule on whether the DO waits
An estimate on each bill before the line’s invoice, from the line’s own charges — never the invoice — and the line’s tariff on a public page of its own, where the line publishes it, and on the line’s own website; a DO, Form 13 or invoice shared on WhatsApp; and reports on screen and as CSV: the customer ledger and ageing, DOs waiting and release times, receipts by day, and each customer’s statement
A customer’s question to the line on its bill, with a reference both sides quote, what it is about and one file — waiting for the line until it answers, with the reply times in the line’s reports
Security deposits by the line’s own rules, paid like an invoice and waived for a customer until a date — paid back by the line once the empty is returned, with the receipt and the account given on the bill
Detention and free days on import bills, from the line’s own tariff: each container’s last free day and running days, with a reminder the day before and on the day, the empty-return receipt the line confirms, customs waiver certificates taken off, and the detention invoice the line checks and posts — paid like any invoice, or kept from the deposit; customs’ own arrival day as the start where it agrees with the bill, the line asked where it differs; extra free days a customer buys at the line’s price; on export bills, from the empty’s pick-up to its gate-in; and a public detention calculator beside the line’s tariff
The electronic delivery order (eDO) for the customer’s own containers, with a QR code any CFS can verify
For an electronic BL, the eBL platform and transfer reference named on the DO request, and the surrender confirmed by the line on the DO’s checklist — SCMTR.io is not connected to eBL platforms
KYC shared once with each line — GSTIN, PAN, licence or IEC and address proof, each number checked as it is typed — and accepted by the line until a date; the consignee authorises its customs broker on SCMTR.io, or the broker sends its letter for the line to accept; factory-destuff bonds, SEZ letters and letters of indemnity with their expiry; and, where the line asks, the DO waits for each
Letters from the line — an authority letter, LOI, BL surrender letter and deposit refund letter in the line’s own words, filled from the bill with the customer’s own name, PAN and containers, to download, sign and send back
DOs naming us, for a CFS or an empty yard: the DO for its containers from every line on the Line desk, each marked delivered at the gate or its empty returned — the line and the customer see it at once — and each released DO e-mailed with its PDF to the CFS, to the terminal for a direct port delivery, and to the port’s custom house where the line gives their addresses, never a test one
VGM and Form 13 on export bills: the shipper forwards each container’s VGM to the line with the weighbridge slip, the line accepts it and issues the Form 13, which it loads into the terminal’s own system with the file SCMTR.io gives — APM Terminals Mumbai’s first — and a gate that checks papers can check by its QR code; the shipper may also sign its VGM with its DSC, and both sides are reminded before the line’s VGM, shipping bill and gate cut-offs, a VGM or gate cut-off the line types where its advisory gives none, and the SI cut-off; where the line asks, no Form 13 before the box’s shipping instructions; the truck on each Form 13 and the line’s mark that the box was loaded at the terminal — the shipper still files its VGM on a DG Shipping–approved website, which SCMTR.io is not, and the line files VGM with the terminal through its own system
On export bills: the empty release order (CRO) with a QR code the empty yard checks — asked for by the customer with the sizes, the yard and the day, a seal allotted to each box — each empty it releases marked at its gate with its EIR: the seal and the box’s condition; the shipper’s instructions (SI) and the draft BL it approves or asks changes on — or a shipper with no account approves on a one-use link; the BL release — originals, sea waybill, telex release or eBL — against a checklist of paid, shipping bill and LEO, VGM and an approved draft; and the forwarding note (Form 11) an inland container depot asks for, built from the bill
A forwarder’s own house desk: its house bills from its CSN, its consignees and their brokers invoiced and paying into the forwarder’s own account, and house DOs with the same QR check at the CFS — beside the line’s DO for the master, which the CFS still needs — and its export house bills, its shipping bills, VGM and Form 13 with the line shown on each and its own house BL released to its shipper once it holds the line’s; switched on with SCMTR.io support once the forwarder is verified for issuing, as the payment terms are finalised
VGM for any shipping line: the shipper, its forwarder or its customs broker gives each container’s VGM with every field the official form asks and the weighbridge slip, and SCMTR.io forwards it to the line — on its Line desk, or by e-mail with a link that shows it still stands; weighbridges offered from SCMTR.io’s register as you type — SCMTR.io is not a DG Shipping–approved VGM website at present
The line’s own system connected through the API: it opens bills, reads each bill, posts its invoices with their PDF and its official receipts, also on any payment already confirmed, and is told by webhook when a payment is confirmed, a DO released, a deposit paid or paid back, an export BL released, an empty release order issued, or a customer’s request comes in
A forwarder’s or broker’s own system works its bills with the line through the API — house bills, shipping bills, VGMs, invoice and DO asks, payments — told as soon as an invoice is posted to it, its DO released or a Form 13 issued, and VGMs for many containers go in from one sheet
On the phone in the SCMTR.io app: each bill’s house bills, invoices, payments, deposits, DOs, Form 13s and export papers, each container’s last free day, the arrival notice, and your approvals, KYC and reports — pay a bill’s open invoices on the line’s own payment page, approve a draft BL, a payment a colleague prepared or a release, or share your KYC, each asked first — with a DO’s or Form 13’s check link shared to WhatsApp and alerts that open the bill
Lines are being switched on with SCMTR.io support as the payment terms are finalised. Line desk invoices and payments, with the TDS withheld, taken to the books you already keep — for a shipping line as sales and receipts, for its customer as purchases and payments: posted to your own Zoho Books organisation, or downloaded as two files made for Tally’s import — your parties, then the vouchers — or as a plain sheet for any other accounts package
Can a shipping line file its SAM and SDM on SCMTR.io?
+
Yes. Open the manifest from a file or build it on SCMTR.io, check it against the CSNs its lines quote, sign with your DSC and send it to ICEGATE. Customs’ reply is read line by line.
Does SCMTR.io build the SAA amendment?
+
Yes. Build amendment starts from the manifest customs accepted and sends only what changed, numbered the way customs holds your lines. Where customs asks for a line to be dropped and re-added, it builds both.
Can several people and branches work on one manifest?
+
Yes. A line’s organisation has branches, view-only members and sub-agents. Several people work on one saved manifest at once, one person on each line, and forwarders send change requests the line approves.
Does SCMTR.io do the eDO, invoices and ePayment for a shipping line?
+
Yes, on the Line desk: customers send their house bills (eHBL) or CSN, the line posts its invoices as its own system raised them, its customers pay into the line’s own account — by bank transfer, and online by UPI, card or net banking once the line connects its payment provider — security deposits and detention are invoiced and paid the same way, and the line issues the electronic delivery order (eDO) with a QR code any CFS can verify. Lines are being switched on with SCMTR.io support as the payment terms are finalised. A shipping line whose organisation SCMTR.io has verified writes to support@scmtr.io; the line opens its bills from its SAM and invites its customers, and a customer can also open a bill itself by naming the line and the master bill, or straight from its own CSN.
Does the Line desk handle VGM and Form 13?
+
Yes, on export bills: the shipper, or its forwarder or customs broker, forwards each container’s VGM to the line with the weighbridge slip, and the line accepts it and issues the Form 13. The line loads its Form 13s into the terminal’s own system with the file SCMTR.io gives — APM Terminals Mumbai’s mass-upload file first — and a gate that checks papers can check each one by its QR code. The shipper still files its VGM on a website DG Shipping has approved, which SCMTR.io is not, and the line files VGM with the terminal through its own system.
Everyone else on the vessel call works here too
SCMTR.io is an independent filing platform for India’s Sea Cargo Manifest and Transhipment Regulations (SCMTR). Forwarders, NVOCCs and consol agents, shipping lines and steamer agents, CFSs, ICDs, transhippers and customs brokers prepare their SCMTR filings on it, check them before ICEGATE sees them, sign them with their own DSC, send them to ICEGATE and follow customs’ answer.