A grandmother calls the membership office wanting to buy household memberships for herself and her two adult children and put all of it on one card. Or a company buys a dozen gift memberships for its staff and sends one check. It sounds simple: three memberships (or twelve), one payment. In Altru, the answer depends on where you process the sale. The back-office membership workflow and the point-of-sale workflow don’t behave the same way.
This article covers what to check, the workable options, and how to keep the finance side clean whichever route you pick.
Why this gets awkward in the back office
The usual back-office path for a membership starts from a single membership or a single constituent: you choose the program and level, add members, then take payment. That flow is built around one membership at a time, so every membership you add that way usually means its own payment entry. For one buyer paying for several memberships, that leaves staff with a few unappealing choices:
- Run the card several times, once per membership. The buyer sees several charges on their statement and may call to ask why.
- Charge the card once outside Altru, then record each membership’s payment separately. This works, but the deposit no longer matches a single card transaction, and reconciliation gets harder.
- Record everything against one membership and fix the rest later. Avoid this one. It skews revenue by level and makes renewal history unreliable.
Before you settle on a workaround, confirm what your version and configuration actually allow. Altru changes over time and organizations set up their membership programs differently. Try the scenario in a sandbox or training environment if you have one, or ask Blackbaud support directly: “Can one payment be applied to more than one new membership in the back office?” Get a clear yes or no before you train staff.
Option 1: Sell the memberships through point of sale
Altru’s daily sales and advance sales workflows are order-based. An order can hold more than one item, and the payment applies to the order as a whole. If your organization sells memberships at the front desk, check whether staff can add several memberships to one order, attach each to the right constituent, and tender once.
Things to test before you rely on it:
- Constituent assignment. Make sure each membership lands on the correct primary member, not on the buyer. For gifts, confirm the buyer is recorded as the giver and the recipient as the member.
- Add-ons and household members. Check whether you can add the additional members and cardholders during the sale or need to go back and add them afterward.
- Revenue and GL mapping. Run a revenue report afterward and confirm each membership posted to the correct program and level, not as one lump sum.
- Card printing and fulfillment. Find out whether cards or acknowledgments generate for each membership or only for the order.
If this works in your setup, it’s usually the cleanest answer: one card swipe, one receipt, separate membership records.
Option 2: Split one payment by hand and document it
If point of sale won’t work for your situation (a mailed check, for example, or memberships that need back-office details the desk can’t capture), process each membership in the back office and divide the payment amount across them. Keep it traceable:
- Process the card once, or deposit the check once.
- Add each membership separately, recording the portion of the payment that belongs to it. Use the same payment method and reference (check number or card authorization) on each.
- Put all of them in the same batch so the batch total matches the single deposit or settlement amount.
- Add a note or attribute on each membership naming the buyer and the shared payment, so the next person who sees three $150 payments from one check understands why.
Talk to your finance team before you adopt this. Some prefer one payment line per membership. Others want the payment recorded once and accept a note-based crosswalk. Agree on it once so desk staff and development staff handle it the same way.
Option 3: Treat bulk buyers as a group sale
When an employer or community partner buys a large block of memberships, the transaction often behaves more like a group sale or a contract than a retail purchase. Some organizations invoice the buyer, collect one payment, and then create the memberships as the recipients’ details come in. If you go this route, decide upfront how the memberships will be dated. A membership created months after the payment can confuse expiration dates and renewal timing.
Keeping reporting honest
Whatever you choose, plan to report on these sales later. A simple membership query that pulls recent memberships along with the payment reference or your shared-payment attribute lets you confirm that:
- each membership has its own record and its own expiration date,
- gift memberships credit the giver correctly for acknowledgments and the recipient for benefits,
- the amounts across the related memberships add up to what was actually collected.
Run it monthly for the first few months after you change the process. It’s the fastest way to catch a desk shortcut before it turns into a cleanup project.
Quick answers
Can Altru charge one card once for several memberships?
Through an order-based sale it often can, because the payment covers the whole order. In the single-membership back-office flow, plan on separate payment entries unless Blackbaud confirms otherwise for your version.
What about renewals for a whole family at once?
The same logic applies. Each membership renews on its own record, so test whether your renewal workflow can take a combined payment before you promise it to members.
Should we just put everyone on one household membership?
Only if they actually live together and your levels allow it. Merging separate households to simplify payment creates benefit and mailing problems later.
