Employee SpotlightAUG 4, 20262 min read
Tommy Huynh documented the check that stands in front of payroll
Every payroll run starts with a file that has to be right. Tommy Huynh submitted that check through Automation Scout with the frequency, the systems and the manual steps written down.
Keenan ChiassonAUG 4, 2026
Before a payroll run, Payroll exports the hours out of TimePro and emails the file over for validation. Tommy Huynh checks it against JET project IDs and task codes, looks for required fields that came through blank or wrong, corrects what he finds, and hands back a file Payroll can process in ADP. Regular runs, adjustments and off-cycle runs all pass through the same gate.
- 10 to 15 files a week, 1 to 2 minutes a round, so roughly 0.7 to 2.2 hours a month
- Systems touched: TimePro, email, Excel, JET, Dataverse, D365 Finance, ADP
- Run by Tommy, with Andrew in Payroll as backup
The hours are small and the brief says so. What makes the task interesting is where it sits rather than what it costs: it is the last look at the data between a timekeeping export and money leaving the company. Catching a bad project ID here is cheap. Catching it after ADP has run is not.
The brief also splits the work honestly. Downloading the file, running the lookups, comparing project IDs and task codes and flagging blank required fields is mechanical. Deciding the correct source value, deciding whether the fix belongs in Dataverse or D365, making that correction and handling an unusual project or task code is judgment. Tommy named the source-system correction as the worst step, because that is the part with no shortcut.
