Sync payroll data with ADP
Run a payroll-data sync from Zenoti to ADP Run for a selected pay period. Hours, earnings, and deductions flow from Zenoti into ADP so the payroll administrator can process pay in ADP. This workflow assumes the integration is already connected — see Connect ADP Run for payroll.
On this page
- Before you begin
- How a payroll sync runs
- Review sync results
- Verify in ADP
- Correct a posted pay period (both states)
- Handle payroll export failures
- Reconciliation
- Tips
Before you begin
Permission: You need payroll management permissions to run payroll syncs.
- ADP Run must be connected and employee mappings configured. See Connect ADP Run for payroll.
- All new employees for the pay period must be mapped to ADP employee IDs.
- Time and commission data for the period must be finalised in Zenoti before export.
How a payroll sync runs
Zenoti posts each pay period's earnings to ADP Run as a batch on the cadence set in Payroll Frequency: on the Payroll accordion. For every mapped employee, the batch carries the commission types mapped to ADP payroll codes in Payroll Codes Mapping; employees mapped to Do Not Process and unmapped employees are skipped.
- Before the period closes, confirm the mappings: open Configuration > Integrations > Integration Settings at center scope, expand Payroll, and check Payroll Codes Mapping and Employee Mapping. Select Sync in either panel to refresh the codes or employees from ADP first.
- Let the scheduled batch run, or ask Zenoti Support to post the period again if a batch has to be re-sent.
Review sync results
- Open the payroll integration report and filter Status to All Statuses, Pending, Processed, or Failed.
- A Processed batch reached ADP Run. A Failed batch carries ADP's response; the usual causes are an unmapped payroll code, an employee ADP no longer recognizes, or a pay period ADP has already closed.
- Correct the mapping or the ADP-side record and let the next batch pick the period up.
Verify in ADP
- Sign in to your ADP Run account.
- Open the payroll run for the period.
- Confirm earnings, hours, and deductions match Zenoti's records employee by employee (spot-check at least five employees including the highest and lowest earners).
- Process payroll in ADP as usual.
Correct a posted pay period (both states)
Open pay period (ADP not yet processed)
- In Zenoti, correct the time, commission, or deduction entries for the affected employee.
- Let the next scheduled batch post the corrected values for that employee. ADP overwrites the previously submitted values on the open pay run.
Closed pay period (ADP already processed)
Once ADP has processed payroll, the previously submitted data cannot be overwritten through a sync — the pay run is closed.
- Correct the underlying data in Zenoti for audit purposes.
- Coordinate with your ADP payroll administrator to issue an adjustment on the next pay run (ADP's retroactive adjustment flow), or to run an off-cycle pay run in ADP if urgent.
- Document the correction in both systems.
Never try to "re-sync" a closed pay period — the risk is double-payment or overwriting records that have already been tax-filed.
Handle payroll export failures
| Failure mode | User-visible symptom | Resolution |
|---|---|---|
| ADP unreachable | The batch stays Pending in the payroll integration report. | Wait for the next run; check ADP status if the batch stays pending. |
| Subscription not authorized | Batches fail and the Payroll accordion's Verify Authorization fails. | Select Authorize and Verify Authorization again on the Payroll accordion. |
| Employee not mapped | The employee is missing from the batch. | Map the employee in Employee Mapping (or confirm Do Not Process was intended). |
| Payroll code not mapped | Make sure all the payroll codes are mapped before saving. when saving, or the batch fails on the code. |
Map every Commission Type to a Payroll Code and select Save. |
| Employee inactive in ADP | The batch fails for that employee with ADP's response. | Reactivate the employee in ADP, or set the employee to Do Not Process. |
| Wrong subscription for the center | Employees land under the wrong ADP employer. | Check the subscription's Parent Center on the Payroll accordion and move the center to the right subscription. |
| Pay period already closed in ADP | The batch fails with ADP's closed-period response. | Use the adjustment path described in Correct a posted pay period. |
Reconciliation
Reconciliation closes the loop between hours captured in Zenoti and payroll processed in ADP.
| Source | Report / view | Match key | Cadence |
|---|---|---|---|
| Zenoti | Payroll export report for the period (from the ADP Run sync page) | Employee ID + earning code + period | Every pay cycle |
| ADP | Payroll register for the period | Employee ID + earning code + period | Every pay cycle |
For each employee, compare Zenoti's hours and earnings to ADP's register. Differences typically come from: (a) late timecard edits that were not re-synced, (b) deductions added manually in ADP, (c) overtime thresholds configured differently in the two systems.
Run the reconciliation before ADP's cut-off so corrections can be applied on the open pay run. After cut-off, use the adjustment path.
Tips
- Run the sync before the ADP payroll processing deadline so you have time to review and correct errors.
- Verify employee mappings regularly — new employees must be mapped before their first payroll sync.
- Keep a log of tokens per center under the Multi-token model so admins do not reassign them by mistake.