InsCipher Help Center

Batch Import, APIs, and Integrations

CSV Batch Import

CSV Batch Import: Filing Services Clients ONLY

This article is designed to help you learn how to use the Transaction CSV batch import tool in InsCipher.

Instructions on How to Perform Batch Import
Troubleshooting Import Errors
Description of Field Names on CSV File
Historical Data Migration
Field Mapping Documentation
Change History

How Do I Perform a Batch Import?

Taking the sample file and filling out the necessary fields, follow these steps to import your CSV batch into the portal.

NOTE: for new clients that are doing data migration, please use this data migration sample file which has the historical data migration fields on it. Your implementation specialist will import the historical data on your behalf.
Click "Save As," choose a name for your file, and remember where you saved it – you'll need that in a minute. Also, be sure to save it as a plain CSV file. The batch can be up to 50 MB. Your batch is now ready to be uploaded into the InsCipher portal!
Now, go to the InsCipher portal and click "Upload Filings":
In the dropdown that opens up, select "Batch Import":
This should bring you to a new page shown below. You will need to select the correct option based on what you are trying to import, filings, documents, or both.
To import the files you can either drag and drop them into the white box or click inside the box and it will bring up a window like the one shown below.
Depending on your selection, please reference the correct instructions below:
1. For Only filings, the sample file above should be used.
2. For Only Documents, you will need to submit a zip file that will contain the documents and a csv for mapping. The screenshot below is an example of the zip file to upload the document "test1.pdf"
  
  Inside that zip file there is a csv labeled "documents.csv", sample here, that has columns for the filing id, the code, and the file name. In this example the csv is linking the pdf "test1" to the filing id 192025.
3. For Both at once you will need to select a csv and a zip file. The "documents.csv", sample here, in the zip file will have a different first column that should be "invoice_number" and should relate to invoice numbers on the transactions document that is uploaded.
Once you have uploaded your files you can press the "Validate" button and if there are no errors you will see the following screen where you can press "Submit":

Congrats! You've uploaded a batch. If your upload was successful, you will see a new screen shown below. You can select "Import Once More" if you need to go through the process for another import or "Filings Import Log" which will take you to the filings import log where you can see your batch's status, imported filings, not imported filings, and error log if there were any filings that weren't able to be imported.

Happy filing!

Note: We recommend choosing a small file to import at first and so you become familiar with the process before you batch import hundreds of policies at once.

How Do I Correct a Batch if There are Errors?

If there are many errors that came through on a batch, you can delete the entire batch by clicking the "Delete" button on the batch:
You can also click under the "Not Imported Filings" or the "Error Log" to download a list of errors in the batch.
When pulling up the error code list, you will see the reason for the error followed by the policy number that was trying to be uploaded.
You will then need to go into the batch and correct the error.
Follow the "How Do I Perform a Batch Import?" instructions above to make the corrections.

Field Descriptions

To download the latest version of the CSV batch import, click here.

Below, you will find a list of the different fields used, the description, and whether or not it is required for the CSV batch import to work.

Note: Some fields are required in order for the transaction to import without error. Others are listed as "required" on the CSV spreadsheet since they are needed to load accurate policy/endorsement information but won't actually cause an error if they are missing at the time of import. There are additional codes that you can find at the bottom of this document such as insurer NAIC codes, description of risk, and lines of business.

Note: Please follow the formatting instructions listed on the CSV import template. For example, dollar symbols and commas must be removed from all currency fields prior to importing.

Field Title (header must be exact on .csv)

Description

Field type

Optional

Required

policy_number

Policy number. Non-unique field.

varchar (50)

✓

expiring_policy_number

Expiring Policy Number

Only Required for Renewal type policies.

varchar (50)

Depends

transaction_type

Updated transaction types can be found here.

varchar (50)

✓

policy_type

Options include:

"standard", "master", "cert".

Unless you do RPG policies, leave this as "standard".

varchar (50)

✓

account_written_as

Use one of these two options:

Brokerage = B

Direct Client = DC

Use "B" if you sell through a retail agent. Use "DC" if the policy is sold directly to the insured. If omitted, the default Agency Admin setting will be used

varchar (50)

✓

policy_effective_date

Policy effective date

date (yyyy-mm-dd)

✓

policy_expiration_date

Policy expiration date

date (yyyy-mm-dd)

✓

transaction_effective_date

Transaction effective date

For endorsements, this is the endorsement date. For New/Renewal policies, this is equal to the policy effective date. If omitted, today's date is used as transaction eff. date

