Send hours to Paycom
Earning codes, the hours file on the 15th and the last day, and optional API access.
Who does this: your payroll lead, with your Paycom representative.
Oh! Thyme sends Paycom the approved hours of each pay period, split by earning code. Until your account has API access, payroll downloads a file and imports it in Paycom.
1. Ask your Paycom rep for two things#
- The hours (earnings) import template for your account.
- Your earning code list.
2. Agree the earning codes#
An export of only Regular and PTO cannot carry what California requires on the pay stub. Pick a code from your own earnings list for each of these, and send them to us:
| Kind of hours | Why it needs its own code |
|---|---|
| Overtime, 1.5x | Hours at each rate must appear on the wage statement |
| Double time, 2x | Same |
| Meal period premium | Premiums are wages and must appear on the statement |
| Rest period premium | Same, and separate from the meal premium |
| Sick leave | If it is separate from PTO |
| Each kind of time off | Holiday, vacation and the rest |
3. Download the file each period#
On the 15th and the last day of the month, go to Pay > Payroll and choose Download Paycom file, then import it in Paycom as you import any hours file.
Before the file is made, Oh! Thyme lists anyone with hours and no Paycom employee code, and any day not yet approved. Days with an open request are held, and the totals count only approved days. Payroll sees which periods were already sent.
Optional: send hours by API#
If you would rather not upload a file, ask your Paycom rep to enable API access for internal use and to issue an API SID and token, and a Push Reporting Group if hours are to be pushed. Paycom may charge for this, so confirm the fee first. Paycom limits each import to 2,000 punches, with a cool-down between imports.
Read more: Paycom earning codes for California.