Business owners, finance operators, and team leads
Configure tip sharing without losing the guest’s intent
Understand how Aplauso keeps a guest’s selected employee, department, or outlet as the canonical destination while allocating the distributable employee portion under that destination’s saved rule.
The practical path
- 1
Identify the exact destination that the guest selected: employee, department, or outlet.
- 2
Review that destination’s resolved rule and the eligible, active people or workforce roles in scope.
- 3
Use a draft and server-side simulation to validate the intended distribution before publishing.
- 4
Publish only a complete, reviewed policy with a recorded reason and effective timing.
- 5
Use allocation and policy history when investigating an amount; do not recreate a split from a guest-facing team list.
Common questions
Does a department tip become an employee tip after it is shared?
No. The department remains the canonical destination. Individual wallet entries represent the resulting employee allocations, not a rewritten guest destination.
Can a later sharing-rule edit change an earlier tip?
No. Policy history and allocation evidence preserve the rule used at allocation time. A new policy governs future allocation decisions only.
What happens when there is no custom rule?
The destination uses its documented default distribution. Do not assume that an outlet, department, or employee inherits a policy from another destination.
How is a shared tip calculated?
The policy first assigns 100 share units across named sharing groups. Each group then divides its units equally or by its approved role weights among eligible people at allocation time. The simulator shows the resulting units, exclusions, rounding rule, and any remainder rule before publication. The payment, allocation, and payout remain separate stages.
Which people are eligible?
Eligibility is evaluated from the exact destination, active workforce role assignments, scope, policy definition, and the allocation time. Inactive, out-of-scope, missing, or unassigned people must remain visible as exclusions rather than being silently included.
Can one setup work for every industry?
No. A hotel, resort, restaurant, caterer, tour operator, transport provider, landscaping crew, spa, wellness provider, venue, and field-service business can all use the same controlled mechanics, but the destination and eligible roles must reflect the real service moment and applicable obligations.
What can a Business report tell us about sharing?
Business reports show authorized, scoped tip activity and trend. They do not replace allocation evidence, payout records, policy history, or payroll reporting, and Business deliberately avoids exposing exact individual tip money.
Can Aria publish our whole sharing policy?
Aria can prepare only an initial, complete 100% shared-team rule for one department and always requires review and confirmation. For multiple buckets, weights, schedules, or an existing policy, use Property settings, Tip sharing, where the full simulation and audit record are available.
How do I investigate one shared tip without exposing earnings?
Start with the tip ID, property, environment, and service time. In Property settings, Tip sharing, open Explain allocation and enter the tip ID. The case file identifies the canonical destination, immutable policy version, eligible sharing groups, exclusions, deterministic rounding, and allocation-run state without showing peer earnings, payout status, or payroll data. Do not reconstruct a past split from today’s roster or current policy. Escalate a verified case with those safe identifiers; for a hotel or resort also include the service shift, for a tour or transport operator include the trip or crew, and for landscaping or field service include the job or crew.
Go deeper with the knowledge base
Use the detailed guide that matches your workflow, or ask the Aplauso assistant a specific question.