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?
Curious also. I've been told it can't be done. The closest I can get to something like that is just the daily G/L posting report, which isn't affected for refunds, etc until the date of the refund, but you only get a cumulative amount, not ticket numbers, etc.
The closest I've come is to pull a report (within the Finance Cube) based on Transcation date. It references total credit, total debit, total ticket purchase, and total ticket refund amounts. That's a good step forward, but it'd be nice if there was a comprehensive, polished solution.