Skip to content
Changelog

What shipped in September 2026

Everything that went live in September 2026, newest first, with the date it went live. The newest changes are on the changelog, and what we are building next is on the roadmap.

159 changes

September 2026

  • Filing

    A line from a CSN finds the MCIN on customs’ record when the forwarder’s CSN has none

    A forwarder’s CSN that only refers to the master bill is given PCINs for its house bills and no MCIN; the MCIN belongs to the other CSN on the bill, the one that declares the master itself, and that is the one the line quotes. “Add a line from a CSN” now finds it on customs’ public record and quotes it, naming the CSN it came from. The containers it adds follow the manifest: the bond flag starts as the one every box already carries, and the final destination is written only where the manifest’s other boxes have one. An item with no description of its own is no longer flagged.

  • Platform

    A question asked of the assistant without signing in is now kept for 90 days, with nothing that identifies you

    Until now a question typed into the assistant on the public site was answered and not kept; only a signed-in person’s was. From 30 September 2026 a visitor’s question is kept too, for 90 days, with its answer and the page it was asked from — and no name, e-mail address, IP address or cookie beside it — so we can see what the public pages fail to explain. The assistant says so under the box you type in, and the privacy policy sets it out. As before, please do not paste bill numbers, party names or a whole filing into the assistant; use the file check.

  • Checks

    Counting customs’ manifest keeps every detail of each line, and a count already made is ready at once

    Count what customs holds now keeps everything customs’ public record gives for each line — the CIN it quotes and its own, the cargo type, every port, the transhipper, each house bill with its figures, and each container with its sequence, type, size, weight, status, agent and bond — and the line map shows all of it, with Copy this line. The panel also shows what ICEGATE records for the vessel call: VCN, IMO, voyage, terminal and inward date. When the same manifest has been counted recently and customs still holds that version, your count is ready straight away; Count again counts it afresh.

  • Checks

    A line declared C that names its CSN by MCIN is stopped again, with a one-press fix

    A manifest line declared C (compare with a CSN) that names the CSN by its MCIN instead of its number and date is red again — customs answers it with 159 “Incorrect Cin Type in MC” — with a button that sets it to Y; a reply carrying 159 says the same. A box two added lines share is no longer said to weigh differently on the vessel’s list when its shares add up to the same figure.

  • Checks

    An SAA line that re-declares a bill a CSN already declares is stopped (error 753)

    Customs answers 753, “Amd-MC-MBL Details Already Exists”, when an SAA adds a master bill as a fresh consolidated line with its own house bills while a forwarder’s CSN already declares that bill. When you open an SAA, SCMTR.io now checks customs’ record for a CSN on each bill the SAA adds as a new line, and stops the file in that case: quote the CSN instead (consolidated with its MCIN, or straight with its PCIN) and leave out the line’s own house bills. A bill customs could not be asked about is listed as not checked rather than passed.

  • Filing

    Country and PAN boxes take the first letter, Form III drops a default organisation name, and a missing HS code shows on the checklist

    In the guided steps, the first letter typed into the shipper country or consolidator PAN box was lost, so it had to be typed twice; it no longer is. Form III prints “For” over the signature line when your organisation still has the name it was given at sign-up, instead of that name. And the printed checklist always shows the HS code row, marked missing — or missing on a named item — where an item has none.

  • Checks

    The check against the line’s SAM before sending says which BLs it could not reach

    Before Sign & upload, a BL the check against what the shipping line filed could not reach in time is shown as not checked yet — it never stops the upload — and the headline counts them, so a partial answer never reads as the whole CSN. Autosave on very large drafts is lighter too.

  • Filing

    Add a line to an SAA from a CSN, quoting the CSN’s MCIN or PCIN

    Adding a line to an SAA from a CSN now quotes the CSN’s master MCIN or PCIN from its acknowledgement, and falls back to the CSN number and date only when neither is known. The line takes the CSN master’s parties, ports, transhipper, weights, items, containers and route, is stamped as an addition, and anything still missing is asked for in one form before it is added. The manifest’s line and container totals move with it.

  • After filing

    See when your file reached ICEGATE, and values the guide does not name

    An acknowledgement now shows when the file it answers reached ICEGATE. A CSN opened read-only lists, under “Also in the file”, values carried under names the filing guide does not use — such as the shipping bill number and date exporters write beside the PCIN.

  • Checks

    Another party’s CSN on your master bill no longer locks your amendment — it warns of error 320

    When another party’s CSN on the same master bill of lading had been accepted, the filing page said your CSN “can no longer be amended or deleted” and switched both off. It is now a warning: the amendment and the deletion stay available, on the filing page and on SCMTR JSON upload, and the page says customs may answer 320 (“CSN is Linked to Other CSN — Amendment is Not Allowed”), in which case the correction goes to the shipping line and your jurisdictional customs officer. A brand-new CSN on such a bill is still stopped, and the shipping line’s manifest works as before (ICES Advisory 37/2026: the amendment stays open, a deletion is the officer’s).

  • Platform

    “Ask a question” in the header, and a feedback button that no longer looks like a chat

    The SCMTR.io Assistant now has its own button at the top of every page, on the public site and in the app, and the first entry of the phone menu (taken out again on 6 October 2026 to make room for the pending split-ups pill; the corner launcher stays). The corner button says “Ask a question” on every screen, phones included, in brighter blue. Feedback has a megaphone instead of a speech bubble, so the two are no longer mistaken for each other.

  • Checks

    An SAA whose declaration says S instead of U is stopped

    The declaration block of an SAA or SDA says what the amendment does to the manifest as a whole, and the guide allows only U or D there — S belongs on the lines and containers it adds. SCMTR.io now stops such a file and says to set it to U.

  • Checks

    An IMO number with the ship’s MMSI beside it is caught, with the number to keep

    Ship-tracking sites print a ship’s IMO and MMSI as a pair, and an IMO field carrying both is refused with error 016, “Invalid Transport Means No/IMO Code”. The field already stopped such a value; it now names the IMO to keep and says the nine-digit number is the MMSI. A 016 on an acknowledgement comes with its own fix steps and, with your CSN beside the ACK, says what your file shows. The export fill from documents also reads more bills of lading correctly, writes customs’ gross weight in the unit your filing already uses, and shows customs’ answer only while the shipping bill on screen is the one it answers.

  • Filing

    Fill an export from its documents: the B/L, then customs’ record of the shipping bill

    The bill of lading step of an export now opens with “Fill this export from your documents”. Drop the B/L’s PDF and it fills the bill, the parties, the containers with their seals and the goods, and keeps the shipping bill number and date the goods description names. Then “Fetch from ICEGATE” shows what customs’ record holds for the shipping bill: the PCIN and its date, whether the let export order is given, the packages and gross weight, the port of discharge and the containers. One press fills what is empty; a field you already filled that customs’ record disagrees with is shown beside it and changed only if you tick it. What is still left to fill is listed last. A PCIN still never comes from a document.

  • Platform

    Large filings save and open faster

    A draft with hundreds of bills now saves and scrolls faster. A file dropped on the inspector opens quicker, a reload reopens it, and on a file with hundreds of master bills a jump to a problem lands on its bill wherever it is in the list.

  • Checks

    Counting customs’ manifest: every line on the map, under the line’s PAN too

    Count what customs holds now keeps each line’s summary for the line map whoever counts it — an agent filing under the shipping line’s PAN included — and the map colours the lines that quote no CSN, the exception, while the count runs. A count no longer stops short at a run of unused line numbers. An SAA whose totals count only its own rows is now a warning rather than an error; a template’s placeholder code where a PAN belongs is an error.

  • Checks

    Check with customs asks about every bill, and remembers what customs confirmed

    Check with customs no longer stops at sixty master bills: it asks about every bill in the file and leads with the ones that need your attention, so you can fix those first. What customs confirmed is remembered for a while, so after a fix only what changed is asked again. The free file check without an account now takes a CSN up to 3 MB, and an ACK dropped onto a filing can be up to 3 MB too.

  • Checks

    A shipping line’s export CSN for a whole vessel is checked, not turned away

    SCMTR JSON upload now checks a CSN up to 3 MB once you are signed in — a line’s SCX for every bill on a ship runs past 2 MB — where it used to stop at 1 MB and send the file to the manifest screen. The free check without an account still takes 1 MB and sends a larger CSN to sign in. A file just under 1 MB no longer fails with “something went wrong on our side”. A CSN that size can be signed and sent from here too, and a file whose spacing makes it too large to carry is refused with its size instead of an error. Foreign cargo transhipped out on an SCX (cargo type TR, movement FT, a consignor abroad with no code) is no longer flagged. A deletion that states zero lines is no longer stopped. And a CSN advice on a large file names the bills it did not ask customs about.

  • Filing

    The port a CSN is reported at, filled in when Settings leave it blank

    If you file at many ports and keep the receiver ID blank in Settings, typing the port of reporting now fills the receiver ID, and with both blank the route’s first port of entry fills both — in the guided steps and the full form. A port you type yourself is never replaced. For cargo delivered to an ICD or SEZ, the port of receipt and the next port now follow the destination when you correct it, as long as you have not set them to something else.

  • Filing

    More filings on a page, and a page that says when SCMTR.io has been updated

    The CSN filing list shows 20, 50, 100 or 300 filings a page. The address book now fills in the blank details of a party it already holds from a file you download, never changing what an entry already says. And if SCMTR.io is updated while a page is open, a bar at the foot says so and offers Reload, instead of buttons that quietly stop working.

  • Vessels

    When the cargo reaches India, from the master bill of lading

    Put a master bill into BL tracking and press Find the arrival, or open the CSN: the Arrival card shows the day the ship is due at the Indian port and its route. For SITC, HMM, ONE, MSC, COSCO, Evergreen, Yang Ming, KMTC, Sinokor and Cordelia the date is read from the shipping line’s own tracking; for other lines the card opens their tracking and your team can add the date it shows, marked as yours. Send on WhatsApp writes a short update with the date, the ship and a link.

  • After filing

    The SAA checks are a pre-check: what would change the manifest by mistake is an error

    Against an up-to-date count of what customs holds on an arrival manifest, a container total below the count, a container added that customs’ lines already name, a bill added that customs already holds from your submitter, and a line added under a number your own manifest already uses are now errors to fix before sending — each is either refused by customs or a change you did not mean; a container total above the count stays a warning. And point at a line on the count’s map to read it: its master bill, cargo, house bills and containers, for a manifest filed under your own organisation’s PAN.

  • After filing

    Open an SAA and see at once what customs would refuse

    The top of the shipping line filing page now says whether the file can be sent: the errors customs refuses, each with how to fix it, and a copy or WhatsApp share of the fixes for whoever made the file. Opening an SAA checks every bill it changes or adds against customs’ public record, and counts the manifest customs holds by itself, with the count’s progress shown as it goes. A wrong line total, a line added under a number customs shows in use and a line addressed under the wrong number are errors; a container total below the count and a container or bill added a second time are warnings. If a check could not run — ICEGATE did not answer, or the count needs a bill — the page says so instead of showing all clear.

  • Platform

    Faster pages when you are signed in, and on large filings

    Your filings, vessel calls and a filing’s own page open markedly faster, the shipping line filing page and the file check load less before you drop a file, and a large consolidation or manifest is checked with less work on every keystroke. The alerts bell counts only what you have not read, and “Mark all read” now marks every alert, not the first thousand.

  • Platform

    The activity log is kept for twelve months, and its record of your filings with the filings

    The record of who did what in your organisation is kept for twelve months and then deleted, as the privacy policy now says, except its record of your filings: who sent each one, what customs answered, every read of a kept file and every support session. That part is kept as long as the filings are, which is as long as customs record-keeping requires.

  • Platform

    See every browser and phone signed in to your account, and sign any of them out

    Settings → Sign-ins, also in the account menu, lists where you are signed in: the browser or app, when it signed in, the IP address it came from and roughly when it was last used. Sign one out, or every one but this browser. When your account is signed in to from a device it has not used before, you get one e-mail saying so.

  • Filing

    The master’s FCL or LCL stays as you set it

    A container’s status on the master bill is FCL until you change it on the master. A house bill no longer turns it LCL, and taking the last house bill off a container no longer blanks it. Where a container is on one house bill and the two disagree, both say so in amber, and one click takes the house bill’s status across.

  • Checks

    A reminder when you leave blank what filings usually give

    A notified party in India with no PAN, a bill with no gross weight, an item with no package count, a container with no seal, weight or agent code, and a few more: the message guide calls them optional, but CSNs and manifests usually give them. Each now gets an amber reminder at the field. None of them blocks signing.

  • After filing

    Count the manifest customs holds before your SAA goes, with no ICEGATE login

    In the Checks tab, Count what customs holds shows every line customs holds now for your vessel call and the containers on them, with no ICEGATE login. Only a manifest filed under your file’s own submitter is counted. Your SAA’s line and container totals, and the line numbers it adds or changes, are then checked against that count. If customs holds a newer version, you are asked to count again.

  • After filing

    A refused SAA still tells the next one how many lines customs holds

    When the only reply here is customs’ refusal of your amendment, it is still used to check your line total and addresses. Reopen the very SAA customs refused and the totals it was refused for (89, 90) are flagged until they change. Both are warnings: a refused reply cannot say for certain what customs holds now.

  • Vessels

    A container two lines share is LCL on the SAM (later changed: it now follows its lines)

    A SAM built here follows the lines for a box two of them share, the Checks tab notes a shared box that is not LCL (a warning), and on an export a box two of your shipping bills share is suggested LCL. You can still change it.

  • Filing

    Paste a party and the city, state, PIN and country land in their own fields

    Foreign parties and bills with no GSTIN included: the end of the address is read for the country, PIN or ZIP, state and city, and the preview says where each value came from. Paste now works on the full form too.

  • Filing

    Parties, vessel and items are remembered when you download a filing or customs accepts it

    The address book used to learn only from filings sent from here. It now learns from a filing you download to file on the portal, and from one customs accepts, so the next filing offers the same consignee, vessel and items in one pick.

  • Checks

    A problem in a filled field is shown at once, and the package type takes letters only

    A pasted, picked or reopened value no longer sits under its field in grey until you touch it; a field you are still typing in waits until you leave it. The package type takes letters only as you type, and a digit in a file’s package type is noted as a warning.

  • After filing

    Your filing says when customs’ record shows the vessel granted entry inward

    The inward date on the line’s manifest record is the one public sign that entry inward was granted. When it appears, the filing says so, and its amendment note names both published positions: Advisory 37/2026’s officer approval, and 373/374.

  • Platform

    A signer opens a preparer’s draft, and Sign & upload asks whether you may send first

    With only signers sending, a signer opens a colleague’s draft from the filing page, checks it and sends it. Sign & upload says whether you may send before it asks for the DSC Signer, a refusal names only people who can act, invitations say Admin and Member, and notices stay until you have read them.

  • Filing

    Correcting a draft clears the spreadsheet import’s hold on it

    A draft held by a note from a CSN spreadsheet import is released once the value the note objected to has been corrected, instead of staying held until the batch is re-imported.

  • Checks

    BL tracking and the free check say SDM and sailing for an export

    An export CSN is matched with the line’s departure manifest, so BL tracking and the free check now say SDM and sailing where they said SAM and arrival, and the check says how many of a file’s master B/Ls customs holds nothing on yet.

  • Platform

    26 more walkthrough films and a new chapter in the SCMTR guide

    Short films for the address book, a vessel’s CSNs from one spreadsheet, Form III, BL tracking, amending after entry inward, the line sharing its SAM and more, each linked from the help page it shows, and a chapter on the line’s SAM before either side files.

  • After filing

    An amendment is checked against the manifest customs holds before it is sent

    An SAA or SDA cannot say what customs holds now, so a wrong line or container total (90, 89), an added box numbered inside customs’ list (394) or a line updated under a number customs does not hold (306, 749) used to be found only by the refusal. Once an accepted reply for the vessel call has been dropped on Shipping line filing, the Checks tab, Build amendment and Sign & upload check the amendment against the manifest it lists, with each total and added number correctable in one press, and the upload is refused while a total or an added number disagrees. Where the reply may not show the version customs holds now, the checks are warnings and say so.

  • Checks

    An export with a transhipment bond and no transhipper is told to drop the bond

    An export CSN naming a transhipment bond on a line with no transhipper PAN used to draw “Transhipper code is normally required” on every such line — the wrong field, since an export needs no transhipper. The note now says so and gives the two ways out: remove the bond, or give the transhipper’s PAN beside it. Amber, as before.

  • Platform

    Signing in is signing up, and a new account is welcomed rather than told the terms changed

    The sign-in page now says why you are there — “Your checked file is waiting”, held for 30 minutes, when you came from the free check — and that the same buttons create a free account; there is no separate sign-up. An account new to SCMTR.io meets “Welcome — one step before you start”, with how files are treated and that your DSC stays on your own token, instead of being told that terms it never saw have changed. Filers who knew the earlier terms still see what changed.

  • Checks

    A CFS at the gateway port takes one leg or two, and the route no longer warns either way

    A CSN whose destination is a CFS under the port the ship called at may carry the sea leg alone, or add a road leg from the gateway. The route step used to ask whether such a destination was a berth or a CFS; it now files the sea leg alone, says so in a plain note, and a road leg into the CFS is yours to add if your practice is to declare it.

  • After filing

    Form III says N.A. for a transhipment bill instead of waiting for an IGM line that never comes

    A house bill moving on to a foreign port is not mapped onto an IGM line, so the form told the filer to wait for a number that never comes and counted the bill as awaited. Such a bill now reads N.A. with the reason, on the sheet, the PDF and the e-mail, and leaves the awaited count. A number customs did give is always printed as it is.

  • Platform

    Managers, signers and company e-mail addresses, set out under Settings → Team and Workspace

    Roles stay Admin and Member. Anyone somebody reports to is now a manager, who sees and corrects their team’s filings; the reporting line is drawn on Settings → Team, and a leaver’s people are handed to someone else when they are removed. Settings → Workspace adds two optional rules: Only signers send — everyone prepares a filing, and only admins and the people marked Signer may press Sign & upload, told before any DSC is asked for — and Company e-mail addresses only, which refuses an invitation to any other address, with named exceptions, and never removes anyone already in.

  • Platform

    A filing agent can file for client companies, and a company can change its agent whenever it likes

    An organisation that files for other companies turns it on under Settings → Workspace and adds a client on Clients — by the PAN a company already on SCMTR.io files under (its admins are asked, and told only who is asking), or by setting up a company new to SCMTR.io. The client chooses Files only or Runs the account, whose ICEGATE ID the files carry, and an end date if it wants one. Its filings and its admins stay its own, and it can end or switch agents at any time without losing a filing. The agent’s people work in a client as its account lead and handlers, are named in its records by the agent’s name, never their e-mail, and never become its members. The header says which company you are filing for.

  • Platform

    A tab left on one organisation can no longer act as another

    If you work in two organisations in two tabs and switch in one, the other used to carry on as the new one — suggestions from the wrong address book, a manifest sent as the wrong company. Each tab now knows which organisation it was opened for, and a request from a tab that no longer matches is refused rather than followed: the tab says so and offers Keep working here or Reload. A draft opened from a link or a reloaded tab is refused unless the organisation you are in can see it.

  • Platform

    The assistant writes its answer as it goes, with its sources listed

    An answer used to take five to seven seconds behind three dots. Now the assistant shows what it is looking at straight away, the answer appears as it is written, and Sources under it links the pages behind the answer — open one to read the whole thing. An answer cut short keeps what arrived and says so.

  • After filing

    A refused amendment that comes back 89 and 90 tells you the line total — a count, not the highest number

    Customs does not renumber a manifest when a line is deleted, so a manifest holding lines 1 to 627 without 456 has 626 lines, and declaring 627 is refused (89, 90). Open the refused reply beside the manifest and the page works out the line total and sets it in one press. The container total is not in a refused reply; take it from the SAM customs accepted and every amendment accepted since.

  • Checks

    One rule for the control number after a 700, and four new answers in the knowledge base

    Four pages disagreed on whether a filing refused with 700 goes back under a new control number; every page now says the same: a refusal in an acknowledgement, 700 included, frees its number; an accepted or still-unanswered send needs a new one, so an amendment always does; and when you cannot tell what became of a send, a new number is the safe choice. New sections answer whether a TG bond is mandatory for a CSN (an ICD yes, an SEZ and DPD no, a CFS by port), how an LCL house bill in a consol box is filed for an ICD through a gateway port, what IEB means on the registration form, and where to look when Continue stays dark on the master bill step.

  • Platform

    A new version of the data processing agreement: the assistant’s search now stays in India

    When you ask the assistant a question, or type a suggestion into the roadmap, the search through our reference material now happens in Mumbai instead of the United States, so that step stays in India. The privacy policy says so, and the data processing agreement now does too, as its version of 26 September 2026 — nothing else in it changed. If your organisation accepted the earlier version, Settings → Enterprise shows it as an earlier version until an Org Admin accepts this one.

  • Filing

    Sign & upload notes what customs already holds under your number or your PAN, without stopping you

    Beside the checks that stop a duplicate, two notes now appear at Sign & upload and never block. One says the control number on this file was already used on this job date — by a filing sent from here, brought in from the portal or recorded as made elsewhere — and what came of it; customs does not process one control number twice on a job date, so the send may come back as already processed, and the note names the filing to open. The other says customs’ own record already lists a CSN accepted under your PAN on this master B/L, so a fresh CSN would be a second copy rather than the amendment you may mean. Each says what to look at; if you know better, you send as you are.

  • After filing

    A manifest reply recorded on the wrong send can be taken off it

    A send gets one answer. When a reply was recorded on the wrong one of two sends of the same manifest — the same file sent twice from different logins, say — it used to sit there for good. An organisation admin can now remove the ACK from that send on the manifest page: the row reads as awaiting customs again and the reply can be recorded on the send it answers. The file you dropped stays in your files; only where it was placed changes.

  • Platform

    Browsers are told exactly which scripts a page may run

    Every page now tells your browser to run only the scripts the site itself produced. A script slipped in by a browser extension, an advert or a tampered network is refused rather than run. Nothing changes in how the app looks or works.

  • Vessels

    The terminal operator code is remembered from what customs accepted, not from what was uploaded

    The berth’s operator code has no published list, and customs checks it against the VCN (13). It used to be remembered the moment ICEGATE took your manifest, so a code customs then refused was offered back on your next manifest at that port. It is now remembered when customs’ reply accepts the send, and a code a reply refuses with 13 is forgotten — record the reply on the send and the next manifest at that port offers the right one.

  • Checks

    You are told when another filer on SCMTR.io has already sent a CSN on your master B/L

    As you type the bill number, and again at Sign & upload, the app says when another organisation using SCMTR.io has already sent a CSN on the same master B/L at the same port — how many, and whether customs has accepted theirs, never who. Two filings on one master are usually the line and the console agent, so it stops nothing; it is the moment to check what customs already holds on the bill, which the notice links to, before the later filing is the one refused.

  • Filing

    An export on the shipping line’s B/L, referenced only, is now a guided choice

    The bill step of a CSN Exit offers a third shape beside the straight bill and the consolidation: the shipping line’s B/L referenced only, with one line per shipping bill. The B/L keeps just its number, the line’s PAN, its totals and its containers; each shipping bill line takes its PCIN, its parties and goods, and its own destination. Until now this shape could only be filed from the full form.

  • Checks

    The HS code search asks DGFT again for a code the list does not hold

    A code the HS list does not hold is now looked up live with DGFT again, rather than answered with its chapter; the chapter is still shown for context.

  • Checks

    Five more values caught before you sign

    Three now stop the send: a UN number with a space around it (032), a master consignment flagged H (056) and a notified party coded as an IEC (045). Two are warnings: an Indian state written in letters (139/143) and a container with no size (072).

  • Vessels

    A nil SAM is told its placeholder row, and a SAM whose arrival is off customs’ record is flagged

    A call that lands no cargo still declares one piece of equipment: the published model is a single placeholder row on the vessel list with the totals 0 lines and 1 equipment. A SAM with neither is flagged, and one press writes the row and the totals. The check also flags a SAM whose expected arrival is on a different day from the one customs holds for its VCN — both warnings.

  • Checks

    The code lists brought up to date

    The coded values the form offers were brought up to date: the HS list now carries DGFT’s full tariff, the UN dangerous-goods list is complete, and missing customs locations were added. A container given different seal numbers on its bills (703) now stops a send while its neighbour (701) warns.

  • Sharing

    Five new webhook events for the line-first handshake

    Systems listening on your webhooks now hear when a line shares its SAM with a BL of yours (alert.line-sam-shared), when a shared line is checked against your CSN (alert.line-sam-share-checked), when a line names you on a BL (alert.line-sam-named), when a CSN is due before the line’s cut-off (alert.csn-due) and when the other side answers on a link you sent (alert.counterparty-replied). Each carries the job number, the port and the BL, never a party.

  • Checks

    Your CSN is checked against the shipping line’s SAM before it goes

    After the line files its SAM, a correction to your CSN is the line’s SAA — a request carriers charge for, with the consignee’s Bill of Entry held meanwhile. So Sign & upload now compares the CSN with what the line filed for every master B/L on it: a difference on a field customs cross-checks (B/L date, packages, container count, load status) needs a reason of your own, any other difference pauses you and never stops you, and a check that cannot reach ICEGATE never holds a send back. If the master B/L’s PDF is on file the CSN is held against that too. And nothing leaves for ICEGATE until a screen names the filing and you tick it.

  • Sharing

    A shipping line can share its SAM before filing it, and set its cut-off for CSNs

    Open the draft SAM or SDM and press Share with CSN holders: each forwarder here holding a CSN on one of its B/Ls is told whether theirs matches your line, differs or is not quoted. A link goes to anyone; a CSN dropped on it is compared and never kept. Name the forwarder on a B/L by PAN, set your own cut-off, and at that cut-off you are told which lines still have no CSN. A forwarder sees one line — its own B/L — and a draft never stops its upload. Forwarders are reminded of the cut-off a day before it, the line’s own where set and otherwise 72 hours before arrival, said as a default.

  • After filing

    Form III for the consignee, from the CSN customs accepted

    Brokers still ask for the old paper IGM’s one-page cargo declaration, naming the IGM line and sub-line each bill sits on. On an accepted arrival notice, tick the bills for one consignee, check the four details a CSN does not carry — shipping line, vessel, voyage, call sign, each filled in and each saying where its value came from — and print, download or e-mail the PDF. The IGM line comes from customs’ own record, never from your CSN’s numbering, and reads Awaited until the line’s manifest is on record.

  • Checks

    What must match between the line’s manifest and your CSN — every field, sorted Fix, Check or OK to differ

    Once the shipping line’s manifest (or another filer’s CSN) is on your master bill, your CSN’s page now lays every field the two can be compared on side by side, and sorts each difference into one of three groups. Fix: fields customs cross-checks — the bill of lading date, the packages, the number of containers and a box’s load status. Check: they should match, and one side is most likely mistyped — a container type, a weight, a port. OK to differ: customs does not compare them here — the first Indian port, the line’s own container bond. Which group a field falls in depends on whether the line’s manifest line actually quotes your CSN: a line that carries the bill with its own house bills is not compared with your CSN at all, and nothing on it is shown as a refusal. The same three words are used in the manifest editor’s ICEGATE check, on Bills and containers (a bill whose only differences are Check now reads “SAM differs — check”), in cases, on the tracker and in the e-mail you get about another filer: “Action needed” for a Fix, “Check:” for a Check, once per filing, and never for a difference customs allows. The reference page “What must match between the shipping line’s manifest and the forwarder’s CSN” lists every field.

  • Vessels

    A shipping line checks a SAM or SDM it opened before, without uploading it again

    Every SAM, SDM or SAA opened, sent or recorded here is now listed under SAM / SDM files kept here on the manifest page, and each version on a vessel call has Open in the editor — press one and it opens as if you had dropped the file, ready to check again against the CSNs the forwarders have filed since. Check the lines that quote a CSN (it was Check every line against customs) now also checks a line that quotes the PCIN or MCIN rather than the CSN number, and checks a departure manifest against the export CSNs. A forwarder’s CSN reference card pastes straight into a manifest line: its reference block fills all eight prior-reference fields at once and refuses a mistyped or swapped character. The card now carries each box’s seal, and when the line drops its manifest back on the card the forwarder sees what it was read as. On an export CSN, Bills and containers and its alerts now say SDM and SDA rather than SAM and SAA.

  • Platform

    A new version of the data processing agreement: where the assistant’s answers are written

    The data processing agreement now sets out where the assistant’s questions and answers may be processed, as the privacy policy already did, in its version of 25 September 2026. Nothing else in it changed: your filings and the files you upload stay in Mumbai. If your organisation accepted the earlier version, Settings → Enterprise shows it as an earlier version until an Org Admin accepts this one.

  • Checks

    Every bill in your CSN checked against customs’ record, and told which version customs holds

    Check with customs on the checker used to stop at six master bills and say so. It now asks about every bill in the file, with the count climbing, under one line for the whole file — how many bills customs holds exactly as the file has them, how many differently, how many not at all — with the bills that need reading first and the rest folded away. Where a bill differs, the dates now say which kind of difference it is: customs’ record carries the date of the latest version it accepted, so a record dated after your file is named as the amendment or re-filing that superseded it. Each coded value is read out beside the code, so a destination that moved from a Nhava Sheva CFS to a Mundra one reads as that. Every bill links to its page on BL tracking, and BL tracking now takes the file the other way: drop the CSN under any result and the whole file is compared, signed in or out. The tracking page’s green line says what it compares — the filings customs holds, against each other — so it can no longer be read as a verdict on your file.

  • Sharing

    Send the shipping line your CSN details in one message, instead of keying them into its portal

    The line cannot file its arrival manifest until it has your CSN, and most lines collect it through a portal you log into and type into — the CSN number and date, the PCIN, the VCN, the container ISO code — with the charges landing on you if it arrives late. Drop your CSN on SCMTR JSON upload, press Check with customs, and once customs’ record answers with a CSN number and date you can send the line the whole handover in one message: the reference, the voyage, every bill with its date in both forms and the MCIN or PCIN customs issued it, every container with its ISO type, size, load status, agent PAN and bond, and all eight prior-reference fields ready to quote. It comes with a spreadsheet the line’s desk can paste straight into its own sheet, the same content as JSON for a system to read, and a page where every value is one click to copy. Every value is read from customs’ own record rather than from your file, so what the line keys is what its own filing will be checked against — the SOC flag and the seal come from your file and say so. Where your file and customs’ record disagree, the message carries customs’ values and lists the differences underneath. Offered for an entry, an exit and the amendments to either. And the checker’s own Email this file now says what customs’ record says: accepted — with the CSN number, the CINs and the handover attached — where the record lists the file’s filer; not on record yet where it lists nobody by that PAN; not checked where the record could not be read.

  • Sharing

    E-mail a CSN before you file it, and e-mail a file you only checked here

    Email used to be offered on a filing that had gone to customs. It is now offered on a draft as well, whatever its reporting event: the consignment as it stands goes to the line, the CFS or your customer so that a wrong container number or a missing PAN can be corrected while it still costs nothing. The message claims nothing — the subject begins “DRAFT — not filed with customs”, the stamp reads “Not filed yet” rather than a green or red verdict, the CSN reads “None — not filed yet”, and there is no customs tracking link on it, because customs has not been told about the bill and an empty lookup reads as lost cargo rather than as an unsent file. The message’s own page keeps a copy of exactly what was sent, so going on editing the draft does not rewrite what your recipient sees. And a file dropped on SCMTR JSON upload can be e-mailed the same way — under the name you dropped it as, with what the check found — for the console agent’s CSN that arrived by mail or the customer’s file you were asked to look over.

  • Filing

    One number names a transmission: your job number is now the control number too

    ICEGATE builds the required file name from your job number, and files made here now use that same number as the control number too — in the header, in decRef and in the file name alike. Customs does take a file where the two differ, and this does not block anything; what it costs is recognising the answer, because customs names its reply after the control number. The one exception is a second transmission of the same job on the same job date, which cannot reuse a number customs has already processed, so it takes one of its own and the filing says so. A refusal does not use a number up, so “Fix and file again” keeps yours. Dropping a file on SCMTR JSON upload now points out when its two numbers disagree, for a CSN and a SAM / SDM alike — as a note, never a refusal.

  • Filing

    Type the country’s name instead of guessing its two letters

    The country boxes took two characters, which meant the only names you could search were the ones whose first two letters you already knew — type BA and you were offered Albania, Antigua & Barbuda, Aruba and Azerbaijan before Bahamas. They are now search boxes: type Vietnam, UAE, South Korea, Turkey, Ivory Coast, Czech Republic or Holland and the right country comes back, accents and “and”s and brackets included, and only ever a code is stored. UK now answers the United Kingdom — it used to answer UA, Ukraine. Two-letter codes still go straight through untouched.

  • After filing

    The checklist prints full pages instead of a nearly empty first one

    A filer reported that the printed checklist’s first page “is having hardly any information”. It was: a master bill section that did not fit in what was left of page one was moved whole to page two rather than split, leaving three bands of summary and half a page of white. Sections and cargo cards now flow across a page break, while headings stay with what follows them and no table row, container line or reconciliation figure is ever cut in half, so a checklist takes fewer pages.

  • Filing

    The container table waits until you have been in a cell before it turns it red

    A brand-new filing in the wizard opened with “Equipment / container ID is required for this reporting event” in red under a row the wizard had just added for you, before you had typed anything. Every other field on the step already waited for you to leave it; the container table now does too. What is required is still on screen, still counted at the foot of the step and still listed in full at review — it simply is not shouted at you about work you are in the middle of starting.

  • Filing

    Checking a manifest against customs now looks up IEC codes too — as a note, never a verdict

    A shape check cannot catch a code that is well-formed and simply not a code. So Check every line against customs now also looks up each IEC-typed consignee code on the file in customs’ own Import-Export Code register, with every line and house bill that carries it listed, and a code the register does not return is noted under the result, in amber: something to check against the bill of lading before you send, not a refusal, because a code just issued at DGFT can be absent while being right. PAN-typed codes are never looked up (a consignee who is not an importer would come back unknown while being correct), a malformed code is already the shape check’s finding, and a lookup that does not answer is said as “not checked”, never as “unknown”.

  • Filing

    Three answers to filers: untick clears the copied consignee, a downloaded file is dated when it is written, and CON is on the package list

    Unticking “Same as consignee” on the notify party now clears the nine copied fields instead of asking whether to keep them — what is cleared is only ever a copy of the consignee, since the tick asks first whenever it would overwrite something you typed — and one press, “Undo — put the consignee’s details back”, restores them. A downloaded CSN file now carries the moment it was written in all three places customs reads a date: the header’s date and time and the job date together; the draft takes the same stamp as the file, so Record a filing made elsewhere still pairs the two — and pairs a draft on its job and control number even when the file was downloaded on an earlier day. And CON (containers) is offered on the CSN’s package-type list: a filer asked what a 20-foot ISO tank files as, and ISO tanks file as package type CON with the count equal to the number of tanks.

  • Filing

    ICES Advisory 38/2026: a manifest line is dropped and re-added, and a CSN may be deleted and re-filed before the SAM

    Customs’ six FAQs of 21 September 2026 are followed here. The manifest amendment builder now refuses an in-place change of a line’s consolidation indicator, consolidator PAN or prior reference (CSN, PCIN or MCIN) and asks you to remove the line and add it back — a removed line’s number is not reused, so the amendment carries the delete and the re-add together, the “first drop … and subsequently re-add” the advisory describes for putting a forwarder’s house bills onto a master bill filed straight. The guide, the FAQ and the knowledge base now say that customs’ stated position is that a forwarder may delete a CSN and re-file corrected particulars before the line’s SAM (amendment stays the lighter route), and that customs says a container’s ISO code and agent PAN are now validated on the line’s manifest rather than the CSN. The advisory is read question by question at /reference/ices-advisory-38-2026-faqs.

  • Platform

    The walkthrough films are linked where you need them — and the assistant hands them out

    Thirteen short films now, one job each, and every help or reference page a film walks through links it under its heading — including three new ones for the shipping line’s side: the SAA that takes a bill off a SAM, the SAA that puts a forwarder’s bill on from their CSN, and the rejection whose ACK names nothing. Ask the assistant how to amend a filing and it answers with the film as well as the steps. The full list is under Using the app; none of the films shows a customer’s data.

  • Platform

    “SAM / SDM” and “Shipping line filing”, in your words, wherever the product said “vessel manifest”

    The page, the tab, the drop targets, the assistant’s answers, the knowledge base and the phone app now all name the shipping line’s filing the way the trade does — SAM / SDM under Shipping line filing — so a help page never sends you to a place the header calls something else.

  • Checks

    Every field in a SAM / SDM is in the field reference — fourteen were missing

    The vessel movement type (FI, II or RI), the rotation date, the expected departure, the next port of unlading, the cargo type, the HS, UN and IMDG codes on a line and the container weight were missing from the field reference. They are back, with ICEGATE’s own wording, and the assistant can now answer questions about them.

  • Platform

    Container domestication: what it is, and why SCMTR.io does not file it

    Asked for as “TCI domestication” by filers in a trade group and in the app. Domesticating a container — turning a line’s duty-free box into a duty-paid one that may stay in India — is a Bill of Entry for Home Consumption under JNCH Public Notice 79/2008, outside the SCMTR messages altogether, and customs publishes no format for it. The knowledge base and the assistant now say so, and say which two things on the arrival manifest it does touch.

  • After filing

    An accepted CSN is recorded on its own, from customs’ record — no ACK to wait for

    Customs’ public record began showing the CSN number and date of each accepted filing in September 2026, and SCMTR.io now watches it for every filing still waiting on an answer. When customs’ record shows a fresh filing sent from here, and agrees with what was sent, the CSN number and date are recorded and the filing turns accepted; its history says the outcome was read from customs’ record, not from an acknowledgement. A rejection never appears on that record, so a refusal still reaches you only in the emailed ACK — a filing still submitted hours after its siblings were accepted is one to look for in the registered mailbox; and a filing accepted before September 2026 may show no number. Keep the ACK all the same: it is customs’ own file and the only one that carries a rejection’s reasons, and dropping one that agrees on a filing already accepted from the record keeps it as the transmission’s own answer. One that disagrees is refused for a person to settle. The Get the CSN number button on the filing’s page still asks the record on the spot.

  • Filing

    The bill of lading opens beside the form, and every value read from it jumps to its page

    A bill of lading dropped as a PDF for reading is now drawn in a panel next to the guided steps — docked to the side on a wide screen, a sheet over the form on a narrower one — with Show the bill / Hide the bill at the top of the steps, and it can be zoomed, rotated and its text copied. Every value read from the bill shows the page it came from, and that page mark is a button: press it and the panel jumps to that page, so a figure is checked against the document without a second window. It shows the PDFs dropped in this sitting; after a reload, drop the bill again. A platform administrator opening a kept file sees it drawn the same way.

  • Sharing

    The printed checklist names the notify party, and prints figures you can paste

    Three things from a filer’s testing. The checklist decided “same as consignee” from the name alone and printed the consignee’s block in its place, so a consignee notifying its own broker was shown notified at its own address; it now compares every field and prints a notify party with details of its own as its own party. Weights printed with thousands separators and at most two decimals, on a sheet whose values are copied into other systems, so a bill filed as 10290.184 read 10,290.18 where it was pasted; they now print as plain numbers, up to three decimals, exactly as filed. And a downloaded CSN file is stamped with the time it was written, so a draft started on Monday and downloaded on Wednesday no longer carries Monday’s time in its header.

  • Checks

    A manifest acknowledgement is not read as a copy of the file it answers

    A reply to a vessel manifest (SACHM23) does not echo every field of the file it answers — its version, message type and amendment types read the same whatever was sent, and a line’s prior reference reads “null” on a refusal. So the checks read what was sent from the file you sent, never from the reply. The advice for a refusal with no code now says to check the declaration block of the file you sent, ask the ICEGATE helpdesk quoting the tracking id, and refile under a fresh job number.

  • Platform

    No more e-mail about the privacy policy — a change is shown in the app, once, for you to accept

    The e-mail announcing changes to the privacy policy, sent to every account holder, was a nuisance and has been withdrawn. A material change to the policy or the terms is now shown the next time you open SCMTR.io and asks you to accept it before you carry on; nothing about it is sent to your inbox. Two of the announced changes were withdrawn with it and never took effect: a question asked of the assistant without signing in is answered and not kept, and usage events are deleted after 30 days. Signed-in assistant questions are kept 90 days. The weekly summary of what you checked and the occasional tip start from 23 September 2026, count only what you do from that day, and stop in one click.

  • Filing

    “Delete the SAM and file an SAA” — what your customer is asking for, and where it is

    The commonest request a shipping line gets right now is a forwarder asking it to delete the SAM and file an amendment, so a consolidation’s house bills reach the manifest. The platform has done that all along; nothing was called it, so nobody found it. Two things change. Removing a line now says what it is — it is how you “delete the SAM” for one bill — and when you build the amendment it spells out in plain words that customs is being told to delete that line from the manifest it holds, that the rest of the manifest is untouched and not re-sent, and that if the bill is going back on corrected you can add it in the same amendment — though customs has not said it takes a deletion and an addition in one SAA. Worth knowing, because the phrase alarms people: the SACHM23 message set has no deletion message at all — its six events are SAM, SAA, SDM, SEI, SDA and SDN — so “delete the SAM” never meant withdrawing the manifest, and never could. And the amendment now tells you who has to approve it before you sign. Whether an officer is involved turns on one fact — has customs granted this vessel entry inward — which the app already knows once you have asked about the manifest. Before entry inward, the process CBIC’s SCMTR team set out for the trade has no officer step (reported to the trade, not published in a notice). After it, you file first and the jurisdictional customs officer approves it afterwards, and customs’ record changes only then; the panel says so, in that order. It also names the flat ₹1,000 customs fee, and warns that the message guide’s errors 373 and 374 read as a flat refusal of what the September 2026 advisory allows — so an amendment after entry inward may come back refused rather than held. Where nobody has asked customs about the vessel, it says that instead of guessing: “not checked” is not the same answer as “no approval needed”, and only one of them is safe to act on. A step-by-step walkthrough is in the knowledge base.

  • Checks

    Customs’ answer to a manifest, read as one story: what happened, and what to do

    A refused SAM or SDM can come back with hundreds of marks that are really one sentence — and an answer to an amendment lists the entire manifest customs holds, so a two-line amendment can return seventeen hundred rows. Above customs’ own list the screen now says what happened in plain words: which rows are yours, which codes are one problem seen from two sides, numbered steps to fix it, and how much of the reading is customs’ word and how much is inference. Codes 385, 399 and 707, which are in no published list, are explained too.

  • Sharing

    An amendment can be emailed, and says that it is one

    The email button was offered on an arrival notification only, so a filer looking at an accepted amendment — with customs’ latest word on the bill — had no way to pass it on. An amendment to an arrival notification now sends the same way. Its subject reads “amendment accepted”, the text says these details replace the ones sent earlier for the bill, and the checklist names the event in words, so the line, the CFS and the broker do not take it for a duplicate. If no ACK is on the filing yet, the composer takes it there and then rather than sending you away to upload it.

  • Filing

    Every port in a list says what kind of place it is, and sea ports come first

    Typing “bangalore” used to offer the air cargo complex first, two SEZs next and the ICD last, with nothing to tell them apart. Every row now carries its kind — PORT, ICD, CFS, SEZ, INLAND, LAND (a land border or rail station) or AIR — and sea locations rank above an air cargo complex, in the Indian list and the world search alike, which also answers to the name on your paperwork (“Bangalore ICD”). The first port of entry offers sea gateways only, because that is where a ship arrives, and says so when an inland name finds nothing.

  • Filing

    The redundant-house-details check (370) names the two blocks to take off, and offers to do just that

    Error 370 — “redundant house details” — is what customs returns when a manifest line says its cargo was declared before and its house bills repeat what that earlier declaration already holds. This screen used to read it as “no house bills here” and offer to delete them. Customs’ own Trade Scenarios table asks for them — a house bill on such a line carries its own reference, its prior reference, its customs location and its containers — and excludes the transport document and the item details. So the check now stops a send where a house bill carries one of those two, and the one-press fix takes exactly those off and leaves the bills. Anything else the table excludes is a warning. A block that is present but empty no longer counts at all, since it is not sent. One more warning is new: an amendment action (amdType) on a full SAM, SDM, SEI or SDN, which tells customs to change a line it does not yet hold. Until now a stray “D” there also silenced this screen’s other checks on that line.

  • Filing

    Entry inward no longer switches the manifest screen off, because it does not end amendment

    Until now, once customs granted a vessel entry inward this screen said the manifest “can no longer be amended” and switched its tools off. That is one of two things customs has published, and it is the older one: the message guide lists errors 373 and 374 that read as a flat refusal, while ICES Advisory 37/2026 of 18 September says an amendment after entry inward is allowed with the jurisdictional officer’s approval — and the process CBIC’s SCMTR team set out for the trade has the amendment filed first and approved afterwards. So the screen no longer switches off: pre-flight stays available, because somebody preparing that amendment is exactly who wants it, and the screen now says what actually has to happen — the shipping line deletes what it filed, files the amendment, and a customs officer approves it — rather than that nothing can be done. (Corrected 25 September: ICES Advisory 38/2026, published on 21 September, settles what “delete” covers — the bill’s own line, dropped and re-added only when the change is to how the bill is consolidated, the consolidator’s PAN or the CSN / PCIN / MCIN it quotes. Any other amendment is an update to the line, with no deletion first.)

  • Filing

    Build an arrival or departure manifest here, with no other software

    A bulk, tanker, break-bulk or tramp call can now be filed from nothing: on Shipping line filing, take Start one from scratch. Give the ship’s IMO number and customs’ own record fills in the call — the VCN, the rotation number and date, the port and the expected arrival — so none of the five is copied off an e-mail. Then pick which of the four filings a call needs, in the words a steamer agent uses: the arrival manifest (what used to be the import IGM), entry inward, the departure manifest (the export EGM) and the departure notification. On an arrival manifest a bill of lading is ten plain questions — the bill and its date, shipper, consignee, what the cargo is, its HS code, how many units, the weight, where it loaded and whether it is dry bulk, liquid bulk or break-bulk — and the other thirty fields of the line are filled in for you, each shown with the reason and none of them locked. The totals, every sequence number and the vessel’s container list are counted from the file, so they cannot disagree with it, and the ports the ship called at are numbered for you. Your filing identity is typed once in Settings and each ship’s particulars are remembered, so its next call asks almost nothing. A departure manifest’s cargo lines are export lines and are added in the editor rather than from the ten questions. The manifest then opens in the editor, where it is checked, signed and uploaded exactly as one opened from a file — nothing reaches customs until you sign, and customs, not this app, decides whether a manifest is accepted.

  • Checks

    The export checklist wherever you look at an export, and two checks that now warn instead of block

    “What customs checks on an export” is no longer only on the guided steps’ last screen: drop an export file on the inspector and the same eight lines read it, and the full form’s issue list opens with “Export checks: N of 8 clear”. Two checks are now warnings rather than stops: an HS code repeated across a bill’s items, naming customs’ code 157, and a container whose weight differs between the master bill and its house bills’ shares, on imports as on exports. A package count that disagrees still blocks everywhere. And an export filed with cargo movement TI or FT is now told, in amber, that an export normally moves as TC.

  • Filing

    File an export (CSN Exit, SCX) through the guided steps

    Exports now have their own path through the guided steps. The first screen asks how many shipping bills the B/L covers: one is a straight bill that names that shipping bill’s PCIN; several is a consolidation, where the master names no PCIN — customs issues it an MCIN — and each shipping bill gets its own line with its own PCIN and its own containers ticked off the B/L. Each check names the code customs answers with and stops the filing before it is sent — a straight bill with no PCIN (159), one PCIN used twice (383/384), packages that do not add up (709) and more. The last screen lists them as “What customs checks on an export”, each line clear or naming what is wrong. Pasting the bill of lading, or dropping its PDF, fills the export’s fields and offers the shipping bill number it names — never a PCIN, which no bill of lading carries. And the two start cards on CSN filing are now named by direction: Import filing — CSN Entry (SCE) and Export filing — CSN Exit (SCX).

  • Filing

    Compact guidance for filers who know the form

    A Guidance switch — Full or Compact — at the top of the guided steps and in the full form. Compact tucks every explanation behind an ⓘ, sizes each box to the value it holds, and lays fields and whole sections side by side across a wide screen; warnings and errors always show. Everyone starts on Full, and once you have filed a few CSNs you are asked once whether you would like Compact.

  • After filing

    BL tracking marks what the shipping line’s manifest bears out

    Where a figure on your CSN is also on the shipping line’s own manifest, BL tracking now says so — a separate confirmation, not two filers copying one number. Every PAN on the public result shows only its last four characters, enough to tell filers apart without handing anyone with a bill number the whole identity.

  • Filing

    Nhava Sheva and Mundra CFS codes in the destination search

    The destination port search now offers the Nhava Sheva and Mundra CFS codes — INNSA1ELP1, INNSA1MSA1 and ten more — instead of other ports’ facilities. Where an operator’s name or bond is not known yet, the row says so rather than guessing.

  • Filing

    Plainer names on the wizard’s first step

    The master bill’s section on the first step is now headed Master Entry; the two ways to start from a bill are Upload bill of lading (PDF) and Paste bill of lading text; and the ports carry the names on your bill — POL, POD and FPOD. The house bill is stated rather than asked — House B/L (HBL) included, with Add HBL or Remove it beside it — and the vessel box uses your words: Vessel name / Voyage, IMO no., VCN, and Fetch VCN here when you do not have one yet. Searching a port by name flags a trade code filings still use.

  • Vessels

    Every vessel call gets its own page

    Vessel calls, in the header, opens a page per ship’s call at a port — the port, VCN and rotation number — where your CSNs on it, every manifest transmission and customs’ reply, and the files either side has shown for it sit together. It appears on its own the moment a filing or a kept file first names the call.

  • Vessels

    See which of your containers are held, and why

    Bills and containers, on each vessel call’s page, reads every bill and container of yours on the ship against the shipping line’s manifest and customs’ record — worst status first, with the one next step for each: no CSN on record, a difference from the manifest, an amended CSN, or nothing open.

  • Checks

    Explain this rejection

    Customs’ reply to a refused vessel manifest names most lines by number only. Explain this rejection finds every refused line’s bill on customs’ own public record, compares it with the CSN it quotes, and says in one sentence whether it is a data error at all — with a CSV and an evidence pack to send the helpdesk.

  • Filing

    Upload bills of lading, the PDFs themselves

    Drop the master and every house bill of lading as PDFs and the wizard fills itself the way a paste does — plus what a paste cannot know: which document is the master and which are the houses, each box’s own seal, and a copy kept so a filing can be checked against it later.

  • Filing

    Build a manifest amendment, and fill in the CSN references it needs

    A shipping line or its agent can now build a minimal amendment from the manifest already open — only the lines that changed — add a line generated straight from the CSN it quotes, and fill a manifest’s missing CSN references from the call’s own CSN list, under the organisation’s own ICEGATE portal login.

  • Filing

    File a vessel’s worth of CSNs in one sitting

    Import a spreadsheet or a folder of CSN files and CSN batches checks every one, walks you through what needs attention, and signs and sends them in turn — one job, not one filing at a time.

  • Sharing

    Send a CSN reference to the carrier, without handing over the filing

    A handshake link opens a read-only page for whoever files the counterpart consignment on your bill — the seven contract figures customs cross-checks, and nothing else of the filing. They can drop their own file back to you from the same link.

  • Sharing

    A shared page to sort out a disagreement on a bill

    Cases opens a page for a problem on a vessel call — a refused manifest line, a CSN that disagrees with the carrier’s — with a read-only link for the other party, messages drafted from what customs’ record actually shows, and a timeline of what has been shared.

  • Platform

    API keys and webhooks, for organisations whose plan includes them

    An Org Admin can mint an API key and register a webhook endpoint under Settings → API, so your own systems can check and send files to SCMTR.io and hear back by signed webhook. Plans are not sold in the app yet — write to support@scmtr.io if your organisation needs this.

  • Platform

    Every file you upload is kept, so a filing’s history stays together

    Declarations, acknowledgements, vessel manifests and customs’ replies are now kept for two years whichever screen you upload them on, so a filing can be linked with its replies and amendments over time and support can work from the files themselves. The updated terms say what is kept and why, and you are asked to accept them the next time you open SCMTR.io.

  • Checks

    A CSN with no acknowledgement is checked against customs’ own record

    Drop a CSN on Check an ICEGATE file without its acknowledgement and it now checks customs’ public record for whether that exact version is on file: green when it is, amber when customs holds a different version — with the fields that differ, weights compared to the two decimals customs keeps — and grey when nothing by your PAN is on record for the bill. The same lookup is the honest answer to “can I file this bill fresh”: a listed bill draws 122/123 and wants an amendment; a blank one is taken, as a new CSN with a new PCIN.

  • Checks

    Export refusals 091, 159 and 365 caught before sending

    On an export, an itinerary leg whose port of call is also its next port of call is refused (091); a previous declaration of type S, B or Y needs the CIN type and the PCIN in the previous-reference block (159); and transhipment cargo whose port of receipt is an Indian port should be local clearance (365). All three now stop the filing before it leaves, naming the code they would have drawn. A cargo-type/movement pair the trade-scenario table does not allow (115) was already caught.

  • Filing

    CFS bonds follow the port the box landed at; the CFS is the transhipper at Chennai and Kolkata

    A Chennai CFS files one bond for cargo landed at Chennai and another for cargo landed at Kattupalli or Ennore and moved to it. The transhipper picker now looks the bond up for the port you report at and offers the CFS your cargo is going to first, saying so when it holds no bond for that landing port. At Chennai and Kolkata, where the CFS operator itself is named as the transhipper for local cargo too, the route now fills the CFS’s PAN and bond, and more CFS and ICD operators were added. Bonds change without notice, so everything fills for confirmation, never silently.

  • Filing

    The shipping line’s PAN filled in for fourteen lines

    For fourteen lines — Maersk, MSC, ONE, OOCL, Evergreen, COSCO, HMM, Gold Star, Emirates, Wan Hai, Interasia, PIL, Hapag-Lloyd and Unifeeder — the Consolidator PAN now fills on every route, marked confirmed. RCL’s two PANs are offered by port, and Wan Hai’s PAN was corrected.

  • Checks

    Apostrophes, a non-breaking space and weights to two decimals

    An apostrophe in a goods description (MEN’S) is allowed, a correctly encoded non-breaking space is allowed and no longer read as an encoding fault, a line break pasted into goods text becomes a space instead of gluing two words, and a weight with more than two decimals gets an amber note saying what customs’ record will show. A master whose weight is whole kilograms over house bills with decimals no longer blocks on the rounding gap — it warns. A consignor country that is a one-letter slip from the port of acceptance’s (KP for KR, NE for NG) is pointed out.

  • Filing

    Sign & Submit, with the DSC token in your machine

    Signing no longer means a trip to the ICEGATE portal. The scmtr DSC Signer — a small installer, signed by TAGQA Pty Ltd, that runs in your notification area and starts with Windows — asks your token for the signature and the filing goes straight to customs. The app tells you when the signer is missing or too old and offers the download; the portal route stays for anyone who cannot install software. Several certificates on one machine are named and chosen from, and the one about to sign is shown before the PIN prompt.

  • Filing

    File a vessel manifest from the editor

    A shipping line or steamer agent can now sign and file a SACHM23 arrival or departure manifest from here — with your own signing tool, or with the scmtr DSC Signer — and the same manifest cannot reach customs twice. The file is checked again before it leaves; errors refuse it, warnings do not. Customs’ answer to a manifest still reaches your registered ICEGATE email: the platform says the file was taken, never that it was accepted.

  • Platform

    Sign in with Microsoft

    The Microsoft 365 work account your office already uses signs you in, beside Google and the emailed link. One condition, Microsoft’s rather than ours: it has to vouch that the address belongs to your organisation’s domain, and if it cannot the sign-in says so and points at the other two routes to the same organisation.

  • Checks

    Rejections 316, 365 and 366 explained, and a refused amendment told the truth

    Error 316 now says where the CSN number and date come from — the positive acknowledgement of the filing being amended, and the date is the half that is usually wrong. Errors 365 and 366 name the port of receipt they are really about and the field in Location & customs to change. And a refused amendment or deletion is no longer told to refile the cargo fresh, which collides with the original; it is told to correct and re-send the amendment.

  • Checks

    A warning before a control number is reused

    Check an ICEGATE file now says when a file’s job number and date look already used by a transmission from your organisation, or when a bill of lading is dated after the job date — the two things ICEGATE refuses by email as “Header validation failed … The Control Number has already been processed”, before any field is checked.

  • After filing

    The same file will not go to ICEGATE twice

    SCMTR.io now recognises a filing it has already sent — even one regenerated with a new control number. If a transmission has already gone and customs has not answered, sending it again is refused with the earlier one named and one click to open it; if customs has already accepted it, you are pointed at an amendment instead. A rejected filing is never in the way, a 700 included. And if you know it has to go again, you can say why, and the reason is kept with the filing.

  • After filing

    When we cannot confirm a filing arrived

    If an upload leaves and no answer comes back — a timeout, a dropped connection — the filing now says exactly that instead of reading as a failure and inviting a second copy. It is locked and marked as sent, because that is the safer assumption, but no tracking number is claimed. SCMTR.io then watches customs’ public record for you, and clears the doubt itself when your filing appears there; dropping the emailed acknowledgement on it settles it too. If nothing ever arrived, an organisation admin can return it to draft.

  • Platform

    Filings are paced, and held when ICEGATE is struggling

    If ICEGATE is struggling to take uploads, filings are held for a few minutes and you are told so. The message says the important part: nothing was sent, and your signed file is unchanged.

  • Filing

    Seal type beside the seal number

    On the master’s container table the seal type is now a column next to the seal number, filled as a bottle seal once a seal number is typed. The other details of a box are the same on nearly every container, so the More row can stay shut.

  • Filing

    Next port of unlading, set once for every house bill

    The route for all house bills on the master step now carries the next port of unlading. It fills itself from the destination — the ICD for inland cargo, the port for a CFS there — and every house bill going that way takes it; a bill sent somewhere else works out its own. In the full form a new house bill takes it from its destination too, instead of the reporting port.

  • Filing

    Plain text, whatever you paste

    ICEGATE refuses a file that is not UTF-8. Every field now converts as you type or paste — curly quotes to straight, long dashes to hyphens, É to E, ₹ to RS, € to EUR, µ to U. A value brought in another way is checked instead, and Check an ICEGATE file lists any character that is not plain text by line and column, with the field it sits in — the line is the one ICEGATE’s refusal email names.

  • Vessels

    Told when the expected arrival moves

    If customs moves the expected arrival day of the call your filing names, you are emailed once with both days, the row says Arrival moved, and the filing’s page shows the day it moved from. Nothing needs amending — the CSN carries no arrival date. The public Track page now shows the expected arrival too.

  • Checks

    The 700 checklist stops calling every refusal a duplicate

    On a filing sent from here, the checklist for a 700 counted the refused transmission’s own control number as a re-use, so every reasonless refusal read as a duplicate. It now leaves that transmission out. The checklist also no longer ranks the causes of a 700, because nobody outside customs knows which is commonest: it runs cheapest check first.

  • Filing

    The master’s PAN follows the line and the route

    A shipping line can file under an agent on some routes, and which one can change with the destination. Pick the line printed on the bill — it is kept with your draft and never sent to customs — and the Consolidator PAN fills for your port and destination: Wan Hai from Chennai to Chennai fills Wan Hai’s own PAN. Where the agent’s PAN is not on file — Wan Hai under its agent from Chennai to Bangalore — the field names the agent and asks you for it. It says whose PAN it is and follows if the destination changes; a PAN you typed yourself is never replaced.

  • Checks

    The VCN on an uploaded CSN is checked

    A CSN made in other software never met the voyage check we run before signing. Open one on Check an ICEGATE file and its VCN is now compared with the calls customs lists for the ship — amber where it looks like another call, or like last voyage’s on a ship that calls weekly. It is advice only: ICEGATE decides.

  • Checks

    One drop target, named Check an ICEGATE file

    The CSNs page had two cards that both took an acknowledgement. There is now one, named for ICEGATE rather than for us: an acknowledgement for one of your filings is recorded on the spot, and anything else — including an acknowledgement for a filing made elsewhere, which used to be refused — opens in the checker already loaded.

  • Checks

    Too long is caught however the value arrived

    A field’s length limit used to stop only typing, so an address picked from the address book or brought in with a file could be longer than ICEGATE allows. A value over its field’s limit is now a red issue however it got there, naming the limit and how many characters to remove.

  • Filing

    Type the route once for every house bill

    On a consolidation the master step now has a route for all house bills — port of loading, final destination, transhipper and item type. Every house bill starts with it; send one bill somewhere else and only that bill changes, and change the route later and every bill you have not touched follows. Nothing extra is sent to customs.

  • Checks

    A changed destination stays on the bill you changed

    In the guided steps each house bill used to copy its route from the one before it, so sending one bill to a different ICD quietly moved every untouched bill after it too. Each bill now takes the master’s route, and the one you change is the only one that changes.

  • Filing

    Pick the shipping line by name

    The master’s Consolidator PAN — the Indian PAN the line files under, printed nowhere on the bill — now searches by the line’s name. The PANs your own filings have used come first, then a reference list, with the agency at your port first where a line uses a different one there.

  • Filing

    Find an inland depot or SEZ by the name you actually use

    Our port list carried the full customs address for every ICD and SEZ, so searching for “Khurja ICD” or “Dahej SEZ” found nothing. You can now search by the short name your paperwork uses, and by the operator’s name even where it has since changed hands. The official name is still what gets filed.

  • Filing

    Paste a weight straight off the bill of lading

    Pasting “12,500 KGS” into a weight or volume box used to be refused outright, so you cleaned it up by hand. It now becomes 12500, and the unit fills itself in beside it if you have not already chosen one.

  • Checks

    The duplicate-bill check works in the full form

    Typing a master B/L checks our records and ICEGATE for whether that bill has already been filed — the check behind rejection codes 122 and 123, caught before you key a whole declaration. It had been in the guided steps only; it now runs in the full form too, on every master consignment.

  • Filing

    The house B/L date says how it compares with the master

    A line beside the house bill’s date tells you whether it matches the master’s, and names the master’s date when it does not. It is a statement, not a warning — a house bill issued on a different day is ordinary.

  • Filing

    Unticking “same as consignee” now asks what to do

    It used to leave the copied consignee details sitting in the notify-party fields, which was easy not to notice. It now asks whether to keep them for editing or clear them; ignoring the question keeps them, so nothing is ever erased for you.

  • Filing

    The ship search sits at the top of the master step

    Finding the vessel is one of the first things you do, so the search moved up beside the step heading. And if you find the ship before typing a bill number, that is no longer lost when the tab closes — the filing is kept in your browser until it is saved properly.

  • Checks

    Cargo type, movement and consolidation are checked as one combination

    Customs does not validate these three fields separately — it checks the combination, which is where rejection codes 115, 118 and 126 come from. The form now checks the same way, and the guide sets out which combinations customs accepts.

  • Sharing

    Uploaded files are kept for seven days

    A file you drop in to be inspected is now retained for a week rather than discarded immediately, so you can come back to it. What is kept, for how long, and who can see it is set out on the privacy page.

  • Vessels

    Your VCN is re-checked before you file

    A vessel call number chosen early can be replaced by the port before you file. It is now checked against customs’ own list of calls whenever you open the filing, and again as you sign or upload. If the call you picked is gone, the page says so and offers the current one — nothing is changed for you.

  • Vessels

    You are told when a VCN changes, without opening anything

    We keep an eye on customs’ list of calls for the ships on your open filings. If the call one of them names disappears, we email whoever created the filing and mark the row. A draft saved with a ship but no VCN is emailed the first time a call appears for it.

  • Vessels

    Ships without an IMO number can be filed

    Barges, country craft and other hulls with no IMO have their own way of being identified in the message. The ship step now handles them, and switches the vessel type with the name so the filing stays valid.

  • Checks

    Master and house container figures are cross-checked, box by box

    Weight and packages are now yours to type at both levels, and the review page shows the arithmetic per container with a tick or a cross. A master that disagrees with the house bills under it is caught before customs does — the mismatch that used to arrive as a penalty.

  • Filing

    Correcting the consolidator PAN carries the container agent code with it

    Fixing a mistyped consolidator PAN on the master used to leave the old agent code on every container, to be corrected by hand. It now follows the PAN, in the guided steps and the full form, including on a draft you reopen later.

  • After filing

    Drop an acknowledgement onto any filing

    A customs acknowledgement can be uploaded from a filing’s own page or straight from the list. We check it belongs to the filing you dropped it on and refuse it if it does not, so an outcome cannot be recorded against the wrong job.

  • After filing

    “Fix and file again” after a rejection

    A refused filing can be reopened on the same job number with a fresh control number, with the errors customs returned listed against the fields they belong to.

  • Filing

    The guided steps are master-first

    Three steps: the master bill with one row per container, then each house bill — which ticks the containers it uses and types only its share — then review. FCL and LCL are worked out from the sharing rather than asked.

  • Sharing

    Read the guide, FAQ and roadmap without leaving the app

    The reference pages open inside the app when you are signed in, instead of throwing you out to the public site and back.

  • Filing

    Text is put into capitals, and unfileable characters dropped

    Filings go to customs in capitals, so party names, addresses and goods descriptions convert what you type and what you paste. Characters that cannot be filed are dropped as you go rather than turning up as a rejection — the B/L numbers are stricter still, because ICEGATE rejects specials there by name.

  • Filing

    Open and correct a vessel manifest

    A SACHM23 manifest of any size opens as a table you can search and correct, checked against the codes ICEGATE uses. Saving writes the file back exactly as it was apart from what you changed.

  • Checks

    See what customs already holds against your bill

    As you type a master B/L we check ICEGATE’s public record for what it already has: whether another party has filed against it, whether one of your own filings is on record, and whether the carrier’s manifest has arrived. It stays quiet when there is nothing to say.

  • Platform

    Filing works without an ICEGATE Open API key

    You do not need an Open API key of your own to file. Acknowledgements are recorded by dropping the file in or by hand, and the filing page says so plainly.

Something you need that is not here? Tell us on the roadmap — everything on it came from someone who files under SCMTR.