Setup & Connection
Information related to the setup and import of transactional data into the InsCipher Connect® Portal.
How this works - and a few other notes
The Integration Tool will automatically extract relevant surplus lines policy data out of your local AIM® database and import that data into Connect® on a daily occurrence. Typically, this occurs around 2 AM Mountain Standard Time (MST). Policies included in the daily import will be those that were marked as having the corresponding invoice:
- Exported
- Collected by the Agency
- Taxed
Individual installment transactions are excluded from the import. From a developer's perspective, these are the invoice transactions that have the StatusID = “E”, CollectedBy = “A”, and the Taxed = "Y" on the invoice header within AIM. In addition, we are bringing in transactions with the MemoInvoiceFlag = "Y" and including all Installment Invoices that have an InvTypeID = "Y". The reason why we are not including all invoices with other statuses is that there may be changes to the invoice prior to it being exported to accounting, and we believe that by only pulling policies in an exported invoice status, Connect® can provide a cleaner and more up-to-date list of transactions.
IMPORTANT:
Be aware that the InsCipher Integration Tool is always working in the background, regardless if you reboot your server. All batches imported will be included in the “Filings Import Log” page in InsCipher Connect® for your review.
TIP:
It is best practice with plans that are billed in installments to charge the entire SL taxes and fees up front so that these can be reported and paid to the state. Should a policy eventually cancel, you would want to create an offsetting invoice so that you can report the unrealized premium to the state and return the returned SL Taxes and Fees back to the insured.
NOTE:
Duplicate transactions with the same Invoice ID number will not be imported. These will show up in the Filings Import log, but as “Not Imported” transactions.
Step 1: Setting up a new integration in InsCipher
To begin using the integration, you will first need to log into your Connect® account. Click on "Setup" in the left navigation bar > “Integrations” > then click on the “ADD NEW” button to start the Integration Wizard. This wizard guides you through a four-step process of installation.
Proceed to Agency Management System tab
- Select “Vertafore AIM” > Click "Continue"
- Select "Create Payment Batch" if you want to utilize the feature described in this article.
- Under the "Choose Physical State Field" setting, indicate which value you want to use in AIM for the Physical / Tax State in InsCipher Connect®.
- Use "Quote State" to pull from the Quote.State field
- Use "Quote Tax State" to pull from the Quote.TaxState field.
Step 2: Downloading and Initializing the Integration tool
Proceed to Integration Setup & Connection tab
In this step, you will be downloading and installing the InsCipher Integration Tool. You will also receive your InsCipher Integration Token in this step, which you then will use during the installation process.
IMPORTANT:
You will have 10 minutes to use this token before you will need to regenerate!
During installation, you will be asked to enter your SQL server login credentials and your Integration Token, after which you will click “Connect” to link up with InsCipher. It can take a few minutes to process. If you are having issues connecting, ensure that your SQL login credentials are correct and that you can read the “InvoiceHeader” and "InvoiceDetails" tables in the database on that server using the same credentials. If you still are having trouble, click on the Send diagnostics button in the top right corner of the IC Tool.
NOTE:
Once the connection is complete, you will get an "Installation successful” message. The application will continue to run in the background and will automatically startup with each reboot. To cancel, disconnect, or adjust settings to your connection, click on the application icon in Windows' tray menu.
Updated about 2 months ago
In Step 3, we'll dive in to how data is pulled from AIM and how to ensure it maps successfully into InsCipher.