Paycom Employee Sync
Sync your employee roster from Paycom and FastQuery keeps user accounts up to date automatically — new hires get invited, transfers move to the right facility, and departures are cleaned up. No more managing accounts by hand.
How It Works
Section titled “How It Works”You create a Push Reporting export in Paycom, and FastQuery connects to your Paycom SFTP on a schedule (every few hours) to pull the latest roster file. Each file is processed automatically:
- New employees get a FastQuery account and an email invitation.
- Transfers are reassigned to the facility matching their location code.
- Departures — sync-managed employees missing from the file are marked for removal and deleted after a 7-day grace period. Users you created manually are never touched by the sync.
Paycom Setup
Section titled “Paycom Setup”- In Paycom, create a Push Reporting export of your employee roster that delivers to the
/Outbounddirectory as a CSV. - On the Paycom integration page in FastQuery, enter your Paycom SFTP username and password for
push.paycomonline.net.
Note: Paycom SFTP passwords expire every 12 months. When you reset the password in Paycom, update it in FastQuery too or the sync will stop.
Report Fields
Section titled “Report Fields”Paycom’s column names are fixed, so build your Push Report with exactly these fields:
| Field | Required | Description |
|---|---|---|
| Work_Email | Yes* | Used as the primary email |
| Personal_Email | Yes* | Used only when Work_Email is empty |
| Legal_Firstname | Yes | First name |
| Legal_Lastname | Yes | Last name |
| Preferred_Firstname | No | Overrides Legal_Firstname when set |
| Preferred_Lastname | No | Overrides Legal_Lastname when set |
| Locations_Code | Yes | Must match the FastQuery location ID |
| Business_Title | No | Job title |
* Include both email fields. Each employee connects through their Work_Email; those without one fall back to Personal_Email. Employees with no email, or no name, are skipped.
A few things to know:
- The Locations_Code must match a FastQuery location ID exactly — employees whose code has no matching location are skipped.
- Export active employees only. The sync treats the file as the full roster, so anyone missing is considered departed.
- The Business_Title is used once, when the account is created, to pick a sensible starting role — managerial titles start as managers. Role changes you make in FastQuery afterward are never overwritten.
Headquarters Staff
Section titled “Headquarters Staff”If your roster includes corporate or office staff under a Locations_Code that has no matching FastQuery location, enter that code under Headquarters codes on the Paycom integration page. FastQuery routes those people to your Headquarters facility instead of skipping them.
Monitoring
Section titled “Monitoring”The Integrations page shows a log of recent sync events — files pulled, accounts created, and any rows that were skipped and why. If a sync looks wrong, check the event log first: the most common causes are a Locations_Code that doesn’t match any FastQuery location ID, or an expired Paycom SFTP password.