Produce Preliminary Statutory Schedules
- Nancy Cohn (Deactivated)
- Kinga Huszno
You can produce Annual and/or Quarterly Schedules at any time after you run the ISTAR Refresh/Valuation for the month.
To run the schedules on a preliminary basis, you set the Report Date equal to the Month End Date that relates to the Statutory Reporting Period. Preliminary schedules are appropriate to monitor transaction activity, position information, and identify missing ISTAR and NAIC data. You must resolve ISTAR NAIC data issues before you can produce final schedules.
Several lookup queries assist with identifying and correcting issues with ISTAR NAIC data:
List DK Lot Activity. Select Insurance > Research > Lot Level Data.
List Client/Entity Relationships. Select Setup > Insurance > Clients.
Refresh/Valuation Status Report. Select Insurance > Processing > Status Reports.
List Preliminary Data Validations. Select Insurance > Control Reports > Exceptions. This query identifies holdings that may DK or that are missing a price for a specified month end period. You can submit for all exceptions, DK and/or missing price, allowing validation for these conditions prior to executing an ISTAR Refresh.
The following table lists issues, reports, and the corrective actions to take prior to rerunning the ISTAR Refresh/Valuation process for several troubleshooting scenarios.
 | Issue |  Report |  Corrective Action |
|---|---|---|---|
"DK" activity is present | List DK Lot Activity | Contact Eagle … Problem likely caused by invalid Processing Security Type. | |
"DKScheduleLineCode" activity is present | List DK Lot Activity | Correct invalid Schedule Line Code / SVO Schedule D Code and/or Group Code combination for the Asset. | |
Asset does not appear on the desired schedule | Schedules | Processing Security Type and/or Maturity Date are in error … Verify/correct. | |
Single or multiple Entities have not been refreshed | Refresh/Valuation Status Report | Verify/correct that "missing" entities are in the Entity list used for ISTAR Refresh/Valuation. | |
Securities in an Entity do not appear in the Client-level Schedule | List Client/Entity Relationships | Verify that the Entity setup (Setup > Insurance > Entities> Edit Entity Insurance Information) has the correct Client ID. |
Notes for the table:
DK. Denotes that ISTAR Doesn't Know the schedule on which to place the security.
DKScheduleLineCode. Denotes that ISTAR knows the appropriate schedule, but Doesn't Know where to place the security on the schedule.