Ticket Sold Amount vs Revenue

I've got a dashboard that tracks each season of our education department's sales. And up to now, everything has been peachy.

However, my widget for total sales revenue seems to be off, and I'm not sure why. It isn't matching up with my finance widgets' figures.

When I'm in the Finance Cube, and I do a breakdown by payment method with a filter for the Title of 2019 Fall Classes, and stick a grand total on there, I end up with $98,664. When I'm in the Ticketing Cube and I do an indicator with Total Ticket Sold Amount, I get $100,122. Now, we do have two negative line items in the Payment Method, Ticket Change and Adjustment, but the total there is $84.

Anyone have any ideas why those two figures would be off by ~1.5%?

Parents
  • What version of Tessitura (and therefor Tessitura Analytics) are you using?  I'm on an older version 15.0.4 and there are a few known problems with package returns that are causing me some problems like this.  There are some workarounds that can make things better if that is your specific problem.  Have you compared your results to any of the ticketing standard reports to determine what might be going on?

    You may want to have a support ticket on this to make sure that your version of the Tickets & Seats eCube is working well. If this is a new issue, it would be great to get this on the developments teams radar screen so the issues can be resolved for all of us.

    --Tom

  • I am also on 15.0.4, so that may very well be my problem. I don't think it's tied to package returns simply because I don't have any packages in that season, but if those numbers are supposed to be even, then I'll raise a support ticket to confirm.

    Thanks, Tom!

  • I don't know in your case if the numbers should work out.  I've not tried cross-checking Ticket & Seats eCube Numbers with Finance eCube Numbers.  It's super cool that you are doing that because, in theory, this should work out.  And it that theroy is not true, it would be great for the rest of the community to understand why that assumption should not hold true.  If you have found a discrepancy, please take the time to submit a Support Ticket.  

    From the point of view of Tessitura Analytics, I'd recommend that you and your organization consider an SP to 15.0.x or upgrade to 15.1.  I know that the development team has been actively working on making Tessitura Analytics more reliable and useful.  We have on our internal roadmap an upgrade to 15.1.4 (due out next month). We are hoping that that version will bring even higher value to our investment in Tessitura Analytics.  

Reply
  • I don't know in your case if the numbers should work out.  I've not tried cross-checking Ticket & Seats eCube Numbers with Finance eCube Numbers.  It's super cool that you are doing that because, in theory, this should work out.  And it that theroy is not true, it would be great for the rest of the community to understand why that assumption should not hold true.  If you have found a discrepancy, please take the time to submit a Support Ticket.  

    From the point of view of Tessitura Analytics, I'd recommend that you and your organization consider an SP to 15.0.x or upgrade to 15.1.  I know that the development team has been actively working on making Tessitura Analytics more reliable and useful.  We have on our internal roadmap an upgrade to 15.1.4 (due out next month). We are hoping that that version will bring even higher value to our investment in Tessitura Analytics.  

Children
No Data