date (yyyy-mm-dd)

✓

invoice_date

This is the date that the policy was invoiced in most states. In GA, this is the Revenue Recognition Date, in HI, this is the Date Issued.

If omitted, the filing effective date will be used.

date (yyyy-mm-dd)

Depends

rpg

Risk Purchasing Group?

Yes = 1
No = 0

tinyint(1)

✓

purchasing_group_name

Required if RPG (rpg field) is set to Yes (or 1).

If not included and RPG = Yes, then the transaction will still import but will show RPG error.

varchar(255 )

Depends

layered_risk

Layered Risk

Yes = 1

No = 0

tinyint(1)

✓

broker_of_record

Broker of Record Change

Yes = 1

No = 0

tinyint(1)

✓

risk_retention_group

Risk Retention Group

Yes = 1

No = 0

tinyint(1)

✓

ecp

Exempt Commercial Purchaser?
Yes = 1

No = 0

If omitted, 0 (zero) value will be imported. Unless you know what this is, set this value to 0.

tinyint(1)

✓

exempt

Is the Insured/Entity considered tax-exempt by the state?

Exempt Yes = 1
Exempt No = 0

Unless you know that the insured/Entity is Tax Exempt, set the value to 0 or leave it blank (the system will default to 0). Currently Required only for the state of Utah.

tinyint(1)

✓

multi_state

Does the insured’s liability reside in multiple states?

Multi state Yes = 1
Multi state No = 0

InsCipher does not calculate Multi-state surplus lines tax breakdowns. With NIMA dissolving in 2016, InsCipher reports 100% of the premium to the home state of the insured and bases the tax percentages off that state. If omitted, the default is No (0). There are only a few states where InsCipher has enabled this field.

tinyint(1)

✓

policy_limit

This is the aggregate policy limit/liability amount associated with the policy.

The requirement depends on State and Agency settings. There are about a dozen states that require this information when filing. For this reason, we recommend that you include the policy limit on every submission. If it isn't required by the state then this amount will be ignored. However, for a specific list, go here.

integer(12)

Depends

property_limit

Property Policy Limit

The requirement depends on State and Agency settings. We recommend that you include the property policy limit on every submission. If it isn't required by the state then this amount will be ignored.

Currently, this field only applies to PA.

integer(12)

Depends

non_admitted_insurer_code_list

This is the NAIC code associated with the insurer. Refer to the Insurance Company import list which can be downloaded here.

For policies with multiple insurance companies, provide the NAIC insurer code list. Multiple values are separated by the pipe symbol “|”.

For Lloyd's policies, use “AA-1122000”. Also, review syndicate_list and syndicate_list_coverage.

This requirement depends on the state requiring an insurance company breakdown. As this varies by state, we recommend importing all transactions with multiple insurance companies, where applicable.

Example: 26883|35351

Must also provide details in non_admitted_insurer_code_coverage
Sample fields with Multi-Companies:

“non_admitted_insurer_code_list": "26883|35351",
"non_admitted_insurer_code_coverage”: ”60|40”

string

✓

non_admitted_insurer_code_coverage

Applicable percentage breakdown. For single insurance companies, list "100" here. For multiple insurance companies, list the breakout. This value would be the percentage breakdown in 100 based values (without the “%” sign). List these in the same order as the non_admitted_insurer_code_list. Multiple values are separated by the pipe symbol “|”.

The requirement depends on if the state requires an insurance company breakdown. As this varies by state, we recommend importing all transactions with multiple insurance companies, where applicable. If a state doesn't allow for multiple to be reported, then our system would select the carrier with the greatest percentage and report the amount with that carrier.

Example: 60|40

string

✓

syndicate_list

Syndicate list breakdown for Lloyd's ONLY policies, for mult-carrier policies that have Lloyd's and non-Lloyd's carriers, please refer to the note below.

Multiple syndicate codes should be separated by the pipe symbol “|”.

The requirement depends on agency settings and if the state requires a syndicate list breakdown when filing. To simplify the import process, we recommend that you import all Lloyd's policies with a syndicate list breakdown (if possible). If the state does not require it, the breakdown will be ignored.

Example:

"non_admitted_insurer_code": "AA-1122000", "syndicate_list": "AA-1120131|AA-1120124", "syndicate_list_coverage": "60|40"

Syndicate lists are required for multiple states. A full list can be found here:

