One service. Two staff. Start with the evidence.
A fictional shared service compares a confirmed 60/40 attribution with two incorrect shortcuts, and explains the one-earner-per-row product limit.
A $220.00 colour service involved Mia and Noah. That fact alone does not tell us how to allocate its $200.00 excluding-tax basis. This fictional investigation supplies explicit contribution evidence and two different commission rates. It shows why dividing the final commission in half answers a different question from assigning the sale correctly.
Worked fictional example · amounts in AUD
The useful part
With confirmed 60/40 basis allocation, Mia’s $120.00 at 40% yields $48.00 and Noah’s $80.00 at 45% yields $36.00. The illustrative total is $84.00; the current workspace does not create that split automatically.
Your working files
Download the allocation registerCSV · Fictional explanatory split with one original reference; not an automatic workspace import.The checkout record is incomplete for this job
SP510 records $220.00 gross and $20.00 supplied tax. The checkout staff column names Mia because she closed the sale. A separate fictional appointment contribution record assigns 60% of the service basis to Mia and 40% to Noah. The case assumes that allocation has been confirmed by the responsible reviewer. Without it, the checkout row supports a sale total but not a staff split.
This distinction matters before any percentage is entered. A payment-taker field, appointment attendance list or duration estimate may be useful evidence, but none automatically defines the commission allocation. Identify what the source actually says and what remains a decision.
Allocate the basis before applying different rates
The supplied $200.00 basis is allocated as $120.00 to Mia and $80.00 to Noah. Mia’s 40% rate produces $48.00; Noah’s 45% produces $36.00. The allocated bases add back to $200.00 and the commissions add to $84.00. Both checks matter: one verifies the sale was allocated once, and the other verifies the result.
| Staff | Confirmed share | Allocated basis | Supplied rate | Commission |
|---|---|---|---|---|
| Mia Chen | 60% | $120.00 | 40% | $48.00 |
| Noah Reed | 40% | $80.00 | 45% | $36.00 |
| Total | 100% | $200.00 | Different rates | $84.00 |
Two plausible shortcuts give different answers
Giving Mia the entire basis produces $80.00 and gives Noah nothing. Applying Noah’s 45% to the entire basis produces $90.00. Splitting either result equally produces $40.00/$40.00 or $45.00/$45.00. None matches the supplied 60/40 attribution with different staff rates.
A weighted rate of 42% happens to reproduce the $84.00 combined total here: 60% of 40% plus 40% of 45%. It still does not explain each person’s amount, and using that blended rate as a standing team rule would conceal the underlying allocation. A matching grand total is not enough to establish a correct staff statement.
A split needs a route back to one original sale
The downloadable allocation register keeps the common reference SP510 on both explanatory rows. It distinguishes the two staff contributions and shows the allocation basis, rates and outputs. It is an evidence worksheet, not a claim that the original sale contained two independent $220.00 charges.
If a source system can export genuine attributed line detail, inspect that report and its definitions. If a working copy must be prepared, keep the original file, record how each derived line was made and check that amounts are not duplicated. Never import both a full original amount and its allocated parts as contributing sales in the same calculation.
What the current workspace will and will not infer
The workspace expects a row with one earning person and one service or retail category. It applies that person’s flat legacy rate or the dated agreement selected for the row’s sale date. It does not read an appointment participation record, infer contribution percentages, split a row automatically or apply a different rate to each participant in one row.
A reviewer can use the public calculators to check the allocation arithmetic, but the tool does not create a validated split import or transfer it into the account. Keep this limitation visible when evaluating the product. A shared-service workflow needs reliable attributed source rows and a documented process, not a hidden assumption inside a percentage field.
A return would need the same allocation evidence
Suppose half the service value were later refunded and the confirmed treatment followed the original allocation proportionally. The total refund basis would be −$100.00, allocated −$60.00 to Mia and −$40.00 to Noah. At the original supplied rates, those adjustments would be −$24.00 and −$18.00, totalling −$42.00.
That is an additional fictional assumption, not an automatic rule. A refund connected to one person’s work, a changed arrangement or a corrected attribution could require another treatment. Link the adjustment to the original allocation evidence and ask the unresolved question before accepting the arithmetic.
The useful outcome is an explicit boundary
This investigation does not end with a new automatic split feature. It ends with a verified $84.00 example and a clear list of inputs needed to explain it: original sale, supplied tax, confirmed contribution shares, each person’s rate and a record connecting the allocation to SP510. We checked the $48.00 and $36.00 calculations against the current engine ratio function.
Use the allocation CSV as a comparison sheet. If your source already supplies equivalent attributed detail, test a small export before committing a full period. If it does not, the missing piece is evidence and process. A calculator can make the consequences visible while leaving the allocation decision with the person responsible for it.
Put it to work.
Inspect source rows, supplied rates and review decisions in the sample workspace.
Explore the sample close