(cross posted to ticketing for extra advice)
Greetings!
We are 10 days into using v11 on our Live server, and have realized a bit of trouble in our processing of money between development and ticketing. We have previously used several different types of On-Account payments, depending on what is getting moved and in which direction, and its been very helpful in financial reconciliation. However, v11 created a new complication because, in essence, ticket transactions are processed on the HOUSEHOLD, but gift transactions are on the INDIVIDUAL (as we have previously marked Name 1/2, and this matches our university system as well).
Previously, in v10, we found a few cases where we needed to "transfer" On-Account between different Tessitura accounts, so we created an in-between check payment type called "On-Account Transfer". Money was debited from one person's true On-Account, and credited to On-Account Transfer; then for the new person, money was immediately debited from On-Account Transfer, and then used acccordingly for tickets or whatnot. Now with our households and individuals, this two-transaction process would happen HUNDREDS of times a year!
Example #1:
Someone buys a subscription online, and tacks on a gift at the end (we use TN Express Web). That money goes into On-Account *to the household (if applicable)* - and we will want to process the gift to an individual.
Example #2:
Someone buys an elevated event, processed in development to the individual who is actually giving the gift. Money for the event tickets is put into On-Account (at the individual level), and would need to be used to pay for the event ticket (at the household level).
(To complicate matters, we realized upon live conversion that our previous year of operating as above has led to tons of On-Account Tracking accounts showing positive/negative numbers in households and individuals, where the individual's amount negates the household amount, or vice versa. Still working on transactions that would zero out the appearance of credit/negative credit in these accounts.)
Is anyone else having this issue, or found a resolution to this issue? I suppose it only effect organizations transacting differently in ticketing and development (household vs individual). Hoping to resolve soon before we dig ourselves into a deeper hole...
Beth
--------------BETH GILLILANDTessitura System Administratorbethgill@umich.edu734-615-9579 ofcwww.ums.org // www.umslobby.org
Unknown said: Is anyone else having this issue, or found a resolution to this issue?
Is anyone else having this issue, or found a resolution to this issue?
We, too, are recently on v11, and have run into the same issue between Ticketing and Development, and so far have used the "Move transactions to household" program to get the dollars where they needed to be, i.e. off of the (brand new, dupe, web generated) affiliate constituent and onto the household. It's not certain that this will always suffice, but so far, so good.
Good point, Chris - so at least our online donations from new logins will lessen the blow...thanks!