Blog

Payroll-ready time export: a hotel checklist

· payroll, export, time clock

A payroll-ready time export is a file with one clear row of hours per person per pay period, split into regular and overtime, built on approved punches and closed to further edits. The format matters less than whether the numbers in it are the ones you meant to pay. Most payroll errors that start in a time clock enter at the export, not the clock, because that is the moment nobody looks.

What the file must contain

At minimum, for each employee in the pay period:

FieldWhy
A stable employee identifier your payroll provider recognizesNames collide; IDs do not
Pay period start and endSo a late file lands in the right run
Regular hoursThe base of the pay line
Overtime hours, by tier if your rules have tiersDifferent rates, different lines
Rate, if it varies by roleDual-rate staff need it, see blended overtime
Property or locationFor multi-property operators
Only approved punchesA pending punch is not a payable one

If you pay holiday premiums or shift differentials, those need lines too, or a note on how you handle them. See holiday premiums and overtime.

Some payroll providers accept a hours import with their own column names and order. ProfitClock’s Smart and Portfolio plans include payroll import files shaped for ADP Workforce Now, Paychex Flex and Gusto, with the layout confirmed at setup; Core gives you approved hours you can enter or reshape yourself. We do not sync directly to a payroll provider. Whichever tool you use, ask your provider for their exact import specification and test it with one real employee before relying on it.

Nine checks before you send it

An invented example: a 40-room motel, 19 employees, biweekly payroll, a placeholder $16/hr wage.

  1. Is every punch approved? Open punches, flags and pending edits are not ready. Run the weekly approval first.
  2. Does the total tie out? Sum the file’s hours and compare with the time clock report for the same period. If they differ, find why before sending. The method is in payroll total vs time clock total.
  3. Is the period right? Start and end dates match your payroll calendar, in the property’s local days, not UTC. A punch at 11:30 PM Saturday belongs to Saturday.
  4. Do the overtime rules match? Spot-check one person over the threshold. At a placeholder $16/hr, 44 hours in a 40-hour week is 40 regular plus 4 overtime; the premium is 4 x $8 = $32 on top of regular pay. Do the arithmetic by hand once. The overtime calculator helps.
  5. Are multi-role staff split correctly? A person working front desk and housekeeping at two rates needs hours by role, not one blob.
  6. Are new hires and departures handled? A last-day punch, a start mid-period, a rehire with an old ID.
  7. Are the edits explainable? Skim the edit history for the period. Any late edit to a closed period needs a reason.
  8. Is anyone missing? Compare the employee list in the file to the people you know worked. A person with zero hours who worked is a missed punch; a person with hours who did not is worse.
  9. Did the file import cleanly? Do a test with one person, then the whole file. Check a sample pay line against what you expected.

The numbers worth writing down

Keep a short log each period:

  • Total hours in the file
  • Total regular, total overtime
  • Number of employees
  • Date sent, by whom
  • Any manual adjustment and why

When something is questioned in nine months, this is the page you will look for.

Why exports fail

  • Duplicate IDs. Two people with the same number in different properties collide. Your payroll provider’s ID, not your clock’s, is the key.
  • Rounded hours. Hours converted to decimals (7.5 versus 7:30) and rounded differently by the clock and the provider produce small differences that add up. Agree on the rounding.
  • Wrong period boundary. Weekly overtime requires a fixed workweek; if the file’s period cuts across it, overtime will land in the wrong run.
  • Late edits. Someone edits a punch after the file went out. The check was already written. Lock closed periods.
  • Format drift. A provider updates their import without telling anyone. Test again after any change on their side.

What not to expect

An export is not a payroll run. It does not calculate taxes, does not know about deductions and cannot tell you whether overtime was owed under your state’s rule. It reports hours as you configured the thresholds. Rules vary by state and change; check yours, and have whoever advises you on payroll review your thresholds.

Buying note

If an export that matches your provider’s layout is a requirement, ask which plan includes it before you compare prices. With ProfitClock, the Smart and Portfolio plans include import files shaped for ADP Workforce Now, Paychex Flex and Gusto, with the layout confirmed at setup, while Core gives you approved hours to enter or reshape yourself; see the pricing page for what each plan includes. A trial on real punches, as in how to trial time clock software, is the way to confirm the file works for you.

Quick checklist

  1. All punches approved. 2. Totals tie to the clock. 3. Period in property-local days. 4. Overtime spot-checked by hand. 5. Roles and rates split. 6. Hires and departures covered. 7. Late edits explained. 8. Nobody missing. 9. Test import before full import.

Start seeing what labor actually costs

Set up your property, put staff on the clock, and read tomorrow morning’s labor number.

14-day free trial · No credit card · Cancel anytime