Manage custom payouts to Zenoti Wallet
Custom payouts let an organization administrator pay an employee an ad-hoc amount β payroll adjustment, gas allowance, per diem, bonus, or expense reimbursement β directly to that employee's Zenoti Wallet. The payout is debited from the organization's Funding Account and credited to the employee's Wallet within a processor-dependent SLA, typically 2β3 business days. Custom payouts are distinct from scheduled tip payouts and from processor-to-merchant payouts.
Audience: Organization or center administrators with the Manage Custom Payouts permission who initiate and reconcile ad-hoc employee payouts.
On this page
- Before you begin
- Funding Account vs bank account β what gets debited
- Initiate a custom payout
- Per-payout amount limit
- Payment-type catalog
- Payout timeline and SLA
- Audit trail and history
- Failure modes
- Employee notification
- Multi-center organizations
- Bulk payouts
- Tax and payroll considerations
- Regional availability
- Troubleshooting
- If the problem persists
- Related articles
Before you begin
- Permission: Manage Custom Payouts (under Payments) β required to initiate, view, and reinitiate custom payouts. To grant it to a role, go to Configuration > Security > Security roles, open the role, and select Manage Custom Payouts under Payments on the Permissions tab. The permission is independent of the Manage Tips Payout permission.
- Tips payout active: The Custom Payouts surface only appears when scheduled tips payout is configured and active for the center. If you do not see Custom Payouts under Configuration > Payments > Employee payouts, complete tips-payout onboarding first (US-only at this time).
- Funding Account configured: The organization's Funding Account must be linked and provisioned. The Funding Account is set up during initial Zenoti Payments onboarding; if it is missing or in a "needs review" state, contact your Zenoti onboarding contact or Zenoti Support.
- Recipient employee: The employee must have an active Zenoti Wallet. If the employee profile does not have Wallet activated, the payout fails with an "invalid wallet" error and you will need to coordinate Wallet activation with the employee out-of-band.
- Per-payout amount limit: Each payout is capped (commonly $1,000 USD-equivalent β see Per-payout amount limit for the exact value as it applies to your organization).
Funding Account vs bank account β what gets debited
The legacy V1 article used both "bank account" and "funding account" interchangeably and that's confusing. They are not the same thing.
| Term | What it is | Used for |
|---|---|---|
| Funding Account | A Zenoti-Payments-managed pool linked to your organization at onboarding. It is the source for custom payouts. | Custom payouts (this article), some other Zenoti-managed disbursements. |
| Bank account (merchant deposit) | The bank account into which your payment processor (Stripe, Adyen, etc.) deposits settled card transactions. | Processor payouts to merchant β see View and manage payouts. |
When you initiate a custom payout, the Funding Account is debited (not your processor merchant deposit account). The Funding Account must have sufficient balance for the consolidated payout total β if it does not, the entire batch fails with an "insufficient funds" error and no Wallet is credited. Top up the Funding Account through the channel established during your Zenoti Payments onboarding (this is typically an ACH from your operating account; the exact mechanism is organization-specific).
Note: "Funding Account" is the term in Zenoti's payouts code (the API endpoint is
GetFundingAccount, the credential key isFundingAccount). When you see the V1 article say "bank account" in the context of custom payouts, read it as Funding Account.
Initiate a custom payout
- At the center scope, go to Configuration > Payments > Employee payouts > Custom payouts.
- Click New custom payout (or the equivalent "Add" button on your environment β the embedded payouts UI label may vary slightly).
- Add the recipient employee. Search by employee name. Add the employee from search results to the payout list. Repeat for additional recipients in the same batch.
- Select the payment type. Pick from the dropdown β Payroll Adjustment, Gas Allowance, Per Diem, Bonus, Expense Reimbursement (or your organization's catalog). See Payment-type catalog.
- Enter the amount. The amount must be at or below the per-payout limit (see Per-payout amount limit).
- Optional β add a note. A short reason or reference for audit purposes.
- Repeat steps 3β6 for additional recipients. The UI is one recipient at a time β see Bulk payouts for guidance on larger groups.
- Click Submit batch. The system validates each line and, on success, debits the Funding Account for the consolidated total and queues each line to credit the recipient Wallets.
The submitted batch appears in the audit log immediately. Each line transitions through Initiated β In Transit β Successful (or β Failed) over the SLA window.
Per-payout amount limit
The per-payout limit is set by Zenoti business policy and is enforced by the system at submission time.
The commonly-set value is $1,000 USD-equivalent per payout line β that is, per individual employee on a single batch entry. The limit is not cumulative per day or per pay period; you can submit multiple separate payouts to the same employee within the same day or pay period, each up to the per-payout cap.
Note: The exact limit value and whether it can be raised for your organization are configured by Zenoti at the policy level. If you need a per-payout limit higher than the default to cover a one-off larger payment (for example, a relocation reimbursement), contact Zenoti Support β do not try to circumvent by splitting into many small payouts, which complicates audit reconciliation and tax reporting.
If a payout line exceeds the limit, the system rejects that line at submission and tells you which line failed. You can split the line into two payouts that each fit under the limit, or contact Zenoti Support for a one-off limit increase.
Payment-type catalog
The payment types available in the dropdown are configured by Zenoti at the integration level. The standard catalog is:
| Type | Typical use |
|---|---|
| Payroll Adjustment | Correction to a previous payroll cycle (missed hours, incorrect rate, retroactive change). |
| Gas Allowance | Mileage reimbursement for staff who use a personal vehicle for work. |
| Per Diem | Daily allowance for travel or off-site work (training, conferences, regional pop-ups). |
| Bonus | Spot bonus, performance bonus, or one-off recognition payment. |
| Expense Reimbursement | Reimbursement for an expense the employee paid out of pocket. |
Custom organization-specific payment types are not configurable at the center level β the catalog is set globally. If your organization needs an additional category, contact Zenoti Support.
Payout timeline and SLA
Custom payouts typically credit the recipient employee's Zenoti Wallet within 2β3 business days of submission, processor-dependent. The exact time depends on:
- The processor handling the payout (Stripe Connect, Adyen, Wisely / ADP for US tips integration, etc.)
- Bank holidays in the recipient's region
- Configured payout-delay setting on the merchant account (
hoursToDelayTheTransactionβ set during onboarding; usually 0)
Note: "2β3 business days" is the typical range. The legacy V1 article variously said "2β3 working days" (overview) and "up to 2 business days" (step 6) β neither value is hard-coded in Zenoti. The system follows the processor's settlement schedule plus any configured payout delay. Communicate "typically 2β3 business days" to your employees, and treat any single payout that takes longer than 5 business days as a failure (see Troubleshooting).
Audit trail and history
Every custom payout is logged in the audit trail.
- Go to Configuration > Payments > Employee payouts > Custom payouts, then open the payout history.
- Filter by date range, recipient employee, payment type, or status.
The audit log shows:
| Column | What it shows |
|---|---|
| Date and time | When the payout was submitted. |
| Initiating administrator | The user who submitted the batch. |
| Recipient employee | Employee profile and name. |
| Payment type | One of the catalog types (above). |
| Amount | The payout amount in the center's currency. |
| Status | Initiated, In Transit, Successful, or Failed. |
| Funding Account debit reference | The Funding Account transaction reference. |
| Wallet credit reference | The recipient Wallet credit reference (populated when status = Successful). |
Failed payouts can be reinitiated from the audit log after you resolve the underlying cause. Successful payouts cannot be reversed from the administrator UI β if a payout was sent in error, contact the recipient employee out-of-band to return the funds, then submit a corrective payout (or work with Zenoti Support on a Wallet adjustment if the original recipient is unreachable).
Failure modes
If a payout fails, the audit log shows status Failed with an indicator of the cause. The common causes are:
| Cause | Symptom | Resolution |
|---|---|---|
| Insufficient funds in Funding Account | The entire batch fails immediately at submission; no Wallet is credited. | Top up the Funding Account through your organization's funding channel, then reinitiate the batch from the audit log. |
| Invalid or unconfigured employee Wallet | The single line for that employee fails; remaining lines proceed. | Coordinate with the employee to activate or re-configure their Zenoti Wallet, then reinitiate the affected line. |
| Payment-type validation rejection | The line is rejected at submission. | Re-select a valid payment type from the catalog. |
| Processor / bank connectivity | The line transitions Initiated β In Transit β Failed mid-window. | Wait one business day and reinitiate; if it fails again, capture diagnostics and contact Zenoti Support. |
| Per-payout limit exceeded | The line is rejected at submission. | Split the amount into multiple payouts under the limit, or contact Zenoti Support for a limit increase. See Per-payout amount limit. |
Employee notification
When a custom payout is initiated, the recipient employee is notified via the channel configured for them in their Zenoti Wallet profile. The standard triggers are:
- Payout initiated β sent at submission, before the funds settle. Lets the employee know money is in transit.
- Payout successful β sent when the Wallet credit posts. Confirms receipt.
- Payout failed β sent if the line fails after In Transit. Tells the employee the payout is being reattempted or requires manual follow-up.
Channel availability depends on the employee's Wallet onboarding (most commonly email and push; Text depending on the Wallet provider).
Multi-center organizations
Custom payouts operate at the center scope. An organization-level administrator who needs to pay employees across multiple centers must navigate to each center separately and submit a payout there.
If you have a recurring need to pay employees across many centers (for example, a corporate-wide bonus or holiday spot bonus), break the work into one batch per center. The audit log is per-center, so each center's payouts appear under that center's history.
Bulk payouts
The current Custom Payouts UI supports adding employees one at a time via search. To pay the same employee more than once in a single batch β for example, a combined gas allowance and expense reimbursement β use the repeat icon next to an employee's row to add a second payout line for them without re-searching.
Bulk import (CSV upload, file-based batch) is not implemented.
If you need to pay 30+ employees in one go (per-diem for a regional offsite, year-end spot bonuses for a department), allow extra time for the manual entry. For very large recurring scenarios, work with Zenoti Support to evaluate whether scheduled tips payouts or another mechanism is a better fit.
Invoice tip adjustments and failed debits
Tip adjustments from re-opened invoices: If an invoice is re-opened and the tip amount changes after a payout has already been initiated, the adjustment is applied to future positive payouts. Tips already deposited to the employee's external bank account are not reversed.
Note: The exact mechanics of tip adjustment processing are under engineering review. Communicate the general policy to employees: adjustments go forward, not back.
ACH reversal on failed debit: If a debit from the Funding Account fails, the reversal typically processes within a few business days. Once the reversal completes, you can top up the Funding Account and retry from the audit log using the Retry option in the Tips payout reconciliation report.
Tax and payroll considerations
Custom payouts are mechanism-only β Zenoti does not classify them for tax or payroll purposes. The recipient's tax treatment of a payroll adjustment, gas allowance, per diem, bonus, or expense reimbursement depends on your jurisdiction's payroll and tax rules.
Before using custom payouts for ongoing categories of compensation:
- Consult your payroll provider or tax advisor about whether each payment type is taxable income to the recipient and what reporting is required (W-2 inclusion in the US, T4 in Canada, regional equivalents elsewhere).
- Establish your own internal policy for which custom-payout categories require additional payroll-system entries to ensure the recipient's tax forms are accurate at year-end.
- Keep the audit log for tax and labor-compliance recordkeeping.
This is your organization's responsibility, not Zenoti's. Treat the audit log as the system of record for the disbursement, and your payroll/tax system as the system of record for tax treatment.
Regional availability
Custom payouts are available wherever Zenoti Wallet is supported. There is no explicit country gating in the Custom Payouts feature itself β availability depends on:
- Zenoti Wallet being live in your region
- Tips payout onboarding being available in your region (currently US-focused; expansion to other regions is in flight)
- Your processor and Funding Account being configured for your region
If you do not see the Custom Payouts surface and you believe Zenoti Wallet is supported for your organization, contact Zenoti Support.
Troubleshooting
- The Custom Payouts surface is not visible. Confirm: tips payout onboarding is complete and active for this center, the Manage Custom Payouts permission is granted to your role, and the tips-onboarding feature flag is enabled for your organization. If all three are true and the surface is still hidden, contact Zenoti Support.
- A submitted batch is sitting at "Initiated" longer than expected. "Initiated" means submitted but not yet picked up by the payout processor. The transition to "In Transit" happens within the next processor sweep (typically within a few hours; up to 24 hours during a bank holiday). If the line stays at "Initiated" for more than 1 business day, capture diagnostics and contact Zenoti Support.
- A payout line shows "Successful" but the employee says they haven't received it. Successful means the Wallet credit posted on the Zenoti side. If the employee can see the credit in their Wallet but cannot withdraw to their bank account, that's a Wallet-to-bank issue (not a Zenoti payouts issue) β direct the employee to the Wallet provider's support. If the employee cannot see the credit at all, capture the Wallet credit reference from the audit log and contact Zenoti Support.
- The Funding Account balance shown in onboarding doesn't match what I expect. The Funding Account is reconciled by Zenoti's funding operations; intra-day debits and credits can lag display. If you submitted a payout and the displayed balance hasn't decremented, give it 24 hours before raising a support ticket. For a balance that's persistently wrong, contact Zenoti Support with the Funding Account ID.
If the problem persists
If a custom payout has failed repeatedly or is stuck after you've worked through Troubleshooting:
- Capture diagnostic detail. Note the affected payout IDs from the audit log, the failure cause shown, the Funding Account debit reference, and the recipient employee's Wallet ID.
- Don't keep retrying blindly. Each retry that fails generates an audit-log entry β if the underlying cause hasn't changed, additional retries won't succeed and clutter the audit trail. Stop retrying once you have one failure with each plausible cause addressed.
- Contact Zenoti Support. Open a support ticket with the diagnostic detail from step 1. For org-wide impact (every payout failing across all centers), include your Funding Account ID and the rough start time so support can correlate with internal telemetry.