Summary

The Altametrics Cloudbridge provides functionality for vendors and third party integrators to export POS/BOH data for automatic uploading to Hubworks applications. This document describes the acceptable formats and file conventions for this purpose.

There are four types of files that can be exported for consumption by Hubworks:

Hourly Summary

Five specific data points (net sales, transaction count, guest count, labor cost and labor hours) broken down by hour. The Hourly Summary can be run every hour during the current business date, or processed at day’s closing.

Day Part Sales Summary

Sales and transactions broken down into 15 minute day parts. Attributes include guest count, transaction count, net sales and gross sales.

Daily Summary

A list of named values, or daily keys. Some keys are standard and required for proper reporting by Hubworks. The exporting system can also generate a number of custom keys. The Daily Summary is uploaded at the end of the business date.

Meta data

A file defining report sections and associated daily keys. Metadata can be exported as needed

If adjustments need to be made to prior business dates (e.g. labor adjustments), the Hourly and Daily Summaries can be re-exported, as long as they are within 10 days of the current business date Data can be provided as a set of four XML or CSV files. The exporting application must adhere to the strict file naming and format conventions which are described in this document.

Export Folder & File Formats

Files must be exported to a subfolder of the common application data folder. This folder varies based on Operating System and environment settings, but is typically as follows:

Windows Vista and above c:\ProgramData\Altametrics\Cloudbridge\HubWorks
Windows XP c:\Documents and Settings\All Users\Application Data\Altametrics\Cloudbridge\HubWorks

The Altametrics Cloudbridge will delete the export files after successful transmission. Any files in the export folder older than 30 days will be deleted automatically.

Hubworks provides two different file types for exporting data: XML and CSV. Although CSV is supported, CSV files will be converted to XML before transmission to Hubworks, so XML is the preferred format. There are four different export files: the Hourly Summary, the Daily Summary, the Day Part Sales Summary and the Metadata. If metadata is written as a CSV file, an XML file will be generated from it, and the XML file will remain on disk until/unless the CSV file is updated.

Hourly Summary

The Hourly Summary includes a list of five specific data points. The Cloudbridge Service will look for an Hourly Summary file for the current business date once an hour throughout the day. Hourly Exports can also be generated for past business dates (up to 10 days past), but these will only be uploaded by the Cloudbridge Service once a day. The exporting application should regenerate Hourly Summaries for previous business dates only if the data has actually changed since the previous export.

The Hourly Summary should contain data only for a single business date. This means that if the business date closes at 2:00 AM, the entries for 1:00 to 2:00 AM represent data from the calendar date after the entries for 2:00 to 3:00 AM.

The Hourly Summary should contain data for each hour of the day where data is available. It is unnecessary to export entries for hours which contain no nonzero values.

Hourly Summary CSV Example

The Hourly Summary can be exported as a CSV file. The file must be named “hourly_YYYYMMDD.csv”, (where YYYYMMDD is the business date) in order to be processed by the Altametrics Cloudbridge. A header row is optional (for readability) but will be discarded by the Cloudbridge. The columns are as follows:

1. The hour (1-24), with 1 being the hour from midnight to 1:00 AM
2. Net Sales
3. Transactions
4. Guest Count
5. Hourly Labor Cost
6. Hourly Labor Hours

Hour, NetSales, Transactions, Guests, LaborCost, LaborHours

9,16.45,2,2.69,0.25

10,260.44,17,35,32.96,3

11,711.80,56,107,43.67,4.33

12,611.58,61,119,57.20,6

Hourly Summary XML Example

Alternatively, The Hourly Summary may be exported in the form of an XML file. The file must be named “hour_YYYYMMDD.xml” (where YYYYMMDD is the business date) in order to be processed by the Altametrics Cloudbridge. A full XML Schema will be provided as an appendix to this document, but a sample fragment is supplied here:


<?xml version="1.0" encoding="utf-8"?>
<HubWorks>
<HourlySummary>
<Values hour="9" netSales="16.45" transactions="2" guests="2" laborCost="2.69" laborHours="0.25"/>
<Values hour="10" netSales="260.44" transactions="17" guests="35" laborCost="32.96" laborHours="3"/>
<Values hour="11" netSales="711.8" transactions="56" guests="107" laborCost="43.67" laborHours="4.33"/>
<Values hour="12" netSales="611.58" transactions="61" guests="119" laborCost="57.2" laborHours="6"/>
</HourlySummary>
</HubWorks>

