Skip to main content

Mews Integration Overview

Comprehensive guide to how Event Temple integrates with Mews, including sync behaviour, Paymaster logic, and reservation flow.

Written by Rachel Baque

At a high level, Event Temple's integration with Mews allows you to do the following:

  • Sync Accounts*

  • Sync Contacts*

  • Sync Room Types

  • Check Live Guestroom Availability

  • Sync Rates

  • Sync Room Blocks

  • Sync Reservations and Pickup Blocks

  • Link a Paymaster to a Booking

  • Post Consumed Charges

  • Sync Prepayment Invoices

* Syncing Accounts and Contacts requires that your chain in Event Temple shares accounts and contacts across all organizations. Accomplish this by having our team enable Global Accounts and Contacts on your behalf.

Sign up for our short Event Temple University course here!


Syncing Accounts

Accounts in Event Temple can be synced with Mews Companies.

In Mews, Companies are shared across all properties in a chain. In order to sync accounts with Companies in Mews you must enable Global Accounts & Contacts for your chain in Event Temple.

When enabled:

  • New accounts in ET are automatically synced to Mews

  • New accounts in Mews are automatically synced ET

  • Deleting an account in one system does not delete it from the other

For more detail please see the full article on MEWS Account Sync below:


Syncing Contacts

Contacts in Event Temple can be synced with Mews Customers.

In Mews, Customers are shared across all properties in a chain. In order to sync Contacts with Customers in Mews you must enable Global Accounts & Contacts for your chain in Event Temple.

When enabled:

  • New Contacts in ET can be set to automatically sync to Mews

  • New Contacts in Mews are NOT automatically synced to ET

  • Updates to a synced Contact in one system are automatically reflected on the Contact in the other system

  • Deleting a Contact in one system does not delete it from the other

  • Existing Contacts in ET that aren't synced to Mews can be manually linked at anytime

For more detail please see the full article on MEWS Contact Sync below:

Please note: Initiating Mews Contact Sync will NOT sync any Contacts that were previously added to the system. They will need to be done manually. Instructions for how to do this can be found in this article, under the subheader, How to Sync an Existing Event Temple Contact to Mews.


Syncing Room Types

In Event Temple, Room Types are the guestroom categories that can be used for Room Blocks.

When integrated with Mews, Room Types in Event Temple are automatically downloaded and kept in sync with Mews Space Categories.

This cannot be turned off and each night the system automatically checks Mews to ensure the Room Types in ET are up-to-date with the Space Categories in Mews.

Note that Space Categories only sync into ET if they have their "Short Name" set in Mews as that is mapped to the Room Type "Code" in ET.

When configuring the integration, this is referred to as the Accommodation Service. In Mews, this service is typically called "Stay" or "Accommodation."

If you are Managing Multi-Service Groups, please see this article for further details:


Checking Live Room Availability

When integrated you are able to check the live availability of your guestrooms without needing to switch to Mews.

From the GRC

While Adding or Editing a Room Block


Syncing Rates

Event Temple automatically downloads the Rates you have configured in Mews so that you can take advantage of the pricing you have already configured there.

The available Rates are downloaded from Mews every night and can be refreshed on-demand from the integration settings in Event Temple. The pricing of each rate is loaded live from Mews when you are building a Room Block.


Syncing Room Blocks

Room Blocks in Event Temple can be synced with Mews Availability Blocks.

When enabled:

  • New Room Blocks in ET can be synced with Mews, the Room Block Sync behavior will reflect you Status Configuration in your settings:

  • New Availability Blocks created in Mews will NOT be automatically downloaded to ET

  • Once created on the PMS, updates to synced Room Blocks are reflected in both systems

  • Deleting a Room Block in ET will not delete it from Mews

  • When updating to Lost in Event Temple it will automatically change the Room Block Status to Lost & cancel the Availability Block in Mews. We automatically set the canceled reason as “Other” with a note “Canceled in ET”

  • Availability Blocks will not show on the Mews Timeline. To be visible in Timeline you have to pick up rooms first.

