Is it possible to build an Employee Election Import in IS for the attached Fidelity deferral import (without creating the file entirely in IDL)?

Originally replied by Eddie Heinzelman on Apr 17, 2026, 9:35 AM.

Barbara,

This is something we've been looking at also. Normally, they are different Deduction xrefcodes for each of these (pre, post, roth). The issue though is getting them to fall under 1 EmpID since there can't be a separate line for each per the Employee Election Import specification. The other issue is translating the SSN from Fidelity into the EmpID in Dayforce. I don't think there is a translation function for this so far. We see Fidelity files quite often, and each time we've had to submit them to the Dayforce SAS team to transform the files as a separate import.

Originally replied by Sage Konstanzer on Apr 17, 2026, 3:39 PM.

A workaround I did for a client once was to have the vendor (not Fidelity, but hopefully Fidelity would be able to) send the file multiple times with different integration reference codes at the beginning of the filename, and then created multiple different integrations, each one picking up a different column of the file. Not pretty, but it did work.

Originally replied by Barbara Buchanan on Apr 17, 2026, 3:49 PM.

@Eddie Heinzelman​ and @Sage Konstanzer​ , thank you both for your comments. I like the multiple file idea, Sage. If multiple mapping doesn't work out (which seems likely), I will go back to Fidelity with that.