ISF Integration
- Silas Canning (Unlicensed)
Analytics
What is an ISF?
An Importer Security Filing (ISF), also known as “10+2,” is a filing required by the CBP (U.S. Customs and Border protection) that documents importing information and details as shipments pass from point to point.
Importers who do not file the ISF properly prior to the shipment of their goods will be penalized (US$5,000 fine). The ISF must be submitted at least 24 hours prior to an ocean’s shipment’s departure to the United States
ISF Integration with Moveware
Typically, an ISF is filed through an authorized broker and their provided platforms.
Alternatively, Moveware offers an electronic integration with a broker called Vilden. This makes filing an ISF easy as it can now be completed through Moveware, with Vilden as a broker.
How to File an ISF in Moveware
In Moveware we will setup a special diary action to remind staff to start the process.
The automated process will start as soon as a Waybill is generated on specific type of jobs. (Normally imports that are not military or government ones. But this can be customized via special development based on cost centers). As soon as the waybill has a departure date and an OBL or House bill number this will start automatically.
MoveWare generates a first filing to Vilden. And generates a diary action called “ISF sent”.
Vilden receives it and sends it to CBP
CBP responds and Vilden generates a response file to us. This also generates a diary action called ISF received.
The filing process started, and the previous steps will repeat every time a modification is done in the Waybill screen.
On every response from CBP the Waybill screen will be updated on ISF Status and ISF comments; both fields will be activated upon interface activation.
From Vilden we will receive the following on each loop and the info will be added to the waybill screen
Status. (This is a code)
Status Response. (This is the explanation of the status and normally tells you if something is missing or is ready)
CBP Number
The loop will continue until Vilden and CBP sends Moveware a status S1. S1 is the status we need to reach. That means that the process is complete and approved.
The automated process can also be stopped manually by adding the following diary action and completing it: “ISF Complete” before it auto stops.
If there is any issue users can go directly to the Vilden web filing app and correct any issue.
How to Set Up ISF
Communicate to your Moveware representative and inform the that you have a Vilden account and are interested in setting this up. We will assist by evaluating your specific needs and modify the base interface to cater your individual database.
Make sure there is a Vilden account.
Communicate Vilden that you will be using an interface for ISF filing.
Vilden will assist with testing prior go live.
On the Server you must have two FTP folders, one for incoming from Vilden and one for outgoing to Vilden.
Both Moveware and Vilden will require access, full write and read permission.
The current interface is done using simple TXT files with special structure, where lines and columns are in predetermined positions. For each implementation a specific adjustment will be required.
In Moveware there are two new codes that must be added:
Export to Vilden’s FTP
Type = Export File
Code = ISF
In the Comments you will need to add the local folder and Vilden’s FTP url. For Instance:
ExportFolder,\\localservername\moveware\MWDOCS\ISF Export
FTPURL,ftp://ftp.vilden.net/xxx/xxxxx/xxxxx/ (this address will be provided by Vilden)
FTPUsername,vildensusername
FTPPassword,vildenspassword
FTPDomain,FTPSSLfabe
Import from Vilden (In this one we will reference the import folder and some subfolders required: Imported and Logs.
Type = Export File
Code = ISFIMPORT
In the Comments you will need to add the local folder and Vilden’s FTP url. For Instance:
ImportFolder,\\localservername\moveware\MWDOCS\ISF Import
ImportedFolder, \\localservername\moveware\MWDOCS\ISF Import\Imported
ImportLogs, \\localservername\moveware\MWDOCS\ISF Import\Logs
On the original Development we use Moveconnect to generate and check files every 5 minutes. This can be modified as needed.