In many small businesses a refund is decided by whoever happens to read the message. One person agrees at once, another asks the owner, a third forgets. Customers notice the difference, and the books show it later as credit notes nobody can explain.
A single page of rules fixes most of this. It does not need a lawyer or new software. It needs four decisions written down.
Step 1: set limits and approvers
Decide who may approve what, by amount. A simple version:
- Up to a small amount (for example 50 EUR): the person handling the request decides alone.
- Medium amounts (for example up to 500 EUR): the team lead approves, in writing.
- Above that, or any case outside the rules: the owner or finance decides.
Pick amounts that fit your average order. The point is that most cases stay at the lowest level. Link the limits to your wider approval habits, as described in a one-page decision record.
Step 2: fix the deadlines
Write down three times:
- Request: how long after delivery the customer can ask, as your terms and local consumer law allow.
- Decision: how quickly you answer, for example within two working days.
- Payout: how quickly the money or credit arrives after approval, for example within seven days.
Check the legal minimums for your country and customer type before you set them. This article is a working guide, not legal advice.
Step 3: record it the same way every time
Every refund or credit note needs the same minimum record:
- the number of the original invoice or order;
- the reason, chosen from a short list (damaged, wrong item, not as described, late, goodwill);
- the amount, split into goods, shipping and tax;
- the approver and the date;
- the way of payment: back to the original method, or a credit note for the next order.
A credit note is a document that reduces an earlier invoice. A refund is the money going back. Many cases need both, so keep them linked. If your invoicing and customer data live in separate tools, see reconciling customers between CRM and invoicing.
Ask your accountant once which entry they want for each case, and write it on the page. After that nobody has to guess.
Step 4: answer the customer with one template
Keep a short reply and change only the facts:
Hello [name], thank you for your message about order [number]. We have approved a refund of [amount] to your original payment method. You should see it within [days] working days. If it does not arrive, reply to this message and we will check it the same day.
Prepare three variants: approved, partly approved with the reason, and declined with the reason and the next option. A clear, polite answer within the promised time prevents most repeat messages. For answering common questions before they arrive, see turning customer questions into web answers.
Step 5: review exceptions monthly
Once a month, take ten minutes and look at:
- how many refunds went above the first limit;
- which reasons repeat, because a repeat reason points to a product or delivery problem;
- cases decided against the rules, and why;
- whether any deadline was missed.
If the same exception appears three times, change the rule instead of approving it again.
Where it usually goes wrong
- The limits are too low, so everything goes to the owner and requests wait.
- Goodwill is not marked as such, so real quality problems hide in the numbers.
- The credit note has no link to the invoice, and the accountant reconstructs it later.
- The rules exist but nobody has seen them. Put the page where the team answers customers.
Summary
Write one page: approval limits by amount, three deadlines, a fixed record for every refund or credit note, one reply template, and a monthly look at exceptions. Most cases then close quickly, and the rest show you what to fix.
Sources
- Common practice for small businesses, offered as a practical guide. No client results or market figures are claimed in this article. Check consumer-law and tax rules for your country.
