ZenotiHelp

Process tips payouts

ZTZenoti Docs Team Updated September 6, 2026 6 min readGuide

Once the tips payout integration is configured, Zenoti posts each business day's tips to the provider through a scheduled job. This article covers the day-to-day work: letting the schedule run, posting a day by hand, reviewing what was posted in the tips integration report, and fixing rows that failed. Setup is covered in Set up tips payout integration.


On this page


Before you begin

Permission: You need organization administrator access to run and review tips payouts.

  • The Tips V2 accordion must be configured, authorized, and active, with employees and centers mapped. See Set up tips payout integration.
  • Employees who should not be paid through the provider must be mapped to Do not Process under Employee Mapping.

How a payout run works

  1. Guests leave tips at the point of sale. Tips are recorded on closed invoices per employee.
  2. After the configured delay, the daily tips job collects the day's tips for every mapped employee at every active center. With the mode set to CC, only credit card tips are collected.
  3. Zenoti posts the day's tips to the provider as a batch and stores the provider's reference and response per employee.
  4. The tips integration report shows the posted amounts, the status of each row, and any variance against the current tip totals in Zenoti.

Payout statuses

Status Meaning
Waiting for Process The payout row is queued in Zenoti and has not yet been submitted to the provider.
Initiated The payout request has been submitted and accepted by the provider.
Transfer Success The provider confirmed funds were moved to the employee's account.
Transfer Failed The provider rejected or failed to complete the payout.
Center Account Inactive The center's provider account is not active; no payouts can be initiated from this center.

These five values are the complete set of payout statuses across both providers.


Let the scheduled job run

  1. Navigate to Configuration > Integrations > Integration settings, expand Tips V2, and open Sync Schedule.
  2. Check the tips job row: SYNC DATE is the business date the next run processes, NEXT RUN TIME is when it runs, and STATUS is the result of the last run.
  3. Leave the job enabled. Change the schedule only when the payout timing changes; the sync date cannot be set earlier than the start date in Configuration.

Post a business day by hand

Use a manual post for the initial catch-up, or to re-post a day after fixing a mapping.

  1. Open Manual Sync on the Tips V2 accordion.
  2. On the Tips row, pick the business date in Choose a date.
  3. Select Post. Zenoti reports Tips : Success or Tips : Failed.

To refresh the employee list from the provider first, select Get on the Employees row.


Review the tips integration report

The tips integration report lists what was posted for a date range of up to seven days. Zenoti rejects longer ranges with The dates you have selected exceed 7 days.

View What it shows
Batch status One row per posted batch: Batch #, Batch Date, Center Code, Center Name, Status, Sync Date, Actual Sync Date, Reference, Response.
Employee level One row per employee in the batch: Employee Code, Employee Name, Cash Tip, Check Tip, Custom Tip, Prepaid Card Tip, CC Tip, Total Tip, Processed Tip, Status.
Invoice level One row per invoice: Invoice #, Guest Name, the tip columns, Status.
Tips variance Posted Tip against Current Tip with the Variance and any Exceptions, for tips that changed in Zenoti after they were posted.

Filter rows with Success and Failure, switch between Employee and Invoice detail, and select Resync to post a failed row again. Refresh reloads the grid.

For rows in Transfer Failed or Center Account Inactive, act on the cause (see Handle payout failures below).


Correct a posted day

  • Before the provider has paid. Select Resync on the failed or corrected row to post it again. Zenoti tracks the row's Reference so the provider does not receive a duplicate.
  • After the provider has paid. The funds are on the employee's card and cannot be recalled from Zenoti. The tips variance view shows the difference between what was posted and the current tip total; settle it with the provider, or adjust the next payout. Do not re-post the same day expecting to overwrite a successful transfer.

Administrators can also edit an employee row or a batch summary from the report (Edit Employee, Edit Summary): choose the field, enter the new value, and select Update. Zenoti requires the new value to differ from the old one.


Reverse or correct a payout (both states)

Before the provider processes (Waiting for Process or Initiated)

If a payout has not yet moved funds (still Waiting for Process and your provider allows pre-dispatch cancellation), you can cancel the row in Zenoti before it progresses. Confirm provider-specific cancellation rules with your provider account representative — neither provider guarantees cancellation once Initiated.

After the provider processes (Transfer Success)

Once Transfer Success is recorded, the funds have reached the employee's account and cannot be reversed from Zenoti. To correct:

  1. Work with the provider directly to reverse or recoup the funds, or record an adjustment in the next pay cycle.
  2. Record the correction in Zenoti so the tips ledger stays accurate (this typically means an offsetting adjustment, not a delete).
  3. If the correction is payroll-relevant, coordinate with your ADP administrator — see Sync payroll data with ADP.

Never "re-run" the same payout period expecting to overwrite a successful transfer — the result is double-payment.


MyZen Tips batches

MyZen Tips payouts are not posted from the Tips V2 accordion. Zenoti builds MyZen payout batches itself and tracks each batch with one of four batch statuses:

Batch status Meaning
Not initiated The batch exists but has not been sent.
In progress The batch has been sent and is pending with MyZen.
Successful MyZen confirmed the batch.
Failed MyZen rejected the batch.

Per-employee payout states in the MyZen tips reports include Initiated, Success, Reversal, Payout Stopped, Employee Opted Out, and Center Account Inactive. See Tips Provider: MyZen Tips.


Handle payout failures

Symptom Cause Resolution
Tips : Failed. on a manual post The provider rejected the batch, or the connection is not authorized. Read the Response column in the report; re-authorize from Configuration if the response is an authorization error, then Resync.
Verification Failed! You are not authorized for this action The signed-in user lacks the permission for the integration. Sign in as an organization administrator.
A center's employees are missing from the batch The center is not mapped or inactive in Locations. Map the center and post the day again.
An employee's tips are never posted The employee is unmapped or mapped to Do not Process. Update the employee mapping in Configuration.
Variance shows on a posted day Tips were adjusted in Zenoti after posting. Settle the difference with the provider or in the next payout.
Rows for a center show Center Account Inactive (MyZen Tips) The center's MyZen payout account is inactive. Reactivate the account with Zenoti's MyZen team before the next batch.
Row moves to Transfer Failed after Initiated. Wisely card not activated Ask the employee to complete card activation; re-run the payout for that employee.
Row moves to Transfer Failed. MyZen account not set up Ask the employee to complete MyZen onboarding; re-run for that employee.

Reconciliation

Source View Match key
Zenoti Tips integration report, batch status view for the period Batch # and Reference
Zenoti Tips integration report, employee level view Employee Code and Processed Tip
ADP Wisely The Wisely program report in the ADP Wisely admin portal Batch reference and employee ID

Reconcile after every payout cycle. A row that is posted in Zenoti but missing at the provider is usually a provider-side lag; a provider row that has no Zenoti batch points to a payment made outside Zenoti.

  • Row in Zenoti as Transfer Success but missing from provider report — usually a provider-report lag; check the next day.
  • Reconcile after every run to catch Transfer Failed and Center Account Inactive rows before the next cycle.

Was this article helpful?
Your feedback helps us improve our documentation.