A guest calls to ask whether their refund went through. You pull up their constituent record, look at recent revenue, and see two lines that both say “Order.” One is the purchase. The other is the refund. Nothing on that summary view says which is which, and with a guest on the phone you’re now squinting at amounts and dates to work it out.
This is a labeling problem more than a data problem. The refund is recorded correctly; it just isn’t described clearly where staff look first. Below is why that happens, how to read the record accurately, and how to keep it from tripping up your team.
Why a refund shows up labeled as an order
In Altru, ticket and merchandise refunds are generally handled against the original sale rather than entered as a free-standing payment. Because the refund is tied back to the order it reverses, the recent revenue summary on the constituent record appears to describe it by where it came from (a sales order) rather than by what it did (money going back out). The result is a refund that carries the same “Order” label as the purchase.
We can’t promise exactly how every configuration of Altru renders this, and it may look different for daily sales, advance sales, and web purchases. If you want certainty for your own setup, process a small test sale and refund in a sandbox (or on a test constituent you clean up afterward) and look at how both lines appear on the record. A quick test like that will tell you more than any general explanation can.
How to tell them apart today
Staff need a reliable way to read what’s actually there:
- Look at the amount. Check whether your refund lines display as negative or as a separate reversal amount. Once you know how your system shows it, that’s usually the fastest tell.
- Open the transaction. Opening the line from the constituent record should give you more detail than the summary does. Confirm in your own system what that detail view shows for a refund, and whether it points back to the original sale.
- Match dates. A refund will usually sit on a later date than the purchase it reverses, with a matching or partial amount.
- Check the full revenue history. The recent revenue panel is a summary. The constituent’s complete revenue list generally carries more columns and more context than the snapshot at the top of the record.
Write whichever of these works best for your setup on a one-page desk reference. Front desk and membership staff answering “did my refund go through?” shouldn’t have to rediscover it each time.
Make refunds easier to spot
Build a refund query
A revenue or sales query filtered to refund transactions, with the constituent name, date, amount, and the original order, gives you a clean list you can check against. Saved as a shared query, it lets anyone confirm a refund without reading the constituent summary at all. It’s also useful at month end when finance asks what was refunded and why.
Consider a smart field
If you use smart fields for constituent-level totals, a field that sums refunds for each constituent can make the number visible on the record. Whether a smart field captures refunds the way you want depends on how your revenue is set up, so test it against a few constituents you already know the answer for before relying on it.
Add a note when the refund is unusual
For refunds that need explaining (a weather closure, a duplicate charge, a goodwill gesture), a short constituent note gives the next staff member the “why” that no revenue line will. Keep the format consistent so notes are easy to scan.
Why it matters beyond the front desk
Mislabeled lines don’t just slow down phone calls. They can mislead anyone using the constituent record to judge a relationship: a development officer reviewing giving and visit history might read two “orders” as two visits. A member services coordinator might assume a family attended twice when they actually cancelled. If people make decisions from the recent revenue summary, a quick note in your internal training about how refunds appear there is worth the time.
It’s also worth reporting the behavior to Blackbaud support if it’s causing real confusion. They can confirm whether what you’re seeing is expected for your configuration and whether anything in your setup changes how refunds are labeled.
Quick answers
Does the “Order” label mean the refund didn’t post?
No. The label describes where the transaction came from, not whether it succeeded. Open the line or run your refund query to confirm it was processed.
Will this throw off revenue totals?
It shouldn’t. The confusion is in how the line is described on the constituent summary, not in the underlying amounts. If your totals or reports actually look wrong, treat that as a separate problem and check it with your finance team or Blackbaud support.
