• Account – Accounting entity used in Salesware module so that customers can charge purchases rather than paying for them with cash or credit. An account consists of invoices.

• Batch – A batch is a collection of credit card charges. Authorization for a credit card charge is usually received from the credit card provider, and then a batch of charges (usually for one twenty four hour period) is submitted for final reconciliation and funds exchange and deposit in the merchant’s bank.

• Booking – A guest reservation. Official bookings are made using the Reservations module, but “bookings” can also be made using the Private Scheduling and Activity/Facility Scheduling modules as well as from SysManager > Accounts > Invoices > Trip Details.

• Close out – End of the day procedures for tallying the day’s sales and other activity.

• Closed on – When closing out using the closed drawer method of closing out the day

• Comps – Complimentary items, usually tickets, given out for free.

• DCI – Department, Category, Item. A DCI is used to uniquely distinguish and organize every item in the Salesware system. Because the way you organize your products in the DCI list directly affects the ways your reports are organized, you need to plan your DCI list carefully.

• Finalized close out – Close outs are finalized using the Close Drawer Report. After a close out is finalized, special permissions are required to go back into the close out and change it. A finalized close out is to be distinguished from a finalized sale.

• Finalized sale – A finalized sale is one which is not saved. With the exception of reservations created using the Reservations module, you cannot recall a sale that has been finalized. A finalized sale is to be distinguished from a finalized close out.

• Invoice – Accounting entity used in Salesware module to enable charges to be made to an account.

• Marketing code – Specials are often assigned marketing codes. Marketing codes are used to indicate some characteristic of the special that the marketing department wants to track (i.e., if the item is being purchased by a male or female). Source codes are defined from SysManager > Activities > Item/Sales Lists.

• Max4Sale – Mechanism used in Salesware module to limit the amount that can be sold of any given item.

• Operator groups – Operator groups are frequently used in reporting, i.e., all F&B operators. Operator groups are defined from SysManager > Activities > System Lists > Salespoint Groups.

• Profit center – Accounting entities used so that sales can be attributed to a variety of categories. Normally every item available for sale in a Salesware installation is assigned a profit center. All sales of each item are tallied in the appropriate profit center. Profit centers are also known as “chart of accounts” in some accounting systems.

• Receipts – Cash, credit and account charges used to pay for merchandise and services.

• Salespoint Groups – Salespoint groups are frequently used in reporting, i.e., all F&B salespoints. Salespoint groups are defined from SysManager > Activities > System Lists > Salespoint Groups. Oftentimes these groups correspond to the salespoint groups used in the global .INI (SysManager > Preferences > Miscellaneous > Global Salespoint INI) for use with the [Salespoint] Group .INI setting in Sales32c.INI.

• Saved sale – Saved sales are saved at the salespoint with the Save button. Saved sales and reservations are quickly recalled at any salespoint.

• Source code – Specials are often assigned source codes. Source codes indicate the source of the special (i.e., a direct mail promotion piece). Source codes are defined from SysManager > Activities > Item/Sales Lists.

• Special – A special is the mechanism by which changes to regular item prices are applied and tracked. Specials are often assigned source and/or marketing codes.

• User-defined fields – User-defined fields are used to label fields that can be used to collect additional information. For example, the user-defined fields defined from SysManager > Activities > Item/Sales Lists can be used to collect addition information in a Reservation Header, which requires the Reservations module.

• Valid on – Similar to revenue recognition, reporting is often done for items when they were/are valid (for example, valid dates for use) rather than when they were actually sold.