Contract list

Validation rules for fields related to contracts.

Note: Verisk Synergy Studio does not support single-day contracts.
Field Description Validation rules Default value
Contract ID Unique system-generated sequential identifier for the exposure set record.
  • Required if you are creating a new record or editing an existing record.
  • Cannot begin with a space or contain commas or semicolons.
  • Can contain up to 100 characters.
Insured Name Client's name.
  • Optional.
  • Must be unique for the book.
  • Can contain up to 60 characters.
Contract Type Code for the contract type. Verisk Synergy Studio v1.0.0 currently supports only the Primary Property policy type. Primary Property
Producer Name Name of the producer of the contract.
  • Optional.
  • Can contain up to 60 characters.
Underwriter Name of the underwriter of the contract.
  • Optional.
  • Can contain up to 60 characters.
Branch Name Name of the branch.
  • Optional.
  • Can contain up to 60 characters.
ID of Expiring Contract Unique user-defined identifier for the expiring contract.
  • Optional.
  • Can contain up to 100 characters.
Status

Code for the submission status.The letters represent the SubmitStatusCode in the database reference:

  • Authorized (A)
  • Bound (B)
  • Cancelled (C)
  • Expired (E)
  • Quoted (Q)
  • Rejected (R)
  • Renewal (RN)
  • Submitted (S)
 Submitted
Currency

ISO 3-character code for the base currency associated with the exposure data for this contract

For analysis at the contract level, the application converts all locations to this base currency.

Refer to the list of valid currency codes.

 US Dollar (USD)
Inception Date Inception data of the contract. Also referred to as the Effective FROM Date. When importing data, use one of the following formats:
  • MM/DD/YYYY
  • DD/MM/YYYY
  • YYYYMMDD
  • YYYY-MM-DD
  • Required if you are creating a new record or editing an existing record
  • Date format is specific to locale of end user.
  • Must be less than the expiration date.
For inception and expiration dates, and other in-force dates, you must specify a date value between 01/01/1970 and 12/31/2038, inclusive, for dates based on U.S. regional settings. If you are not using U.S. regional settings, use a date value other than 01/01/1970, such as 01/01/1990.		 1/1/[current year]
Expiration Date Contract expirationn data. Also referred to as the Effective TO Date. When importing data, use one of the following formats:
  • MM/DD/YYYY
  • DD/MM/YYYY
  • YYYYMMDD
  • YYYY-MM-DD
  • Required if you are creating a new record or editing an existing record.
  • Date format is specific to locale of end user.
  • Must be greater than the inception date.
For inception and expiration dates, and other in-force dates, you must specify a date value between 01/01/1970 and 12/31/2038, inclusive, for dates based on U.S. regional settings. If you are not using U.S. regional settings, use a date value other than 01/01/1970, such as 01/01/1990.		 12/31/[current year]
Perils

Numeric code for the single peril or set of perils insured under this contract.

Note: To specify multiple perils in a single entry within an import file, separate the corresponding peril codes with a plus (+) symbol, for example: PWH+PES.
 All perils (PAL)
Line of Business (LOB) Name of the user-specified line of business.
  • Lines of business should be unique between property and workers' compensation, if you need to see data separately for property and workers' compensation.
  • Can contain up to 60 characters.
 Unknown
Policy Form User-defined policy form.
  • Can contain up to 60 characters.
 Unknown
Locations Count Location count for the exposure set. Read-only
Layer Count Number of layers in this contract. Read-only
Layer Level Reinsurance Count Number of reinsurance treaties in the layer(s) in this contract. Read-only
Location Level Reinsurance Count Number of reinsurance treaties associated with the location(s) that this contract covers. Read-only
Total Replacement Value Total replacement value for all coverage combined.
  • Defaults to a value in the application user interface, provided that an exposure summary has been generated for the exposure view.
  • Value changes if Display Currency settings change for the project.
TRV Currency The currency used to calculate the TRV.
  • Defaults to the currency selected when the exposure view was created.
  • The application dynamically converts all location TRVs using the exposure view currency and conversion rate; it does not store these values in the database.
User Defined Field 1 (UDF 1) User-defined field 1. Used for purposes of aggregation.
  • Optional.
  • May be alphanumeric and may include hyphens and underscores.
  • Can contain up to 60 characters.
User Defined Field 2 (UDF 2) User-defined field 2. Used for purposes of aggregation.
  • Optional.
  • May be alphanumeric and may include hyphens and underscores.
  • Can contain up to 60 characters.
User Defined Field 3 (UDF) User-defined field 3. Used for purposes of aggregation.
  • Optional.
  • May be alphanumeric and may include hyphens and underscores.
  • Can contain up to 60 characters.
User Defined Field 4 (UDF 4) User-defined field 4. Used for purposes of aggregation.
  • Optional.
  • May be alphanumeric and may include hyphens and underscores.
  • Can contain up to 60 characters.
User Defined Field 5 (UDF 5) User-defined field 5/ Used for purposes of aggregation.
  • Optional.
  • May be alphanumeric and may include hyphens and underscores.
  • Can contain up to 60 characters.