Day Part Sales Summary

Sales information, including net and gross sales, guest and transaction counts can be summarized by 15-minute day parts. This gives a finer level of detail than the hourly summary, but tracks fewer data points. Even though there is some overlap of the data points from the Hourly Summary and the Day Part Sales Summary, both exports are independent and both should be populated by the exporting application.Day Part Sales information should contain information for a single business date. If the business date changes after midnight, this means that the data will contain elements from two different calendar dates.

Each line has a start time, represented in HH:MM format, with the period from midnight to 12:15 AM being “00:00”, and the period from 12:45 PM to midnight being “23:45”.

The Day Part Summary file may be exported as “daypart_YYYYMMDD.csv” or “daypart_YYYYMMDD.xml”

Day Part Summary CSV Example

StartTime,NetSales,GrossSales,Transactions,Guests

07:00,19.38,20.93,3,3

07:15,34.17,36.90,6,6

07:30,32.29,34.87,4,6

07:45,52.94,57.18,9,9

Day Part Summary XML Example


<?xml  version="1.0" encoding="utf-8"?>
<HubWorks>
<DayPartSales>
<DayPart start="07:00" netSales="19.38" grossSales="20.93" transactions="3" guests="3"/>
<DayPart start="07:15" netSales="34.17" grossSales="36.90" transactions="6" guests="6"/>
<DayPart start="07:30" netSales="32.29" grossSales="34.87" transactions="4" guests="6"/>
<DayPart start="07:45" netSales="52.94" grossSales="57.18" transactions="9" guests="9"/>
</DayPartSales>
</HubWorks>

Daily Summary

The Daily Summary is a list of Data Keys (named values). There is a list of standard key names that must be provided. Standard key names always begin with “$cb_” or “$hub_”. Standard key names are case-sensitive.

The exporting application may also include custom data keys for fields that are not included in the standard keys. Custom key names may include alphanumeric characters, dashes and underscores. Values with invalid key names will be omitted from the upload. Custom key names are always converted to uppercase.

The Altametrics Cloudbridge processes Daily Summary export files after the close of the business date. If the exporting application detects modifications to prior business dates, export files for those dates may also be generated, as long as these are not more than 10 days in the past.

Daily Summary Keys

The following Daily Keys are listed by report section. Keys in bold are required to fulfill requirements for that section. Keys in italics are optional, but highly suggested if available to the exporting application.

Sales


• $cb_Gross_Sales_Amt
• $cb_Net_Sales_Amt
• $cb_Transaction_Cnt
• $hub_Discount_Total_Amt
• $cb_Guest_Cnt
• Additional custom keys. The section may not exceed eight keys total, 
  including standard and custom keys.

                              

Labor


• $cb_Actual_Labor_Hours_Amt
• $cb_Actual_Labor_Dollars_Amt
• $hub_Overtime_Labor_Hours_Amt
• $hub_Overtime_Labor_Dollars_Amt
• Additional custom keys. The section may not exceed eight keys total, 
  including standard and custom keys.


                              

Cash and Deposits


• $hub_Deposit_Total_Amt
• $hub_Sales_Tax_Total_Amt
• Up to six additional custom keys. Custom key names should not begin with 
  a $ sign.
                              

Payment Amount Totals


• $hub_PAYMENT_Total_Amt
• Up to seven payment keys in the form of $hub_PAYMENT_[PAYMENTCODE]_Amt,
  where PAYMENTCODE is defined by the exporting application. 
  Typical examples would be $hub_PAYMENT_CASH_Amt or $hub_PAYMENT_VISA_Amt. 
  Only the top 7 payment types (by amount) should be included in the 
  Hubworks feed.
  The $hub_PAYMENT_Total_Amt should be the total of all payments, including
  those payment types not included in the top seven. Free POS Reports 
  will include an implied “Other Payments” to account for the difference
  between the $hub_PAYMENT_Total_Amt and the sum of the top seven 
  payment types.

                              

Payment Count Totals


• $hub_PAYMENT_Total_Cnt
• Up to seven payment keys in the form of $hub_PAYMENT_[PAYMENTCODE]_Cnt,
  where PAYMENTCODE is defined by the exporting application. Typical 
  examples: $hub_PAYMENT_CASH_Cnt or $hub_PAYMENT_VISA_Cnt. Only the 
  top 7 payment types (by amount) should be included in the HubWorks 
  feed, matching those included in the Payment Amount Totals section.
  The $hub_PAYMENT_Total_Amt should be the total of all payments, 
  including those payment types not included in the top seven. 
  Free POS Reports will include an implied “Other Payments” to 
  account for the difference between the $hub_PAYMENT_Total_Amt and 
  the sum of the top seven payment types.

                              