NOTE: Should you have Lloyd's and Non-Lloyd's carriers, then import transactions with multiple insurance company breakouts where the syndicates would be included in this breakout rather than as a separate syndicate field.

string

Depends

syndicate_list_coverage

Syndicate list breakdown percentages listed as a whole number without the percentage sign "%".

Multiple values are separated by pipe the symbol “|”. Keep the percentages in the same order as the list above.

The total amount for the array must equal up to 100.

string

Depends

risk_description

Description of Risk

For New York, Ohio, and Pennsylvania, we require specific import codes to be used when importing.

For all other states, import this as a text value description of the coverage.

See this table for a list of the state-specific codes. To download the table, hover over the top right corner of the table, click on the three dots, and then export to CSV.

varchar(255 )

Depends

transaction_line_of_business_list

This is an InsCipher-specific import code. We recommend using the Generic Import codes, which can be found here: Generic Line of Business / Coverage Code List If you want to use state-specific codes, you can. These can be found here.

For policies with a single LOB, enter the single import code. If there are multiple LOBs, then these would be added and separated by the pipe symbol “|”.

The requirement depends on whether the state requires a line of business breakdown. As this varies by state, we recommend importing all transactions with multiple lines of businesses, where applicable. If the state only allows for a single LOB when reporting, our system would select the coverage that is associated with the greatest premium amount $.

string

✓

transaction_line_of_business_coverage

The premium breakout (rounded to the nearest cent) without the dollar sign in the string.

Single LOB - enter one value.

Broken-out premiums should be separated by a pipe symbol “|” and should be in the same order as the transaction_line_of_buisness_list.

Whether there is a single line of business or multiple, the premium total should always equal the total added in the premium field above.

DON'T ADD "$" signs or the import will fail

string

✓

premium

Policy premium

If omitted 0 (zero) amount will be imported

decimal(12, 2)

✓

agency_fee

Policy / Broker / Agency Fee or other revenue-generating fee charged and retained by the brokerage to cover admin costs.

If omitted 0 (zero) amount will be imported

decimal(12, 2)

✓

inspection_fee

Inspection / Audit / Underwriting Fee or fee retained or required to be charged by the carrier.

If omitted 0 (zero) amount will be imported

decimal(12, 2)

✓

sl_tax

Surplus Lines Tax (name may vary slightly by state).

The requirement depends on the Agency account setting if tax import is optional.

If left null, 0 (zero) amount will be imported.

decimal(12, 2)

✓

stamping_fee

Stamping Fee (name may vary slightly as FSLO fee in Florida).

The requirement depends on the Agency account setting if tax import is optional.

If applicable in the state and the amount is left null, then 0 (zero) amount will be imported.

decimal(12, 2)

✓

sl_service_charge

Currently active only in the states of OR and MS.

If applicable in the state and the amount is left null, then 0 (zero) amount will be imported.

decimal(12, 2)

✓

municipal_fee

Currently active only in KY.

If applicable in the state and the amount is left null, then 0 (zero) amount will be imported.

decimal(12, 2)

✓

fm_tax

Fire Marshal Tax based on Line of Business. Active in IL, OR, MT, and SD and is based on premium amount.

The requirement depends on the Agency account setting if tax import is optional.

If applicable in the state and the amount is left null, then 0 (zero) amount will be imported.

decimal(12, 2)

✓

empa_tax

EMPA tax is active in the state of FL and is based on Line of Business. This value is also used (field is renamed on the UI) as the CT Healthy Home Assessment for property type coverages in CT.

If applicable in the state and the amount is left null, then 0 (zero) amount will be imported.

decimal(12, 2)

✓

total

We recommend leaving this as null

total amount = premium + all taxes + all policy fees.

If omitted, the system will sum up and import the total automatically.

decimal(12, 2)

✓

commission_received

Is commission received? Currently only applies to NH.

Yes = 1
No = 0

If the commission is received, policy fees cannot be charged. If omitted, a 0 (zero) value will be imported.

tinyint(1)

✓

mailing_insured_name

Full insured name as it appears in policy documents

varchar(100 )

✓

mailing_address

Insured mailing address

varchar(255 )

✓

mailing_address2

Insured mailing address line 2 (if applicable) - ie. apartment #, suite, etc.

varchar(255 )

✓

mailing_city

Insured mailing city

varchar(100 )

✓

mailing_zip_code

Insured mailing zip code

varchar(20)

✓

mailing_state_code

Insured mailing state. 2 letter state code abbreviation.

Example: "CA" = California or "FL" = Florida

varchar(20)

