Integrations · ERP and job software
SCMTR.io beside your ERP or job software: jobs in as draft CSNs, CSN numbers back
Updated
SCMTR.io works beside the job software you already run. A job from any job system or ERP becomes a draft CSN on SCMTR.io — sent as a spreadsheet or through the API. A person checks the draft, signs it with their own DSC and sends it to ICEGATE, and the CSN number, the CINs and customs’ reply go back to the job.
Two ways in, for whatever your job system can do
It needs no API of its own: a spreadsheet export is enough.
- 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
Your export’s own columns, named once
An import profile says which of your columns is which, so nobody renames a header again.
- A named profile for each job system or branch that sends sheets, and one default
- The column that holds your own job number is named in it — it is how each CSN number finds its job
- A sheet read under a profile needs no matching again
- Profiles are kept under Settings → Connect and chosen on the Batches screen, or named when the sheet is sent through the API
A person checks, signs and sends
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.
- Opened on SCMTR.io, each draft shows what is still left to fill; Check all on the batch runs the checks over every draft at once
- The same checks as any CSN: red must be fixed before it can be sent, amber is worth a look
- The drafts of one sheet or one request sit together as a batch on the Batches board
- With “Only signers send” on, others prepare and a signer checks and sends with their own DSC
What goes back to the job
Under your own job number, by whichever way your job system can take it.
- 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
See it on a demonstration job system
An invented job system with invented jobs, labelled a demonstration everywhere.
- In a demonstration, a job is sent to SCMTR.io from it and the draft that appears is opened
- The CSN number is seen coming back on the job
- Ask support@scmtr.io to show it to you before you change anything of your own
What stays in your job system
- Your jobs, customers, rates and invoices: SCMTR.io keeps none of them
- Your job numbers: SCMTR.io carries yours and never renumbers a job
- Which jobs to send, and when: nothing is pulled from your system
Questions forwarders ask about their job software
Read next
Which ERPs and job systems does SCMTR.io work with?
Any that can export a spreadsheet or call an API. SCMTR.io names no job system as connected, because nothing is built for one brand: the sheet your software already exports, read under an import profile that names its columns, is enough.
Does my job system need an API?
No. A spreadsheet export is enough: drop it on Batches, where it is read under the import profile you choose. The API is there for software that can call one.
Does SCMTR.io send the CSN to customs by itself once the 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.
What happens if the same job is sent twice?
Nothing new is made. A job sent again under the same job number is answered with the filing it already made, and you are told whether what you sent now differs. The draft is never overwritten — someone may already have corrected or sent it.
How does the CSN number get back to my job system?
On a write-back sheet downloaded from Settings → Connect, as an event your system is sent or reads, or through the API by your job number — with the filing’s state, the CSN number and date, and the MCIN or PCIN.
Does it work for export CSNs?
Not yet from a job system: a job sent in becomes an import CSN draft. An export CSN is made on SCMTR.io from its shipping bill, whose details are fetched from ICEGATE.
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.
What does it cost?
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.
Send your next job as a draft CSN
Filing is free — every filing feature, no caps, no card. Connect is free on every plan, like the API.