A school group books 40 student tickets. A week out, five students drop. You refund those five. Then on the morning of the visit, three more don’t show, and the teacher asks for money back on those too. You open the same order, go to refund the same ticket line again, and Altru may not let you.
This catches box office and finance staff off guard because the first refund worked fine. The second one is the problem. Below is what’s going on, the workarounds admins actually use, and how to set up your process so a second refund doesn’t become a puzzle every time.
What’s actually happening
In practice, Altru tends to treat a refund as something that happens to an order line once. After a partial refund has been processed against an item, many organizations find that the same line can’t be refunded a second time through the normal refund workflow, even when there’s still paid quantity or money left on it.
We’d be careful about stating this as an absolute rule, because behavior can depend on the sales channel (daily sales, advance sales, group sales, or web), how the item was paid, and whether the original payment has been deposited or the revenue has already posted. If you’re unsure how your version handles it, test it: in a sandbox or training environment, sell a multi-quantity ticket, refund part of it, then try to refund more. That ten-minute test tells you more than any forum thread, and Blackbaud support can confirm the expected behavior for your setup.
Workarounds that hold up
1. Refund the full line and re-sell what the guest keeps
This is the cleanest option when the second refund comes up. Refund everything left on the item, then sell the quantity the guest is keeping as a new transaction. In the school example: refund the remaining 35 tickets, then re-sell 32.
The downside is extra steps and a second payment to collect. If the original card was charged, the guest sees a refund and a new charge, so tell them before you do it. Make sure the new sale uses the same price type and any discount from the original, or your revenue won’t match what was agreed.
2. Refund outside the item, then document it
Some organizations issue the money back through their payment processor directly and then record the adjustment in Altru so revenue stays accurate. This keeps the guest experience simple (one refund, no new charge) but it shifts the burden to finance. Only do this if your finance team has signed off on the method and knows how it should appear in batches and reports. Otherwise your deposits and Altru revenue will drift apart and someone will spend month-end chasing it.
3. Issue credit instead of cash
For the second refund on a group visit, a credit toward a future visit is often acceptable to the customer and avoids touching the original order again. How you track that credit (a voucher or gift certificate if you already use them, a note on the constituent record, a balance carried on a future group sales booking) depends on what your organization already uses. Pick one method and stick to it, so credits don’t get lost.
4. Hold the first refund until the numbers are final
The best fix is avoiding the second refund in the first place. For group sales especially, set a policy that changes in headcount are collected and refunded once, at a fixed point: after the visit, or at a cutoff date. Partial changes before then get noted on the booking but not refunded yet. One refund per order, processed when the count is final, sidesteps the limitation entirely.
Which workaround to use when
- Walk-up or daily sales, guest is standing in front of you: refund the full line and re-sell. It’s fast and everything stays in Altru.
- Group sales with a balance or deposit: hold refunds until the final headcount, or adjust the booking before the remaining balance is paid if your process allows it.
- Web orders paid by card weeks ago: talk to finance before you do anything. Refunds on older, deposited payments are where processor-side refunds and Altru records most often fall out of sync.
- Guest is fine with credit: issue credit and leave the original order alone.
Keep the paper trail clean
Whatever route you take, a second refund done by workaround looks odd later. A few habits help:
- Add a note on the order or constituent record explaining what happened: “Refunded remaining 35, re-sold 32, net 3 refunded per teacher request.” Anyone who opens that record later can follow what happened without asking you.
- Reconcile against the processor. At least weekly, compare refunds in your payment processor with refunds in Altru. A query on refund transactions for the period is enough to spot mismatches early.
- Limit who can do workaround refunds. Front desk staff can process a straightforward first refund. Anything involving a re-sell or processor-side refund should go to a supervisor or the box office lead, so it’s done the same way every time.
- Write it into your refund policy. If guests know refunds are processed once, at a set time, you’ll get fewer second requests to begin with.
Quick answers
Can I just edit the original refund to a larger amount?
Generally, no. Once a refund has been processed and especially once it’s in a posted batch, treat it as fixed. Make any further change as a new transaction rather than editing history.
Does refunding the full line and re-selling mess up attendance counts?
It can, if tickets were already scanned or redeemed. Check whether the re-sold tickets need to be marked as used, and run your attendance report afterward to confirm the totals look right.
Is this a configuration setting I can change?
We’re not aware of a setting that turns on repeated partial refunds on one line. If you suspect there is one for your version, Blackbaud support is the right place to ask.
