The four ways money goes back to a customer — and the two things that are not refunds.
Status at ebf7cf0: Gap — the backend and frontend accept only Overpaid and Checking Fee. Checking Fee is not on the approved list, and three of the four approved types are missing.
Money must be returned to the customer.
| Type | When |
|---|---|
| Deposit | A deposit is returned to the customer |
| Booking Fee | A booking fee is returned |
| Overpaid | The customer paid more than the balance |
| Compensation | Money paid to the customer as compensation |
| Not a refund | What it actually is |
|---|---|
| A forfeited booking fee | An outcome on the deposit payment, not money returned. Records reason and audit history on that payment. |
| Materials coming back from a technician | A stock return — component 18, Inventory. (Charlie, 16 September 2026.) |
Refund covers money back to the customer only.
Story. As Account, I want to request Deposit, Booking Fee, Overpaid or Compensation refunds, so that returned money has the correct business reason.
Acceptance. The request links source payment, amount, reason, requester and evidence.
Story. As Account, I want refund approval controlled by an on or off setting and threshold, so that governance can change without code.
Acceptance. The starting configuration is approval on with threshold zero.
Story. As the system, I must treat a forfeited booking fee as a payment outcome rather than a refund, so that money is not falsely returned.
Acceptance. Forfeiture records reason and audit history on the deposit payment.
Backend and frontend accept only Overpaid and Checking Fee. Deposit, Booking Fee, Compensation, the approval switch, the threshold and forfeiture handling remain gaps.
AppSheet brings 58 refund rows across.
New to these terms? See the Glossary.