Revenue Share
Pooled gratuities and service charges, split among eligible staff by points and hours, reviewed and approved into payroll.
How a distribution works
A revenue share takes a pool — the month's service charges, a gratuity fund — and divides it among staff who qualify. The split is points-and-hours based: you assign points to groups (departments, divisions, levels, statuses, or titles) and optionally to individuals, eligibility rules filter out people below your minimum hours, and the pool distributes proportionally across what remains. Approval pushes each person's share into payroll as a one-time allowance for the pay period.
Calculations decide how a share behaves
A share runs on a Calculation, and the calculation is what decides which fields you get. Two capabilities matter most:
| Capability | What changes |
|---|---|
| An amount per day | Instead of typing one pool total, you enter a figure for each day and the share total is whatever the days add up to. The Amount field is replaced by a note saying so, because a missing field would otherwise read as a bug. |
| Day-level points | Points can be entered per person per day rather than once for the period — useful where someone's weighting genuinely varies day to day. This is opt-in per calculation; where it isn't enabled you'll be told "this calculation does not allow day-level point entry". |
Some calculations also offer a group view as well as the per-person grid, so you can check the split at the level you actually manage.
Creating one
- Create Revenue Share: enter the Amount to distribute (or the per-day amounts, if that's the calculation), a description, and pick the Pay Frequency and Pay Period it lands in.
- Choose the Filter Type (how staff are grouped) and the Allowance the payout flows through — only allowances named with a "Revenue Share" prefix appear, which keeps these payouts identifiable on payslips and reports.
- Assign points per group, and per individual where someone's share should differ from their group's. Add people pulls in anyone the filters missed.
- Check Who this covers before going further — it's the coverage panel that answers "is this the population I meant?"
- Submit, then work through the share page.
Entering an amount per day
Save as: admin-guide__gratuity__index__shot3.png
Reviewing the split
The share page is where the maths faces scrutiny. The grid shows each person's points, Weighted hours, the rate Per weighted hour, and their amount, with Grouping and Change view to look at it per person or per group. Alongside it:
| Figure | What it tells you |
|---|---|
| In share / Left out | Who qualified and who didn't — the exceptions list says why, typically that someone hasn't worked the minimum hours. |
| Amount taken / Distributed / Left over | What you put in, what actually went out, and any remainder. A stubborn Left over is the first thing to explain before approving. |
| Highest / Lowest / Average | The spread, so an outlier is obvious without reading every row. |
On a per-day calculation, a day nobody worked is reported as such — "Not spread, nobody worked those days" — rather than silently vanishing into the remainder.
Recalculate after any edit. It recalculates into an unsaved preview first, so you can see the effect before committing; Save amounts keeps it and Discard throws it away. If you try to leave with unsaved changes you'll be warned.
The share page — distribution grid and stat tiles
Save as: admin-guide__gratuity__index__shot2.png
Points carried over from the last share
Most teams' points barely change period to period, so a new share pulls the points forward from the previous one rather than making you retype them. A banner names the share they came from, and clears as soon as you write any points of your own.
It matches on payroll group, grouping and calculation, and only looks at earlier periods. Group points always carry; per-person points carry only where they are proportions — a calculation that works in money units, or one where daily amounts are edited by hand, is left alone, because copying those forward would either move last period's payouts or put the day matrix out of step.
Importing points and amounts
For anything beyond a handful of people, import rather than type. Download points template gives you the right shape; Import brings points back in, and Import amounts does the same for per-day figures. You can drop a file straight onto the dialog.
The preview accounts for every row before anything is applied, and refuses duplicate rows rather than letting the last one silently win. Each import session applies once — re-submitting the same one won't double up — and a failed import reports as failed rather than looking like it worked.
An import preview that refuses a duplicate
Save as: admin-guide__gratuity__index__shot4.png
Approving and reversing
Approve creates the payroll allowances. Return to draft reopens a submitted share; Recall reverses an approved one, as long as the pay run hasn't been approved. Whether a share can move at all is decided on the server, and when it can't, the reason is stated plainly rather than leaving you to guess — commonly that the linked allowance or the covering pay run has already been locked.
Salaried staff are supported as well as hourly. The eligibility thresholds — Minimum Daily Hours and Minimum Hours Worked — live in the module's Settings.
Where a share was calculated per day, the payslip shows the daily breakdown rather than a single lump, and that breakdown carries through to the print view.
A revenue share end to end (6–7 min)
Save as: admin-guide__gratuity__index__vid1.mp4
Revenue Share requires its module license plus the payroll and time & attendance modules (hours drive eligibility), and is restricted to payroll and HR administrators.