The documentation on v12 suggests that Price Layers can be used to set up composite tickets, including "donations": To wit...
"Price layers define the prices for a performance and the financial settings (such as GL accounts for ticketing revenue) for the prices. Multiple price layers can be applied to a performance, allowing the total price of a ticket to be segmented into multiple GL accounts, such as when selling a ticket that also includes a meal, inside charge, or a donation" -- (Tessitura v12.1: Ticketing Setup and Administration > Ticket Pricing > Performance Pricing > Price Layers)
This appeared to hold great promise for our events that combined, say, a meal price and a contribution in a single ticket. However, when we implemented such a scenario, while we are able to associate the contribution "layer" of the ticket with the appropriate GL account, we could see no way of associating that portion of the ticket price with the purchasing constituents so that they were being credited with the donation. In the past we accomplished this through the established "on account" payment method" strategy, pushing the donation recording from the ticket office to our development office. Seems that the same is needed here...somewhat rendering the apparent advantages of Price Layers in THIS particular regard moot.
Has anyone been successful in making this work differently and more successfully than I describe?
Jim
Hi Jim,
We are now on 12.5 now and would love to accomplish that same thing where we sell as a ticket but the entire price of the ticket to the event is considered a donation, so ideally it would create a donation record with all the advantages of the development folks keeping up with it there. What we did last year was sell the ticket online (so it followed that simple flow without any custom web coding), then someone after the fact would have to go in and modify the order to change the ticket price to comp and use the credit balance to create a contribution in the order. This accomplished both things we wanted (a contribution record and tracking ticket inventory for the event) but they were frustrated with it being a manual process. It was alot of housekeeping so we would love to take a different approach but I'm not sure anything in 12.5 has changed in this area.
Maybe someone from the Tessitura Team has any ideas?
Thanks
Henry
I am following this old thread. Has anyone found a better way to combine events/meals/contributions?
Ideally I would love to have a pricing rule that says if X production purchased with X price type then a contribution of $X to X fund is applied to the order- just to keep things straight. I am trying to do this with fees right now but someone has to manually adjust the fee to be a contribution.
Thanks,
Janna