A customer accepts $240 in store credit for a collection. The employee clicks twice because the first request appears slow. Later, a manager sees a $480 balance and deletes one entry. The balance is now correct, but the record no longer explains the duplicate, the correction, or who fixed it.
That is why store-credit controls need to cover the action, the approval, and the repair.
Treat each kind of credit change differently
Card-shop store credit usually enters or leaves through several paths:
- an accepted trade;
- a return handled under shop policy;
- a redemption at checkout;
- a promotional or courtesy grant;
- an imported opening balance;
- a correction or reversal.
Do not put every path behind one "adjust balance" permission. A counter employee who can redeem credit does not automatically need to create a $500 courtesy grant or rewrite an imported balance.
Use a role and threshold table
The exact amounts are shop policy, but the table should be explicit. Here is an example, not a universal recommendation:
| Action | Counter employee | Manager | Owner |
|---|---|---|---|
| View balance and ledger | Allowed | Allowed | Allowed |
| Redeem available credit | Allowed | Allowed | Allowed |
| Issue from accepted trade | Allowed after acceptance | Allowed | Allowed |
| Manual courtesy credit up to $25 | Needs approval | Allowed | Allowed |
| Manual credit above $25 | Blocked | Needs owner approval | Allowed |
| Correct or reverse an entry | Blocked | Allowed with reason | Allowed with reason |
| Change credit policy | Blocked | Blocked | Allowed |
If the shop chooses different limits by location, make the active location visible before the employee acts.
Connect trade credit to the accepted trade
For a trade, the credit entry should not be a freehand balance change.
Example accepted settlement:
| Field | Value |
|---|---|
| Trade | T-526 |
| Customer | Avery Brooks |
| Estimated resale value | $320.00 |
| Store-credit offer | $240.00 |
| Accepted at | Aug. 16, 3:42 p.m. |
| Accepted by | Morgan S. |
| Credit ledger entry | SC-8812, +$240.00 |
The trade and ledger entry should point to each other. Retrying the acceptance should return the same result, not add another $240.
Make manual reasons pass the "tomorrow" test
The next manager should understand the change without calling the employee.
Weak reason:
fixed customer
Useful reason:
Corrected duplicate +$240 issuance for accepted trade T-526. Original entry SC-8812 remains; reversal SC-8819 posted after confirming only one settlement was owed.
A reason should identify the business event, original entry, correction, and evidence. It should not include opinions about the customer.
Never repair history by editing the old number
If the original $240 entry was wrong, leave it visible and add the correcting entry.
For a full duplicate reversal:
| Ledger entry | Amount | Running effect |
|---|---|---|
| SC-8812 trade issuance | +$240.00 | +$240.00 |
| SC-8813 duplicate issuance | +$240.00 | +$480.00 |
| SC-8819 correction of SC-8813 | -$240.00 | +$240.00 |
The customer receives the correct balance and the shop keeps an honest explanation.
Check whether the credit was already spent
A reversal can create a negative balance if the customer used the duplicated credit before the error was found.
Suppose the customer received $480, redeemed $300, and now has $180. Reversing $240 would produce -$60.
Do not force the ledger negative unless the shop has a deliberate policy and supported workflow for that outcome. Stop, preserve the history, and escalate the case. A receivable or loss decision is different from pretending the duplicate never happened.
Review patterns, not only large amounts
A $200 correction is easy to notice. Ten $20 courtesy grants just under a threshold may matter more.
Review by:
- employee and location;
- action type;
- amount and round-dollar frequency;
- reason quality;
- time of day;
- repeated changes to one customer;
- corrections soon after issuance;
- activity just below approval limits.
Repeated corrections may reveal weak training or duplicate submissions, not misconduct. Start with the record.
Remove access when the job changes
When an employee moves from manager to part-time counter coverage, their old correction permission should not follow them automatically. When an employee changes locations, confirm both role and location scope.
Use individual accounts. "Front register" cannot explain which person issued or reversed credit.
Use this review record
For every sensitive change, retain:
- customer;
- location;
- original entry ID and amount;
- related trade, return, or import;
- new correction or reversal entry;
- actor;
- approver when required;
- factual reason;
- date and shop-local time;
- balance before and after;
- blocked attempt when the result would violate policy.
Store credit is easier for employees to use when the routine path is clear. It is easier for customers to trust when the exceptional path cannot erase its own history.