Immediate costs and rewards loom larger than future ones.
More quotes09.12: a billing error is confirmed.
Amount: £186.
Refund status: discretionary under the current policy.
09.20: someone points out that the customer has yet to notice.
09.24: refunding now will worsen the weekly number.
09.31: a draft explanation says the charge resulted from “account configuration”. The configuration belonged to the company.
09.46: the error is assigned for review.
10.05: the reviewer asks whether any term allowed the charge.
10.18: no term can be found.
10.22: finance asks whether the amount could remain as credit.
10.29: the customer has no scheduled future purchase.
10.34: refund approved.
10.41: payment initiated.
11.03: the customer receives a message naming the error, amount and expected arrival date.
11.17: reply: “Thanks.”
11.43: finance confirms the refund will settle in three days.
14.08: the configuration fault is traced to a default introduced during the previous release.
15.20: the default is changed for new accounts. Existing accounts require a separate query.
Next month, the customer buys from a cheaper competitor. There is no testimonial, loyalty story or sudden reward for institutional virtue.
The weekly number closes £186 lower.
The account history now contains the charge, correction, reason and approving person. When a similar configuration error appears two weeks later, support finds the earlier entry.
Three affected accounts are identified before the customers report anything. Finance issues the corrections in one batch.
Two customers reply. One stays silent. A fourth account has already closed and needs a different payment route.
The month-end review lists four refunds and one cause. It closes at 16.30.