Ticket orders with contributions - reporting

Leslie,

I don't know if what we do is a "best way," but I wanted to share something for consideration.

We don't sell tickets to performances on our TNEW (our local performing arts center does our ticketing and uses ProVenue; argh), but we do sell our education classes and donors occasionally add on donations.

Since those donations come in under the Ticketing part of Tessitura, that can make the reporting a little muddy. If, however, you go into the Order and zero out the Contribution line item (putting it On Account for the constituent), you can then apply that Contribution using any Source or any Fund that would make it easier for you to track such gifts.

Even though our ticket sales/subscriptions don't go through Tess, we do have a specific Fund set up (Donation w/ Tkt Purchase) to record those gifts as well. That definitely helps with our reporting too.

Thank you,

Brian

Hi Leslie,

We used to have a similar process, but the time it takes to do that work I felt was higher than the value.

About a year ago we switched our Tnew web gifts to write directly to a fund. This means that it captures the same data that the ticket order captures. We have a generic "Online Transaction" source for for web transactions and the worker shows up as "Web API." I was pleasantly surprised this year by our subscription renewal period - because fixed packages receive a rollover order, the contributions all have the same subscription source description which was terrific to capture.

I've been very happy with this new system and especially happy at how much staff time we save by letting these transactions take care of themselves rather than being manually entered.

Best,
Megan

Seattle Symphony