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
Hi Amy,
I believe that the fiscal year on a posting report for a ticketing order is assigned by either the fiscal year column in tr_season or the fiscal year box in the fee details.So in an order where you suspect this is happening verify that the correct production season is assigned to the production in ticketing setup > production elements, then verify that the season in question has the correct fiscal year assigned in tr_season and also check the fiscal year on any fees that are on the order by going to ticketing setup > fees.
Maybe there is something that I'm missing but I don't think source codes have anything to do with it.
Cheers and happy Friday to you!
I would also check the campaign associated with the performances. If some or all of the performances in the orders in question have campaigns for the previous fyear, I think that would cause what you describe on the post report.
Amanda is totally correct, I just tested this out and it does affect the fiscal year on the posting report. I thought I was missing something more granular.