A school cancels its field trip three days out. You refund part of the deposit, keep a cancellation fee, and six months later someone in finance asks why that group’s revenue looks the way it does. The refund is in Altru. The reason for it lives in somebody’s inbox, if it lives anywhere.
Group sales refunds tend to need more explanation than ordinary daily sales refunds: partial amounts, negotiated fees, weather cancellations, a chaperone count that changed at the last minute. So it’s reasonable to want a comment right on the refund. The short version: depending on how your Altru is set up, the refund step itself may not give you a free-text place to record why, so most teams capture the reason somewhere attached to the order or the group’s constituent record instead.
First, confirm what your refund screen actually offers
Before building a workaround, check what’s in front of you. Open a test group sales order in a sandbox (or a low-stakes real one, with your finance lead’s blessing) and walk through a refund end to end. Look for:
- Any reason or category list on the refund. If one exists, find out whether its values are configurable in your code tables, because a well-chosen list beats free text for reporting.
- Any comment, note, or reference field on the refund or the resulting payment record.
- What shows up on the revenue record and in the batch afterward, since that’s what finance will look at later.
If you can’t find a comment field and aren’t sure whether one should be there, ask Blackbaud support directly and mention your Altru version. Behavior can differ by release and by the security rights on your user role, so don’t assume a colleague’s screen matches yours.
Where to put the reason when the refund has no comment field
Option 1: a note on the group sales order
If your group sales orders allow notes or comments, this is the most natural home. The explanation sits next to the reservation, the deposit, and the refund, so anyone reopening the order sees the whole story. The downside is reporting: notes on an order are easy to read one at a time and harder to pull into a query across many orders.
Option 2: a note or interaction on the constituent record
Recording the refund reason on the group contact’s or organization’s constituent record works well when the reason matters for the relationship (“cancelled twice in one season,” “refund approved by the director as a goodwill gesture”). It’s visible to anyone who looks up that school or tour operator later. Use a consistent note type or interaction category so you can find these again with a query.
Option 3: a reason code your team agrees on
If you only need reporting, not narrative, a short controlled list does more than free text ever will. Something like:
- Group cancelled, full refund
- Group cancelled, fee retained
- Headcount reduced
- Weather or facility closure
- Pricing or entry error
Store the code wherever your setup allows it to be queried: a configurable refund reason if one exists, an attribute on the order or constituent, or the start of a note in a fixed format (for example, “REFUND: Headcount reduced, approved by J. Smith”). A fixed prefix sounds old-fashioned, but it makes notes searchable and keeps staff from writing three paragraphs.
Make it a habit, not a heroic effort
Whichever place you choose, the part that actually breaks down is consistency. A few things help:
- Write the rule into your group sales procedure. “Every group refund gets a reason note on the order before the batch is committed” is easy to follow and easy to check.
- Say who approved it. For partial refunds and waived fees, the approver’s name is often the detail finance wants most.
- Record the original terms you were honoring. If the refund follows your cancellation policy, say which clause (for example, “more than 14 days out, deposit returned”). That keeps refunds explainable when the policy changes next year.
- Review once a month. Build a query of group sales refunds for the period and spot-check that each one has a matching note. Gaps show up fast, and a single reminder usually fixes them.
Keep finance in the loop
Refunds touch batches and revenue, so talk to whoever reconciles group sales before you settle on a method. They may already record reasons on their side, in the batch or in a separate log, and you’d rather have one source of truth than two that disagree. Agree on which record holds the explanation and which one simply points to it.
Quick answers
Can I edit a refund later to add a comment?
Once a refund is posted and the batch is committed, treat the financial record as fixed. Add the explanation as a note on the order or constituent rather than trying to change the transaction.
Is free text or a reason list better?
Use both if you can: a short reason code for reporting, plus a sentence of context for the unusual cases. If you can only have one, pick the code.
