There is a report called The 'Item Analysis' that helps a property fulfilll Charges for a given dateis found under REPORTS | DAILY REPORTS. This report records all of the items sold in "Add Charge" OTHER than Room Rent in a chosen date range. The Items Details Reports tallies all the Item Groups (such as MEALS) and Item Details (such as Dinner) between a given date range. Since each Inventory Group and Inventory Item is setup in the Setup area of BookingCenter, you can have as many Inventory Items and Goups as desired. Total quantity summaries of Items to be fulfilled (or sold) can be run for multiple days or a single day only. The 'Date' column shows what 'System Date' the Charge posting was made on (if set automatically) Or, if your property allows it, a future date might have been entered when the Charge was posted to a folio, and that future date will be the one listed under the 'Date' column. Note that the date posted on the Charge affects when the Item will be picked up. For example, one can sell an Item today (via 'Add Charge' to a folio), January 12, 2011 and have the date tracked as March 23, 2011 on the Folio so that that particular Item will appear on the Item Analysis report for when it's actually 'required' to be used - March 23, 2011. Thus, if an Item is future-dated, that item is considered a 'current liability' to be sold/fulfilled at a future date and is not reported on the date for today, January 12, 2011. Note, however, that any Payment for the Charge is always 'now' (will appear on the Transaction report when payment is posted) and cannot be future-dated. So don't get confused with charging for an Item and paying for it. Learn about the Advanced Charges report (tracking what Charges are to be delivered in the future) by reading this article: https://support.bookingcenter.com/index.php?/Knowledgebase/Article/View/491. Learn about editing the date a Charge is to be 'fulfilled' so that it appears properly on the Item Analysis report in this article: https://support.bookingcenter.com/index.php?/Knowledgebase/Article/View/476.
|