Knowledge Base guideHouse Points & Rewards / House Points administration · Updated 18 Nov 2026
Get support

Administrator: Investigate duplicate or incorrect reward requests

Overview

Order reconciliation should preserve the history of staff decisions and any changes to pupil point balances.

Who this is for: Administrators and authorised staff.

Before you start: Use an authorised administrator or rewards management account.

Step-by-step instructions

  1. Find the relevant pupil and the suspected duplicate requests.
  1. Compare item, cost, request time and current status.
  1. Check whether any reward-point deductions or physical collections have occurred.
  1. Follow the supported cancel, decline or adjustment workflow when approved by school policy.
  1. Verify the final point balance and fulfilment status, and record the reason for any correction.

Troubleshooting

  • Do not delete database rows directly to hide duplicates.
  • If an order was collected already, involve the designated staff member before reversing it.

If you still need help

Use the existing 'Still need help?' button below this article. Tell IT what feature you were using, what went wrong and which device or browser you used. Never submit passwords, sign-in codes, financial information or unnecessary pupil details.

Search terms

duplicate reward order, double deduction, reward correction, redemption audit

Staff review note: Confirm the named feature, exact on-screen controls and permissions against the current House Points site before publishing this guide.

Practical guidance for this task

Find the pupil’s request history and compare item, timestamp, status and points deducted. Determine whether there are two separate submissions or a display duplication before changing either request.

If something does not work as expected

Do not approve or refund both entries automatically. Preserve transaction references and escalate unclear cases to an authorised administrator for reconciliation.

Information to include in a support request

Provide the affected page or feature, approximate time, device and browser, the exact error if shown, and the checks already tried. Do not include passwords or unnecessary pupil information.

Still need help?

Send a request and include the steps you already tried.

Submit a ticket

Rate this article

How useful was this article?
Add a correction or suggestion (optional)
Do not include passwords, pupil details, or other private information.