Hello everyone!
We have recently stumbled upon an 'inconsistency' in Analytics as it relates to sales reporting and how we match that to our financial reporting.
As we try to dig in to something like "weekly" or "daily" sales we have come across totals that vary based on the day we pull them. For example:
This has made it difficult to assure Board & VP's (with confidence) that our numbers are accurate. My questions are two-fold:
I think part of our issue is that the Tessitura database is a very fluid thing - especially as it relates to the order-date. Changes / adjustments made to orders (exchanges, returns, etc) will change how past days get reported on. Order Date isn't like a batch report date (or transaction date), which have a definitive end.
Thanks in advance for any & all feedback!
Hope I'm understanding you right. Do you mean the difference between ORDER DATE (when the order object was set up) and TRANSACTION DATE (when money was put through). For trouble shooting i like to drill down to the order or even SLI in consistency and have a look at the changes. You could look at any sales with that inconsistant order date and see if there were any transactional changes in the period that you noticed the discrepancy. I usually find it was an upgrade/downgrade/ refund or occasionally another sale in the same order #.
Transactions by Posting Report can also help
H
Thanks Heath!
Overall - yes. We're trying to manage the understanding of "order date" vs "transaction date" for both ourselves and the executives here. We don't need to know about every little discrepancy, but seeing them has caused confusion among everyone here. Right now, we have our feet in two different reporting structures: a static excel report and Analytics. The excel report mostly provides us context for YOY sales and pacing. We just converted over to Tessitura, so our ticketing history is a work-in-progress.
We're mostly trying to manage expectations of "accuracy" as it relates to Analytics (and sales reporting in general). Between myself and our Database Manager, I'd like to think we're mostly building them correctly - but it's been difficult trying to explain these discrepancies (re: structure) upward.
I guess what I'm saying is (and looking for reassurance on): is our hypothesis that using 'Order Date' as a way to reference point-in-time sales a losing battle until shows / performances / seasons are fully closed? Secondarily - should best practice indicate that our daily / weekly / monthly reporting stay in one area (analytics) as opposed to trying to manage a static file as well? Knowing that changes in accounts can impact how order-date reports, this to me seems likely.
Ed
Yes, "As Of" reporting is difficult with Tessitura. The Finance eCube is probably the only one that is well set up for this. Because transaction history is always added when adjustments are made. In the other eCubes values that you have seen in the past are open to later amendments. Returns, Exchanges, and so forth. This will typically subside after the performance date. But, give it a few days.