2.  System Details  Revenue Center Details  Employee Details  Cashier Details  Time Period Details  Serving Period Details

3. Detailed Sales and Tip Profile Tracking Group Profile

4.  There are two parts to balance in Micros reports.  Sales + Tax +Service Charges = Total Revenue  Payments  If these match, the report balances to itself  Also the tracking group profile totals should match the detail sales and tip profile

5.  Each Part can be balanced individually  Net Sales = Sum of all Major Groups – Subtotal Discounts  Tax = Sum of Taxes in the Tracking Group Profile  Service Charges = Sum of all service charges in Tracking Group Profile  Not all information may be displayed or tracked in the tracking group. For example, taxes are not always put into the tracking groups.

6.  Checks Carried Over/Begun/Paid/Outstanding  Most of the time begun = paid  There will be carried over totals if there are open checks from the previous day or when from a previous shift employee detail reports.  There will be outstanding totals if not all the checks are closed when the report is run

7.  Begun checks totals will equal the total revenue total  Paid checks will equal the total of all tenders  Employees/Revenue Centers will have transfers in/out  Only responsibility for the check is transferred, not sales

8.  Added Tenders not being tracked  Reopen Checks  Added Major Groups not being tracked  Tip Percentage being withheld and not accounted for  Added Discounts not being tracked  Non Revenue Service Charges

9.  All Employee reports totals when added up don’t match the System totals  Site does not have all employee reports. For example, managers sometimes ring up sales and forget to run reports on themselves.  Employees are ringing up sales after they print their report. This can be intentional. A server runs a report then rings up more sales and pockets the cash. This can be prohibited by locking out the employee when the report is run. Takes a little program but if the site is having problems with this it can help.

10.  Employees reports are coming up short  Employee lost money  Employee gave wrong change  Another employee is using their number to ring up sales. Employees are using 4 digit numbers to sign in. Put employees on mag cards to solve this problem.

11.  The Voids field includes two figures. The first is the  number of void items. The second is the value of the  void items.  The number of void items is calculated as follows:  + number of voids of menu item entries  + number of voids of service charge entries  – number of voids of void entries  The value of void items is calculated as follows:  + value of void menu item entries  + value of voids of service charge entries  – value of voids of void entries

12.  Mgr Voids  The count and value of the voids that required manager authorization.  Error Corrects  The count and value amount of items that were voided in the current round. This is considered an error correction, rather than a void.

13.  The total value of all sales activity. Discounts, returns, voids, and credits are included as positive numbers. This number is never reset; it always accumulates. This field is used in conjunction with Change In Grand Ttl and Credit Total to verify system accounting security.  Grand Total is calculated as follows:  + previous Grand Total  + Change in Grand Ttl  This is like the odometer on your car it does not get reset.  This number used to used to make sure a manager did not reset the system in the middle of a shift and pocket the sales after the reset. Hardly ever used in today's systems.  Grand Total is not used to balance revenue.

14.  A total created when a round results in a negative Balance. If the negative balance was created by voiding a menu item, the tax associated with the item is posted to Credit Total.  If the negative balance was created by a negative value menu item, the entire value of the menu item and any associated taxes is posted to Credit Total.  In either case, the amount posted to Credit Total cannot exceed the negative balance of the round.  For example, a server voids two lobster dinners priced at $20 with $2 total tax for a void total of $42. In the same round, the server orders several more menu items with a total value (including tax) of $41. The transaction value of the round is -$1.  Since the round resulted in a negative balance, and the negative balance was created by voiding menu items, the tax associated with those menu items ($2) will post to Credit Total. However, the negative balance of the round is only $1; the amount posted to Credit Total cannot exceed this amount. In this example, -$1 is posted to Credit Total.  This field is used in conjunction with Change In Grand Ttl and Grand Total to verify system accounting security.  Credit Total is not used to balance revenue.