Revision Date | Revised By | Summary of Revisions | Section(s) Revised |
---|---|---|---|
10/11/21 | Sande Meith | Initial draft | All |
6/5/25 | Sande Meith | Correct the 15th to the 5th of the month | 1 |
09/15/25 | Training | No longer using process guide; content created as job aid, located in Benefits job aid chapter. | All |
Process Overview
Purpose
The Delta Dental Benefits Interface sends employee and dependent dental enrollment data from CHRS to Delta Dental each month.
Key Points
- File format: HIPAA EDI 834 (standard benefits enrollment file).
- Delivery method: Secure File Transfer Protocol (SFTP).
- Coverage: Active employees and their dependents enrolled in:
- Delta Dental PPO
- DeltaCare USA HMO
- Extra data (e.g., Group Division Number, Business Unit) is added by a CSU modification.
- Data security: Must follow CSU Level 1 and Level 2 data security policies.
Monthly File Timeline
- Due: No later than the 5th of each month by 3:00 pm.
- Covers: The previous month’s activity (e.g., August activity sent by September 5).
- Campuses should finish early to allow time for error checks.
Annual Open Enrollment File
- Separate file for January 1 changes.
- Due: December 5 by 3:00 pm.
Error Handling
- Upload errors to Delta Dental’s secure server must be fixed by the campus contact.
- Corrected files must also be resent no later than the 5th by 3:00 pm.
- Delta Dental requires a valid file from every campus (including the Chancellor’s Office) to begin processing.
Important Consequence
If a campus fails to send a valid file:
- Delta Dental marks all employees and dependents from that campus as terminated.
- This causes loss of dental coverage.
Reconciliation with SCO
- Delta Dental compares:
- CSU HIPAA EDI 834 file(s)
- Monthly deduction file from the State Controller’s Office (SCO)
- If no deduction is found on the SCO file and no record is on the CSU file → the employee is considered terminated.
- Unresolved issues escalate to Human Resources Management (HRM).
One (1)-Step Daily Processing
Daily Steps
- Run the Fix Unique Constraint Errors job aid.
- Review CSU Snapshot Unique Constraint errors.
- Resolve all errors for your campus.
- Confirm that the Refresh Benefits Snapshot has successfully completed overnight.
- This must be done before running the Delta Dental interface.
Four (4)-Step Monthly Processing
Before You Begin
- CMS-Benefits will complete the one-time setup for your campus.
- In CHRS, the Refresh Benefits Snapshot runs automatically each night — you don’t need to run it manually.
Monthly Steps
-
Check for errors
- Run the Fix Unique Constraint Errors job aid.
- Review and resolve any CSU Snapshot Unique Constraint errors.
-
Verify Refresh Benefits Snapshot
- Confirm that the nightly Refresh Benefits Snapshot ran successfully.
- See Section 5.0 for detailed instructions.
-
Run the Delta Dental file
- Run the HIPAA EDI 834 process (Delta Dental Benefits Interface – CSUBB012 SQR) to success.
-
Upload the file
- Use CSU security protocols.
- Upload the file to Delta Dental’s secure server (SFTP).
Verify that the Nightly Refresh Benefits Snapshot Process Ran to Success
Use this process to verify that the nightly Refresh Benefits Snapshot process ran to success the night before.
-
Navigation: Click on the NavBar Icon
- Menu > PeopleTools > Process Scheduler > Process Monitor.

- On the Process List page, delete your User ID from the User ID field.
- Enter the User ID of CHR_SCHEDUCSU.
- Verify that it says 1 and Days in the frequency fields.
- Click on the Refresh button.
- Locate the BEN100AD job.
- Verify that the Run Status says Success.
- If the Run Status does not say Success, for example, if the Run Status says Error, work with your technical resource to create a Service Now ticket for CMS-Benefits.
- If the Run Status says Error, do not run the HIPAA EDI 834 process to create the Delta Dental interface. Do not run the HIPAA EDI 834 process to create the Delta Dental interface until CMS-Benefits resolves the error and BEN100AD runs successfully.
Review Snapshot Information
Use the Review Snapshot Information page to review the records included in a successful run of the Refresh Benefits Snapshot process.
- Navigation: Click on the NavBar Icon
- Menu > Benefits > Interface with Providers > Review Snapshot Information.

- Enter the Empl ID to and then click on the Search button review specific employee detail information.

2. The Review Snapshot Information page appears.

3. Click on the Detail link associated with the dental plan to review specific plan information on the Enrollment Snapshot Detail page.

