Updated Methodology for Carry-over & Outstanding
We have updated the methodology we are using to account for check modifications (discount, comps, voids). With the new approach we will be changing how these deductions are applied to the check. Instead of altering the initial record of an item, the initial record will remain untouched and a new negative record will be posted. This will help maintain day over day reporting consistency.
Example: A check was begun and closed on 7/23/23. The following business day [7/24/23] a comp is applied to that same check.
Old methodology: we would update the original record of the items to be in a "No Show" state which would alter the order data for that business day, and a new record would be fired at the reduced rate on the current business day. (Orders Type Reports were changing after the trading day was over)
With the new methodology enabled: the new comp record (negative) will be associated with the 7/24 business day and the order amount on the 7/23 business day will remain unchanged.
This new methodology will be available with the TRAY HQ 5.10 deployment to coincide with a site's week start date to avoid inconsistencies in reports that contain a full week of data, or any of the following reports which overlap that time span:
- Order Summary
- Menu Mix
- Comps
- Discounts
- Voids
- FM Report
- Labor
- Labor Summary
- Staff Summary
- HQ Server Checkout
Depending on the date range requested you could encounter one of the following three scenarios:
In the event you want to query more than one site and if these sites have the new carry-over methodology enabled at different times, the user could run into a scenario where the date range selected contains the date when the site had the new carry-over flag enabled. In that case you will have two choices:
- Change your report to work around the dates
- Or proceed anyway understanding that the data will be inconsistent for the overlapping timeframe where these changes were enabled
Comments
0 comments
Article is closed for comments.