After the initial import is completed and saved, if you refresh Item Explorer with the sponsor open (using the refresh button towards the top of the Item Explorer window), you will notice that all of the people have a status of Ineligible. This is because each person has no status as of the last snapshot date (because no snapshot has been run yet). To get status for each participant, you need to run a snapshot

• Open the Manage Valuation Snapshots Screen: on the Valuation tab, press the Valuation Snapshots button.
• Open the Create Valuation Snapshot Screen: press the Add button.
• Run the Snapshot: the Snapshot Date must equal the conversion date. All of the other inputs can be left alone for now. Press the OK button.

After the initial snapshot is run, a window will appear that provides a summary of participant counts as of the snapshot date. While these counts sometimes match the valuation counts without additional work, this is generally not the case and you will need to modify your data in order to match these counts.

Identifying why you are off on your participant counts requires you to first identify which participants are off on status. To do this, you should do the following (even if you match, you should still do the following to confirm that you do not have offsetting errors which resulted in correct net counts):

• 1) Open the Snapshot File: on the Snapshot Results screen, press the View button. This will then open the Valuation Extract File. This file is ultimately what is used to feed your valuation software with DB Precision data each year.
• 2) Sort the Results by SSN: on the Data tab in Excel, press the Sort A to Z button (has A, Z and a down arrow). This will sort all of the extracted data by SSN in ascending order.
• 3) Open the Conversion File: if you do not already have it open, open the Conversion file in Excel and select the Snapshot tab, making sure that your cursor is in cell A1.
• 4) Copy the Snapshot Results: go to the snapshot results file and click on the top left of the sheet to select all cells in this Excel sheet. Right-click the selected range in Excel and choose Copy from the resulting menu.
• 5) Paste Results: go back to the conversion file and paste the copied data to the A1 cell of the Snapshot tab.
• 6) Select Pasted Range: select the entire range of copied data in your conversion file by putting your cursor on cell A2 of the snapshot tab and then press Ctrl-Shift-End on your keyboard.
• 7) Name the Pasted Range: with the range still selected, put your cursor in the Name Box in Excel (top left above the left-most column) and type tableSnap to assign this range with that name.
• 8) Create Compares Section of Import Tab: on the Import tab of your conversion file, to the right of both your data and derived items (status for example), highlight a column in yellow leaving at least one blank column after your derived columns.
• 8) Create SSN Compare Column: to the right of this newly highlighted column, leave at least one blank column and the type SSN in the first row.
• 9) Write the Compare Formula: in the second row of this SSN compare column, you will need to write a formula that compares status between the snapshot and the imported data. If your SSN was in the first column of the import tab and DB Precision status was in column V, your formula in row 2 would be as follows: IF(V2<>VLOOKUP(A2,tableSnap,2), 1, 0).
• 10) Filter Results: the above formula will return a 1 for any participant where status in DB Precision does not match what was expected upon import. If you then filter your import tab by this column (highlight the first row of the import tab and then select Data - Filter in Excel), you will see all participants where status does not match by then only displaying results where this column equals 1.

Below is a list of the most common reasons that status in DB Precision does not match the status reported on import and how to correct for these differences.

• Beneficiary with Hire Date: if any of the participants that you imported who were beneficiaries had a hire date (usually that of the former spouse), these participants will be counted as both active and beneficiary in DB Precision (dual status). To correct this, you should delete the employment date for this Person in DB Precision (Historical Dates screen for that Person) as well as delete the date from the import tab of the conversion file.
• Active with Termination Date: if an active participant is imported with a termination date and no rehire date, DB Precision will treat such a participant as terminated (vested or non-vested). If you are confident that the participant is active, you should make a note of the missing rehire date and then either estimate it based upon other information reported (such as earnings) or use a rehire date equal to the day after the termination date. You should enter this estimated rehire date both in DB Precision (Historical Dates screen for that Person) as well as in the conversion file (highlight this date in yellow). Conversely, if you believe the termination date is invalid, delete it from both DB Precision and the conversion file.
• Active with Benefit Information: when any type of benefit information exists in the import file for a person, even if it is payment start date with no benefit, DB Precision will create a benefit for that person and then classify the person as terminated vested or retired. Such benefits should be deleted from DB Precision (Benefit Payment Information screen) as well as from the conversion file.

If you have checked for the above issues and are still not matching status counts between DB Precision and what was imported, review our help topic on how DB Precision determines status by clicking here.