M3 - How to connect

Step 1: Sign Up for M3

If you don’t already have an account with M3, sign up at M3’s website.

Step 2: Add M3 Integration

Follow the steps below:

  1. Go to your Account Account menu icon.png
  2. Select Apps & Marketplace Apps and Marketplace icon.png
  3. Search for M3
  4. Click Learn More
  5. Click Submit Request
    Once you agree on the pricing with the support team, you will see the CONNECT APP button.


6. Authorize the app to access your Cloudbeds data.

7. Follow the prompts to complete the integration setup.

Step 3: Configure M3

Custom Transaction Codes

    1. Navigate to the Main Menu
    2. Accounting in Cloudbeds.
    3. Select Transactions to access the configuration page.
    4. Map your Custom Transaction Codes to M3 Account IDs. For example:
      • Populate your M3 account numbers into the Code column on the Transactions page
      • Your M3 account manager can guide you on which account numbers to map transactions.

Cloudbeds summarizes your transactional data using these Custom Transaction Codes daily and syncs it to M3. You should use the M3 account IDs for the Custom Transaction Code IDs you configure in Cloudbeds, using the same M3 account ID on each Cloudbeds transaction that should go into that M3 account.

Note: Custom Transaction Codes apply only to new transactions after configuration. Configure these codes before the first day of data sync to avoid discrepancies. These codes are visible on transactions in Cloudbeds Insights Reports.

App Settings

  1. Go to Marketplace > Connected Apps > M3 App Page.
  2. Select Settings.
  3. Configure the following and Submit to save.
        • Start Date: The date when data sync begins.
        • Historical Start Date: If you wish to sync historical data, set an earlier date (ensure Custom Transaction Codes were configured before this date).
        • M3 Shortname and Property ID: Your property ID should always be filled in with a 6-character combination of your M3 short name and M3 property ID. M3 provides this data.

Remember that the Custom Transaction Codes must have been configured in Cloudbeds for the integration to work, so the historical date should not be before the data that you finished configuring the Custom Transaction Codes.

Daily Data Sync

Cloudbeds will automatically sync the previous day’s data to M3 at 6 AM local time starting from the configured start date.

Why Do I See “Cloudbeds-Unmapped-Transactions” in M3?

Reason: The “Cloudbeds-Unmapped-Transactions” account in M3 is used for transactions that do not have a Custom Transaction Code. This typically happens when new types of transactions are created, such as a new product or payment type, but the corresponding Custom Transaction Code has not yet been added to the Accounting page.

How to resolve:  Add or update the Custom Transaction Code for the transaction type on the Accounting page. Once configured, future transactions of that type will be mapped appropriately to the correct account in M3.

By regularly updating your Custom Transaction Codes, you can ensure all transactions are accurately attributed in M3.

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.