Future Adjustments reporting within Tessitura/Analytics

I've drawn up a set of reports in Analytics, based on Performance Date (total sales, total revenue, paid vs free, etc.). Each row is a performance, with the attached sales/revenue/etc. Naturally, these update daily as changes go through. Over the last few weeks, our Finance department has raised questions about how returns/exchanges affect daily numbers.

They want the snapshot for each day to be static, and they want any subsequent transactions (returns/exchanges) to be noted on future dates, not on the initial date. In other words; if we had 10 tickets sold for May 1st, as of May 1st that'll reflect- 10 tickets, $100 in revenue. If, a week later, one ticket is refunded, they want those changes to be noted on subsequent dates (changes/refunds/exchanges). The metaphor they used was looking at a bank statement- each transaction affects the final total, but is reflected on the date it occurs, not on the target visit date.

Have folks done that before? Is that something that has been worked through?

Parents
  • Instead of using Transaction date, you might want to use Post Date as that, theoretically, would be what Finance uses in their ERP system.
     
    One of the idiosyncrasies of Tessitura is that transactions do not directly tie to Line Items, Sub Line Items, or Sub Line Item Details. Transactions are in a different table structure that only connects at the Order level.
     
    With that in mind, using the Transactions from the Finance Cube, you can have consistent revenue numbers by Transaction/Post Date, but you will need to pull items such as number of seats, etc from the Ticketing Cube by Sale/Order Date. And unfortunately, those numbers will change as refunds/transfers take place.
     
    Brian Ramos
    Controller
                                                                     
    Opera Philadelphia
    Direct 215.893.5940
    Main 215.893.3600
    Guest Services 215.732.8400
    operaphila.org



    Connect    facebook    twitter   youtube    instagram    gold_ghost copy  
     
Reply
  • Instead of using Transaction date, you might want to use Post Date as that, theoretically, would be what Finance uses in their ERP system.
     
    One of the idiosyncrasies of Tessitura is that transactions do not directly tie to Line Items, Sub Line Items, or Sub Line Item Details. Transactions are in a different table structure that only connects at the Order level.
     
    With that in mind, using the Transactions from the Finance Cube, you can have consistent revenue numbers by Transaction/Post Date, but you will need to pull items such as number of seats, etc from the Ticketing Cube by Sale/Order Date. And unfortunately, those numbers will change as refunds/transfers take place.
     
    Brian Ramos
    Controller
                                                                     
    Opera Philadelphia
    Direct 215.893.5940
    Main 215.893.3600
    Guest Services 215.732.8400
    operaphila.org



    Connect    facebook    twitter   youtube    instagram    gold_ghost copy  
     
Children
No Data