When synced with Mews, a Room Blocks pickup values will be automatically calculated based on the reservations against the Availability Block in Mews.

Room Blocks in Event Temple do not obey Mews restrictions.


Sync Reservations and Pickup Blocks

While integrated with Mews, you are able to create reservations directly from Event Temple!

You can see this from any booking's summary page:

If the booking has a Room Block, the reservations will be created against the "Availability Block" in Mews as "pickups"

If the booking does not have a Room Block, the reservations will not be created against any Availability Block in Mews


Linking a Paymaster to a Booking

Event Temple allows you to specify a Booking Paymaster. This will be the Contact in Mews that all charges are posted to by default. If left unspecified, charges will be posted to the booking's primary contact.

If desired, you can configure your integration to automatically set the Paymaster when your booking is marked Definite. If enabled, setting a booking as definite will:

  1. Create a new Contact in Event Temple, The Contact will be named:

  • first name = “<org code> <booking id>”

  • last name = “<booking name> PM”

The org code is only included in the first name if there are multiple Organizations in the chain.

2. Sync the contact with Mews and classify the customer profile in Mews as a Paymaster Account

3. Set this contact as the Booking's paymaster


Paymaster Visibility Across Chains

If your chain has Global Accounts & Contacts enabled, Paymasters created in one organization will appear in all organizations across the chain. This is expected behavior in Mews, since both Companies (Accounts) and Customers (Contacts/Paymasters) are shared chain-wide.

Note: This can sometimes create confusion if booking IDs or contact names are similar across organizations. To help avoid this:

  • Event Temple auto-generates Paymaster names using the format:
    First Name = [Org Code] [Booking ID]
    Last Name = [Booking Name] PM

  • The Org Code prefix helps distinguish which org a Paymaster belongs to.

Note: If you’re seeing unexpected Paymasters or bookings linked across organisations, double-check the Contact name format or reach out to our support team to confirm if Global Accounts & Contacts is active.


Posting Consumed Charges

When integrated with Mews, Event Temple can automatically post consumed charges to Mews at the end of each day. Otherwise, you can post charges manually at any time.

Before the system can post charges you must:

  • Map your Revenue Categories (ET) to your Accounting Categories (Mews)

  • Map your taxes

Automatically Posting Charges

Automatic posting requires Contact Sync to be enabled

When enabled, each night Event Temple will post all of the previous day's charges to Mews.

How this works:

  • Only occurs for definite bookings

  • Charges will be posted under the Paymaster

    • If no paymaster is specified it will fall back to the booking Primary Contact

    • If the Primary Contact is not synced the auto posting will fail

  • Only charges in designated Revenue Categories will be automatically posted

  • If any postable charges do not have a tax specified, the posting will not proceed

Manually Posting Charges

At any time you can go to the Menu Items tab on a Booking and select which charges you would like to post to Mews.


Syncing Prepayment Invoices

Oftentimes you will want to simply charge your client for a percentage of the total booking cost well before the booking actually takes place. By using prepayment invoices you can easily send this initial payment from Event Temple, and then when the event concludes you can send a final Invoice from Mews that properly deducts the advance payment.

When Prepayment Invoices are fully paid and finalized, they are automatically synced with Mews.

If enabled, here's what will happen when a prepayment invoice is paid in full:

  1. A new bill will be created in Mews under the booking's paymaster

  2. The prepayment invoice charges will be grouped by tax and added to the bill

  3. Each invoice payment will be added to the bill

  4. The bill will be closed

  5. A new bill will be created in Mews under the booking's paymaster

  6. The prepayment invoice charges will be grouped by tax and added to the bill as negative charges

When it comes time to generate the final invoice from Mews, these negative charges will cause the final invoice to be appropriately deducted.

Did this answer your question?