Connecting to FTP

Connecting to FTP

Target audience: This feature is for clients accessing our FTP space to upload ratebooks or to recieve new user sign ups and enquiries through CSV.

You will need…

  • It is assumed you have some familiarity with FTP or similar file transfer systems.

  • An FTP program (client) capable of FTP over TLS, such as WinSCP, and FTP credentials for the ratebook upload area (we will supply separately).

  • FTP connections behind NAT will use passive mode which will require a corporate firewall to allow connections to the server on an arbitrary outgoing port.

  • Ratebooks prepared to agreed format, and it is expected that supplied ratebooks are within the following parameters:

  • Term from 2, 3, and 4 years

  • Access to the configured admin email inbox to receive reports and notifications from the import system.

FTP configuration

Host:If not supplied separately, use upload.gensen.software
Port:(leave blank or default in most clients)
Username:(as supplied)
Password:(as supplied)
Protocol:

Depending on FTP client terminology, you may need to select one of:

  • FTPS
  • FTP + SSL
  • Require explicit FTP over TLS

On request, we can also set up SFTP (FTP over SSH) using public key cryptography, which will be more secure and may be easier to automate.

Note: If you get errors when connecting, the issue may be with your corporate firewall, in which case you need to allow outgoing TCP connections to the host (as defined in the table above) on ports between 49152 and 65534, and make sure that passive is selected as a transfer mode in your FTP client.

⚠️

Caution:

  • A successful import will unpublish all previous ratebooks, except:

    • when importing in test mode (all changes will be discarded)
    • multi-ratebook sites
    • or in case of fatal error (all changes will be discarded).
  • Row-based errors within the import (invalid vehicle or rate information) will prevent that row from being imported.

  • Row-based warnings or notices within the import won’t prevent the row from being imported, but may suggest unexpected or missing data that should be checked.

  • After performing a production import there will be a brief downtime (around 5–10s) while ratebooks are reloaded.