From the Data Flows Settings section, click Add Bank.
A data flow depends upon the bank and describes the flow, the file standard, payment types (checks, wires, etc), and then the account number. The number of data flows depends on the Lockbox accounts. After adding a bank, you just need to provide the FTP path of the file location and the file name to get started.
The following section is displayed. Add the bank in two steps (establish bank connection and install a bundle in NetSuite). In step 1, press Click to Configure.
Step 1: Bank Connection: Provide bank server credentials. Press Click to Configure.
Name: Name your connection so that you can easily reference it from other parts of the application. For example: 'NetSuite - firstname.lastname@example.org'
Connection type: This field lists all the application and technology adaptors supported by integrator.io. Application adaptors like NetSuite or Salesforce are the easiest to use, especially for less technical users. Technology adaptors like the REST API adaptor require a more technical understanding of the applications being integrated, but once you learn how to use a specific technology adaptor, you will be able to integrate a multitude of different applications without having to wait for integrator.io to expose specific application adaptors. If you do not find a matching application or technology adaptor, the only other connectivity option is to use the integrator.io extension framework to develop a custom Wrapper. Please contact support if you need more info on Wrappers, or are interested in learning more about the integrator.io developer extension framework.
Host: The URI of the S/FTP server host. Typically this value will look something like 'ftp.mycompany.com', or sometimes just a raw IP address '220.127.116.11'. It is also very common for S/FTP servers to be behind a firewall, and to support accessing resources behind a firewall, you will need to make sure all of the S/FTP specific integrator.io IP addresses (listed right below the HOST field) have been white-listed on your S/FTP server infrastructure.
User name: The username that you would like to use to connect with the S/FTP server.
Password: The password associated with the username that you are using to connect with the S/FTP server. Please note that there are multiple layers of protection in place (including AES 256 encryption) to keep your password safe.
Advanced Settings: Set this field to override the default port number. In most cases, this field can be left empty. Only on rare occasions are S/FTP servers configured to run on alternate ports.
Use passive mode: This field tells integrator.io to use Passive Mode instead of Active Mode when connecting to the FTP server. This field is enabled by default; uncheck this checkbox if you want to use Active Mode instead. If Active Mode is used, your FTP server must accept traffic from the inbound port range 15000-15100. Note that this field is only relevant for FTP connections, and will be ignored for SFTP. If you want to know the difference between Active and Passive Modes, there is a good explanation here: http://www.jscape.com/blog/bid/80512/Active-v-s-Passive-FTP-Simplified
User Directory Is Root: This optional field is used to tell integrator.io if this connection’s Relative Path is relative to your S/FTP login's user directory or to the server root folder. Suppose your files are located on the server at "/usr/local/iio/files/download"--if your S/FTP server account places you in your user directory after login ("/usr/local/iio") then you need to check this checkbox and use "/files/download" as your Relative Path, but if you go straight to the server’s root directory ("/") after login then leave this checkbox unchecked and use "/usr/local/iio/files/download" as your Relative Path.
Entry Parser: This optional field can be used to explicity identify the system specific S/FTP implementation. In most cases no value should be selected. You only need to set this field if your S/FTP server is an uncommon type (not Windows or Linux), or it does not support the 'SYST' command. Possible values are: ['UNIX', 'UNIX-TRIM', 'VMS', 'WINDOWS', 'OS/2', 'OS/400', 'AS/400', 'MVS', 'UNKNOWN-TYPE', 'NETWARE', 'MACOS-PETER']
Step 2: CashApp bundle: Install Cash Application Manager bundle in NetSuite. Press Click to Install.
In the next step, select ‘Click to Install’ the Cash Application Manager bundle. A new NetSuite window is displayed with the Celigo Cash Application Manager bundle. Click ‘Install’. If the Celigo Cash Application Manager bundle is already installed in your NetSuite account, then this step is skipped. Before installation, you can view the components specific to Cash Application Manager.
After completing the installation, you can see the list of banks and associated data flows in the settings.