The System Import Screen is used to import participant data from a csv or text file into DB Precision for a sponsor.

Click the OK button and your import will begin. Note: Selecting OK will not change the data in the database. You will have the opportunity to cancel so no changes are made to the database.The status bar in the lower left of the screen will let you know how your import is progressing.

After DB Precision has read your file, an import results summary will appear. It is important to review this output as it may reveal problems with the import BEFORE you save the changes to the database.

• File to import: space to specify the full path (including file name) of the file being imported.
• Import Definition: select the import definition you want to use. The name in this box will be pre-populated with the current definition if you opened this screen with an Import Definition selected.
• Import Date: The general rule is to enter the date one day prior to your valuation date. This will ensure that any name changes will be in effect for any exports for valuation, statements, etc. Note that this date is used for the effective date of any name changes; it will not affect participation date, etc.
• Preview Button: press this button to view the columns specified in the Import Definition alongside the data specified in the import file selected as described above.
• Display transactions resulting from import: checking this box will show all changes that will be made to the data as a result of the import
  • Do not check new entrants for being possible duplicate participants: Skips the possible-duplicate-participant check for new entrants. This is separate from checking repeated identifiers within the import file.
• Display validation warnings for people imported: checking this box will run standard validation errors on all people being imported
• Ignore rows with critical errors and write row contents to error file: checking this box will allow the import to continue even if there are problems with your file. Only the rows with errors will not import. If you do not check this box and DB Precision comes across an error during the import, the error will appear and the import will stop (upon the first error).
• Use the following if Plan Number is not specified: if plan number for each benefit being imported has not been specified and the sponsor has multiple plans, you may check this box and choose a plan (assuming all benefits being imported are for the same plan).
• Treat any duplicate SSN/ID in the import file as a critical error: classifies a repeated SSN or Person ID in the import file as a critical error. The separate Ignore rows with critical errors and write row contents to error file option controls whether erroneous rows can be skipped while the import continues.
• Benefits imported are for a Cost of Living Adjustment (COLA) effective on: Check this if your plan has a COLA and the benefits being imported are for an increase effective on the date you specify here.
• Overwrite any existing benefit with new imported benefit: check this box if you want to completely replace any existing benefits for people being imported with those that are being imported.
  • Only overwrite benefits where existing plan number matches that of the imported benefit: Restricts benefit replacement to existing benefits with the same plan number as the imported benefit. Use this with the overwrite selection when benefits for other plans should be retained.
• Identify participants from following snapshot not contained in import file: checking this box will check for "drop-offs" - people who were on the last snapshot, but are not on the import file. If all of your data is being imported in one file, then check this box. Otherwise leave it unchecked.
• Only import data for existing participants: check this box if you have a closed group and you may want to make sure that you do not accidentally import data for participant who will never enter the plan