✓

insured_entity

Insured entity types are used for states that may consider certain entity types tax-exempt. If omitted, "commercial" will be used.

Insured Entity Types are listed below:

Import Code

individual = 1

commercial = 2

governmental = 3

federal = 4

tribal = 5

state_approved_tax_exempt = 6

hospital_alliance = 7

Currently only applies to FL, NC, SC, TN & TX. If known, this can be imported for every state and InsCipher will ignore the value in the states where it isn't applicable.

varchar(100 )

Depends

physical_same_as_mailing

If the Physical State is the same as the Mailing State, then set this value = 1

If the Physical State is NOT the same as the Mailing State, set this value = 0.

IMPORTANT: If you make the physical state the same as the mailing state then you will need to make sure that both addresses are added with valid "States" codes or you will receive an import error.

tinyint(1)

✓

physical_address

Physical address

Required if Physical State is NOT the same as Mailing State.

varchar(255 )

Depends

physical_address2

Physical address line 2 (if applicable) - ie. apartment #, suite, etc.

varchar(255 )

Depends

physical_city

Physical City

Required if Physical State is NOT the same as Mailing State.

varchar(100 )

Depends

physical_zip_code

Physical zip code

Required if Physical State is NOT the same as Mailing State.

varchar(20)

Depends

physical_state_code

Physical state. 2 letter state code

Required if Physical State is NOT the same as Mailing State.

varchar(20)

Depends

retail_producer_name

Retail Producer Name

Required for filing in DE, OR, MS, MO, WA, and CA if the business is written through a Retail Agent/Producer.

varchar(255)

Depends

retail_agency_name

Retail Agency Name

Required for filing in DE, OR, MS, MO, WA, and CA if the business is written through a Retail Agent/Producer.

varchar(255)

Depends

retail_agency_license

Not used by any states currently. Can leave blank.

varchar(255)

NOT ACTIVE

retail_producer_license

Retail Producer License

Required for filing in DE, OR, MS, MO, WA, and CA if the business is written through a Retail Agent/Producer.

varchar(255)

Depends

retail_phone_number

Retail Producer's Phone Number

varchar(255)

Depends

retail_email

Not used by any states currently. Can leave blank.

varchar(255)

NOT ACTIVE

retail_address

Retail Producer’s Address Line 1

Required in DE, OR, MS, MO, WA, and CA if the business is written through a Retail Agent/Producer.

varchar(255 )

Depends

retail_address2

Retail Producer’s Address Line 2 (if applicable) - ie. apartment #, suite, etc.

varchar(255 )

Depends

retail_city

Retail Producer City Location (if applicable)

varchar(100 )

Depends

retail_state

Retail Producer City Location (if applicable)

varchar(20)

Depends

retail_zip

Retail Producer City Location (if applicable)

varchar(20)

Depends

umr_number

Lloyd's transaction number

Required in NJ and MS if Lloyd's is a carrier on the policy.

varchar(20)

Depends

sla_transaction_number

NJ Transaction Number (Format XXXXX-XX-XXXXX)

Required in NJ

Numeric (12)

XXXXX-XX-XXXXX

Depends

agent_notes

Agent Notes

Populates the Agent Notes section on the Filing Details page of a Filing Agent/Filing Agency Admin user.

Include only if you want to add other information about the policy not captured in any of the other fields.

varchar (255)

✓

agent_id

Agent ID or Agency ID

Each Agency and Agent user is assigned an “Agent ID”. This value associates the transaction to a specific agency group or user. It is required so that InsCipher knows which agency to associate with the transaction.

To get this ID, you will need to log into the InsCipher Connect portal, go to Setup > User List and Settings > and view the Agency ID in the table for your Agency Admin user accounts.

integer

✓

invoice_number

This is the invoice number (or unique transaction ID) generated by your Agency Management System (AMS).

This number allows users to trace imports to existing transactions within the management system as is a value we recommend importing.

This number will be used to identify possible duplicate transactions. Identified duplicate transactions will be excluded from being imported.

varchar

✓

business_group_id

Business Group ID

This is if you have divisions, regions, or other business groups that you want to assign to a transaction for tracking.

This value, if imported, can be found on the Tracking tab in the filing details page of a Filing Agent/Filing Agency Admin User.

Most clients choose to leave this field blank

varchar (50)

✓

customer_code

Customer Code

This is if you have specific customer classifications in your management system that you want to be associated with a transaction for tracking.

