M3 PMS/POS Integration

M3 PMS/POS Integration Overview

M3 PMS/POS Integration is a public API for posting daily activity to M3's daily report module within Accounting Core application. API allows for the brands and third party PMS/POS vendors to communicate directly to M3's Accounting Core improving reliability and visiblility to the integration process.

When data is posted through M3 PMS/POS Integration API M3 will identify and store unique codes that are used for mapping transaction items to Daily Report items. Once items are mapped, then Night Auditors will see the data when accessing M3's Daily Report where the data can be validated before posting daily activity and affecting the general ledger. Data will also be available as preliminary data in M3's Insight application with preliminary data being updated with audited data once the daily report is rolled over for the day.

PMS Data Requirements: Minimum standard

A. Occupancy/Revenue/Hotel Statistics (Any Hotel specifics that are available should be in the file)

1. Ex. should be broken down by segmentation. SMERF, Government, Group, Retail, Discount. Should also include Comp and out of order

B. Total Room Nights (by market segmentation is preferred)

1. Total Room Sold, if possible, without segments

C. Total Room Revenue, (by market segmentation is preferred)

1. Total Room Revenue, if possible, without segments

D. Transaction Details (Ex. Grouping by Revenue, Non-Revenue and Payments. Some examples (Not an exhaustive list) smoking, pet, miscellaneous income, laundry, taxes, payments, cash, VISA, Master Card, American Express etc…)

1. Transaction Code
2. Transaction Description
3. Transaction Amount

E. AR Aging Details (May vary depending on client needs) - get all bills

1. Current Balance
2. Aging buckets (examples provided below)
3. 30-60 days
4. 60-90 days
5. 90-120 days
6. 120+ days
7. Ending Balance

F. Hotel Ledger (May vary depending on client needs)

1. Advanced Deposit Ending
2. Advanced Deposit Net Change
3. Guest Ledger Ending
4. Guest Ledger Net Change
5. A/R (or City) Ledger Ending
6. City Ledger Net Change
7. A/R (or City) Pending Ledger

POS Data Requirements: Minimum standard

Select 'Link' for sample POS sample payload for /activities

Need to capture the following segmentation data

1. Business Unit or Outlet ex. Tim's Pizza, Starbucks, etc...
2. Revenue Centers for each business unit ex. Dining Room, Room Service, Carry Out, etc...
3. Category for each revenue center that include
   1. Food
   2. Beer
   3. Wine
   4. Liquor
   5. Non-alcoholic
   6. Retail
   7. Other
4. Capture the revenue and statistics by meal period
   1. Gross Sales
   2. Net Sales
   3. Promotional Sales
   4. Cover Count
   5. Check Count
   6. Adjustments (Nice to Have)
5. Capture the Payment data
   1. Cash
   2. VISA
   3. Master
   4. American Express, etc.
6. Capture the Tax info
   1. Food
   2. Misc. etc.

RE: PMS and POS Data: Above lists minimal sample request of items that drive value. That said, our system can support any elements that are desired. When posting, the accountingID should be assigned to the smallest element and will be used for mapping within M3's system.

Should you have questions or would like assistance, please contact M3's Integration department through the following email addresses.

Become a partner