Day Part Amount Totals


• $hub_DP_Total_Amt
• Up to seven day part keys in the form of $hub_DP_[DAYPARTCODE]_Amt,
  where DAYPARTCODE is defined by the exporting application. Typical
  examples: $hub_DP_BKFST_Amt or $hb_DP_LUNCH_Amt.

                              

Day Part Amount Counts


• $hub_DP_Total_Cnt
• Up to seven day part keys in the form of $hub_DP_[DAYPARTCODE]_Cnt,
  where DAYPARTCODE is defined by the exporting application. 
  Typical examples: $hub_DP_BKFST_Cnt or $hb_DP_LUNCH_Cnt.


                              

Category Amount Totals


• $hub_CAT_Total_Amt
• The top seven sales mix categories (by sales) in the form of 
  $hub_CAT_[CATEGORYCODE]_Amt, where CATEGORYCODE is defined by the 
  exporting application. Typical examples: $hub_CAT_BEVERAGE_Amt or
  $hb_CAT_SANDWICH_Amt. Only the top seven should be included, and 
  any additional categories beyond the top seven will be filtered.
  The $hub_CAT_Total_Amt should be the total of all categories, 
  including those not included in the top seven. Free POS Reports 
  will include an implied “Other Categories” to account for the 
  difference between the $hub_CAT_Total_Amt and the sum of the top
  seven categories.


                              

Category Amount Counts


• $hub_CAT_Total_Cnt
• The top seven sales mix categories (by sales) in the form of 
  $hub_CAT_[CATEGORYCODE]_Cnt, where CATEGORYCODE is defined by
  the exporting application. 
  Typical examples: $hub_CAT_BEVERAGE_Cnt or $hb_CAT_SANDWICH_Cnt.
  Only the top seven should be included, and any additional categories
  beyond the top seven will be filtered. The $hub_CAT_Total_Cnt should
  be the total of all categories, including those not included in 
  the top seven. Free POS Reports will include an implied 
  “Other Categories” to account for the difference between the 
  $hub_CAT_Total_Cnt and the sum of the top seven categories.
                              

Custom Daily Keys

The exporting application may provide additional custom sections and custom data keys. The total number of daily keys must not exceed 100, including both standard and custom keys.

Daily Summary Files

The Daily Summary can be exported as a CSV file named “daily_YYYYMMDD.csv” (where YYYYMMDD is the business date). A header row is optional (for readability) but will be discarded by the Cloudbridge. The columns are as follows:

1.Key name

2.Value

Daily Summary CSV Example

Key Value
$cb_Gross_Sales_Amt 10742.25
$cb_Net_Sales_Amt 10703.78
$cb_Transaction_Cnt 621
$cb_Guest_Cnt 646
$hub_Discount_Total_Amt 52.32
$cb_Actual_Labor_Hours_Amt 114.88
$cb_Actual_Labor_Dollars_Amt 1481.76
$hub_Overtime_Labor_Hours_Amt 6.41
$hub_Overtime_Labor_Dollars_Amt 84.80
$hub_Deposit_Total_Amt 1507.07
$hub_Sales_Tax_Total_Amt 630.71
$hub_PAYMENT_Total_Amt 11735.5
$hub_PAYMENT_CASH_Amt 1612.3
$hub_PAYMENT_AMEX_Amt 3967.77
$hub_PAYMENT_MASTERCARD_Amt 2955.45
$hub_PAYMENT_VISA_Amt 2867.23
$hub_PAYMENT_GIFTCARD_Amt 7.79
$hub_PAYMENT_TRAVCHECK_Amt 24.22
POS_REFUNDS_AMT 18.23

Daily Summary XML Example

The Daily Summary can also be exported as an XML file named “daily_YYYYMMDD.xml” (where YYYYMMDD is the business date). A complete XML Schema will be supplied as an appendix to this document, but a sample XML fragment follows:


<?xml  version="1.0" encoding="utf-8"?>
<HubWorks>
<DailyKeys>
<Key name="$cb_Gross_Sales_Amt" value="10742.25"/>
<Key name="$cb_Net_Sales_Amt" value="10703.78"/>
<Key name="$cb_Transaction_Cnt" value="621"/>
<Key name="$cb_Guest_Cnt" value="646"/>
<Key name="$hub_Discount_Total_Amt" value="52.32"/>
<Key name="$cb_Actual_Labor_Hours_Amt" value="114.88"/>
<Key name="$cb_Actual_Labor_Dollars_Amt" value="1481.76"/>
<Key name="$hub_Overtime_Labor_Hours_Amt" value="6.41"/>
<Key name="$hub_Overtime_Labor_Dollars_Amt" value="84.80"/>
<Key name="$hub_Deposit_Total_Amt" value="1507.07"/>
<Key name="$hub_Sales_Tax_Total_Amt" value="630.71"/>
<Key name="$hub_PAYMENT_Total_Amt" value="11735.5"/>
<Key name="$hub_PAYMENT_CASH_Amt" value="1612.3"/>
<Key name="$hub_PAYMENT_AMEX_Amt" value="3967.77"/>
<Key name="$hub_PAYMENT_MASTERCARD_Amt" value="2955.45"/>
<Key name="$hub_PAYMENT_VISA_Amt" value="2867.23"/>
<Key name="$hub_PAYMENT_GIFTCARD_Amt" value="7.79"/>
<Key name="$hub_PAYMENT_TRAVCHECK_Amt" value="24.22"/>
<Key name="POS_REFUNDS_AMT" value="18.23"/>
</DailyKeys>
</HubWorks>

Metadata Export

Metadata allows the exporting system to describe the daily keys by providing meaningful labels and grouping them into report sections. Metadata can be exported in either XML or CSV formats. Metadata need only be updated when it changes. Unlike other exports, the metadata file is undated, and will not be deleted after export. Metadata is merged with each Daily Summary export. Any keys appearing in the metadata not appearing in the Daily Summary will be omitted from the metadata before transmission to Hubworks. For example, there may be 40 different sales mix categories defined in the POS, and each of these can be defined in the metadata, but the Cloudbridge Service will filter all but the top seven before transmitting to Hubworks. Labels can include any alphanumeric characters, most punctuation, and space characters. Punctuation characters may not include single quotes, double quotes or ampersands. Whitespace will be normalized, i.e. leading and trailing whitespace will be trimmed, tabs, newlines and other whitespace characters will be converted to space characters, and consecutive whitespace characters will be reduced to a single space character.

The metadata can be exported as a CSV file. The first line of the CSV file is reserved for column labels. The columns are as follows:

• Report Index, a nonnegative integer for grouping report sections together

• Section label, for grouping daily keys together

• Daily Key name

• Decimal Places, a nonnegative number defining how many positions to the right of the decimal point that should be displayed on reports

• Is Currency: a Y or N indicating whether a currency symbol should be displayed on reports

• Label for the daily key to be displayed on reports

Metadata CSV Example

Section,Key,DecimalPlaces,IsCurrency,Label

Sales,$cb_Gross_Sales_Amt,2,Y,Gross Sales

Sales,$cb_Net_Sales_Amt,2,Y,Net Sales

Sales,$cb_Transaction_Cnt,0,N,Transactions

Sales,$hub_Discount_Total_Amt,2,Y,Discounts

Sales,POS_REFUNDS,2,Y,Refunds

Labor,$cb_Actual_Labor_Dollars_Amt,2,Y,Labor Cost

Labor,$cb_Actual_Labor_Hours_Amt,1,N,Labor Hours

Labor,$hub_Overtime_Labor_Dollars_Amt,2,Y,Overtime Cost

Labor,$hub_Overtime_Labor_Hours_Amt,1,N,Overtime Hours

Cash and Deposits,$hub_Deposit_Total_Amt,2,Y,Total Deposits

Cash and Deposits,$hub_Sales_Tax_Total_Amt,2,Y,Sales Tax

Metadata XML Example