Create the HIPAA EDI 834 File (Delta Dental Benefits Interface File)
Purpose
- The Delta Dental Benefits Interface file sends employee and dependent enrollment data from CHRS to Delta Dental.
What the process produces
- A text file containing the enrollment data.
- Interface history details that you can use to review employee dental information.
- This section provides the steps necessary to generate the HIPAA EDI 834 file (Delta Dental Benefits Interface file).
- Prior to generating the running the HIPAA EDI 834 file (Delta Dental Benefits Interface file) a Run Control needs to be created for your User ID. Note that this task is generally a one-time setup.
- Navigation: Click on the NavBar Icon
- Menu > Benefits > Interface with Providers > Create HIPAA EDI 834 File.

- If you already have a Run Control ID, enter the existing Run Control ID. If you do not have a Run Control ID, click on the Add a New Value tab and enter a new Run Control ID called [Campus_Name]_Delta_Dental_Interface_File and then click on the Add button.
- The Create HIPAA EDI 834 File page appears.

- Populate the fields above as directed below:
Page Field |
Description |
---|---|
As of Date |
Displays the last date the Enrollment Reporting Snapshot was run (which should be greater than or equal to the first day of the current month for the standard monthly file). For Open Enrollment file, as of date is 01/01/2XXX. |
File Effective Date | Use the first day of the current month for the standard monthly file. For Open Enrollment file, use 01/01/2XXX. |
File Enrollment Date | Use the first day of the current month for the standard monthly file. For Open Enrollment file, use 01/01/2XXX. |
Acknowledgement Requested | This field must be blank. |
Test File | Select this check box to use the file as a test file, rather than a production file. This field must be blank for a production file. |
EDI Partner ID | Enter the trading partner for your campus for the transmission. Select [CAMPUS NAME]-Delta. |
File Type | This value must be set to: Full File Replacement. CSU will send “all” active employee and dependent records only. The following values are available for selection from the drop-down menu: Full File Audit: Select this value to create a file that contains records for all employees, including terminations. Full File Replacement: Select this value to create a file that contains current records only as of the date of the file. The system drops all terminated employees from the file. Update Only File: Select this value to create the Open Enrollment Changes Only file that contains only those records where changes have occurred to either the employee or any of his/her dependents records that are relevant to the vendor and can be tracked in CHRS through the use of effective dates. Note: When Update Only File is selected, the following two fields appear, and are required: From Date and To Date. |
Include All Vendors | This field must be blank. Valid values are only those vendors who are classified as providers on the Provider/Vendor table and also appear on the Snapshot Plan table. |
Vendor (Payer) Selection | |
SetID | Select SetID of CSUID. |
Vendor ID | Select Delta Den |
Short Vendor Name | Automatically populated. |
Vendor Name | Automatically populated. |
Federal EIN | Automatically populated, displays value from the Provider/Vendor table. |
Include All Companies | This field must be blank. Select to include all companies who appear both on the Company table and on the Snapshot Plan table. |
Company | Select the appropriate campus value. Enter the company (employer) to be included in the transmission. Valid values are only those vendors who appear both on the Company table and on the Snapshot Plan table. Note: The companies selected for the 834 transaction must have a valid FEIN entered on the Company table. The system will generate a warning message if the FEIN is missing for one or more companies. |
Description | Automatically populated. |
Federal EIN | Automatically populated, displays value from the campus Company Location table. |
Include all Plan Types | Select to include all plan types that appear on the Snapshot Plan table. This field must be blank. |
Plan Type | Select Plan Type 11. Valid values that appear on this list are only those plan types that appear on the Snapshot Plan table. |
Additional 5010 Selections: Benefit Plan Selection |
The Include All Benefit Plans box should be unchecked. Enter all Delta Dental benefit plans to be included in transmission to the Benefit Plan Selection boxes. |
Group Number Selection | Value for Group Number must be set to * (asterisk). Select any dental benefit plan that has an asterisk. |
Max Members in Transaction Set | Value defaults automatically. Specify the maximum number of members to be included in each transaction set of the transmission. The default value is 10,000 which is the maximum allowed by the reporting standard, but you can set a lower number not less than 100. |

- If you receive this warning message, please click the OK button. You can disregard this warning message.
- Click on the Save button. The next time you run the file, you will only be required to update the File Effective Date and File Enrollment Date fields.
- Click on the Run button.
- If able, select PSUNX for the Server Name.
- Select the checkbox for the Delta Dental Interface, process name CSUDELTA.
- Click on the OK button.
- The Process List page appears.
- Click on the Refresh button until the CSUDELTA process completes.

