A customer says they should have $165 in store credit. The screen shows $110. The fastest response is not a $55 adjustment. It is a timeline that explains what the customer saw, what the ledger contains, and whether any entry was duplicated, delayed, corrected, or hidden from the screen they used.
Lock the scope before changing anything
Write down:
- customer identity;
- store and location;
- shop timezone;
- amount the customer expected;
- amount currently shown;
- last date both sides agree was correct;
- trade, purchase, or conversation that triggered the question.
The last-known-good point keeps the review from becoming an argument about the customer's entire history.
Rebuild the ledger from the anchor
Example last-known-good balance: $80.00 at Aug. 1 close.
| Date and shop time | Entry | Amount | Running balance |
|---|---|---|---|
| Aug. 3, 2:14 p.m. | Trade T-704 accepted | +$120.00 | $200.00 |
| Aug. 5, 6:20 p.m. | Purchase redemption | -$35.00 | $165.00 |
| Aug. 7, 10:03 a.m. | Manual correction | -$55.00 | $110.00 |
The disagreement is now attached to the Aug. 7 correction, not the whole balance.
Trace the correction to its source
Open the correction and look for:
- original entry it corrects;
- employee and approver;
- reason;
- related trade or sale;
- before and after balance;
- whether the customer had already spent the value;
- audit event and request time.
Suppose the reason says, "Removed duplicate trade credit," but only one +$120 trade issuance exists. The record does not support the correction.
If two +$120 entries exist and one is hidden by a filter, the correction may be valid even though the customer's recent-history screen made it look wrong.
Separate historical-as-shown from restated understanding
Do not rewrite what the shop showed on Aug. 5.
Maintain two explanations:
- Historical as shown: what entries and balance were visible at each time;
- Restated understanding: what the balance should be after confirmed mistakes are corrected.
If an Aug. 3 duplicate was discovered on Aug. 7, the Aug. 7 correction belongs on Aug. 7. Deleting the duplicate from Aug. 3 makes it harder to explain why employees and the customer saw a higher balance for four days.
Check the screen, filters, and location scope
Sometimes the ledger is correct and the visible view is incomplete.
Check whether the screen:
- shows only the active location;
- hides reversed or corrected entries;
- stops at the first page;
- uses UTC date boundaries instead of shop-local time;
- displays a cached balance;
- omits imported opening balances;
- labels trade issuance differently from manual credit.
Do not post a financial adjustment to repair a display problem.
Correct with a new entry
If the Aug. 7 -$55 correction was unsupported, post an approved +$55 correction that points to it.
The final ledger would show:
| Entry | Amount |
|---|---|
| Trade issuance | +$120.00 |
| Redemption | -$35.00 |
| Unsupported correction | -$55.00 |
| Correction of unsupported correction | +$55.00 |
Starting from $80, the balance returns to $165 without erasing any step.
Explain the result in plain language
A useful customer response is specific:
We started from the $80 balance both records showed on Aug. 1. Your Aug. 3 trade added $120 and your Aug. 5 purchase used $35, which produced $165. A $55 correction was posted on Aug. 7 without a matching duplicate entry. We restored that $55 with a new correction today. Your current balance is $165, and the full history remains visible.
Do not blame an employee before the record supports that conclusion.
Use this dispute worksheet
- Customer and location:
- Shop timezone:
- Expected and displayed balance:
- Last-known-good date and amount:
- Post-anchor entries in order:
- Related trade / sale / import IDs:
- Hidden, paginated, or filtered entries checked:
- Unsupported or duplicate entry:
- Historical-as-shown result:
- Restated current result:
- Correcting entry and approver:
- Customer explanation and contact time:
The right outcome is not merely a number both sides accept. It is a balance the shop can reproduce from the ledger the next time someone asks.