Skip to content

Integrations · Connect

SCMTR.io works beside the job, accounts and yard software you already run

Updated

SCMTR.io works beside the job, accounts and yard software you already run. Jobs come in from any job system or ERP — as a spreadsheet or through the API — and become draft CSNs that a person checks, signs and sends. CSN numbers, CINs and customs’ replies go back to the job. Line desk invoices and payments are posted to the books you already keep, and a yard or transport system reads the events it acts on.

In: a job from your job system becomes a draft CSN

From any job system or ERP, as a spreadsheet or through the API. Every job arrives as a draft: a person checks it, signs it with their own DSC and sends it to ICEGATE. Nothing is sent to customs without a person.

  • A spreadsheet as your job system exports it, dropped on Batches: name its columns once as an import profile, and each master bill in the sheet becomes a draft CSN
  • Through the API: your system sends each job under its own job number — or sends the same spreadsheet — and is answered job by job: whether a draft was made, was already there or was refused and why, with the draft’s link and the notes made on any value that was changed or could not be read
  • The same job sent again never overwrites its draft: the answer names the filing it already made and says whether what you sent now differs
  • Import CSNs today; an export CSN is made on SCMTR.io from its shipping bill

SCMTR.io with your ERP or job software

Back: the CSN number, the CINs and customs’ reply

What your job system needs to know about each job it sent, under your own job number.

  • Each filing’s state, its CSN number and date, and the MCIN or PCIN customs issued — read by your system through the API, under your own job number
  • Events as they happen — a draft made, a CSN sent, customs’ reply recorded, a bill reaching the line’s manifest — pushed to your system as signed webhooks, or read from an event feed by a system that cannot receive them
  • A write-back sheet, downloaded from Settings → Connect — every filing, or those changed since a day you give: one row a filing, with your job number, its state, the CSN number and date and the CIN, for your job system to take in

What the API takes and gives

Books: Line desk money in Tally or Zoho Books

For a shipping line and for its customers, where the line works its bills on the Line desk.

  • 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
  • Tally: two files made for Tally’s import — your parties first, then the vouchers — downloaded from Settings → Connect for the days you choose, written with your own ledger names
  • Zoho Books: an Org Admin connects your own Zoho Books organisation by signing in to Zoho and choosing its accounts, and disconnects it whenever you choose
  • SCMTR.io never touches a record in your books that it did not post: it reads your account and tax names for you to choose from, looks up contacts, invoices or bills and payments so that none is made twice, makes them, and updates or voids a document it posted when that document changes or is cancelled on the Line desk

Line desk money to Tally or Zoho Books

Yards and transport: the events your system acts on

A CFS’s, ICD’s, empty yard’s or transporter’s own system, told as it happens.

  • The events a yard or transport system acts on: customs’ reply to a CSN recorded, a bill reaching the shipping line’s manifest, entry inward granted on a bill you watch, a delivery order released, an empty release order or a Form 13 issued, a container’s free days ending
  • Each event names the filing, bill or paper that changed and what happened; your system reads the rest through the API with its own key
  • Pushed to your system as signed webhooks, or read from an event feed that keeps each event for 30 days

Events for yard and transport systems

Is SCMTR.io an ERP?

  • No. SCMTR.io is not an ERP: it keeps no job register, no accounts ledger and no yard or transport system of its own. You keep the software you run, and SCMTR.io does the SCMTR filing beside it — taking jobs from it as drafts and giving CSN numbers, CINs and customs’ replies back.
  • Your jobs, your customers and your rates stay in your job system
  • Your ledger stays in your accounts package: SCMTR.io posts to it and keeps none of its own
  • Your gate, your yard plan and your vehicles stay in your yard or transport system
  • Signing and sending stay with a person, on SCMTR.io, with their own DSC

Questions about working beside your software

Read next

Is SCMTR.io an ERP?

No. SCMTR.io is not an ERP: it keeps no job register, no accounts ledger and no yard or transport system of its own. You keep the software you run, and SCMTR.io does the SCMTR filing beside it — taking jobs from it as drafts and giving CSN numbers, CINs and customs’ replies back.

Does SCMTR.io work with my ERP or job software?

Yes, with any job system that can export a spreadsheet or call an API. Nothing is built for one brand of job software, so it does not matter which you run: each job becomes a draft CSN on SCMTR.io, and the CSN number, the CINs and customs’ reply go back to the job.

Does SCMTR.io send the filing to customs by itself once a job arrives?

No. Every job arrives as a draft: a person checks it, signs it with their own DSC and sends it to ICEGATE. Nothing is sent to customs without a person.

Does SCMTR.io work with Tally and Zoho Books?

Yes, for the Line desk’s money. 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. SCMTR.io keeps no ledger of its own.

Can our yard or transport system hear from SCMTR.io?

Yes. It is told as it happens — customs’ reply to a CSN recorded, a bill reaching the shipping line’s manifest, entry inward granted on a bill you watch, a delivery order released, an empty release order or a Form 13 issued, a container’s free days ending — pushed as signed webhooks or read from an event feed. Each event names the filing, bill or paper that changed, and your system reads the rest through the API with its own key.

Is Connect free?

Nothing. Connect is free on every plan, like the API. The API keys, the webhooks, the event feed, the import profiles and the write-back sheet are all part of it.

Where do we set it up?

Under Settings → Connect: your connections and what came through each, in words, the import profiles, the write-back sheet, the Zoho Books connection, and the two Tally files and the plain sheet. An Org Admin connects the books. API keys and webhook addresses are made under Settings → API.

Keep the software you run. File beside it.

Filing is free — every filing feature, no caps, no card. Connect is free on every plan, like the API.