If you receive this warning message, please click the OK button. You can disregard this warning message.
- Verify that the CSUDELTA run status is Success. Work with your technical resource to review and if needed create a Service Now ticket if the run status is Error.
- If the Run Status is Success, click on the CSUDELTA link.
- The Process Detail page appears.

- Click the CSUBB012 link.
- The Process Detail page appears. Click on View Log/Trace.
- The View Log/Trace page appears.
- The file ending in .TXT is the Delta Dental interface file. The file ending in .OUT contains the record count of the interface file. The file ending in .LOG is the process log file.
- Download the file ending in .TXT to a secured server and prepare it for transmission.
Security Guidelines and Interface File Transmission
Why security matters
The Delta Dental Benefits Interface contains sensitive employee and dependent data. Campuses must follow CSU data security policies, standards, and HIPAA guidelines when processing and transmitting these files.
Data classifications
-
Level 1 (L1) – Confidential Data
- Protected by law (e.g., California Public Records Act, federal laws).
- Unauthorized use could cause severe damage (financial loss, legal issues, reputational harm).
- Examples:
- Birth date + last 4 of SSN + name
- Social Security Number + name
- Health insurance information
-
Level 2 (L2) – Internal Use Data
- Not always legally protected, but still sensitive.
- Unauthorized use could harm CSU or violate privacy.
- Examples:
- Name + full or partial birth date
- Non-directory education records
Who can access
- Only authorized campus personnel with assigned roles.
- Access is limited to those with a business need-to-know.
Step 3: File upload to Delta Dental
- Log in to Delta Dental’s secure server (SFTP): https://ftp.delta.org
- Use the User ID and password assigned to your campus.
- Follow instructions in the MOVEitDMZ Manual (available on Delta’s site) to upload the file.
Monthly file processing
- Run and transmit the file by the 15th of each month.
- Delta Dental reviews files for errors:
- If errors are found, Delta sends details to the campus.
- The campus updates records, reruns the process, and resubmits a Full File Replacement.
- Once all errors are resolved, Delta combines all campus files for processing.
- Errors found after files are combined will be addressed by HRM.
Data storage and retention
- Files may be securely stored at the campus for troubleshooting.
- Purge files within 60 days of the run date to ensure secure handling.
- Employee identifiable data should never be shared outside authorized use.
Error Handling
What happens after file submission
- Delta Dental automatically validates each campus file.
- A confirmation e-mail is sent to the designated campus contacts if the file is valid.
If errors are found
- The designated contacts receive a secure e-mail from Delta Dental listing the validation errors.
- Correct the errors in Oracle/PeopleSoft.
- Generate a new file.
- Resend the corrected file to Delta Dental no later than 3:00 pm on the 20th of the month in which the errors were reported.
Support
- A Delta Dental Enrollment Analyst is assigned to CSU and available for assistance.
Key Timing
- All 23 campuses (including the Chancellor’s Office) must upload and pass initial file validation by the 20th of each month.
- Once all files are validated, Delta Dental merges the files on the 20th.
Why it matters
- If a campus delays or fails to send a valid file, it impacts the entire CSU system.
- Missing campus records cause termination of benefits for affected employees and dependents.
Additional Audit Step
- Delta Dental audits dependent data against the monthly deduction file from the State Controller’s Office (SCO).
Appendix A - Data Typically Included in HIPAA EDI 834
The data included in the HIPAA EDI 834 (Delta Dental Benefits Interface) file is based on the values entered on the Create HIPAA EDI 834 File Page Run Control.
Data Type |
Specific Data |
---|---|
Benefits Data |
New Enrollments Coverage Code Benefit Plan Primary Care Physician (PCP) Covered Dependents Plan Terminations |
Job Status |
|
Personal Data |
|
Appendix B – Screenshots of Open Enrollment Changes Only File
- Campuses generate an annual “Changes Only” file in December.
- This file captures transactions effective January 1 of the next calendar year (for example, January 1, 2013).
- To create the Open Enrollment file, update the Oracle/PeopleSoft page as shown in the screenshots.
- For this file, the As Of Date, File Effective Date, File Enrollment Date, and From Date must all be set to 1/1/XX of the following year, and the File Type must be Update Only File.
Related Job Aids
End of Article
0 Comments
Add your comment