Prescience vs. your current health plan
Using Dayforce does not by itself determine your health coverage. Compare the plan you use today with Prescience Diamond and Prescience Choice using the same employee census, coverage date and employer contribution. Your current plan might be arranged through a broker, carrier or PEO; this comparison does not assume Dayforce sells insurance.
| What changes | Prescience Diamond | Prescience Choice | Your current health plan |
|---|---|---|---|
| How coverage works | A company health plan with an effective $0 deductible and Prescience care navigation, with benefits specified in your quote. | An individual coverage HRA (ICHRA): the employer sets an allowance and employees choose their own individual health plans. | Use your plan documents to identify the carrier coverage and any employer-funded benefits. A broker or payroll brand alone does not identify the plan. |
| Employee deductible and costs | Designed for an effective $0 deductible for covered care under the Diamond benefit terms. Review the quoted copays, coverage limits and eligibility requirements. | Deductibles, copays and networks depend on each employee's selected individual plan. Compare the allowance with the premium and expected out-of-pocket costs. | Compare employee premium contributions, deductible, copays and out-of-pocket maximum from the actual plan, including any employer HRA or HSA funding. |
| Doctors and prescriptions | Carrier network selected for your group, with options such as Blue Cross Blue Shield or UnitedHealthcare where available, plus the Prescience Network and Prescience Extended Network. Confirm the exact network, doctors and prescription coverage in your quote before switching. | Employees compare the local individual plans available to them and check their own doctors and medications. | Use the current carrier's provider directory and drug formulary as the baseline. Keeping a payroll platform does not guarantee keeping a network. |
| Employee support | Prescience provides care navigation and benefits support alongside the quoted health plan. | Prescience helps employees compare plans, enroll and manage their health allowance. The selected insurer supplies the underlying coverage. | Identify what your carrier, broker and benefits administrator each handle today, including help finding care and resolving benefit questions. |
| Employer budget | Request a group-specific quote and compare the full annual employer cost, including the benefits and services in the proposal. Savings depend on the group and plan design. | Budget for the employer allowance plus the administration fee in your proposal. Compare how the allowance works for employees in different locations. | Add premiums, employer contributions, administration and any bundled service costs. Use the renewal offer, rather than last year's price, when comparing a renewal decision. |
| HR and payroll | Confirm the workflow for retaining Dayforce, employee changes and approved deductions before launch. | Confirm how allowance administration and any applicable deductions fit your Dayforce account. | Document the existing enrollment and payroll process, plus any broker, PEO or service agreement that affects a change. |
Tell us whether you want to keep Dayforce for your existing HR or payroll workflow. An outside health plan may require a separate enrollment and deduction process; account compatibility must be confirmed.
- Export your Dayforce census Use the instructions above and include all current W-2 employees, including people who may waive coverage. Identify owners and contractors separately.
- Upload the CSV and complete your quote request Select the file on this page, then complete company details and account verification. Review the imported employee information in the quote flow.
- Compare the actual offers Have your current plan summary, renewal pricing, employee contributions and must-keep doctors ready for the comparison. Use the same census and start date, then confirm coverage and payroll timing before making a change.
Upload your census to compare options. Read more about Prescience's employer benefits and pricing. Your written quote and plan documents determine the offered benefits and costs.
Start with your Dayforce account
The existing provider snapshot calls this entry Ceridian Dayforce. Use the employer's current Dayforce product and account details when arranging the handoff, rather than treating an older brand label as a different payroll system. Confirm the applicant company and the employee population before requesting a report. An administrator serving several entities should specify which entity's employees are included.
Our onboarding guide starts with Reporting and an employee demographics report, or a census prepared by the Dayforce administrator. Request the fields shown in onboarding and review the exported Excel or CSV data. A report that was built for a different operational purpose may omit birth dates, home locations or identifiers needed to reconcile enrollment. Have the report owner resolve those gaps before upload.
Benefit deductions may be controlled by an existing workflow or integration in the employer's account. Identify that owner and agree how the new elections and amounts will be entered. Staff-assisted setup must account for the employer's payroll calendar and any approval deadlines. Check the actual completed run, because a saved configuration does not establish that the intended employees were charged the intended amounts.
Confirm these details before setup
- Match the historical Ceridian Dayforce directory name to the employer's current account.
- Ask the report administrator for the correct company population and census fields.
- Coordinate any existing deduction feed and check the first completed payroll after the change.
Agree on the applicant's legal company name, the employees being considered for coverage, and the person who can authorize payroll changes. If the same administrator manages several companies, identify the exact account in every handoff. An employee list from the wrong company can look plausible while producing the wrong quote or deduction instructions. Keep these decisions with the employer's account records so a different administrator can understand the setup later.
Separate four tasks: preparing a census, choosing and enrolling in coverage, setting payroll deductions, and confirming the completed payroll. They can involve different systems and people. A successful census upload does not enroll employees, and a saved deduction does not prove that a carrier has activated coverage. Name an owner for each task and agree how the employer will know it is finished before announcing the start to employees.
Compare the full setup before choosing a plan
Compare the work and costs the employer will actually retain under each option. A lower-looking health-plan amount is not a complete comparison if changing the arrangement also adds payroll administration or removes a service the employer needs. Ask for account-specific terms and a written quote. This page does not supply vendor pricing, promise savings or establish that an outside plan is compatible with an existing contract.
| Option | What to confirm |
|---|---|
| Keep the current benefits arrangement | Confirm the renewal terms, coverage and employee experience. Keeping the existing workflow can be preferable when it meets the employer's needs and avoids a costly transition. |
| Keep payroll and change health coverage | Confirm that the service agreement permits the change, identify the enrollment and deduction owners, and account for any separate administration charges or manual work. |
| Change payroll or leave a bundled service | Compare the entire replacement arrangement, including payroll responsibilities, access to historical records, employee communications and the effort needed to coordinate the transition. |
Keep unresolved items visible rather than treating them as completed integration features. The employer should know which steps have an agreed owner, which need confirmation from the current provider, and which depend on the final plan selection. Make the coverage decision with those operational facts in view, not only a platform logo or the availability of an employee export.
Prepare the Dayforce employee census
The following is the starting point used in our employer onboarding guide. Report names, permissions and menus can change or differ by account; ask your platform administrator to confirm the current steps. The goal is a complete employee CSV, not a particular button sequence.
- Have your reporting administrator open Reporting and Analytics > Reporting > Reports and the Reports tab.
- Choose Create > Report from Topic and select an employee HR topic, such as HR Profile - Current Contact Information. Configure the required employee columns and scope, then save the report.
- Select the saved report, choose Run > Report, and enter its required filters.
- Expand Output and Page Format Options, select the required output format (CSV if available, otherwise Excel), and click Run Report. Download the result from Message Center; save as CSV if it is Excel.
Include the employer's W-2 employees, including people who may waive coverage, and clearly identify contractors. Use the field list shown in onboarding to check names, dates of birth or requested age information, home locations and work locations. Preserve employee identifiers where available. A list of email addresses alone is not enough to reconcile family coverage, eligibility information and later payroll deductions. If a value is missing, flag it for follow-up instead of inventing it.
Save an Excel export as CSV before uploading it. Check the selected worksheet, remove report headings and totals that are not employee records, and review any dates or identifiers the spreadsheet reformatted. Keep a copy of the original export for the employer's reconciliation. Select your CSV in the upload area above and complete account verification to import it securely. Do not put employee data in a support comment or a shared marketing document. Employees can add spouse and dependent details during the subsequent enrollment process.
Arrange payroll deductions
For Dayforce, plan on staff-assisted setup unless Prescience confirms another supported workflow for your actual account. The employer's payroll administrator may need to enter or approve the deduction changes. We do not infer automated write access from a vendor appearing in the Finch directory. Agree who makes the change, who reviews it, and which payroll deadline applies before promising employees a particular first deduction date.
Send the payroll owner the final approved elections and contribution instructions. Those should identify the employee, the elected coverage, the employee share, the employer share, the effective date and the pay schedule. Keep employee deductions separate from employer contributions. Ask the payroll and benefits advisers to confirm the appropriate tax treatment for the plan and worker; IRS Publication 15-B describes why benefit treatment and owner exceptions need review. Do not choose a tax code merely because it resembles an old deduction label.
Identify old deductions that should end and existing benefit connections that might overwrite a manual update. Decide how to handle a change made after a payroll approval deadline, an off-cycle check, a final paycheck or an employee starting partway through a month. The monthly contribution does not by itself answer those timing questions. Record the agreed treatment before staff enter the amounts, and avoid taking both the full old deduction and the full new deduction for the same coverage period without review.
A worked payroll handoff
An employer's older vendor records say Ceridian, while its administrators use Dayforce. The team confirms the account and company before preparing the census. A report created for another entity is rejected and rerun, preventing staff from setting up benefit deductions for employees outside the group applying for coverage.
The example concerns the employee's contribution, not the total plan price or a promised saving. If the employer pays part of the premium, that employer contribution must be tracked separately. If the employee changes coverage during the year, recalculate from the approved change and the remaining applicable deduction periods. Do not divide a full-year amount by the remaining checks unless the employer's agreed policy actually calls for that result.
Verify the first payroll and keep records current
Review the first completed payroll, not only the setup screen. Match each enrolling employee to the approved deduction amount and the correct coverage period. Also check people who waived coverage, left the company or ended a prior election, because an unintended deduction can be just as important as a missing one. Compare the employer and employee portions separately. Where there are multiple pay groups, review an affected completed run from each group before declaring the handoff finished.
Record differences and assign an owner to resolve them. A missing employee might reflect an identifier mismatch, a report filter, an approval deadline or an election that was never finalized. A duplicated amount might come from an old deduction or a second benefits workflow. Investigate the underlying record before making a compensating change in another system. Confirm how any correction will appear on the employee's next pay statement and keep the employer informed of the agreed resolution.
After launch, agree how new hires, terminations, location changes and revised elections reach the people responsible for payroll and benefits. A one-time census export is a snapshot, not a continuing synchronization service. Reconcile changes to the current employee roster and the approved plan instructions. If you change payroll providers later, preserve the deduction history and repeat the account, schedule and first-payroll checks with the new administrator rather than carrying forward an unverified assumption.
Sources and scope
Provider report steps come from the census guidance used in Prescience onboarding; your administrator should confirm current menus and permissions. Payroll setup descriptions reflect the supported Prescience workflow. Vendor documentation describes the vendor’s capabilities and does not prove a Prescience connection.
- Dayforce
- Dayforce export help
- Dayforce export documentation 1
- Dayforce export documentation 2
- Dayforce export documentation 3
- Finch provider directory (the source of the July 24, 2026 name snapshot)
- Finch: automated and assisted integrations are different
- IRS Publication 15-B: benefit tax treatment
- Dayforce logo source