<HubWorks>
<MetaData>
<Section label="Sales">
<Item key="$cb_Gross_Sales_Amt" label="Gross Sales" decimalPlaces="2" isCurrency="Y"/>
<Item key="$cb_Net_Sales_Amt" label="Net Sales" decimalPlaces="2" isCurrency="Y"/>
<Item key="$cb_Transaction_Cnt" label="Transactions"/>
<Item key="$hub_Discount_Total_Amt" label="Discounts" decimalPlaces="2" isCurrency="Y"/>
<Item key="POS_REFUNDS" label="Refunds" decimalPlaces="2" isCurrency="Y"/>
</Section>
<Section label="Labor">
<Item key="$cb_Actual_Labor_Dollars_Amt" label="Labor Cost" decimalPlaces="2" isCurrency="Y"/>
<Item key="$cb_Actual_Labor_Hours_Amt" label="Labor Hours" decimalPlaces="1"/>
<Item key="$hub_Overtime_Labor_Dollars_Amt" label="Overtime Cost" decimalPlaces="2" isCurrency="Y"/>
<Item key="$hub_Overtime_Labor_Hours_Amt" label="Refunds" decimalPlaces="1"/>
</Section>
<Section label="Cash and Deposits">
<Item key="$hub_Deposit_Total_Amt" label="Deposits" decimalPlaces="2" isCurrency="Y"/>
<Item key="$hub_Sales_Tax_Total_Amt" label="Sales Tax" decimalPlaces="2" isCurrency="Y"/>
</Section>
</MetaData>
</HubWorks>

Log Files

The Altametrics Cloudbridge will provide the log files to give the authors of the exporting system some insight into how the system is behaving. Log files follow a similar dated naming convention, although the date in the log file name will be the current date, not the businessdate. The Cloudbridge service will automatically delete any log files older than 10 days.

The logs folder varies based on Operating System and environment settings, but is typically as follows:

Windows Vista and above

c:\ProgramData\Altametrics\Cloudbridge\logs

Windows XP

c:\Documents and Settings\All Users\Application Data\Altametrics\Cloudbridge\logs

Appendix A: XML Schema

A complete up-to-date copy of the Hubworks XML Schema can be downloaded from

https://cloudbridge.xformity.com/services/download/HubWorks/HubWorksXML.xsd.

Appendix B: Standard Metadata Format

The following metadata XML file is provided as a guideline for exporting applications.


