Payroll
Payroll tracks what each person earns — commission by skill, sliding scales, tips, forfeited deposit shares — and settles it: payouts on whatever schedule you keep, pay periods you close when you’re ready, and a pay stub for every period. It’s built for contractor (1099) pay. REV23 records what you paid and preps the numbers for 1099 season; it does not calculate tax withholding, produce W-2s, or file anything — studios running W-2 employees keep their payroll provider for that.
Turning it on
Section titled “Turning it on”Enable Payroll for the Cloud at Settings → Cloud → Features, then opt into it per studio at Settings → Cloud → Studios. Set the studio’s time zone first — pay period boundaries are read in the studio’s local time, and changing the time zone later never moves boundaries already set.
Enabling payroll for a studio opens its first pay period, and the start you pick is permanent — it anchors the studio’s payroll history:
- Now (recommended) — the clean start, right if the team is already paid up through today by other means. Earlier sales stay on the books for reports but never appear on a pay stub.
- Earlier date — sales between that date and now land on the first stub to settle. Use it only when there’s unsettled commission that should flow through REV23 payroll — the dollar total that would carry in is shown before you commit, so check it against your own records first.
Turning payroll off — for a studio or the whole feature — hides it and preserves everything; turn it back on and the periods are still there, original anchor included — a live ledger can’t be re-anchored. One consequence to know: closing a period while a studio’s payroll is off doesn’t open a new one, so the next period starts when payroll comes back on.
Running solo? Payroll becomes earnings tracking by period — most one-person shops skip it and read the Earnings report instead. You keep 100% either way.
How the pieces fit
Section titled “How the pieces fit”Earnings post themselves. Every completed sale and ended session writes commission and tip lines to the earnings ledger — with or without payroll enabled, which is why the Earnings report works for every studio. What payroll adds is settlement: a running balance per person (earned minus paid), payouts recorded against it, and pay periods that reconcile everything into frozen stubs.
Paying never waits on a period. Hand out the day’s cash, record a stack of checks, settle one person — any time. Closing a period is the bookkeeping act: it locks the window, generates stubs, and starts the next one.
- Pay periods — opening, closing, backdating, and what “closed” locks
- Earnings & commissions — where the numbers come from and how rates resolve
- Paying your team — cash payouts, recording payments, deductions, corrections
- Compensation — each person’s rates, per-studio overrides, tax info
- My Pay — what each team member sees about their own pay
Permissions
Section titled “Permissions”Running payroll — opening and closing periods, recording payouts, deductions, and adjustments — is a single permission, Payroll → Manage, deliberately all-or-nothing: anyone trusted with part of the job needs all of it. The built-in Payroll role packages it for a bookkeeper: run payroll, see everyone’s rates and amounts, trace an earning back to its sale — but not edit anyone’s rates, which stays with the owner.
Seeing pay splits two ways, and the split matters. Everyone with a skill automatically sees their own rates and earnings through My Pay. Seeing everyone’s numbers takes the separate grants Compensation → View (Everyone) and Earnings → View (Everyone) — a manager who should watch the whole board needs them explicitly. See Roles & Permissions.
Webhooks
Section titled “Webhooks”Payroll supports the following webhook events:
| Event | Description |
|---|---|
| pay_period.closed | A pay period was closed. |
| payout.processed | A payout was recorded. |
| earning.created | An earning was recorded. |
| earning.reversed | An earning was reversed. |