Source Codes-FY Year

Hi Amy,

When we noticed that happening with us I was able to determine that, at least in our case, this was happening when the money was being removed from an On Account.

For example, if someone used the wrong source when purchasing or directly returning a performance or package, the money still accurately posted to the FY attached to the campaign to which the performance or package.  If, however, the wrong source was used in an order where tickets were returned, the money was put to an On Account and the money was later picked up in that order to be placed elsewhere (like an unused ticket clearing house payment method) the FY reflected the campaign to which that source was tied.

While I'm certainly no programmer, I can only assume that the logic and/or process behind this is that when you are releasing money from a performance or package it's pretty straight forward as to what campaign the money should be tied.  However, if money is sitting in an On Account it is no longer tied to a performance or package and therefore all Tessitura can tie the money to is the source on the order being used for the transaction.  Again, that's all speculation on my part, but it's all I could come up with.

So far as changing sources in orders, that may be helpful for certain marketing purposes, but will not affect anything financially if the transaction has already posted.  My guess at the easiest financial fix would be:

Undo the transaction in the order with the original and incorrect source (so you're pulling money out of the incorrect FY it went into), change the source to the appropriate one, redo the transaction.  This will fix your GL as of the day you do this.

I apologize for the length but if your situation is similar to what we encountered, I hope this helps.

Best,

Charlie

Hi Amy,

When we noticed that happening with us I was able to determine that, at least in our case, this was happening when the money was being removed from an On Account.

For example, if someone used the wrong source when purchasing or directly returning a performance or package, the money still accurately posted to the FY attached to the campaign to which the performance or package.  If, however, the wrong source was used in an order where tickets were returned, the money was put to an On Account and the money was later picked up in that order to be placed elsewhere (like an unused ticket clearing house payment method) the FY reflected the campaign to which that source was tied.

While I'm certainly no programmer, I can only assume that the logic and/or process behind this is that when you are releasing money from a performance or package it's pretty straight forward as to what campaign the money should be tied.  However, if money is sitting in an On Account it is no longer tied to a performance or package and therefore all Tessitura can tie the money to is the source on the order being used for the transaction.  Again, that's all speculation on my part, but it's all I could come up with.

So far as changing sources in orders, that may be helpful for certain marketing purposes, but will not affect anything financially if the transaction has already posted.  My guess at the easiest financial fix would be:

Undo the transaction in the order with the original and incorrect source (so you're pulling money out of the incorrect FY it went into), change the source to the appropriate one, redo the transaction.  This will fix your GL as of the day you do this.

I apologize for the length but if your situation is similar to what we encountered, I hope this helps.

Best,

Charlie

Hi Charlie,
Thank you so much! That is exactly the case. Most of these transactions are orders from the web site that are created with on account payment methods. It makes perfect sense. I am so happy to hear this, I don't feel crazy now.
Thanks!
Amy

>>> "Charlie Garbowski Jr." 11/13/2009 4:56 PM >>>

Hi Amy,
When we noticed that happening with us I was able to determine that, at least in our case, this was happening when the money was being removed from an On Account.
For example, if someone used the wrong source when purchasing or directly returning a performance or package, the money still accurately posted to the FY attached to the campaign to which the performance or package. If, however, the wrong source was used in an order where tickets were returned, the money was put to an On Account and the money was later picked up in that order to be placed elsewhere (like an unused ticket clearing house payment method) the FY reflected the campaign to which that source was tied.
While I'm certainly no programmer, I can only assume that the logic and/or process behind this is that when you are releasing money from a performance or package it's pretty straight forward as to what campaign the money should be tied. However, if money is sitting in an On Account it is no longer tied to a performance or package and therefore all Tessitura can tie the money to is the source on the order being used for the transaction. Again, that's all speculation on my part, but it's all I could come up with.
So far as changing sources in orders, that may be helpful for certain marketing purposes, but will not affect anything financially if the transaction has already posted. My guess at the easiest financial fix would be:
Undo the transaction in the order with the original and incorrect source (so you're pulling money out of the incorrect FY it went into), change the source to the appropriate one, redo the transaction. This will fix your GL as of the day you do this.
I apologize for the length but if your situation is similar to what we encountered, I hope this helps.
Best,
Charlie

From: Amy Aldrich
Sent: 11/13/2009 12:43:49 PM

Happy Friday Everyone,
We've had some revenue from FY10 showing up as FY 09 on our posting reports. I've deduced that it seems to be stemming from operators using the incorrect source codes from a past season in the orders. So, I am manually going in and correcting the source codes on all of the individual orders. Is there an easier way to adjust these incorrect sources and is this solving the problem?
I am confused however as to the logic behind how some source codes from past seasons do not make the revenue show up in the wrong FY but some source codes do? Some source codes have an end date and some do not. I can't seem to figure it out.
Your insight is appreciated!!
Thanks,
Amy Aldrich
Boston Symphony Orchestra
Ticket Operations Manager
aaldrich@bso.org




This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Ticketing Forum. You may reply to this message to post to the Ticketing forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

Hey Amy!

If the "wrong FY" orders are coming from the web, you will want to be sure to adjust the default web source code in T_DEFAULTS to the new one for FY10.

David

So I just noticed it seems like the campaign displayed on the detail post report references the campaign from the order (which is the campaign from the source_code), not the campaign from the performance or pkg or whathaveyou (the campaign in t_transaction).

So based on the above, the campaign used to determine the fyear for the post is not necessarily the campaign displayed on the report, for all transactions, not just payment to payment transactions. Is that right? (Has that always been the case?)

I'm looking at TP_TKT_BATCH_REPORT_DETAIL and wondering if I'm muddling it.