A teacher books a field trip for 60 fourth graders. Three weeks later the check arrives, but it comes from the school district’s accounts payable office, or the PTA, or a parent who agreed to cover the balance. The reservation sits under the teacher’s name in Altru. Now someone at the sales desk has to decide whose payment this is, and where it should show up.
This comes up constantly with group sales: school districts, scout councils, tour operators, corporate outings, and family reunions where one person books and another pays. Below is how to think about it, what to test in your own Altru database, and a few setups that keep both the booking and the money traceable.
The core problem
An Altru group sales reservation is built around one patron (plus a contact, for organizations). Payments taken against the reservation are generally tied to that reservation and its patron. Whether your version and configuration let you name a different constituent as the payer on a reservation payment is something to confirm directly, not assume. Behavior has shifted over time, and security settings can hide options from some users.
To find out what yours does:
- Take a test payment on a reservation in a sandbox or training database (not production) and look at which constituent the revenue lands on afterward.
- Check the payer’s constituent record and the patron’s record. Note where the payment appears in each one’s revenue history, if at all.
- If you can’t tell, ask Blackbaud support specifically: “Can a group sales reservation payment be recorded with a payer other than the reservation patron, and how does that appear on each record?”
If the answer is no, or “only partially,” the options below will still get you a clean audit trail.
Option 1: Make the paying organization the patron
Usually the cleanest fix is to set up the reservation so it’s in the payer’s name from the beginning. When a school district, company, or tour operator is paying, book the reservation to the organization and list the teacher or coordinator as the contact.
- Revenue lands on the organization, which is who you’ll invoice and who you’ll chase for late payments.
- The coordinator stays reachable for logistics, arrival times, and chaperone counts.
- Over time you build a real picture of which districts and companies send groups, which helps when you plan school outreach or corporate sales.
The catch is that you have to know who’s paying at booking time. Add a “Who is paying for this visit?” question to your group booking intake, whether that’s a phone script, an inquiry form, or an email template. A lot of these headaches come from never asking.
Option 2: Change the patron after the fact
If the reservation is already booked to the wrong constituent and hasn’t been paid yet, see whether your users can edit the patron on the reservation before payment is applied. Test this in a sandbox first. Changing the patron after payments or deposits exist may be restricted, or may not move revenue that’s already posted. Don’t count on it for reservations that already have money on them.
Option 3: Keep the patron, document the payer
Sometimes the reservation really does belong to the person who booked it. A parent might cover a scout troop’s balance, for example, with no organization involved. In those cases you can take the payment on the reservation as usual and make the real payer easy to find:
- Make sure the payer has a constituent record. Search before you create one, since group payers are a common source of duplicates.
- Add a relationship between the payer and the reservation patron (or the patron’s organization), so anyone looking at either record can see the connection.
- Record the payer on the payment or reservation in whatever note or comment field your team uses, with the check number or payment reference.
- Add a note on the payer’s record pointing back to the reservation, so a later “did you get our check?” call can be answered quickly.
This won’t put the revenue on the payer’s giving or purchase history. For most group visits that’s fine. Group admission is earned revenue, not a gift, so you aren’t issuing a tax acknowledgment to the payer anyway.
When the “payment” is actually a gift
Be careful with one situation in particular: a donor or foundation that underwrites field trips for a school that couldn’t otherwise afford them. That’s philanthropy, and your development team will probably want it recorded as a gift on the donor’s record, with the donor acknowledged and credited. Talk to finance about how to handle the reservation side. Some organizations record the gift separately and then apply a discount or a designated payment to the reservation. Others zero out the reservation under a sponsored-visit rate. Choose one method, write it down, and use it every time, so the revenue isn’t counted twice.
Split payments
Sometimes the district pays for students and parents pay for their own chaperone tickets. Try to split these at booking time where you can, either as separate reservations or as clearly labeled line items. One reservation with three or four payers mixed together is the hardest kind to reconcile when finance closes the month.
Make it repeatable
- Pick a default rule. For example: “If an organization pays, the organization is the patron.”
- Add the payer question to every group booking.
- Create a short reference sheet for sales staff that covers which option to use and which fields to fill in.
- Run a monthly query of group reservations with notes that mention a third-party payer, and check them against deposits so nothing gets missed.
Quick answers
Can I move a posted reservation payment to another constituent?
Don’t assume you can. Moving posted revenue usually involves finance and may affect batches that are already closed. Test in a sandbox and check with Blackbaud support before trying it in production.
Should the payer get a receipt?
Yes, a payment receipt or paid invoice that references the reservation. Don’t send a donation acknowledgment unless the payment was actually recorded as a gift.