<?xml  version="1.0" encoding="UTF-8"?>
<HubWorks>
<MetaData>
<Section label="Sales">
<Item key="$cb_Gross_Sales_Amt" label="Gross Sales" decimalPlaces="2" isCurrency="Y"/>
<Item key="$cb_Net_Sales_Amt" label="Net Sales" decimalPlaces="2" isCurrency="Y"/>
<Item key="$cb_Transaction_Cnt" label="Transactions"/>
<Item key="$hub_Discount_Total_Amt" label="Discounts" decimalPlaces="2" isCurrency="Y"/>
<Item key="POS_REFUNDS" label="Refunds" decimalPlaces="2" isCurrency="Y"/>
</Section>
<Section label="Labor">
<Item key="$cb_Actual_Labor_Dollars_Amt" label="Labor Cost" decimalPlaces="2" isCurrency="Y"/>
<Item key="$cb_Actual_Labor_Hours_Amt" label="Labor Hours" decimalPlaces="1"/>
<Item key="$hub_Overtime_Labor_Dollars_Amt" label="Overtime Cost" decimalPlaces="2" isCurrency="Y"/>
<Item key="$hub_Overtime_Labor_Hours_Amt" label="Refunds" decimalPlaces="1"/>
</Section>
<Section label="Cash and Deposits">
<Item key="$hub_Deposit_Total_Amt" label="Deposits" decimalPlaces="2" isCurrency="Y"/>
<Item key="$hub_Sales_Tax_Total_Amt" label="Sales Tax" decimalPlaces="2" isCurrency="Y"/>
</Section>
<Section label="Payment Amounts">
<Item key="$hub_PAYMENT_VISA_Amt" label="Visa" decimalPlaces="2" isCurrency="Y"/>
<Item key="$hub_PAYMENT_CASH_Amt" label="Cash" decimalPlaces="2" isCurrency="Y"/>
<Item key="$hub_PAYMENT_MC_Amt" label="MC" decimalPlaces="2" isCurrency="Y"/>
<Item key="$hub_PAYMENT_AMEX_Amt" label="AMEX" decimalPlaces="2" isCurrency="Y"/>
<Item key="$hub_PAYMENT_DISCOVER_Amt" label="Discover" decimalPlaces="2" isCurrency="Y"/>
<Item key="$hub_PAYMENT_Total_Amt" label="Total" decimalPlaces="2" isCurrency="Y"/>
</Section>
<Section label="Payment Counts">
<Item key="$hub_PAYMENT_VISA_Cnt" label="Visa"/>
<Item key="$hub_PAYMENT_CASH_Cnt" label="Cash"/>
<Item key="$hub_PAYMENT_MC_Cnt" label="MC"/>
<Item key="$hub_PAYMENT_AMEX_Cnt" label="AMEX"/>
<Item key="$hub_PAYMENT_DISCOVER_Cnt" label="Discover"/>
<Item key="$hub_PAYMENT_Total_Cnt" label="Total"/>
</Section>
<Section label="Delivery Amounts">
<Item key="$hub_DELIVER_TO GO_Amt" label="TO GO" decimalPlaces="2" isCurrency="Y"/>
<Item key="$hub_DELIVER_ONLINE DELIV_Amt" label="Online Deliv" decimalPlaces="2" isCurrency="Y"/>
<Item key="$hub_DELIVER_HERE_Amt" label="HERE" decimalPlaces="2" isCurrency="Y"/>
<Item key="$hub_DELIVER_FAX/ONLINE_Amt" label="Fax/Online" decimalPlaces="2" isCurrency="Y"/>
<Item key="$hub_DELIVER_Total_Amt" label="Total" decimalPlaces="2" isCurrency="Y"/>
</Section>
<Section label="Delivery Counts">
<Item key="$hub_DELIVER_TO GO_Cnt" label="TO GO"/>
<Item key="$hub_DELIVER_ONLINE DELIV_Cnt" label="Online Deliv"/>
<Item key="$hub_DELIVER_HERE_Cnt" label="HERE"/>
<Item key="$hub_DELIVER_FAX/ONLINE_Cnt" label="Fax/Online"/>
<Item key="$hub_DELIVER_Total_Cnt" label="Total"/>
</Section>
<Section label="Discounts">
<Item key="$hub_DISC_CMP_Total_Amt" label="Total Comp Amount" decimalPlaces="2" isCurrency="Y"/>
<Item key="$hub_DISC_CMP_Total_Cnt" label="Total Comp Count"/>
<Item key="$hub_DISC_PRO_Total_Amt" label="Total Promo Amount" decimalPlaces="2" isCurrency="Y"/>
<Item key="$hub_DISC_PRO_Total_Cnt" label="Total Promo Count"/>
</Section>
<Section label="Daypart Amount Totals">
<Item key="$hub_DP_LUNCH_Amt" label="Lunch" decimalPlaces="2" isCurrency="Y"/>
<Item key="$hub_DP_DINNER_Amt" label="Dinner" decimalPlaces="2" isCurrency="Y"/>
<Item key="$hub_DP_LATE NIGHT_Amt" label="Late Night" decimalPlaces="2" isCurrency="Y"/>
<Item key="$hub_DP_Total_Amt" label="Total" decimalPlaces="2" isCurrency="Y"/>
</Section>
<Section label="Daypart Count Totals">
<Item key="$hub_DP_LUNCH_Cnt" label="Lunch"/>
<Item key="$hub_DP_DINNER_Cnt" label="Dinner"/>
<Item key="$hub_DP_LATE NIGHT_Cnt" label="Late Night"/>
<Item key="$hub_DP_Total_Cnt" label="Total"/>
</Section>
<Section label="Category Amount Totals">
<Item key="$hub_CAT_FOOD_Amt" label="FOOD" decimalPlaces="2" isCurrency="Y"/>
<Item key="$hub_CAT_CATERING_Amt" label="CATERING" decimalPlaces="2" isCurrency="Y"/>
<Item key="$hub_CAT_BEV_Amt" label="BEV" decimalPlaces="2" isCurrency="Y"/>
<Item key="$hub_CAT_OTHER_Amt" label="OTHER" decimalPlaces="2" isCurrency="Y"/>
<Item key="$hub_CAT_LIQUOR_Amt" label="LIQUOR" decimalPlaces="2" isCurrency="Y"/>
<Item key="$hub_CAT_Total_Amt" label="Total" decimalPlaces="2" isCurrency="Y"/>
</Section>
<Section label="Category Count Totals">
<Item key="$hub_CAT_FOOD_Cnt" label="FOOD"/>
<Item key="$hub_CAT_CATERING_Cnt" label="CATERING"/>
<Item key="$hub_CAT_BEV_Cnt" label="BEV"/>
<Item key="$hub_CAT_OTHER_Cnt" label="OTHER"/>
<Item key="$hub_CAT_LIQUOR_Cnt" label="LIQUOR"/>
<Item key="$hub_CAT_Total_Cnt" label="Total"/>
</Section>
</MetaData>
</HubWorks>