Service Charge Distribution
Collected, retained, split and paid — inside the payroll run
The month's service charge arrives as one figure and has to leave as several hundred. HumanR holds the pool per site, applies your admin retention, splits the rest across eligible staff equally or by days actually worked, and distributes it through the payroll run — with every share reviewable before a single rufiyaa moves.
See it live — demo in minutes →Sound familiar?
A separate spreadsheet deciding what each person is owed
Arguments about who was eligible, and for how much of the month
Rounding that leaves the pool a few cents short of what was collected
No record of last month's split once this month's sheet overwrites it
What you get
A pool per site, per month
Record what was collected, in the currency it was collected in — resorts commonly collect in USD while paying packages in both USD and MVR.
Admin retention you set
A retention percentage snapshotted onto each pool, pre-filled from the site and defaulting to 1% — the Maldives cap — leaving the rest distributable.
Equal or earned
Split evenly across eligible staff, or weight each share by days actually present in the month, taken from attendance rather than assertion.
Eligibility that matches payroll
Eligible staff are the site's own payable employees — the same set the run pays, so the pool and the payslip never disagree about who works there.
Review before it pays
Every share is listed for review and HR can exclude someone for the month with a tick. The remaining shares are recomputed so they still sum exactly to the distributable amount.
Distributed by the run, corrected by the run
A pool is stamped with the run that paid it. Reopen or regenerate that run and the stamp clears — what was actually distributed is always recomputed from finalized lines, so no total can drift.
Reportable like everything else
Pools and individual shares are a reporting source, so last March's split is still answerable in full next March.
Straight from the product
Real screens from the demo company — the same system your login opens.
Frequently asked
Is the 99% / 1% split hard-coded?
No — the retention percentage is yours to set per site and is snapshotted onto each month's pool. It defaults to 1%, the Maldives cap, which leaves 99% distributable; operations under different rules set their own figure and keep the same machinery.
How do we handle someone who joined mid-month?
Choose the prorated basis and their share is weighted by the days they were actually present, drawn from attendance. On the equal basis they take a full share like everyone else — the choice is yours, per pool.
What if we need to exclude someone this month?
Untick them in the share list. Nothing changes on their employee record, and the other shares are recalculated so the pool still distributes in full.
What happens if we have to reopen a payroll run that distributed a pool?
The pool returns to undistributed and can go out again with the corrected run. The 'already paid' figure is never a stored counter — it is always recomputed from finalized payroll lines, so reopening cannot leave it double-counted.
See it with your own data-shaped data
Request a demo and we'll email you a personal login to a fully loaded demo company — explore real screens with realistic data within minutes.
No credit card. No sales call required. A real login, emailed to you.