This value, if imported, can be found on the Tracking tab in the filing details page of a Filing Agent/Filing Agency Admin User.

Most clients choose to leave this field blank

varchar (50)

✓

sop_name

Service Of Process Name

Currently, only applies to AL.

Service of Process (aka service of suit) is a clause used in the event of a failure to pay amounts claimed under the policy, insurers agree to submit to any court of competent jurisdiction in the US to accept summonses and complaints. If asked for in the portal, including the Service of Process information that is included in the policy documents.

varchar(100 )

Depends

sop_address

Service Of Process Address

Currently, only applies to AL.

varchar(255)

Depends

sop_address_2

Service Of Process Address 2 (if applicable) - ie. apartment #, suite, etc.

Currently, only applies to AL.

varchar(255)

Depends

sop_city

Service Of Process City

Currently, only applies to AL.

varchar(100)

Depends

sop_state

Service Of Process State. 2 letter state code

Currently, only applies to AL.

varchar(20)

Depends

sop_zip

Service Of Process Zip Code

Currently, only applies to AL.

varchar(20)

Depends

dc_naic

Declining Carrier NAIC Code

Declining Carrier is an admitted insurance carrier that has declined the request for coverage.

Multiple values are separated by pipe symbol “|”.

Currently available in SC, TN, IN, NY, and CA; necessary for SL-2 creation when batch filing.

Here is a mapping sheet that describes all of the declining carrier fields.

varchar(255)

Depends

dc_date_declined

Currently available in NY and CA; necessary for SL-2 creation when batch filing

date (yyyy-mm-dd)

dc_declining_reason

Currently available in CA; necessary for SL-2 creation when batch filing

varchar(255)

dc_underwriting_consideration

Only used in NY

varchar(255)

Depends

dc_representative_name

Currently available in CA; necessary for SL-2 creation when batch filing

varchar(255)

dc_representative_title

Currently available in CA; necessary for SL-2 creation when batch filing

varchar(255)

dc_representative_email

Currently available in CA; necessary for SL-2 creation when batch filing

varchar(255)

dc_representative_phone_number

Currently available in CA; necessary for SL-2 creation when batch filing

varchar(255)

wind_storm_exclusion

Windstorm Exclusion Flag

Flag on whether or not windstorm exclusion applies. Only applied to certain property coverages and only applies in TX and FL.

TRUE = 1
FALSE = 0

tinyint(1)

Depends

wind_storm_eligible_for_pool

Eligible For Windstorm Pool?

Only applied to certain property coverages and only applies in FL.

TRUE = 1
FALSE = 0

Boolean

Depends

wind_storm_deductible

Windstorm/Hurricane Deductible

Amount of windstorm/hurricane deductible related to certain property coverages. Only applies in FL.

If not applicable, leave blank.

decimal(12, 2)

Depends

wind_storm_primary_amount

Windstorm Primary Amount (Coverage A)

Amount related to certain property coverages. Only applies in FL.

If not applicable, leave blank.

decimal(12, 2)

Depends

wind_storm_other_coverages_deductible

All Other Perils Deductible

Amount related to all other deductibles not mentioned in the other fields above. Only applies in FL.

If not applicable, leave blank.

decimal(12, 2)

Depends

transaction_documents

Section for uploading transactional documents (Policies, Diligent Effort forms, etc.) during API submission. If omitted, documents will need to be added separately using the document import API. Or they can be added manually to the filing details page for each policy.

(see below)

Depends

└ code

Document import code examples can be viewed here.

varchar

✓

└ url

Full document URL that can be accessed by our system and downloaded.

For security reasons, many of our clients use a temporary URL (expiring after 120 mins) with a one-time use token.

varchar (255 )

✓

└ id

The unique document ID number. This is optional and used for import tracking purposes only.

integer(11)

✓

Additional Fields Applicable For Initial Data Migration

We recommend bringing in the current year's transactional data in order for the system to be able to account for what filings have been filed to date. To assist in this process, we have added the following fields to make the data imported contain the correct filing and paid dates.

Data migration will be done by your InsCipher Implementation Consultant. Please fill out the data migration sample file and email this to your consultant, rather than trying to import this file yourself. You will not need to do any data migration for the state of Idaho and Utah as these transactions are already in the InsCipher database.

Field Title

Description

Optional

Required

migrated

Used to track InsCipher-filed transactions vs. client-filed transactions. All items listed as 4=FILED as the transaction_status should also be listed TRUE=1 in this column.

TRUE = 1
FALSE = 0

✓

