The school group came, the field trip happened, and the invoice went out. Three reminders later the district says it only owes for 42 students, not the 60 you reserved, or it says nothing at all. Now there’s a group sales order in Altru with a balance due that isn’t going to be paid, and it keeps showing up on every outstanding-balance report you run.
No single button settles this. The right fix depends on why the money isn’t coming, and the wrong fix (deleting things, or editing posted revenue to make the number disappear) causes reconciliation problems that outlive the dispute. Here’s how to sort it out.
Start by naming the reason
Before touching the reservation, decide which of these you’re dealing with. Each one leads to a different record change.
- The group disputes the count or the items. They say fewer people came, a program was cancelled, or a lunch add-on never happened. This is a question of what was actually delivered.
- The group disputes the price. They were quoted a different rate, expected a school discount, or think the chaperone policy was different.
- The group agrees it owes but won’t or can’t pay. A small nonprofit folded, a tour operator went quiet, a teacher left and nobody at the school owns the invoice.
The first two are corrections. The third is bad debt. Treating a correction as a write-off overstates what you earned; treating bad debt as a correction hides a real loss from your finance team.
If the dispute is about what was delivered
Pull your own evidence first: the confirmation you sent, the final headcount you received (if any), and your arrival or scan records for that day. If your confirmation clearly stated the minimum or the change deadline, you have a policy to point to. If it didn’t, most organizations end up accepting the group’s number.
When you agree the original order was wrong, adjust the reservation itself so the items and quantities match what was delivered. That way the order, the revenue, and the attendance all tell the same story. How much you can edit after the visit date, and after payments or deposits have been applied, depends on your Altru setup and security rights. If an edit is blocked, check with whoever administers your group sales configuration, or ask Blackbaud support how your version handles changes to a reservation that already has payments on it.
If the dispute is about price
Find the quote or confirmation the group actually received. If staff promised a rate that never made it into the reservation, honor it and correct the pricing or apply the discount you’d normally use for that situation. Use an existing, named discount rather than inventing a one-off adjustment, so you can report on how often it happens.
If the group is simply asking for a better deal after the fact, that’s a business decision, not a data problem. Get a yes or no from someone with authority, then record it the same way.
If it’s genuinely uncollectible
This is where you need finance in the room, because the answer is partly an accounting policy question.
- Set a collection cutoff. For example: three documented contact attempts over 60 to 90 days, then escalate. Write it down so the decision isn’t made case by case.
- Agree on how it gets recorded. Altru supports write-offs in some revenue areas, but whether a group sales balance can be written off directly, and how that posts to your general ledger, depends on your configuration. Test it in a sandbox or confirm with Blackbaud support before doing it on a live order. Some organizations instead reduce the order with an approved adjustment and let the finance team book the loss separately.
- Leave a note on the reservation and the constituent record. Record what was owed, why it wasn’t collected, and who approved closing it. The next coordinator who books that school will want to know.
- Decide on future bookings. Many organizations require prepayment in full from any group with an unpaid history. A constituent attribute or note makes that visible at booking time.
What not to do
- Don’t delete or cancel the whole reservation to make the balance go away. The visit happened; you lose attendance history and may create revenue that no longer matches deposits.
- Don’t change prices on items to zero without a reason code. It works, but six months later nobody can tell a comp from a collection failure.
- Don’t leave it open indefinitely. Stale balances make your receivables report useless, and staff stop trusting it.
Making the next one less likely
Most unpaid group balances trace back to the booking, not the visit. A few habits help:
- Collect a deposit at booking, and state in the confirmation whether it’s refundable.
- Set a final-count deadline and a minimum billable count, and put both in writing on every confirmation.
- Collect the balance before or on the day of the visit when you can, rather than invoicing afterward.
- Capture an actual billing contact, not just the teacher or trip leader, so someone still owns the invoice if they leave.
- Run a regular query of group reservations with a balance due and a past visit date, so problems surface in weeks rather than at year-end.
Quick answers
Can I just refund the deposit and call it even?
Only if that’s actually the settlement you agreed to. Keep the deposit applied unless the group is owed it back; refunding money you earned to close out a dispute should be an explicit decision.
Should the front desk or group sales coordinator handle the write-off?
The coordinator can document the history and propose the outcome. The approval and the accounting entry should sit with whoever owns receivables, usually finance.
