Deduct Moola from a Team Member

---

At a glance

Deducting Moola removes an amount from a team member's balance. The most common reason is correcting an over-award or an award given to the wrong team member. A note on the deduction preserves the context so the transaction log stays auditable. The team member is notified that Moola was charged and why.

Before you start

1. You need a role with the Deduct Moola permission. By default, this is Manager and above. If you cannot find the Deduct action, your role may not have this permission; see Request a Permission Change.
2. Identify the team member and the specific amount. A specific number with a clear reason reads better in the transaction log than a rough estimate.
3. Prepare a short reason for the note. "Correcting an over-award from earlier today" is better than no note at all; "reward was given in error, re-awarded to the correct team member" is ideal.
4. Estimated time: under one minute.

Steps

1. Select Team from the left navigation menu and click the team member's name. Alternatively, long-press or click their name in the Shifts-screen lineup or layout, then select Profile.
2. Click the Moola tab in their profile's tab bar.
3. Click the Deduct button.
4. Enter the Moola amount and a note explaining the reason. [VERIFY: exact label for the deduct confirm button.]
5. Confirm the deduction. The team member's balance drops by the amount immediately.
6. The team member receives a Charged Moola notification that includes the reason you entered.
7. You should now see the deduction recorded in the Moola Transaction Log (Team, then Moola Transaction Log in the top right) with your name as the acting leader, the amount, and the timestamp.

Video

Video coming soon.

Common gotchas

I cannot find the Deduct button.

The Deduct button sits on the Moola tab of the team member's profile, alongside Reward and Transfer. If it is missing entirely, your role may not have the Deduct Moola permission. Manager and above typically do. For a permission adjustment, see Request a Permission Change.

I deducted the wrong amount or the wrong team member.

Deductions do not have a built-in undo. The fix is a compensating award on the same profile, with a note explaining the correction. Open the Moola tab, click Reward, enter the amount, and write a note like "Reversing incorrect deduction from earlier, balance corrected." Both transactions stay in the log so the record is honest.

The team member says the deduction looks wrong or unfair.

Deductions are visible to the team member in their Moola history, with the note you wrote. If the note does not explain the reason clearly, the team member is more likely to raise it as a concern. Keep notes specific and neutral in tone.

I wanted to deduct more than the team member's current balance.

[VERIFY: whether the product allows a deduction that would push the team member's balance negative, or whether the deduction caps at the current balance. The source article does not specify the behavior at zero.] The cleanest workflow is to deduct up to the current balance, note the situation, and address the remainder through a direct conversation with the team member and their manager.

The team member's balance did not change after I pressed Deduct.

Refresh the page. If the balance still looks unchanged, check the Moola Transaction Log; if the deduction is recorded there, the balance display is cached and will update on next page load. If there is no record in the transaction log, the deduction did not save; try again, and if it still does not stick, submit a support ticket.

Related articles

1. Award Moola to a Team Member (How-To, Core)
2. Understand Moola (Reference, Core)
3. Request a Permission Change (How-To, Core)
4. Approve or Reject a Moola Redemption (How-To, bonus)

Still stuck

If the Deduct button is missing despite confirmed permission, the balance does not update after a deduction, or the transaction log shows the deduction without the balance reflecting it, submit a support ticket and include:

1. Your store number.
2. The team member's name.
3. The amount you tried to deduct.
4. The time of the attempted deduction.
5. A screenshot of the Moola Transaction Log and the team member's profile Moola tab.
6. What you expected to happen versus what happened.

Support typically responds within one business day.

---

Pre-publish checklist status

1 86d4f9e4-b543-47d8-a2e3-47c80d02c338 complete All seven sections filled.

2 9daef284-9566-4677-8df6-99e04bde31cb complete Final step is a confirmation step.

3 11ed4b49-2aaa-4107-a4e2-95809803dccd complete No em dashes.

4 b9cc1e6b-91c7-4f71-8064-c57a503f4bb4 complete No hedge words.

5 d08697b1-2998-4427-ae72-7a6f6b583098 complete Role references are permission-based, not role-name-based.

6 2ca8f62c-db52-4089-b620-a2ae3cf8b685 complete Step count within the seven-step guidance.

7 afa1574b-fc5c-4ff0-8b53-c9900db2cd5c complete Navigation paths verified against existing KB source material.

8 84bb9a20-7ca9-452c-aae4-0371eacf055a complete No real identifying data in body or metadata.

9 3b7428b4-c670-474b-923d-953157cf6bc3 incomplete UI verified against Production before publishing.

10 079befd7-ed07-4271-80bd-3757e44af9dc incomplete Screenshots to be inserted at decision points (Step 2: Moola tab with Deduct button, Step 4: deduct form with amount and note field).

11 999f9fb0-7243-463b-aa4a-55e8d076e846 incomplete Related article links activated once those articles exist.

12 07b8c284-3084-4b9c-9d2a-b4e464dbb111 incomplete VERIFY blocks resolved (confirm button label, negative-balance behavior).

13 0f3fb237-6c4f-4846-ac24-924015f91934 incomplete Primary search term tested in HubSpot KB search (likely "deduct moola," "take moola back," "remove moola," "fix moola mistake").

14 2d2771ee-5e72-4af0-944d-c3b3e3fdc087 incomplete Reviewed by Jared.

15 7cad2bd2-beb2-41a5-a159-88e297865349 incomplete Reviewed by Kevin.

Source

Source of content is the existing kb.oneclickapp.com Moola article (uploaded Turn 21) Deducting section, which names Manager-and-above as the default permission, the profile-based entry path, and the Charged Moola notification behavior. Gotchas are inferred from the symmetric relationship to Award (the inverse workflow's ticket patterns apply in reverse) plus the zero-balance edge case flagged during this draft.