stamping_fee_invoice_id

Stamping Fee Invoice ID

If applicable, this value, if imported, relates to any state's stamping fee invoice number. Most clients choose to leave this blank during the data migration process.

Note: this value cannot be forced for Utah/Idaho transactions.

✓

stamping_fee_date_paid

Stamping Fee Paid Date

If applicable, this value, if imported, designates the data that a filing's stamping fee was paid to the state.

Note: this value cannot be forced for Utah/Idaho transactions.

✓

sl_tax_invoice_id

SL Tax Invoice ID

If applicable, this value, if imported, relates to any state's SL Tax invoice number. Most clients choose to leave this blank during the data migration process.

Note: this value cannot be forced for Utah/Idaho transactions.

✓

sl_tax_paid_date

SL Tax Paid Date

If applicable, this value, if imported, designates the data that a filing's SL Tax was paid to the state.

Note: this value cannot be forced for Utah/Idaho transactions.

✓

other_taxes_paid_date

Other Fee Paid Date

If applicable, this value can be used as a catch-all to track the date that any other state tax or fee was paid to the state.

Note: this value cannot be forced for Utah/Idaho transactions.

✓

unique_id

Unique ID

This value is often reserved for certain state-specific ID codes, such as MO's Risk Number, IL's countersignature number, or NY's affidavit number. Import this value during your initial data migration for reference.

✓

transaction_status

Transaction Status

To be added by InsCipher prior to import. Value can be a number below representing the corresponding transaction status. Unless you are importing documents at the same time, unfiled transactions should be listed as 1=Saved

1 = Saved

2 = Submitted

4 = Filed

Note: this value cannot be forced for Utah/Idaho transactions.

✓

date_filed

Date Filed

If applicable, the date that the policy was filed with the state. If the Date Filed is added, the system will auto-default the transaction status to "Filed".

Note: this value cannot be forced for Utah/Idaho transactions.

✓

license_number

License Number

Only will import if a valid license number exists for the same physical state.

If left blank, the system will default to the "Default License".

✓

date_submittedfiling_admin

Filing Admin

Assigning a filing ✓admin here will override the system's configuration that auto-assigns certain transactions to certain filers based on type, location, etc.

✓

date_submitted

Submitted Date

The date that the transaction is submitted into InsCipher. If left blank, the system will default this to be today's date or the date the batch is imported into the InsCipher Portal.

✓

transaction.filing_fee

Filing Fee

The contractual filing fee is to be charged by InsCipher for any transactions to be filed by InsCipher after the client go-live.

✓

transaction.rush_filing_fee

Rush Filing Fee

The contractual rush filing fee is to be charged by InsCipher for any transactions that shall be filed by InsCipher after the client go-live that are already over 30 days beyond the transaction effective date. These filings are rushed to avoid late penalties applied by the states.

✓

Field Mapping Informational Packet

For information related to Lines of business import codes, Insurance company import codes, Description of Risk import codes, Filing Types, Tax Titles, and Document Requirements, refer to this mapping packet.

Change History

DATE	DESCRIPTION OF CHANGE
7/18/2023	Added NY to the Declining Carrier field description
6/20/23	Title adjustment only (removed old date)
5/24/2023	Added CA to declining carriers and retail producer
5/19/2023	Updated CSV for FS and Data Migration
3/22/2023	Updated Entity Type fields in article and CSV
1/24/2023	Update the sample file. Clarified several sections and removed n/a fields.
1/17/2023	Added file size limit to article
12/21/2022	Added clarification around the InsCipher-only Transaction_Status field for historical data imports. Updated the CSV import template accordingly.
10/24/2022	Added migration field clarification. Added note on formatting for currency.
10/13/2022	Removed export_list field
10/4/2022	Updates to wind storm fields and data migration fields added to data migration csv file
8/26/2022	New fields added: property_limit, layered_risk, broker_of_record, risk_retention_group, multiple sos and dc fields
5/20/2022	Added historical data migration section to description field list and to sample csv file.
2/1/2022	Added Change History Log. Added links to new FS Mapping Packet, UMR number, SLA transaction number, clarified language related to syndicate list.

CSV Batch Import: Filing Services Clients ONLY

This article is designed to help you learn how to use the Transaction CSV batch import tool in InsCipher.

Table Of Contents

How Do I Perform a Batch Import?

How Do I Correct a Batch if There are Errors?

Field Descriptions

Additional Fields Applicable For Initial Data Migration

Field Mapping Informational Packet

Change History