Does anyone have experience processing miscellaneous (non-ticketing/contribution) payments?Specifically, we use third-party payment processing for things like collecting payments from food trucks and vendors. There is a desire to consolidate these functions into Tessitura. The most obvious thing that comes to mind is treating these as tickets and doing some things like flexible pricing and separate seasons. I'm wondering how commonplace this is and what folks have done to accommodate these needs. Open to ideas!Thanks!Chaz
We've handled a very small number of non-event-type transactions in Tessitura, using both Performances and On Account Payment Methods, depending on the purpose. I'd start with how you want to report on the transactions, and work backwards from there.
An editable user-defined fee is a handy and low-setup way to collect these ad-hoc charges using ticket orders. I do recommend making complete constituent accounts for the vendors, and adding notes to the order explaining what was involved, maybe an invoice number, etc. just for good housekeeping.
Thanks- this is where my brain was going. Far less overhead than building out performances.
Did you want to take paymentt online?
Not for this particular situation, although it may be a consideration later