A guest calls three days after a refund and asks for proof it went through. The card statement doesn’t show it yet, their employer wants documentation for an expense report, or they simply want something in writing. Your staff processed the refund correctly in Altru, but now someone has to produce a receipt and get it into the guest’s inbox.
Purchases and refunds don’t always get the same receipt treatment. Plenty of organizations have a tidy confirmation email for a ticket sale and nothing at all for the money going back out. This guide covers what a refund receipt needs to say, the realistic ways to get one to a guest from Altru, and how to make it routine instead of a favor someone does by hand.
Start by confirming what your Altru setup does today
Before building a workaround, find out exactly what your current configuration produces when a refund is processed. Altru’s receipt options depend on where the sale happened (daily sales, advance sales, group sales, or a web form) and on how your organization has set up receipts and email. We don’t want to guess at a specific screen or setting, because it varies by setup and changes over time.
The fastest way to know for sure:
- Run a test refund in a sandbox or training environment using your own email address on a test constituent record. Note whether anything is printed, offered for email, or sent automatically.
- Repeat it for each sales channel you refund from. A refund on a front-desk sale and a refund on an online order may behave differently.
- Ask Blackbaud support whether an emailed refund receipt is available for your version and how it is turned on, if your test turns up nothing.
If a printable refund receipt exists in your workflow, staff can always fall back on saving it as a PDF and attaching it to a regular email. That works when a guest asks once in a while. It does not scale, and it depends on someone remembering to do it.
What a refund receipt should actually say
Whatever method you use, the guest should be able to answer their own questions from the email alone. Include:
- Refund amount and what it was for (the original tickets, membership, event registration, or donation).
- Refund date and the original purchase date, so it can be matched to a statement.
- How the money is coming back: to the original card (with the last four digits if you have them), as cash, or as a credit on account.
- A realistic timeline for card refunds to appear. Your processor sets this, not Altru, so use their language.
- What changed: tickets that are no longer valid, a membership that was canceled, or a donation that will not appear on a year-end tax summary.
- Your organization’s name, address, and a contact for questions.
The donation line matters more than it looks. If a gift is refunded, the donor should not later receive an acknowledgment or annual statement that still counts it. Check that your acknowledgment process excludes refunded revenue before you rely on it.
Making refund emails automatic with a query
The dependable approach is to treat refunds like any other event you communicate about: identify them with a query, then send from that list on a schedule.
1. Build a refund query
Create a query that returns refund transactions from a recent window, such as the last day. Pull the constituent’s name and email address, the refund amount and date, the original transaction details, and the payment method. Test it against refunds you processed recently and confirm every one shows up exactly once.
2. Decide who should not get the email
Exclude records with no email address, constituents who have opted out of email (a transactional receipt is generally different from marketing, but follow your organization’s policy), and internal or test records. Partial refunds and exchanges deserve a look too; an exchange that nets to zero probably shouldn’t produce a “your refund has been processed” message.
3. Send on a schedule
Once a day is usually enough; a refund receipt doesn’t need to arrive within minutes, but it should land before the guest starts calling. How you send depends on your tools: some organizations export the query results to their email platform, others use whatever communications tools they already run against Altru queries. Confirm in a sandbox that any send method you pick reads only the refund query, not a broader list. Keep a record of what was sent so staff can answer “did they get it?” without digging.
4. Keep the card processor’s notice in mind
Some payment processors send their own refund notification. If yours does, check what it says and make sure your email doesn’t contradict it on amounts or timing. Two emails that agree are fine. Two that disagree generate phone calls.
Practical habits for the desk
- Confirm the guest’s email address on the constituent record at the moment of refund. A refund is often the first time anyone notices it’s wrong.
- Add a short note to the record explaining the reason for the refund. It helps whoever answers the follow-up call.
- Give staff one sentence to say: “You’ll get an email receipt for this refund within a day.” Then make sure that’s true.
Where Social Good fits
If you’d rather not export a refund list and send it by hand every day, Email Designer sends automated, branded emails from Altru queries, so a refund query like the one above can drive a refund receipt email on a schedule without manual exports. Altru still holds the refund transaction; the email just reports it.
Quick answers
Can I just forward the original purchase confirmation?
Not as proof of a refund. It shows money coming in, not going out, and can confuse an expense reviewer. Send something that states the refund itself.
Should refunded donations get a separate message?
Usually yes. Donors care about the tax side, so state plainly that the gift has been refunded and will not be counted as a contribution.
