Ticket Recon - Transition from Weekly to Daily

Former Member
Former Member $organization

Hello everyone! 

We are starting the transition from doing ticket reconciliation weekly to daily. For years we have we run a series of standard reports in conjunction with a very convoluted, complex spreadsheet. It doesn't work very well, and it can take a lot of time to find the issue if something doesn't match since we're going through so many orders. 

Would anyone be willing to share their process: what reports you pull, your strategy, perhaps an Analytics dashboard? 

We have a unique situation when it comes to ticketing. We do ticketing for an orchestra, but we also provide ticketing services (on contract) for a theatre that brings in presented shows from promoters. The revenue and fees from these two different entities must be separate. In addition, the fees for both kinds are slightly different. We have order based fees, percentage seat level fees, and flat seat level fees, but some of them differ based on MOS. Our challenge with Analytics is that fees are not directly tied back to a performance, so we can't report on them to reconcile in the Finance cube. And no, we can't put these fees into layers. 

We have never reconciled daily, so any advice, strategies, widgets, reports, etc are appreciated! Thank you in advance!

Erin

Ticketing and Data Services Manager

Parents
  • Without getting into the details, but since the reporting is the bottleneck, could you just have separately named fees for each situation? Since they are separate fees, you could then report on them in reports or Analytics. I'm guessing that this idea is the lowest hanging fruit.

    For example: Orchestra_Order_Fee, Orchestra_SeatLvl_Fee, Orchestra_Flat_Fee, Theater_Order_Fee, Theater_SeatLvl_Fee, and Theater_Flat_Fee.

Reply
  • Without getting into the details, but since the reporting is the bottleneck, could you just have separately named fees for each situation? Since they are separate fees, you could then report on them in reports or Analytics. I'm guessing that this idea is the lowest hanging fruit.

    For example: Orchestra_Order_Fee, Orchestra_SeatLvl_Fee, Orchestra_Flat_Fee, Theater_Order_Fee, Theater_SeatLvl_Fee, and Theater_Flat_Fee.

Children
No Data